Construction RFI Guide: How to Write and Manage RFIs | Projul

If you have been in construction for any length of time, you have dealt with RFIs. Maybe you have written hundreds. Maybe you have been on the receiving end of poorly written ones that made no sense. Either way, RFIs are one of those things that can make or break a project timeline.

The problem is that most contractors treat RFIs as an afterthought. They fire off a vague question, wait weeks for an answer, and then wonder why the project is behind schedule. That approach costs real money.

This guide breaks down everything you need to know about construction RFIs. How to write them so they actually get answered quickly, how to track them without drowning in paperwork, and how to avoid the common mistakes that lead to expensive delays.

What Is an RFI in Construction?

An RFI, or Request for Information, is a formal written question sent during a construction project when something in the plans, specs, or contract documents is unclear, missing, or contradictory.

Think of it this way. The architect draws the plans. The engineer does the calcs. But no set of construction documents is perfect. There are always gaps, conflicts, or details that need further explanation. The RFI is the official tool for getting those answers.

Here are a few examples of when you would submit an RFI:

• The plans show a wall dimension that conflicts with what is shown on the reflected ceiling plan
• A specified material has been discontinued and you need direction on an acceptable substitute
• The drawings do not show how to handle a transition detail between two different finish materials
• A structural note references a detail sheet that does not exist in the plan set

RFIs create a paper trail. That paper trail protects you if there is a dispute later about what was communicated and when. Without a formal RFI process, you are relying on verbal conversations and handshake agreements, which do not hold up when things go sideways.

When Should You Submit an RFI?

Not every question needs an RFI. If you can find the answer in the plans or specs by looking more carefully, do that first. RFIs should be reserved for legitimate issues that require direction from the design team.

Submit an RFI when:

• Something is missing from the plans. A detail is referenced but not included, or a section of the building has no finish schedule.
• Two documents conflict with each other. The architectural plans show one thing, but the structural plans show something different.
• A specified product is unavailable. The material called out in the specs cannot be sourced, and you need approval for a substitute.
• The design intent is unclear. You can interpret a detail more than one way, and building it wrong would be costly to fix.
• Field conditions do not match the plans. You open up a wall and find something unexpected that changes the planned approach.

Do not submit an RFI when:

• The answer is clearly stated in the plans or specs and you just missed it
• You want to suggest a value engineering idea (use a separate VE proposal for that)
• You are trying to document a change order request (use the proper change order process)
• You want to complain about a design decision (that is a conversation, not an RFI)

Submitting unnecessary RFIs slows down the process for everyone. Design teams get buried in questions, and your legitimate RFIs get stuck in the queue behind questions that did not need to be asked.

How to Write an RFI That Gets a Fast Response

The number one reason RFIs take forever to get answered is because they are poorly written. A vague RFI forces the architect to go back and forth with you before they can even understand what you are asking. That kills response time.

Here is what a well written RFI includes:

1. A Clear, Specific Subject Line

Bad: “Question about wall”

Good: “Clarification needed on wall type at Grid Line B between floors 2 and 3, Sheet A301”

The subject line should tell the reader exactly what the RFI is about without opening it. When someone is reviewing a list of 50 open RFIs, a clear subject line helps them prioritize.

2. Reference the Exact Location in the Documents

Every RFI should reference the specific drawing sheet, detail number, specification section, or page number where the issue exists. Do not make the reader hunt for it.

Include:

• Sheet number and detail reference
• Specification section and paragraph
• Grid lines or room numbers
• Any other location identifiers that apply

3. Describe the Problem Clearly

State what the issue is in plain language. What is unclear? What is conflicting? What is missing? Be specific. The person reading this might be reviewing it days after you wrote it, and they might not have the context you had in the moment.

4. Explain Why It Matters

Help the reviewer understand the impact. Is this holding up a concrete pour? Is it blocking a material order with a 12 week lead time? When the design team understands the urgency, they prioritize accordingly.

