Free Construction RFI Template

The complete guide to construction RFIs

If you searched "RFI template construction" or "construction RFI sample", you're almost certainly looking for two things at once: the format to use, and a sense of how the RFI process actually works on a real job. This guide covers both. The free Excel template above is the format. The sections below explain when to issue an RFI, what to include, how to track them, and how to write ones that get fast responses instead of sitting in the architect's queue for three weeks.

What is an RFI in construction?

An RFI stands for Request for Information — the formal mechanism contractors use to get design or scope clarification from the architect, engineer, or owner in writing. It's not a complaint, not a change order, and not a submittal. It's a question with a paper trail.

You issue an RFI whenever the drawings or specs don't tell you something you need to know to build the work correctly. The question goes to the design team. The response comes back in writing and becomes part of the contract record. If the response changes the scope (adds work, costs money, or extends the schedule), the next step is a Change Order Request (COR) and ultimately a Change Order (CO). If the response is "build per the documents", you build per the documents and the file is closed.

RFIs are one of the most important documents on a construction project — but only when used correctly. Used well, they protect the contractor from doing wrong work and give the architect a chance to clarify intent before money is spent on rework. Used badly, they pile up unanswered, drift into change-order disputes, and slow the job down. The difference is almost entirely about how you write them and how you track them.

When should you issue an RFI?

The right time to issue an RFI is as early as possible — before the work is built, before materials are ordered, before the schedule slips. The wrong time is "after we already built it the wrong way and now we need to figure out who pays for the rework." Issue an RFI when:

• The drawings conflict. Architectural shows one ceiling height; mechanical drawings show ductwork that won't fit. Issue an RFI before building either way.
• The specification is missing or ambiguous. Specifications call for "Type X drywall" but don't say which manufacturer or fire rating. Issue an RFI.
• A detail is missing. The drawings show a wall section but the connection detail at the floor is not shown. Issue an RFI.
• You discover an unforeseen condition. You open up a slab and find existing utilities not on the as-builts. Issue an RFI.
• A submittal comes back with conflicting comments. The structural engineer wants one thing; the architect wants another. RFI.
• An owner-directed verbal change. The owner says "while you're at it, move that door three feet." Issue an RFI to formalize before doing the work.

Don't issue RFIs for things that are clearly in the documents — read carefully first. Don't issue RFIs as a substitute for design coordination (that's the architect's job, not yours, but pestering them with questions answered on Sheet A-203 hurts your credibility). Don't issue RFIs as a backdoor change-order claim — frame the question neutrally and let the response drive the COR.

The 6 elements every good construction RFI includes

The template above gives you a single-page format with the standard fields. Here's what each element should contain:

1. RFI Header

RFI number (sequential, project-prefixed if you have multiple projects), date issued, project name and number, the parties (Contractor, Architect, Owner, copies), and a one-line subject. Example subject: "RFI-024 — Curtain wall anchor detail conflict at Grid 12/A".

2. Reference

The specific drawing sheet, detail number, specification section, or contract clause your question relates to. "Sheet A-405, Detail 3" or "Spec Section 09 21 16 paragraph 2.3.A" is right. "The drawings" is wrong — you'll get pushback.

3. Question / Description

State the issue as a question. Be specific. Include enough context that the architect can answer without re-reading the entire drawing set. Examples:

"Detail 3/A-405 shows a 3/8" steel anchor plate at the curtain wall connection to the structure. Sheet S-202 Note 5 calls for 1/2" minimum at all curtain wall anchors. Which thickness governs?"

One issue per RFI. If you have three questions, write three RFIs — it keeps the tracking clean.

4. Proposed Solution

This is the single highest-leverage element on the RFI form. Architects respond fastest when you've done their work for them. Don't just ask "what should we do?" — propose a recommendation: "Recommend using 1/2" plate per S-202 Note 5 since it's the stricter standard. Cost impact: none. Schedule impact: none."

If your proposed solution is acceptable, the architect simply marks it "Approved" and the file closes. If they want something different, they have a starting point to push back from. Either way, response time drops dramatically.

5. Cost / Schedule Impact

State whether the question (or its likely answer) affects cost or schedule, and by how much. Be conservative — saying "no impact" when there clearly is impact undermines you when the bill comes. Saying "$50K impact" on a question that turns out to be trivial damages credibility. Pick one of: "No impact", "Possible impact — TBD pending response", "Cost impact estimated $X", "Schedule impact estimated X days".

6. Response and Sign-Off

A space for the architect to write their answer, date it, and sign. The contractor counter-signs to acknowledge receipt. Both signatures lock the response into the contract record.

How to write an RFI that gets a fast response

Some teams average 3-day turnarounds. Others sit at 21 days. The differences are entirely in how the questions are written:

• Lead with the proposed solution. Architects skim. If your first paragraph is the question without a recommendation, they tag it "needs research" and move on. If your first paragraph says "Recommend doing X for these reasons", they evaluate the recommendation in 30 seconds.
• Attach the drawing extract. Don't make the architect dig out the sheet. Screenshot the relevant detail, mark it up with the issue, and include it.
• One issue per RFI. Splitting two unrelated questions into separate RFIs cuts the response time on both — neither sits because the other is hard.
• Use neutral language. "Detail X conflicts with Spec Y, please clarify" reads as a question. "Detail X is incorrect and we will need a change order" reads as a fight. The first gets answered fast; the second triggers legal review.
• Don't bundle change-order asks. If you suspect the answer will trigger a CO, file the RFI clean. Then if the response confirms a scope change, file the COR separately.

RFI numbering and tracking conventions

Most teams number RFIs sequentially within a project — RFI-001, RFI-002, RFI-003 — and never reuse numbers. Some use a prefix system on multi-building or multi-phase jobs: RFI-A-001 for Building A, RFI-B-001 for Building B. Some include the originating trade: RFI-024-MEP. Pick a system at project start and stick with it.

