Brixzly

Tag: RFI

  • How Should You Track and Manage an RFI Log on Your Construction Project?

    Quick answer

    An RFI log is a simple spreadsheet or document that records every Request for Information you send to your contractor, when you sent it, what you asked, and what answer you received. Without one, you lose track of critical decisions and create the exact conditions where disputes happen. The key is to start it immediately and update it the same day you send or receive an RFI.

    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.

    If you’re managing your own project without an architect or general contractor, reading and tracking RFI responses can be overwhelming. We built Brixzly because owners deserve organized access to the information that shapes their projects. You can upload your RFI log and documentation to see connections you might miss reading them individually, and get flagged when answers create scope or cost impacts you didn’t expect.

    FAQ

    What’s the difference between an RFI and a change order?

    An RFI is a question that seeks clarification or confirmation about existing scope. A change order is a written agreement to change the scope, price, or timeline. If an RFI answer requires a change order, they should be linked in your log. If the RFI answer doesn’t change scope or cost, no change order is needed.

    Do I need an RFI if I’m just asking the contractor a quick question?

    If the answer matters to your project record, yes. “Quick questions” are exactly where misunderstandings happen because you’re not documenting the answer. The only questions you don’t need to log are ones where the answer doesn’t affect the work — like “When will you be here next Tuesday?”

    What if my contractor doesn’t want to use an RFI system?

    Every contractor is used to RFIs — they’re standard in the industry. If yours resists, that’s a red flag. At minimum, establish in writing that you’re using RFIs to track important questions and their answers. If they still refuse, consider whether you trust them enough to manage your project without documentation.

    Can I combine multiple questions into one RFI to save time?

    No. Multiple questions in one RFI create multiple chances for confusion or partial answers. Send separate RFIs. It takes 30 seconds longer and prevents problems later.

    What should I do if my contractor’s answer doesn’t match what I understood?

    Send a follow-up RFI immediately clarifying what you thought you heard and asking them to confirm or correct it. Document the discrepancy in your log. If this becomes a pattern, address it in person and establish clearer communication. If the disagreement affects cost or scope, treat it as a change order discussion, not just an RFI question.

    Do I need to share my RFI log with my contractor?

    Yes, ideally. A shared log prevents two different versions of reality. If your contractor refuses to share, maintain your own log anyway — it’s still your protection. For major projects with an architect or owner’s rep, all three of you should be using the same RFI log.

  • How to Write an RFI That Gets You the Answer You Need

    Quick answer

    An RFI—a Request for Information—is a formal written question to your contractor asking him to clarify something in the plans, specifications, or scope. Write it clearly, describe exactly what you’re asking about, and explain why it matters. The clearer your RFI, the faster and more useful the answer will be.

    You’re reviewing the drawings for your addition and you see a detail that doesn’t make sense. The electrical plan shows a circuit breaker box in two different locations. You could ignore it and hope it resolves itself. Or you could ask now, before the work starts. That’s what an RFI is for.

    Why RFIs Matter More Than You Think

    I’ve managed enough projects to know that the smallest unclear detail can become expensive later. A misunderstanding about material specs, dimensions, or installation method doesn’t stay small. It becomes a change order—a written amendment to your contract that adjusts scope or price. And by then, the contractor has already started working based on his interpretation, not yours.

    An RFI is your chance to ask questions before work begins. It creates a written record of what was unclear and what the answer was. That record protects both you and your contractor. It prevents arguments about “who said what” later.

    Most homeowners wait too long to ask. They hope things will become clear once work starts. That almost never happens. The time to ask is now, when changes are still simple and inexpensive.

    What an RFI Actually Is

    An RFI is a formal request, not a casual question. You could ask your contractor in a text or phone call, but an RFI is written and dated. It goes to the architect and the contractor. Everyone sees the same question and the same answer.

    Your contract probably already defines how RFIs work. It will say who submits them, who answers them, and how long the answer should take. Read your contract’s section on RFIs before you write your first one. Most standard contracts allow 5-7 business days for an answer.

    An RFI is not a complaint. It’s not an accusation that something is wrong. It’s a neutral question asking for clarification. Keep that tone throughout.

    Step 1: Identify What You’re Actually Asking

    The biggest mistake is writing an RFI that’s too vague. “This doesn’t look right” is not useful. The contractor cannot answer it because he doesn’t know what specifically you’re questioning.

    • Reread the plans or specification section that confuses you
    • Identify the exact detail, dimension, material, or location in question
    • Write down what you see in one document and what you see elsewhere that contradicts it
    • Ask yourself: “What specific thing do I need the contractor to tell me?”
    • Do not write the RFI until you can answer that question in one sentence

    Example: Instead of “The bathroom tile looks confusing,” write “The floor plan shows 2×2 ceramic tile, but the detail section shows 3×6 porcelain tile. Which is correct?” The contractor knows exactly what to answer.

    Step 2: Reference the Exact Location in the Documents

    Your contractor and architect have dozens of drawings. You need to tell them exactly where to look. Vague references waste everyone’s time.

    • Name the specific drawing or specification section (example: “Sheet A4.2, Kitchen Elevation”)
    • Include the drawing number, date, and revision if available
    • Reference the exact detail number or callout if there is one
    • For specifications, cite the CSI division number—the standard numbering system for construction specs—and the section name (example: “CSI Division 09 – Finishes, Section 09 29 00, Gypsum Board”)
    • If the conflict is between two documents, reference both
    • Take a screenshot or scan the relevant pages and attach them

    Example: “Sheet A2.1 – Floor Plan, revision dated March 15, shows the kitchen island at 36 inches wide. Sheet A4.3 – Kitchen Elevation shows the island at 42 inches wide. Which dimension should the contractor build to?”

    Step 3: Describe What You See, Not What You Think

    Stick to facts. Don’t interpret or guess at what something means. Let the contractor and architect answer the question based on the actual documents.

    • State exactly what the plan shows (example: “The detail shows the window trim installed flush to the exterior sheathing”)
    • State what the specification says (example: “The spec requires a 1-inch rain screen gap behind all exterior cladding”)
    • Do not assume you know what’s wrong
    • Do not suggest a solution or correction
    • Do not accuse anyone of making an error
    • Use neutral language: “the drawing shows” not “the drawing is wrong”

    Example: “The standard detail for exterior wall assembly shows 6 inches of stone veneer. The opening detail for the window shows stone veneer extending 2 inches on both sides of the window frame. For a 36-inch window, this creates a conflict. Please clarify the intended veneer width at window openings.” This approach respects the professional work already done while asking for clarification.

    Step 4: Explain Why You’re Asking

    A one-sentence explanation of why this matters makes the RFI faster to answer and shows you’re serious, not nitpicking.

    • Explain the practical impact (example: “This affects the rough opening size for the HVAC ductwork”)
    • Note if the unclear detail affects timing or sequencing (example: “The contractor needs to know this before framing the wall”)
    • Mention cost implications only if they’re real (example: “The material choice affects the budget”)
    • Keep this brief—one or two sentences maximum
    • Frame it neutrally: “to move forward” not “to avoid problems”

    Example: “This affects the framing timeline because the contractor needs to know the exact opening size before he builds the header.”

    Step 5: Ask a Clear Question, Not Multiple Questions

    One RFI should have one main question. If you have multiple unrelated questions, write multiple RFIs. This keeps each one focused and easier to answer.

    • End with a direct question that requires a specific answer
    • Avoid compound questions like “Should the tile be 2×2 or 3×6, and if 3×6, should it be porcelain or ceramic?”
    • Ask “Which dimension should the contractor build to?” not “Is there an error here?”
    • Request a specific answer format if it helps (example: “Please provide a marked-up drawing showing the correct location”)
    • Do not ask for design advice or opinions

    Example: “The plans and spec disagree on the tile size. Please confirm: Is the kitchen floor tile 2×2 ceramic or 3×6 porcelain?” The contractor knows exactly what answer you need.

    Step 6: Attach Relevant Documentation

    Screenshots and marked-up pages save time and reduce the chance of misunderstanding. The contractor doesn’t have to dig through documents to understand your question.

    • Scan or screenshot the exact pages you’re referencing
    • Circle, highlight, or arrow the specific detail in question
    • If there are two conflicting details, attach both pages marked side-by-side
    • Use a PDF annotation tool or mark-up app to highlight what you’re asking about
    • Attach the file to your RFI
    • Keep file sizes reasonable—under 10 MB total

    Example: Attach Sheet A2.1 with the island width circled on the floor plan, and Sheet A4.3 with the different width highlighted on the elevation. The contradiction is now impossible to miss.

    Step 7: Submit It Formally Through the Right Channel

    Your contract defines how RFIs are submitted. Follow that process. If your contract doesn’t say, ask your contractor or architect how they want to receive RFIs before you send your first one.

    • Use email if that’s what your contract requires, and send it to all parties listed in the contract
    • If your project uses a construction management platform, submit it through that platform
    • Include “RFI” in the subject line with a brief description
    • Number your RFIs in sequence (RFI #1, RFI #2) for easy reference
    • Date it and note the date it was submitted
    • Keep a record of every RFI you submit and every answer you receive
    • Do not submit RFIs in texts, phone calls, or casual emails unless the contract explicitly allows it

    Example: Subject line: “RFI #3 – Kitchen Island Dimension Conflict.” Include the date submitted and send it to the GC, the architect, and anyone else your contract specifies.

    What to Watch For

    • An answer that doesn’t actually answer your question—push back and ask for clarification
    • An RFI that comes back marked “See the plans” without additional explanation—this is not a useful answer, request a specific clarification
    • A delayed answer that arrives days after the contractor has already started the work—this is a red flag and may indicate a change order is coming
    • An answer that requires a change order to implement—if the clarification changes scope or cost, that becomes a separate change order document
    • An RFI that contradicts your contract—if the answer conflicts with what your contract says, the contract usually wins, but ask your architect to confirm
    • Multiple similar RFIs getting different answers—this suggests confusion in the design and may require an architect meeting to resolve

    Questions to Ask Your Contractor or Architect

    Before you start submitting RFIs, make sure you understand the process. These questions will clarify how your project handles them.

    • How should I submit RFIs—email, a specific platform, or printed form?
    • Who do I send RFIs to, and who else will see them?
    • How long should I expect to wait for an answer?
    • If I don’t get an answer in that time, what’s my next step?
    • If an RFI answer requires a change to the scope or cost, how does that become a change order?
    • Should I number my RFIs myself, or will you do it?
    • If the plans are unclear on multiple related details, should I ask them all in one RFI or submit separate ones?
    • What happens if the architect and contractor disagree on the RFI answer?
    • Can I submit RFIs before work starts on that part of the project, or only during construction?

    The Bottom Line

    An RFI is your tool to get clarity before work starts. Write it clearly, reference exactly what you’re asking about, and keep it focused on one question. A well-written RFI takes the contractor five minutes to answer. A vague one takes an hour, or doesn’t get answered at all. Start submitting RFIs the moment you see something unclear in the plans or specifications. Don’t wait for construction to begin.

    When you’re reviewing construction documents on your own, unclear details are easy to miss or misinterpret. We built Brixzly to help owners catch these kinds of conflicts before they become problems. If you’re managing a project and want a second set of eyes on your plans and specifications before you write RFIs, Brixzly can highlight the details that need clarification.

    FAQ

    What’s the difference between an RFI and a change order?

    An RFI asks for clarification on what’s already in the contract. A change order—a written amendment to your contract that adjusts scope or price—changes the scope or cost. If an RFI answer requires new work or changes existing work, that becomes a change order. The RFI comes first; the change order comes after if needed.

    How many RFIs is too many?

    There’s no such thing as too many RFIs if they’re legitimate questions. Some projects have dozens. Others have none. The goal is to clarify everything before work starts, so submit as many as you need. If you’re submitting 50 RFIs and getting inconsistent answers, that’s a sign the design itself needs a meeting to resolve larger conflicts.

    Can the contractor refuse to answer an RFI?

    The contractor should answer every RFI submitted under the contract process. If he ignores an RFI, document it and follow your contract’s escalation process. Most contracts require the architect to weigh in if the contractor and owner disagree on an RFI answer.

    What if the contractor answers an RFI but then does something different during construction?

    If the contractor doesn’t follow the RFI answer, that’s a quality issue and a potential breach. Document it with photos and written notes. Bring it up immediately in your next site meeting. This is where keeping copies of every RFI and answer protects you—you have proof of what was approved.

    Should I write an RFI for minor questions or just ask the contractor in person?

    For anything that affects scope, dimensions, materials, or sequencing, write an RFI. A casual conversation about a detail has no record. If the contractor’s answer is different from what the plans show, you have no proof. Written RFIs cost a few extra days but they protect you. For truly minor questions—like “What time will the crew arrive”—a conversation is fine.

    Who pays for work that an RFI clarifies?

    If the RFI clarifies what was already in the contract and scope, the contractor does the work under the original contract. If the RFI answer changes the scope or cost, a change order follows. This is why the RFI answer matters—it determines whether the work is included or requires additional payment.

top