5. Suggest a Solution

This is the one that most contractors skip, and it is the single best way to speed up RFI responses. If you can suggest a reasonable solution, the architect often just approves it instead of having to come up with their own answer from scratch.

For example: “We suggest substituting Product X with Product Y based on matching performance specs. See attached cut sheet. Please confirm this is acceptable.”

6. Attach Supporting Documents

Include photos, sketches, markup drawings, product cut sheets, or anything else that helps the reviewer understand the issue and evaluate your suggested solution. A picture is worth a thousand words, especially when you are describing a field condition.

RFI Tracking and Logging

If you are managing more than a handful of RFIs on a project, you need a system for tracking them. Losing track of an open RFI is one of the fastest ways to create a project delay.

What to Track

At minimum, your RFI log should include:

• RFI number. Sequential numbering that everyone on the project uses consistently.
• Date submitted. When the RFI was sent to the design team.
• Subject. A brief description of the question.
• Priority. How urgently you need an answer.
• Status. Open, under review, answered, or closed.
• Date response needed. Based on your project schedule and contract requirements.
• Date response received. When the answer actually came back.
• Response summary. What the answer was and any actions required.
• Cost and schedule impact. Did the response trigger a change order or schedule adjustment?

Who Manages the RFI Log?

On most projects, the general contractor maintains the master RFI log. The project manager or project engineer is usually responsible for keeping it current. Subcontractors should maintain their own logs as well, but the GC log is the official project record.

Review the Log Regularly

Do not just create an RFI log and forget about it. Review open RFIs at every project meeting. Flag anything that is overdue. Follow up on items that are approaching their response deadline. A stale RFI log is almost as bad as no log at all.

Using project management software that includes built in documentation tracking makes this much easier. When your RFI log lives in the same system as your project schedule, you can see exactly how open RFIs affect your timeline without switching between tools.

Common RFI Mistakes That Cost You Time and Money

After years of working with contractors, here are the mistakes we see most often:

1. Writing Vague RFIs

“What do you want us to do with this wall?” is not an RFI. It is a question that will generate more questions. Be specific about what wall, what issue, and what you need to know.

2. Submitting Too Many RFIs at Once

Dumping 30 RFIs on an architect on a Friday afternoon is a great way to ensure none of them get answered quickly. Batch your RFIs reasonably and prioritize the ones that are actually time sensitive.

3. Not Including Enough Context

If you reference a field condition, include a photo. If you are asking about a material substitution, include the cut sheet. Make it easy for the reviewer to understand and respond without asking follow up questions.

4. Waiting Too Long to Submit

If you spot an issue during plan review, submit the RFI immediately. Do not wait until you are about to start that phase of work. The earlier you ask, the more time the design team has to respond without impacting your schedule.

5. Not Following Up on Overdue RFIs

An RFI that sits unanswered for three weeks is not the design team’s problem alone. It is your problem too, because it is your schedule that suffers. Track response deadlines and follow up before they pass, not after.

6. Using RFIs for the Wrong Purpose

RFIs are for requesting information. They are not change orders, not value engineering proposals, and not complaint letters. Using them for the wrong purpose undermines the process and annoys the people who have to respond.

7. Poor Numbering and Organization

When your RFI numbers do not follow a consistent system, or when RFIs are scattered across emails, text messages, and random documents, things get lost. Standardize your numbering and keep everything in one place.

How RFIs Impact Your Project Timeline

Every open RFI represents a potential delay. The math is simple. If an RFI takes 14 days to get answered, and the work that depends on that answer is on your critical path, you just lost two weeks.

Now multiply that across a project with 100 to 200 open RFIs. Even if most of them are not on the critical path, some will be. And the cumulative effect of small delays adds up fast.

Here is how RFIs typically affect timelines:

Direct delays. Work cannot proceed until the RFI is answered. The crew either sits idle or moves to a different area, which disrupts your planned sequence.

