How to Track RFIs and Keep Your Construction Site Moving

What is an RFI and why do contractors use them?

An RFI — Request for Information — is a short, written question a contractor or subcontractor sends to the design team, usually the architect or engineer, when something in the drawings or specifications is unclear. The question might be about a missing dimension, a material not specified, two drawings that appear to contradict each other, or a detail that looks impossible to build as drawn. Using a written RFI instead of a quick phone call creates a dated, named record of both the question and the answer, which matters enormously when a dispute arises months later. On any project of ten or more tasks, RFIs will happen: the question is not whether they occur but whether they are tracked in a way that protects the contractor and keeps the site moving.

Why does a slow RFI process delay the whole site?

When a design question goes unanswered for a week, work in that area typically pauses or proceeds at risk. A plastering crew cannot finish a wall section if they do not know whether the architect wants a flush or recessed junction at the door frame. A concrete pour cannot proceed if the rebar arrangement is contradicted by two different drawings. Every day those questions sit waiting is a day the crew either stands idle in that zone or moves to less efficient work elsewhere and comes back later, adding unnecessary cost. On a tight six-month build, even three or four unresolved RFIs accumulating at the same time can eat a week of schedule before anyone identifies them as the cause.

What should every RFI include?

Keep each RFI short and specific. Include a unique reference number so it can be tracked across conversations, the date it was submitted, the name of the person submitting it, the drawing or specification it refers to including the revision number, a one-paragraph description of the question, and a clear requested-response-by date. Attach a photo or drawing crop if the question is about a physical detail — a picture of an ambiguous junction cuts reply time dramatically compared to a text-only description. Do not bundle more than one topic in a single RFI: if you have three separate questions about different drawings, send three separate RFIs so each can be tracked, answered, and closed independently.

How to build a simple RFI log without specialist software

A dedicated tab in your project spreadsheet or a shared file does the job for most SME contractors. Columns to include: RFI number, submission date, submitted by, drawing reference, question summary, response-due date, date answered, answered by, answer summary, and status as open or closed. The discipline is not the format — it is opening the log every Monday morning and updating every row. An accurate RFI log lets you see at a glance how many questions are sitting with the design team, which ones are overdue for a response, and whether any of those blocked areas appear as tasks scheduled to start this week in the Gantt planning view.

A worked example: the beam detail on Khun Prasit's Bangkok office fit-out

Khun Prasit is managing a three-month office fit-out across two floors of a Bangkok building. His structural drawings reference beam B3A at a slab penetration, but the rebar schedule does not include B3A at all. He submits RFI-007 on Monday morning, attaches a crop of the two conflicting drawings, and notes that the concrete pour for that bay is scheduled Friday. He marks the response-due date as Wednesday, giving the engineer two working days to check and reply. The engineer responds on Thursday confirming the rebar arrangement, and Prasit closes RFI-007 in the log with the answer saved. The pour proceeds Friday, only one day behind the original plan. Without the tracked RFI, a phone call on Tuesday might have produced an answer nobody wrote down — and three months later during a quality inspection, no one could confirm what had been authorised.

How do you set response-time expectations with the design team?

Agree on a standard turnaround at the start of the project — three to five working days is typical for straightforward questions. Include this in the pre-construction meeting minutes so it is a shared understanding rather than a one-sided demand. When you submit an RFI, always include the date you need a response by and the reason: pour scheduled Friday, response needed by Wednesday. Design teams are more responsive when they understand why the deadline exists. If an RFI is overdue, follow up in writing rather than by phone — a short message noting the overdue date and the site impact creates a paper trail that is useful if the delay results in a claim for additional cost.

How does linking an RFI to a Gantt task prevent unplanned downtime?

The most practical connection between an RFI and your schedule is a simple note on the affected Gantt task: blocked pending RFI-007, expected resolution Wednesday. Anyone reviewing the Gantt planning view can immediately see which tasks are waiting on design answers rather than discovering the blockage only when a crew arrives and has nowhere to work. When the RFI is resolved, update the note and adjust the task start date if needed. Using on-site progress updates in SiteBoard to mark the task as blocked, with the RFI number in the note field, means both the site team and the project manager see the dependency in real time without needing a phone call to establish the current state.

What is the difference between an RFI and a variation order?

An RFI is a question: you are asking for clarification on something already within the contract scope. A variation order is an agreement: both parties accept that the scope has changed and that the price or time or both will be adjusted. The two documents often follow each other — an RFI reveals that the original drawing was unbuildable, the architect provides a revised detail, and the revised detail requires extra material or labour, triggering a variation order. Tracking both separately is essential. An unanswered RFI that causes a measurable delay is a legitimate ground for a time extension claim; a verbal scope change that was never put into a variation order is a dispute waiting to happen.

Can you send RFIs by LINE and still track them properly?

You can use LINE to initiate the conversation, but a LINE message is not a tracked document. The date it was sent is buried in a group chat scroll, the reply looks like any other message, and a year later neither you nor the design team can easily locate either. If your team sends RFIs through LINE, copy the content into your RFI log the same day: assign it a reference number, record the sent date, and paste the reply into the answer column when it arrives. The LINE message starts the conversation; the RFI log is the record that holds up when a defect claim or dispute arises.

When should you submit an RFI instead of calling the architect?

Almost always, even for questions that feel minor. A phone call is faster, but a written RFI is safer. If the answer given over the phone turns out to be wrong, there is no record of what you were told. Practical exceptions exist: genuinely minor judgement calls that are entirely yours to make as the contractor, and emergency situations where delay is measured in hours — in which case, make the call and immediately follow it with a written RFI confirming what was agreed. For anything that touches structure, waterproofing, or regulatory compliance, always put it in writing first. The cost of sending an RFI is minutes; the cost of relying on an unrecorded phone conversation can be months of dispute.

Keeping the RFI log current and making it part of the weekly review

The RFI log only works if someone owns it daily and it is reviewed alongside the schedule. Assign one person to update it — typically the site foreman or project coordinator — and make the log part of every weekly site review together with the Gantt. At the start of each week, check all open RFIs, flag any that are overdue, and identify which Gantt tasks are at risk because of outstanding answers. Over the life of a project, a complete RFI log is also a permanent project record: every design question, every answer, every date — exactly the kind of evidence that resolves warranty disputes and protects you from unfair defect claims after handover.