Skip to main content
Two site engineers review a drainage drawing beside an industrial construction work area

Construction RFI log builder

Keep each technical question, source drawing and response reference visible while the official project process stays in control.

Updated

Share

This log does not issue an RFI

Administrative tracker only. It does not issue a contractual communication, set a response deadline, authorise work, approve a design or turn a response into an instruction. Use the project contract and controlled project system. Submit the formal question through the project system and follow the actual contract, design coordination and response process. A response may need review before it can be used on site.

Build the working record

Entries stay in this page's memory. They are not stored or uploaded by this tool and are lost when you leave or reload. Download a text copy, print or save as PDF before leaving. Saved copies cannot be imported back into this form. Use role and document references instead of unnecessary personal information.

Key details are prompts, not a certification checklist. Blank, unknown, pending and not applicable mean different things: state the appropriate position explicitly. Long text fields allow 10,000 characters; short fields allow 2,000.

Log identity

Identify the project and the controlled system where formal questions and responses are issued.

This page does not connect to or update the named system.

Enter YYYY-MM-DD where known, or explicitly state Unknown, Pending or Not applicable. Date text is preserved, not validated.

Technical queries

Use one row per query. Copy the formal reference and response from the actual project system, not from this working log.

Entry numbers show the current order and change when entries move or are removed. Use document references, not these numbers, for cross-references.

Query 1

Enter YYYY-MM-DD where known, or explicitly state Unknown, Pending or Not applicable. Date text is preserved, not validated.

Copy the date agreed in the project process. This tool does not calculate contract or design deadlines. Enter YYYY-MM-DD where known, or explicitly state Unknown, Pending or Not applicable. Date text is preserved, not validated.

Enter YYYY-MM-DD where known, or explicitly state Unknown, Pending or Not applicable. Date text is preserved, not validated.

Supporting evidence index

List references to original project documents. Files are not uploaded, copied or authenticated here.

Entry numbers show the current order and change when entries move or are removed. Use document references, not these numbers, for cross-references.

Evidence item 1

The record has not been checked. No approval is inferred.

Clear all entered values and added entries? This cannot be undone. Save a copy first if needed.

Remove this entry and its entered values? This cannot be undone.

Preview the current print record
 

Keep the question tied to its source

An RFI, or request for information, is a project team's way of recording a question that needs an answer. The exact process and document name vary by contract and project. This offline log helps a package team see which questions are open, which drawings or specification clauses they concern and where the formal response is stored.

Give each query the reference used in the controlled project system. Record the drawing number and revision, the location or asset affected, the question itself and the decision that is waiting. A broad entry such as "please clarify drainage" is difficult to route. State the exact conflict or missing detail and what work or decision depends on it.

Example: a drainage drawing conflicts with a detail

A fictional query could identify drawing C-104 revision 3 and detail C-210 revision 2, name the affected chamber, and ask the designer to confirm which connection detail applies. Record the activity waiting for that answer and the project-agreed response target.

After submission, copy the formal RFI reference into this log. When the designer replies, record the response reference and any conditions. Ask the responsible project reviewer to decide whether a revised drawing or a separate instruction is needed before the crew proceeds.

Track the response without changing its meaning

Copy the response reference and date from the project system. Keep a short summary for the working log, but do not replace the source response with that summary. If the answer contains conditions, exclusions or a request for more information, keep those visible. A response is not automatically a design approval, instruction or permission to proceed.

The HSE's planning guidance says relevant pre-construction and design information should be considered when the construction phase is planned. This log is an administrative aid for locating project questions; it does not decide whether information is sufficient for safe work.

Separate a question from a change

A technical answer can clarify an existing requirement, ask for more evidence or lead to a proposed change. Keep the query history intact and route any change through the contract's separate approval and change-control procedure. A query log is not a substitute for the formal instruction or change-control route.

Use the log as a working index

Use role and document references. Do not enter confidential project documents or unnecessary personal details.

Entries stay in this page while it is open. They are not uploaded or saved to Rospower Projects. Download or print a copy, check it against the source system and file it under your organisation's document-control rules. Use the project's common data environment (CDE) as the authority for formal status, recipients, issue dates and superseded responses.

Keep the RFI open if you still need clarification. A filled response field does not close an action automatically, and this tool does not send reminders or notify the designer.

Share

Related resources

Send an enquiry

Request a callback

We'll call you back during work hours (Mon-Fri, 9am-5pm).