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.
What does a proper construction RFI example 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.
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. In Trunk Tools platform data, an estimated 17.2% of draft RFIs are already answered by previous RFI responses or other project documents, meaning the question never needed to go out at all. This can lead to tension with the design team, owner’s rep, and owner when it happens frequently.
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.
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.
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.
Frequently asked questions
How is an RFI supposed to look like on a construction project? It should be short and structured rather than a loose email. It should be written clearly and cite relevant sources to ensure prompt response from the design team. Finally, you should check to ensure the answer to the question is not already present in project documents or previous RFI responses.
What information should a construction RFI include? An RFI number, project name and number, date submitted, expected response date, the responsible contractor, a subject line, the drawing or spec section in question, a specific question, a proposed solution if one exists, a cost or schedule impact flag, and any supporting sources or attachments.
What is an example of a well-written construction RFI? A well-written RFI names the exact drawing sheet or spec section in conflict, asks one specific question instead of several bundled together, and proposes a solution rather than leaving the design team to originate one.
Why do RFIs get sent back for clarification? The most common reasons are a vague question, a missing drawing or spec reference, or a question the project documents already answer.
Is there a standard construction RFI template? There's no single universal format, but most templates include the same core fields: project and RFI number, drawing or spec reference, the question, a proposed solution, an expected response date, and a cost or schedule impact flag.
By the Trunk Tools team. Last updated August 26, 2026.
Sources: Trunk Tools platform data.