You’re three weeks into construction. Your contractor asks about the tile pattern in the master bath. You thought you’d settled this. He says you never clarified it. Now you’re in a standoff — and you have no written record of what was actually agreed. This happens because owners don’t track RFIs systematically.

What an RFI Is and Why It Matters

An RFI — a Request for Information — is a written question you send to your contractor asking them to clarify something in the design, scope, or construction documents. It’s not a change order. It’s not an instruction. It’s a question that produces an answer that becomes part of your project record.

I’ve sat through project meetings where no one could remember who said what about a specific detail. The contractor remembered it one way. The owner remembered it differently. The architect wasn’t sure. If someone had tracked these conversations in an RFI log, there would be no argument — just a date, a question, and a documented answer.

Without an RFI log, you’re working from memory and emails scattered across your inbox. Contractors have the same problem, but they’re used to it. You’re not. An RFI log puts you on equal footing because it creates a clear, dated record that both you and your contractor can reference.

Step 1: Set Up Your RFI Log Structure

Your RFI log doesn’t need to be complex. It needs to be consistent and easy to update. Start with a simple spreadsheet or shared document that both you and your contractor can access.

• Create a column for RFI number (start with RFI-001 and increment)
• Create a column for the date you sent the RFI
• Create a column for the topic or location (kitchen, master bath, foundation, etc.)
• Create a column for your specific question
• Create a column for the contractor’s answer
• Create a column for the date you received the answer
• Create a column for status (pending, answered, waiting for clarification)
• Create a column for any related change order number if the RFI led to a scope change

Example: RFI-004 sent March 15: “Kitchen electrical — can we move the island receptacle 18 inches to the left per the updated layout?” Answered March 17 by contractor: “Yes, moving as requested, no cost impact.” Status: Answered. No change order.

Step 2: Write Clear RFI Questions

A vague RFI gets a vague answer. Your job is to ask a question so specific that there’s only one reasonable interpretation. Before you send anything, read it back to yourself and ask: Could my contractor honestly answer this differently than I expect?

• Ask one specific question per RFI, not multiple questions bundled together
• Reference the exact document, drawing, or specification that creates the confusion
• If the question involves a measurement or location, include the specific dimensions or drawing reference
• State what you think you understood, then ask the contractor to confirm or correct it
• Avoid questions that sound like instructions — ask for clarification, not action
• Include a deadline if you need the answer by a certain date (but make it reasonable)

Example: Wrong: “What about the bathroom finishes?” Right: “Sheet A3.2 shows tile flooring in the master bath. Does this include the area inside the shower enclosure, or is that a separate material specification?”

Step 3: Send RFIs in Writing and Track the Date

Never ask an RFI question verbally on a phone call or in person. Verbal answers don’t count. You need a paper trail. This isn’t about distrust — it’s about clarity for both of you.

• Email your RFI to your contractor with the RFI number in the subject line
• Include all the context they need to answer without asking follow-up questions
• Ask for a written response by a specific date (typically 3-5 business days)
• Log the date you sent it in your RFI log immediately
• If your contractor uses their own RFI system, use theirs but also maintain your own log
• Keep a folder in your email or document system where you save every RFI and response

Example: Email subject: “RFI-007: Kitchen Cabinet Hardware” sent March 22. Body includes the question, a reference to the cabinet schedule, and a request for response by March 27.

Step 4: Record the Answer and the Date You Received It

When your contractor responds, update your log the same day. Don’t wait. Delays in logging create gaps, and gaps are where misunderstandings hide.

• Copy the contractor’s exact answer into the RFI log — don’t paraphrase or interpret
• Record the date you received the answer
• If the answer is unclear or incomplete, mark the status as “Waiting for Clarification” and send a follow-up RFI
• If the answer requires a change to scope or price, note the related change order number
• If the answer affects other parts of the project, make a note in your log so you can reference it later
• Have your contractor sign off on your log entry if possible, or confirm via email that your record matches their answer

Example: RFI-007 answered March 25: “Contractor states hardware schedule per Builder’s Hardware specification Section 08700 — brushed stainless steel, 3-inch pulls, cup style. This matches the allowance in the contract.” Status: Answered. No change order needed.

Step 5: Watch for RFIs That Turn Into Change Orders

Some RFIs uncover issues or lead to scope changes. When that happens, the change order should reference the RFI number. This keeps the paper trail clean and prevents the contractor from claiming they answered something they didn’t actually agree to.

• If an RFI answer requires a change order, request the change order immediately
• The change order should reference the RFI number and date
• Update your RFI log to show which change order corresponds to which RFI
• Review the change order scope against the RFI answer to make sure they match
• Never let a contractor claim an RFI was “just an answer” when the answer actually changed the scope
• If the RFI answer affects cost or schedule, that’s a change order, not just an RFI

Example: RFI-012 asks about asphalt driveway thickness. Contractor answers: “Per plans, 4 inches. Soil conditions at your site require 5 inches. Cost impact $800, timeline impact 1 day.” This is a change order. Create CO-003 that references RFI-012 and includes the $800 cost and timeline adjustment.

Step 6: Review Your RFI Log Regularly

Your RFI log is only useful if you actually look at it. Schedule time each week to review pending RFIs, follow up on unanswered questions, and make sure nothing is stuck in limbo.

• Set a standing time each Friday to review your RFI log for status
• Identify any RFIs that are past their response deadline and send a follow-up
• Look for patterns — if the contractor is consistently slow answering questions in a certain area, address it directly
• Before you approve a draw request or pay application, verify that all RFIs relevant to that phase are answered
• Use your RFI log as a checklist before major milestones (rough-in inspection, final walkthrough, etc.)
• Share your RFI log with your architect or owner’s rep if you have one — they should be using it too

Example: Every Friday, you spend 10 minutes checking your RFI log. You notice RFI-015 (electrical panel location) was sent 10 days ago and still shows “pending.” You send the contractor an email: “RFI-015 is now 10 days old. Can you provide a response by Monday morning?”

What to Watch For

• RFIs that get answered verbally and never documented — this defeats the entire purpose
• Answers that are so vague they don’t actually clarify anything (“We’ll figure it out on site” is not an answer)
• Long delays between when you send an RFI and when you log it, creating a gap in your record
• Scope changes that happen without a change order, hidden inside an RFI answer
• Multiple RFIs asking the same question because the first answer was unclear
• RFIs that are really change orders in disguise — questions about additions or upgrades, not clarifications
• Your contractor refusing to answer RFIs in writing because they claim it’s too formal

Questions to Ask Your Contractor

Before you start your project, have a conversation with your contractor about how you’ll handle RFIs together. This prevents friction later and makes clear that you’re organized and professional.

• Do you have an RFI process you prefer, or should we use my format?
• What’s a realistic timeline for you to answer most RFIs — 3 days, 5 days, or longer?
• If an RFI requires a site visit or research, how do we handle that timeline?
• Should I email RFIs to you directly, or is there a specific person on your team who handles these?
• If an RFI answer will cost money or take extra time, will you include that in the answer or send a separate change order request?
• Can we both keep the same RFI log so there’s one record we’re both working from?
• If we disagree about what an RFI answer means, how do we resolve that?
• Are there questions you’d rather I ask your architect or designer instead of you?

The Bottom Line

An RFI log is not optional if you want to keep your project on track. It’s the single clearest way to prevent misunderstandings from turning into disputes. Start it on day one, update it the same day you send or receive an RFI, and review it every week. When you close your project, it becomes your documentation that you managed it professionally and kept detailed records of every decision. If something goes wrong later, that log is your proof of what was actually agreed.