Free RFI Template + How To Build One That Actually Gets Answered
You sent the RFI three days ago. No response. You follow up. The engineer says they never received it. Turns out it went to the wrong inbox, got buried under twelve other emails, and nobody knew it was sitting there until you called.
A well-structured RFI template, combined with a consistent tracking system, is how you fix it.
This post covers what goes into a construction RFI template, how to write RFIs that get fast, complete responses, and includes a free downloadable template you can use on your next project today.
What a Construction RFI Is (and What It Isn't)
A Request for Information is a formal written question submitted by a contractor or subcontractor to the design team asking for clarification on something in the contract documents. That could be a drawing conflict, a missing detail, an unclear spec, or an ambiguity in the scope of work.
An RFI is not a substitution request, a change order request, or a way to propose a different approach to the work. If you're asking the engineer to approve a different material than what's specified, that's a submittal. If you've discovered scope that isn't addressed in the contract, that's likely a change order conversation.
The RFI is specifically for: "The contract documents say X, but we need clarification on Y before we can proceed."
When it's used correctly, it creates a documented record of the question and the official answer. That documentation protects you when disputes come up later.
What Goes Into a Construction RFI Template
A complete RFI template has two components working together: the individual RFI form you fill out and send, and the RFI log you use to track every open RFI across the project.
Project Information
Project name, RFI number, spec section, submitted by, submitted to, date submitted, and due date. These fields aren't optional. A missing due date means the reviewer has no accountability. A missing spec section means reviewers don't know which discipline is responsible.
The Question
This is the core of the document. Be specific. Reference the drawing number, the grid line, the detail number, the spec paragraph.
"We need clarification on the steel connection" is not an RFI. "We need clarification on how the W6 beams above the stair tower connect to the CMU walls at grid lines 7.8/B, see Detail 11 on S-8" is an RFI.
Attachments
Any supporting documentation: the drawing in question, a photo from the field, a sketch showing the conflict. If you're referencing a detail, attach it.
Response Section
A dedicated place for the design team to document their response, response date, and any attached revised drawings or specifications.
Impact Assessment
Cost impact, schedule impact, and whether a change order is required. Fill this in even when the answer is no. Documenting "no cost impact, no schedule impact" protects you just as much as documenting when there is an impact.
The RFI Log
The log is the master list of every RFI on the project. It tracks status across the full project lifecycle, not just individual RFI documents.
A good RFI log shows RFI number and title, spec section, who submitted it and who it was sent to, date submitted, due date, date closed, days open, current status, assigees cost and schedule impact flags, and notes.
Without it, you find out an RFI has been sitting unanswered for three weeks when you call the field and learn the concrete pour got pushed because nobody had an answer on the embed locations.
How to Write an RFI That Gets a Fast Response
The design team's review time gets most of the blame for slow RFI turnarounds.
Sometimes that's fair. More often, the delay starts before the RFI is even sent.
Check the Contract Documents First
Before you write anything, do the homework. Review the relevant drawings, section details, project specifications, and any applicable submittals. The answer is there more often than you'd expect, in a note buried in a detail, a spec paragraph that addresses the condition, or a submittal that was already approved covering that exact scope.
Submitting an RFI when the answer already exists in the contract documents wastes the design team's time and slows down the responses you actually need. Consultants notice when RFIs come in that could have been answered with a closer read of the drawings.
Building a reputation for doing the legwork first means your RFIs get taken more seriously and turned around faster.If you've reviewed the documents and the answer genuinely isn't there, now you have an RFI.
Write One Question Per RFI
When you bundle three questions into one RFI, the reviewer either answers the easy ones and punts the hard one, or they hold the whole thing until they can answer all three. Either way, you wait longer.
Reference the Exact Drawing, Sheet, and Detail Number
Don't make the engineer hunt for the information. Tell them exactly where to look. Sheet number, detail number, grid line reference. If there's a conflict between two drawings, cite both.
State the Schedule Impact Upfront
Reviewers prioritize when they understand the schedule consequence. If you don't have the answer by Friday and concrete placement gets pushed two weeks, say that. If the RFI isn't on the critical path, say that too.
Set a Realistic Due Date
Standard RFI response time is five to seven business days for most items. Complex structural or MEP questions may require more. A two-day turnaround on a question that requires engineer of record review and a drawing revision will get you a rushed, incomplete answer.
Coordinate Between Trades Before Submitting
If your mechanical contractor has a conflict with the electrical contractor's conduit routing, sort out what the question actually is before the RFI goes to the design team. An RFI that comes back answered, but creates a conflict with another sub you didn't catch, means writing another RFI to fix the first one.
RFI Tracking: The Part Most Teams Get Wrong
The most common tracking failure isn't losing RFIs. It's knowing an RFI was submitted and then losing visibility on where it stands. It goes out on Monday. By Thursday, nobody's sure if it was received. By the following Tuesday, it's overdue.
Your RFI log should tell you, at a glance, every open RFI on the project, who currently has the ball, and whether anything is approaching or past its due date.
That requires the log to be updated consistently, and it requires someone to own that update process. Whoever owns it needs to close RFIs in the log the same day a response comes in, follow up on anything within a day of its due date, and flag overdue items to the PM before they become schedule problems.
Free RFI Template Download
The template linked below includes three sheets.
RFI Log
Tracks every RFI on your project with auto-calculated days open and summary counts by status. It comes pre-loaded with two sample RFIs from a real structural steel question on the Pharmablock Addition project so you can see exactly how to fill it in.
RFI Form
A complete individual RFI document ready to fill in and send. Covers all required fields: project information, question, attachments, response, and impact assessment.
How to Use
A quick reference guide with tips for faster approvals and common mistakes to avoid.
When the Spreadsheet Stops Being Enough
On a single project with a handful of active RFIs, a well-maintained spreadsheet and a consistent email process will get the job done.
It starts to break down when you're running three projects at once, RFIs are going out from multiple subs to multiple reviewers, and you need to know the status of every open item across your portfolio without making five phone calls.
SubmittalLink was built for that. You create the RFI in the platform, assign reviewers, and the system routes it, sends notifications, tracks the RFI assignees, and keeps the log current automatically.
Sequential or parallel review, depending on how the question needs to be handled. And if you want to tighten up your RFI questions before they go out or clean up a response before it comes back to the field, the built-in ‘Enhance with AI’ feature helps you do that without leaving the app.
If you want that same organization without the manual upkeep, book a 15-minute demo and we'll show you how it works.
The Bottom Line
A well-built RFI template gives you a consistent format. The log gives you visibility.
Neither matters without the discipline to write one question per RFI, reference the right drawing, and set a realistic due date.
If you find yourself spending more time maintaining the spreadsheet than managing the job, that's what SubmittalLink is for.