Material procurement delays. If the RFI involves a material substitution or specification clarification, you cannot order the material until you have an answer. Long lead time items make this even worse.

Cascading schedule impacts. A delay in one area often pushes other work back. Electrical cannot rough in until the wall layout is confirmed. Drywall cannot start until electrical is done. One unanswered RFI can affect multiple trades.

Change order negotiations. If an RFI response results in additional work, you now need to negotiate a change order before proceeding. That adds more time to the process.

The best defense against RFI related delays is speed. Submit RFIs early, write them clearly so they get answered on the first pass, and track them aggressively so nothing falls through the cracks.

Digital RFI Management vs. Paper

If you are still managing RFIs on paper, through email chains, or in a shared spreadsheet, you are making the process harder than it needs to be.

The Problems with Paper and Email RFIs

Paper gets lost. Literally. It gets left on a desk, filed in the wrong folder, or thrown away by accident. When you need to reference an RFI from six months ago during a dispute, good luck finding it.

Email chains become unmanageable. An RFI that goes back and forth three or four times creates a thread that is impossible to follow. Add in the people who reply all, the people who forget to reply all, and the attachments that get stripped by email servers, and you have a mess.

Spreadsheet logs fall out of date. Someone has to manually update the spreadsheet every time an RFI is submitted, responded to, or closed. That person is usually the project manager, who already has 50 other things to do. The log falls behind, and now it is unreliable.

No accountability. When an RFI gets lost in an email thread, it is hard to prove when it was sent, when it was received, and how long it took to get a response.

Why Digital RFI Management Is Better

A dedicated project management platform solves these problems:

Everything is in one place. Every RFI, every response, every attachment, and every revision lives in a single system. Nothing gets lost.

Automatic tracking. The system records when an RFI was created, sent, received, and answered. You do not have to manually update a log.

Notifications and reminders. The system can alert you when a response is overdue or when an RFI has been sitting open for too long.

Mobile access. Your field team can submit and review RFIs from the job site without driving back to the office. When a superintendent spots an issue at 7 AM, they can document it with photos and submit the RFI before the morning meeting.

Reporting. You can pull reports showing RFI response times, identify bottlenecks, and use the data to hold design teams accountable for timely responses.

Projul’s project management tools keep your documentation, scheduling, and communication in one platform. That means your RFIs are connected to your project schedule, so you always know which open questions are affecting your timeline. No more jumping between spreadsheets, email, and a separate scheduling tool.

Building a Better RFI Process for Your Team

Improving your RFI process does not happen overnight, but it starts with a few simple changes.

Create an RFI template. Give your team a standard format to follow so every RFI includes the right information. This reduces back and forth and speeds up response times.

Train your team. Make sure everyone on your crew knows when to submit an RFI and how to write one properly. A 30 minute training session can save hours of wasted time on poorly written RFIs.

Set internal deadlines. Do not just track when the design team owes you a response. Set internal deadlines for when your team should submit RFIs based on the upcoming schedule. If you need an answer before you pour the slab, submit the RFI with enough lead time built in.

Review RFIs at every project meeting. Make RFI status a standing agenda item. Review what is open, what is overdue, and what is coming up. This keeps everyone accountable and prevents items from falling through the cracks.

Use software that connects the dots. When your RFI tracking, project scheduling, and document management all live in one system, you spend less time managing the process and more time building. That is the whole point.

If you are ready to get your project documentation under control, check out Projul’s pricing to find a plan that fits your team.

Final Thoughts

RFIs are not glamorous. Nobody gets into construction because they love writing formal information requests. But handling them well is one of the biggest differentiators between contractors who finish projects on time and on budget and those who do not.

Write clear RFIs. Submit them early. Track them aggressively. Follow up on overdue responses. And use tools that make the process easier instead of harder.

Your future self, the one who is not dealing with a schedule delay or a dispute over what was communicated, will thank you.