RFI Logging and Tracking SOP
Use this when: Questions to the design team are getting lost, or nobody can say which ones are still open.
Owner: [project coordinator] 1. Log each RFI before sending it: number, date, drawing or spec reference, question, and who asked. 2. Write one question per RFI. Attach photos or markups. 3. Propose a solution if you have one, and mark any cost or schedule impact. 4. Set a required response date based on the work it affects. 5. Send it through the agreed channel, and copy the people the contract requires. 6. Review open RFIs at the weekly site meeting. Chase any that are overdue. 7. When answered, tell the crew and update the drawings on site. 8. If the answer changes cost or schedule, raise a change notice right away. 9. Close the RFI in the log, and file the response.
Before you use this: Your contract may set notice periods for changes and delays, so check them. A late notice can cost you the claim.
Fill in the items in square brackets and adapt this to your business. It's a starting point, not legal or professional advice.
More for construction
Bid Follow-Up Call Script
You've submitted a bid and want to learn where it stands without sounding pushy.
AI Prompt to Pull Requirements from Bid Documents
You need a first-pass checklist from a large tender package, for an estimator to verify.
More sops
New Listing Launch SOP
A listing agreement is signed and you need every launch to happen the same way.
Service Call Close-Out SOP for Technicians
Job notes, photos and follow-ups vary from one technician to the next.
Leak Inspection Report SOP
Reports differ by technician, and managers or insurers keep coming back with questions.
Check your key numbers with the Operator ScorecardSAZ's construction practice