Article
How do you write a construction RFI that gets answered fast? (template and example)
A free construction RFI template with a worked example: what to include, how to cite sheets and specs, and how to check an RFI is needed first.
Aug 26, 2026 · By Trunk Tools team · 5 min read
A construction request for information (RFI) gets answered fast when it asks one clear question, names the sheet, detail and spec section, attaches photos, suggests an answer, and says what work is waiting on it. Check first: on Trunk Tools' platform, 19.5% of potential RFIs were already answered in project documents or prior RFIs (platform data).
An RFI in construction, short for Request for Information, is a formal written question a contractor sends to the design team when a drawing or a spec section doesn't give the field enough information to build correctly. The architect or engineer's written answer becomes part of the official project record, carrying the same weight as the drawings and specs it clarifies.
RFIs should be concise, well-sourced, clearly written, and contain all relevant information to increase the likelihood of a timely, satisfactory response from the design team.
01
What should an RFI look like?
An RFI should contain the following basic information for the design team. You can download a fillable copy using the button above.
- RFI #
- Project name and number
- Date submitted
- Expected response date
- Responsible contractor
- Subject
- Drawing/spec reference
- Question
- Proposed solution
- Cost/schedule impact
- Additional sources/attachments
Why these components? The subject line lets anyone scanning the RFI log find it without opening it. The drawing or spec reference points the design team straight to the conflict instead of making them search for it. The question is a single, specific ask, not several bundled together. The proposed solution gives the architect something to approve instead of starting from a blank page. The responsible contractor field routes any follow-up to the right party without someone tracing it back through the log, and attaching the source documents up front lets the architect verify the conflict without requesting them separately. The expected response date and cost or schedule impact turn a routine question into one the design team can prioritize correctly and reply to promptly.
02
How do you check whether an RFI is needed?
Search for the answer before you write. Check the specification section and the sheets the question touches, any addenda or bulletins issued since, approved submittals for that work, and earlier RFIs on the same detail. If the answer is there, send it to whoever asked and skip the RFI.
TrunkRFI, the Trunk Tools agent for RFIs, runs that search for you. Type the question into TrunkRFI, or let it pick up the draft RFIs your subcontractors create in your connected project management system. It searches the specs, drawings, submittals, addenda and past RFIs. If the answer exists, it shows you where. If not, it drafts the RFI at the length you pick (concise, balanced or detailed) and writes it back to that system for your team to review and submit.
03
What are the most common mistakes in a construction RFI?
Whether you're working from a sample RFI construction teams shared with you or drafting from scratch, these are the three mistakes that most often send an RFI back for clarification:
- Vague framing. "Please confirm door frame type" tells the design team nothing about which door, which drawing, or which spec section is in conflict, so they have to ask a follow-up question before they can answer the original one.
- Missing drawing or spec reference. Without it, the architect has to go find the context themselves, which adds days to an already slow loop.
- Asking a question that's already answered. On Trunk Tools' platform, 19.5% of potential RFIs were already answered in project documents or prior RFIs (platform data). This can lead to tension with the design team, owner’s rep, and owner when it happens frequently.
04
How do you write a construction RFI?
- Check whether the answer already exists in the drawings, the specs, or a prior RFI before drafting a new one.
- Identify the exact drawing sheet or spec section causing the conflict.
- Frame one clear question. Split multiple issues into separate RFIs.
- Propose a solution if you have one; it gives the design team something to approve rather than originate.
- Set a response-needed-by date tied to your schedule and aligned to contractual terms.
- Flag the potential cost or schedule impact so it isn't a surprise later.
- Submit it through your project management system so it's logged, dated, and trackable.
05
How do RFIs get processed once they're submitted?
An RFI moves through a consistent chain: a subcontractor or field team raises the question, a project engineer drafts it using the steps above and submits it via a project management system, and the architect or engineer of record answers it before it routes back to the field. Every RFI gets logged in the project's RFI register with its status tracked to closure. If the answer reveals a scope, cost, or schedule impact that wasn't part of the original contract, the RFI becomes the documentation trail behind a change order.
06
How Trunk Tools helps you draft a better RFI
TrunkRFI, the RFI agent built on Cortex, Trunk Tools' construction intelligence layer, fills in these fields automatically, including the responsible contractor, spec reference, question, proposed solution, and supporting attachments, by scanning the full project document set before a draft ever reaches the design team. If the question is already answered, it flags that so you can avoid sending an unnecessary RFI. If it genuinely needs to be sent, the agent drafts a complete RFI, leaving a project engineer a few minutes of review instead of the roughly 30 minutes a draft normally takes. It also analyzes the response from the design team and makes recommendations on next steps, a process that often takes 4+ hours.
07 — FAQ
Frequently asked questions
Is there a standard RFI form?
No single form is required. Use the form your contract or the owner names, or this template if none is named. Whatever the form, it should carry the RFI number, the question, the sheet and spec section, a suggested answer, the date you need a response, and any cost or schedule impact.
Should an RFI propose a solution?
Yes, when you have one. A suggested answer shows the design team what you plan to build, so they can confirm it in a line. The architect or engineer still makes the call.
How many questions should one RFI ask?
One. A single question gets a single answer that is easy to track, and one open item cannot hold up the answer to another.
Who signs an RFI?
The general contractor's project manager or project engineer usually submits it, often on a subcontractor's behalf, and the architect or engineer of record answers it. Your contract sets the exact roles.
Can AI draft an RFI from my documents?
Yes. TrunkRFI first checks the specs, drawings, submittals, addenda and past RFIs for an existing answer. If there is none, it drafts the RFI, and a person on your team reviews and submits it.
Last updated November 3, 2026. Written by John Altieri, Construction Subject Matter Expert at Trunk Tools.
Sources: Trunk Tools platform data.