The RFI log is the project-level tracker showing every RFI's status. Standard log columns:

The free Excel workbook above includes a 30-row pre-formatted log tab. Most jobs end up with 50-300 RFIs depending on size and complexity, so extend the log as needed.

How long should an RFI take to respond?

Most construction contracts specify a response window — often 7-14 calendar days. AIA A201 Section 4.2.7 references "reasonable promptness". For practical purposes:

• Critical RFIs (blocking ongoing work) — 24-72 hours
• High-priority RFIs (affect work within 2 weeks) — 5 business days
• Normal RFIs — 7-10 business days
• Low-priority RFIs (long lead clarifications) — 14 business days

If your average response time is creeping above two weeks, the conversation with the design team is about workflow — not specific RFIs. Surface the metric in your weekly OAC (Owner-Architect-Contractor) meeting: "We have 18 open RFIs older than 14 days. Here are the top 3 affecting next month's schedule."

RFI vs Change Order vs Submittal — what's the difference?

These get conflated. They're separate documents with separate purposes:

• RFI — A question. You're asking for clarification of intent or scope. The response may or may not trigger a change.
• Submittal — A proposal. You're showing the architect what you intend to install — shop drawings, product data, samples, mock-ups. The architect approves or asks for corrections.
• Change Order Request (COR) — A proposed change. You're saying "the scope has shifted and here's what we propose for cost and schedule." The owner can approve or reject.
• Change Order (CO) — An executed change. Signed by the owner, contractor, and architect. Becomes part of the contract.

An RFI sometimes becomes the trigger for a COR ("the response added scope — here's the cost"), but the documents are filed and tracked separately. Pair this RFI template with our free Change Order template when a response triggers a scope shift.

AIA G716, ConsensusDocs 200, and custom RFI forms

If your contract is AIA, the contractually-referenced RFI form is AIA Document G716. ConsensusDocs 200 contracts reference their own form. DBIA design-build contracts have their own variation. Each is functionally equivalent — same fields, same purpose, different headers and copyright statements.

This free template is a generic format that captures all the same elements. Use it on:

• Projects without contract-mandated forms
• Internal documentation when the official AIA form is paywalled
• Subcontractor-to-GC RFIs (which usually don't require AIA forms)
• Early-design pre-construction questions

Sample RFIs by trade

Electrical sample RFI

"Subject: Receptacle layout conflict, Room 312
Reference: Sheet E-203, Detail 4
Question: Detail 4/E-203 shows a duplex receptacle at +18" AFF on the south wall of Room 312. Sheet A-203 shows a built-in casework at the same wall location, with no power outlets shown in the casework. Should the duplex be relocated above the counter at +44" AFF, or omitted?
Proposed solution: Relocate to +44" AFF above the counter, code-compliant for kitchenette use. No cost impact.
Cost impact: None. Schedule impact: None."

Mechanical sample RFI

"Subject: VAV-7 location conflict with structural
Reference: Sheet M-301, Equipment Schedule
Question: VAV-7 is shown at column line C/4 between RTU-2 supply ducts. The flange at that location interferes with the W14x30 beam shown on Sheet S-201. Confirm if VAV-7 can be relocated 4'-0" east, or if the duct should be re-routed.
Proposed solution: Relocate VAV-7 4'-0" east per attached sketch. Maintains throw and CFM per design.
Cost impact: $0. Schedule impact: 0 days."

Structural sample RFI

"Subject: Footing depth at northeast corner
Reference: Sheet S-101, Foundation Plan
Question: Foundation excavation at Grid F/8 encountered existing rock at 4'-6" below planned bottom-of-footing. Original drawings show no rock and call for 8'-0" footing depth.
Proposed solution: Bear footing on rock at current 4'-6" depth, with rock surface prepared per Section 03 30 00. Saves excavation cost and time.
Cost impact: -$2,800 (savings). Schedule impact: 0 days."

Common RFI mistakes

1. Asking three questions in one RFI. Forces the architect to answer all three to close one file. Split them.
2. No proposed solution. Makes the architect do the work. Doubles response time.
3. Vague references. "The drawings" or "the specs" — be specific to sheet and detail.
4. Adversarial language. "The architect's drawings are incorrect" gets a slow, defensive response. "The drawings conflict at X — recommend resolution Y" gets a fast collaborative one.
5. Not tracking response time. If you don't measure, the architect doesn't either. Weekly RFI status meetings transform this.
6. Filing too many RFIs. If your project hits 20+ RFIs per week, the design isn't issue-free — but it might also mean you're not reading the documents carefully. Self-audit before sending.
7. Not closing the loop. An RFI that gets a verbal answer but never a written response stays "Open" forever. Insist on written closure.

When to move beyond Excel for RFIs

For small jobs (under 30 RFIs total), the Excel template + an email folder is fine. Past that, the manual process starts to crack:

• The log gets out of sync with the actual file folder
• Different team members maintain different versions
• Response time slips because nobody's tracking it actively
• Searching for "the RFI about X" requires a manual scroll through 80 rows
• The architect's responses live in email, separated from the log

That's where dedicated RFI tracking software earns its keep. Field PM ships with an integrated RFI module: open RFIs are tracked alongside the project schedule, response times are calculated automatically, foremen can flag a question from a daily field report that auto-creates an RFI draft, and the GC can generate a status report for the OAC meeting with one click. Start a 14-day free trial — no credit card required.

Related construction templates

• Change Order template — for when an RFI response triggers scope change
• Daily Field Report template — to document the issue that prompted the RFI
• Punch List template — for close-out items that started as field RFIs
• JSA template — when an RFI response triggers new safety considerations
• All free construction templates