Field documentation
How to write an RFI
By the DailyBuild team - Published - 5 min read

Short answer
Write an RFI with one question per RFI, state exactly which drawing and spec section it relates to, describe the conflict factually, note the cost and schedule impact, and propose a solution the reviewer can simply confirm. Clear, single-issue RFIs with a proposed answer come back fastest.
Key takeaways
- One question per RFI. Bundled questions get partial answers and stay open.
- Always cite the drawing number, detail, revision and spec section.
- Describe what the documents say, not what you think somebody did wrong.
- Propose a solution - most reviewers will confirm a reasonable proposal rather than draft one.
- State the date you need an answer by and the impact if you do not get it.
An RFI, or request for information, is how the field asks the design team a formal question about the contract documents. It is not a complaint, a change order request or a design service request. It is a written question with a written answer that becomes part of the project record.
When to write an RFI
- The drawings conflict with each other or with the specification.
- Information is missing - a dimension, a detail, a finish, a connection.
- A field condition does not match what is shown.
- The documents are ambiguous and two readings are defensible.
- A specified product is unavailable and a substitution needs direction.
If the answer is already in the documents, do not write an RFI. Reviewers who receive RFIs answerable by reading the drawings start treating the whole log as low priority, which slows down the ones that matter.
Anatomy of a good RFI
| Section | What to put in it |
|---|---|
| RFI number and date | Sequential number, date submitted, and the date a response is needed |
| Subject | A short specific title - not 'question about slab' |
| Location | Building, level, grid lines, room number |
| References | Drawing number, detail number, revision date, spec section and paragraph |
| Question | One question, stated factually in two or three sentences |
| Background | What the documents show and what the field condition is |
| Proposed solution | What you suggest, with a sketch or marked-up drawing if useful |
| Impact | Cost impact, schedule impact and what work is on hold |
| Attachments | Marked-up drawings, photos of the condition, product data |
Weak RFI versus strong RFI

Weak
"The details for the second floor don't work. Please advise ASAP, this is holding us up."
There is no drawing reference, no location, no description of the conflict and no proposal. The reviewer has to do the investigation before they can even understand the question, so the RFI sits.
Strong
"Detail 5/A5.02 (rev 3, dated Jan 14) shows the level 2 slab edge at elevation 114'-6", while structural drawing S2.01 shows top of slab at 114'-4" at the same grid line C-4. Field survey confirms the deck is set for 114'-4". We propose holding the structural elevation of 114'-4" and adjusting the exterior sill flashing per the attached sketch. Curtain wall fabrication release is scheduled for Mar 9, so a response by Mar 5 avoids a delay to that release."
Same issue, but the reviewer can confirm or correct it in one reading. The references are exact, the conflict is stated without blame, a solution is proposed and the deadline is tied to a real event rather than the word urgent.
Write the question so it can be answered yes
Open-ended questions produce open-ended answers, which produce follow-up RFIs. Convert the question into something confirmable.
| Instead of | Write |
|---|---|
| What size should this beam be? | Please confirm W12x26 as shown on S3.01 governs over the W12x22 noted in the schedule. |
| How do we waterproof this? | Please confirm the detail 3/A7.11 membrane turn-up applies at this condition, as shown on the attached sketch. |
| What finish goes here? | Room 214 is unlabeled on the finish schedule. Please confirm it matches adjacent room 213, finish type P-2. |
Response times
Contracts normally set the review period for RFIs; seven to fourteen calendar days is common but it is a contract term, not an industry rule, so check your general conditions. Whatever the period, put the date you need the answer on the RFI and tie it to the activity it affects. An RFI that will delay a fabrication release or a pour should say exactly that.
What not to put in an RFI
- Multiple unrelated questions bundled together.
- Blame, sarcasm or commentary about the design team - the RFI is a permanent project record.
- A change order request disguised as a question.
- A request for the design team to do design work that is the contractor's means and methods.
- Vague urgency with no date and no named impacted activity.
- Questions already answered by a prior RFI - reference the earlier answer instead.
Track RFIs in a log
An RFI is only as useful as the log behind it. Track number, subject, date submitted, date required, reviewer, date answered, the answer summary and whether the response carries a cost or schedule impact. Sorted by date required, the log tells you every week which questions are actually threatening the schedule.
Frequently asked questions
Try DailyBuild on your next jobsite
Unlimited users on every plan. Set up a project and file your first report today.
14-day free trial · No credit card required to start · Cancel anytime