M04.03
RFIs that get answers
A professional RFI is a scalpel. A bad one is a complaint.
- Write an RFI with one question and a proposed path
- Log dates so delay is visible
- Never hide an RFI in a 14-topic email
- 01Spot conflict
- 02One question + proposed path
- 03Need-by tied to sequence
- 04Send via contract chain
- 05Log dates
- 06Chase before idle
- 07File answer
- 08PCO if it costs money
Anatomy
Number, date, job, spec/sheet reference, the conflict in one short paragraph, a proposed interpretation, a clear question, and a needed-by date tied to the sequence. Attach a clouded drawing. Send through the GC's process, not around it, unless the contract says owner-direct.
Example (good)
RFI 014 — Sheet A-401 shows 6" integral cove at Room 12. Spec 09 67 00 3.4 calls 4" cove. Finish schedule says 'resinous base as spec.' Proposed: 6" integral cove at Room 12 to match the drawing, with a PCO if the spec governs at 4". Please confirm height and termination at the existing FRP.
- Not this
What do you want us to do about the floor?
ThisName the two documents that disagree and propose one path.
- Not this
CC the owner, architect, and twelve vendors to apply pressure.
ThisFollow the contract chain. Escalate with Eric if dates slip.
Takeaways
- One question per RFI.
- Show the conflict on the documents.
- The log proves delay when we need it.