How to Write an RFI Owners Actually Answer

A Request for Information exists to resolve a genuine ambiguity or conflict in the contract documents, not to cover yourself, not to negotiate scope through the back door. Owners' reps and architects can tell the difference immediately, and a sloppy RFI gets a slow, vague answer. Here's how to write one that doesn't.

Start with the specific conflict, not a general question

Bad: "Please clarify the door hardware for the second floor."

Good: "Sheet A-201 detail 4 calls for a panic bar exit device on door 214, but the hardware schedule on A-601 lists a standard lever set for the same door number. Which governs?"

The second version tells the recipient exactly what to look at and exactly what decision they need to make. The first one requires them to go figure out what you're actually asking.

Reference the exact documents

Sheet number, detail number, spec section. If there's a discrepancy between two documents, cite both. This isn't bureaucratic box-checking. It's what lets the architect actually locate the conflict without a phone call.

State the cost and schedule impact, if there is one

If the answer could affect price or schedule, say so explicitly and give a date by which you need the answer to avoid delay. "No response needed by [date] means we proceed per [assumption]" is a legitimate and common pattern. It puts a deadline on the response without being adversarial about it, and it protects you if the RFI goes unanswered.

One question per RFI

Bundling three unrelated questions into one RFI because it's "one email either way" guarantees a partial or delayed response. Whoever's answering has to loop in three different people, and the whole thing waits on the slowest one. Separate RFIs move independently and close independently.

Attach what you have, don't make them ask for it

Photos, markups, shop drawing excerpts, whatever's relevant to understanding the conflict. An RFI that requires a follow-up email just to get context everyone assumed was obvious burns a cycle you didn't need to burn.

Track ball-in-court, not just "sent"

The most common way RFIs actually cause delay isn't a bad answer. It's an RFI that sat unanswered because nobody was tracking whose court it was in. A due date with an actual alert, not a spreadsheet column nobody checks, is the difference between "closed in four days" and "closed in four weeks after someone finally noticed."

---

Groundwork's RFI module tracks ball-in-court automatically, links every RFI to the drawings and spec sections it references, and alerts before something goes overdue. See it in the product overview.