On this page
- Step 1: Decide whether you need an RFI
- Step 2: Find out exactly what the field needs
- Step 3: Write the subject last: element plus location
- Step 4: State the conflict with references
- Step 5: Propose a solution
- Step 6: Ask for a specific answer and attach the evidence
- Step 7: Set the needed-by date and flag impact
- Step 8: Route it, track it, close it
- Worked example: the same RFI, written twice
- Common mistakes
- How os.construction handles it
- FAQ
To write an RFI that gets answered, ask one specific question about one element, cite the exact sheet, detail and spec section, state the conflict in a sentence or two, propose a solution the designer can accept or reject, attach a marked-up sheet or photo, and set a needed-by date taken from the schedule. Before writing it, check that the answer isn’t already in the drawings, specs, addenda, ASIs or an earlier RFI.
Most of the time lost on RFIs is lost before the designer reads them: a question the documents already answer, a subject line nobody can find in the log, or a question so open that the engineer has to design from scratch to answer it. The steps below fix those. The free RFI writing checklist covers the same ground as a printable sheet.
Step 1: Decide whether you need an RFI
Spend five minutes trying to answer the question yourself. Search the current drawing set, the specifications, every addendum, any ASIs or bulletins, and the RFI log. A question already answered in an addendum costs the designer’s goodwill and the field a day.
Then check that it really is a question about the documents. It isn’t an RFI if it is:
- A submittal. Product data, shop drawings and samples go through the submittal process.
- Means and methods. How you build it is usually the contractor’s call, not the designer’s.
- A substitution request. Most specs have a separate substitution procedure.
- A request for a price or a change. That’s a change event, with an RFI as backup if a question started it.
Step 2: Find out exactly what the field needs
Talk to the foreman or sub who raised it. “The duct doesn’t fit” is a problem; what they need to keep working might be a dimension, a yes or no, or a choice between two options. Get the measurements, take photos, and find out when the crew reaches that area. That date drives step 7.
Step 3: Write the subject last: element plus location
The subject is what everyone sees in the RFI log and in the meeting minutes. Make it say what and where: “Corridor 3B supply duct clearance at beam, grid C–D”, not “Ceiling question” or “Clarification needed”. Someone scanning the log three months later should know which RFI this is without opening it.
Step 4: State the conflict with references
In one or two sentences, say what the documents show and why it doesn’t work. Cite every sheet, detail and spec section involved, so the reviewer can open them without hunting. If two documents conflict, name both and say which one you think governs. Keep it factual: what’s drawn, what’s measured, what’s in the way.
Step 5: Propose a solution
Put your preferred fix in the RFI. A designer can approve or adjust a proposal much faster than they can create one, and you know the field conditions better than they do. If there are two reasonable options, give both and say which you prefer and why. The designer still decides; the proposal just narrows the question.
Step 6: Ask for a specific answer and attach the evidence
End with the answer you need: a dimension, a product, a detail, “confirm Option A”. Attach a marked-up sheet, a sketch or a photo with the conflict circled. A photo with a tape measure in it does more than a paragraph.
Step 7: Set the needed-by date and flag impact
Set the due date from the schedule, not by habit. If the work is three weeks out, say so; if the crew is stopped tomorrow, say that, and call as well as send. Stay inside the response period your contract or RFI procedure sets: under AIA A201-2017, the architect responds in writing within agreed time limits or otherwise with reasonable promptness, and many projects put a working-day period in Division 01.
Mark whether the question may affect cost or schedule: yes, no or to be determined. That doesn’t commit anyone to a change, but it puts the possibility on record early.
Step 8: Route it, track it, close it
Assign it to the person who can answer, copy the people who need to know, and log it with a number. Review open RFIs by ball in court every week, usually in the OAC meeting. When the answer comes back:
- Check that it actually answers the question. If it doesn’t, follow up the same day.
- Distribute the official answer to the field and every affected trade, not only the one that asked.
- Mark the drawings or field set with the RFI number.
- If the answer adds cost or time, open a change event and give notice under the contract.
- Close the RFI and record the closed date.
Worked example: the same RFI, written twice
The ceiling crew on level 3 finds that a supply duct will hang below the ceiling in a corridor. Here is the RFI as it often gets sent:
RFI-147: Ceiling question Duct conflicts with ceiling in corridor on L3. Please advise.
The engineer now has to find the corridor, the duct and the ceiling, work out the conflict, and design a fix. Expect a reply asking for more information, and a week gone.
Here is the same RFI written with the steps above:
RFI-147: Corridor 3B supply duct clearance at beam, grid C–D
Documents: A-301 (reflected ceiling plan) shows an acoustical ceiling at 9’-0” AFF in corridor 3B. M-203 shows a 24×14 supply duct running below the W16 beam between grids C and D. S-201 gives the bottom of that beam at 10’-2” AFF.
Conflict: With 14” of duct below a 10’-2” beam, plus hangers and insulation, the bottom of the duct sits about 8’-10” AFF, below the 9’-0” ceiling, for roughly 18 feet between C and D.
Proposed solution: Option A (preferred): transition to a 34×10 duct between C and D, which has slightly more cross-section than the 24×14 and clears the ceiling. Engineer to confirm pressure drop is acceptable. Option B: lower the ceiling to 8’-8” between C and D.
Answer needed: Confirm Option A or Option B, or give other direction.
Needed by: 14 March. Ceiling grid in corridor 3B starts 17 March per the current look-ahead.
Cost / schedule impact: To be determined. Option A requires duct fabrication changes.
Attachments: M-203 marked up with the conflict circled; photo of the beam with tape measure.
Everything the reviewer needs is on one page. The engineer can check the duct size (24 × 14 = 336 square inches; 34 × 10 = 340) and answer “Option A accepted” the same day. If Option A changes the sheet-metal sub’s price, the RFI is the backup for the change event.
Common mistakes
- Asking without looking. A question already answered in the documents or an addendum costs a round trip and goodwill.
- Several questions in one RFI. The easy answer waits for the hard one, and the log can’t show which part is open.
- No references. “See drawings” makes the reviewer search.
- No proposed solution. The designer has to create one, and may not pick the one that suits the field.
- A due date set by habit. Everything marked urgent means nothing is.
- Using an RFI to ask for money. If the answer changes the work, open a change event and follow the contract’s notice requirements; don’t wait for the RFI to do it for you.
- Answering only the asker. Other trades keep building to the old detail.
Track how long answers take, too. The RFI response time calculator works out average and overdue days from your log, which matters if late answers ever support a time extension.
How os.construction handles it
RFIs save as a draft until they’re ready, then open to the assignees. Ball in court is worked out from the RFI’s state, overdue RFIs are flagged in the log, and the answer that settles the question can be marked official. An RFI links to drawings, submittals, change events and photos, and a change event can name the RFI it came from. The RFI to change order guide follows that path through to billing, and construction RFI software covers what to look for in any RFI tool.
FAQ
What should a construction RFI include?
A number, a subject naming the element and location, the drawing sheet, detail and spec section involved, a one- or two-sentence description of the conflict or gap, a proposed solution, the specific answer you need, a marked-up sheet or photo, the date the field needs the answer, and whether cost or schedule may be affected.
How many questions should one RFI ask?
One. If you bundle a simple question with a hard one, the simple answer waits for the hard one, and the log can't show which part is still open. Related questions about the same detail can share an RFI if they will be answered together; unrelated ones should not.
Who answers an RFI?
Usually the architect, who answers directly or routes the question to the consultant responsible, such as the structural or mechanical engineer. Subcontractors normally send RFIs through the general contractor. Questions that only the owner can decide, such as a program or finish choice, are often routed to the owner through the architect.
How long does the design team have to answer an RFI?
Whatever the contract and project procedures say. Under AIA A201-2017 the architect responds in writing within any agreed time limits or otherwise with reasonable promptness. Many projects set a number of working days in Division 01 or the RFI procedure. Set each RFI's needed-by date from the schedule, inside that period.
Is an RFI the same as a change order request?
No. An RFI asks what the documents mean. If the answer adds work, cost or time, open a change event and give whatever notice the contract requires; the RFI and its answer become backup for the change. Don't use RFIs to ask for a price or to propose a substitution, which have their own procedures.
Share this article