When Should Contractors Issue RFIs on a Project?

A crew is ready to install, but the structural detail conflicts with the architectural plan. The wrong move is not asking a question. The wrong move is building on an assumption and trying to sort it out after concrete, steel, or finishes are already in place. When should contractors issue RFIs? As soon as the contract documents contain an ambiguity, conflict, omission, or condition that could affect the work, cost, quality, safety, or schedule.

An RFI is not paperwork for paperwork’s sake. It is a formal notice that the documents or field conditions do not provide enough direction to proceed responsibly. Used at the right time, it protects the contractor, gives the design team a clean decision point, and creates a record before a small gap becomes rework, a change order fight, or a schedule claim.

Issue an RFI Before the Work Becomes Irreversible

The best time to issue an RFI is before the affected work starts, before related work covers it up, and before the unanswered issue controls the crew’s next move. That sounds obvious, but RFIs are often delayed because a superintendent expects the answer at the next coordination meeting or a foreman believes the field can “make it work.”

That approach may save an email today. It can cost far more when the answer later changes installed work, disrupts sequencing, or exposes the contractor to an allegation that it failed to follow the plans.

If a question affects layout, material selection, dimensions, elevations, routing, access, tolerances, code compliance, or the sequence of work, raise it early. The same applies when field conditions differ from what the drawings show. Existing utilities in the wrong location, an unshown obstruction, unsuitable substrate, and inaccessible work areas are not issues to solve quietly and document later. They need written direction.

Early does not mean premature. Contractors should review the full drawing set, specifications, addenda, relevant submittals, and known field conditions before issuing an RFI. A vague question that the documents already answer wastes time and damages credibility. A focused RFI based on a real document conflict is different.

When Should Contractors Issue RFIs for Document Conflicts?

Issue an RFI when two or more contract documents give directions that cannot reasonably be followed together. Common examples include an architectural ceiling plan that conflicts with a mechanical duct route, a structural opening that does not align with equipment requirements, or a specification that calls for one product while the finish schedule names another.

Do not assume one discipline’s drawing automatically controls. The contract may contain an order-of-precedence provision, but that does not always resolve a constructability problem. Even if the contractor has a reasonable interpretation, the record should show that the conflict was identified and sent to the party authorized to clarify it.

The same rule applies to omissions. If the drawings show a system but omit a necessary connection, support detail, penetration detail, termination point, or required component, submit an RFI. The question should not be, “Please advise.” State exactly what is missing, where it occurs, what the contract documents currently indicate, and what decision is required to keep work moving.

A good RFI does not design the project for the architect or engineer. It identifies the issue and may offer workable options, but it asks the responsible party to select or approve the direction. That distinction matters when you assign responsibility later.

Issue RFIs When Existing Conditions Do Not Match the Plans

Renovation and occupied-work projects produce some of the most expensive unanswered questions in construction. Existing conditions are frequently concealed, incomplete, or different from available as-builts. A contractor that discovers an issue in the field should document it immediately with dated photos, location details, measurements, and a daily report entry.

Then issue the RFI before proceeding through the affected area whenever possible. If a hidden condition requires immediate protection, safety work, or emergency stabilization, take the necessary steps first and document why. But do not let an emergency field response replace formal notice and a request for direction.

For example, a subcontractor opens a wall and finds unmarked conduit where the planned opening must go. The crew should photograph the condition, record the time and precise location, notify the superintendent, protect the area, and submit an RFI requesting revised direction. If the work stops, the daily report should also capture the manpower affected, equipment standing by, work planned, work performed, and the time lost.

That supporting record is what connects a field condition to a potential delay or added-cost event. An RFI alone proves a question was asked. It does not automatically prove the operational impact.

Safety, Code, and Quality Issues Cannot Wait for Convenience

An RFI should be issued immediately when the documents appear to create a safety concern, conflict with code requirements, or require work that cannot meet manufacturer instructions. The contractor should not proceed with a known unsafe or noncompliant condition simply because the drawings appear to call for it.

This is especially critical around fall protection, firestopping, egress, structural connections, electrical clearances, hazardous-material interfaces, and temporary conditions. Depending on the situation, the contractor may also need to stop work in the affected area, notify the appropriate project personnel, and document the condition in safety and daily reporting records.

There is a trade-off here. Stopping work has a schedule consequence. Continuing work with a known safety or code problem carries a much larger one. The field record should make clear what was found, who was notified, what action was taken, and when direction was received.

Do Not Use RFIs to Cover a Missed Scope Review

RFIs are a protection tool, not a cure for avoidable estimating or coordination failures. Before issuing one, confirm that the answer is not already in the bid documents, approved submittals, meeting minutes, addenda, or prior responses. Repeatedly asking questions that should have been resolved through normal document review creates noise and slows down the real issues.

Contractors should also avoid using an RFI as a disguised change order request. If the scope is clear but more expensive than anticipated, the right path may be a notice of change, a request for proposal, or another process required by the contract. An RFI can establish that clarification is needed, but it should not overstate entitlement before the facts are known.

The practical test is simple: can the crew proceed in accordance with the contract documents without guessing? If the answer is no, an RFI is likely appropriate. If the answer is yes but the contractor wants a preferred method approved, the matter may belong in a submittal, coordination meeting, or internal planning process instead.

Write RFIs That Get Answered and Hold Up Later

A strong RFI is short, specific, and complete enough for the recipient to make a decision. It should identify the drawing, detail, specification section, location, and date of the issue. Include photos, marked-up sketches, or excerpts from the documents when they clarify the conflict.

Describe the condition without argument. State the impact factually: work cannot proceed in the indicated area, material procurement is pending, installation sequencing may be affected, or the current direction conflicts with another document. If timing matters, give the actual decision date needed to avoid impact. Do not invent urgency. Explain it.

Keep the language professional. “Field discovered a conflict between A5.2 Detail 4 and M3.1 duct elevation at Grid B-7” is useful. “Plans are wrong, need answer ASAP” is not. The first statement helps resolve the issue. The second creates friction without building a reliable record.

Once the response arrives, distribute it to the people doing the work and confirm whether it changes cost, time, materials, or means and methods. A closed RFI that never reaches the foreman is still a field failure. If the response directs added work or causes delay, preserve the RFI alongside daily reports, photos, manpower records, schedule updates, and required contract notices.

Tie RFI Timing to Daily Documentation

RFIs do their best work when they are part of a consistent documentation process, not a separate administrative task. The daily report should show the conditions surrounding the question: weather if relevant, workforce on site, work area, planned activity, disruption, conversations, and resulting downtime or resequencing.

This matters when an RFI sits unanswered. If a design clarification delays installation for three days, the project record needs more than the original question and response date. It needs evidence of what could not proceed, what resources were affected, what alternate work was available, and whether the contractor mitigated the impact.

A mobile field reporting process makes that record easier to capture while the facts are fresh. Construction Reporting Apps is built around that field-first need: clear daily records that support communication now and defensible project files later.

The jobsite does not reward contractors for absorbing ambiguity. Raise the question while the condition is visible, the work is still controllable, and the project team has time to make a decision. A timely RFI, backed by accurate field documentation, is often the difference between a manageable clarification and an expensive argument.

Grant