RFIs for Small GCs: Ask the Question Before You Build It Wrong

The cheapest question you'll ever ask

Every experienced contractor has a rework story: built the wall, hung the door, set the tile, then found out the client meant something different, and had to tear it out and do it again on their own dime. Almost every one of those stories starts with an assumption that a quick question would have settled.

That's all an RFI is: asking the question instead of assuming the answer. It costs two minutes. The rework it prevents can cost a day of labor, a pile of wasted material, and a frustrated client. The math is not close.

What an RFI looks like on a small job

Forget the formal commercial paperwork. On a residential job, an RFI is simply a clear, written question with the answer captured in writing. It might be a text, an email, or a note in your job software:

> "The plan shows the vanity centered on the wall, but the window's off-center. Do you want it centered on the wall or centered under the window? Reply and I'll proceed."

What makes it an RFI rather than just chatter is two things: it's specific (a real decision, clearly framed), and it's documented (the question and the answer both exist in writing). That's the whole discipline.

Why the habit pays off

It prevents rework. The obvious win. A question asked before the work is a five-minute pause; the same issue found after is a tear-out. Ask before you build anything you're unsure about: placement, orientation, finish, dimension.

It surfaces decisions the client owes you. Half of RFIs are really "I need you to decide something before I can proceed." Framing it as a clear question, with the note that work waits on the answer, pushes the client to decide promptly, which keeps your schedule moving. A slow answer is now visibly *their* delay, which your daily log records.

It protects you when answers change. Clients change their minds and, honestly, misremember what they said. When you have a written question and a written answer, "that's not what I wanted" becomes "here's your reply approving exactly this." The documented RFI is part of the broader paper trail that protects you.

It coordinates the trades. Many RFIs come from your subs: the electrician needs to know outlet heights, the tile setter needs the layout. Routing those questions to the client and getting a clear answer before the sub proceeds is a core part of managing subcontractors and prevents the wrong thing getting built.

When to raise one

You don't need an RFI for every decision; that's just annoying. Raise one when:

• The plans, selections, or instructions are ambiguous or contradictory
• A field condition doesn't match what was drawn or assumed
• A decision hasn't been made and the work can't proceed without it
• A sub asks you something you can't answer without the client
• You're about to do something irreversible and you're not 100% sure

The test: *if I guess wrong here, is it expensive to undo?* If yes, ask first.

Keep the questions and answers with the job

The value of an RFI is entirely in the documentation. A question asked and answered verbally, then forgotten, protects no one. The habit only works if the question and its answer are captured and easy to find later, ideally tied to the job so you can point to it months down the road.

That's the practical failure mode: RFIs scattered across text threads and half-remembered conversations. When a client questions a decision six weeks later, you need to produce the answer in seconds, not dig through your phone. Keeping questions, answers, and decisions attached to the job is what makes the RFI habit actually protective. TradesMetrics keeps job communication and records together, so the answer that covers you is where you can find it.

Where to go next

Pair this with managing subcontractors and the daily log that saves you. For the full picture, see the field ops hub and the construction project management pillar.