Task 1 · typically 60 min, a few times a week
Write and chase RFIs and submittals
Have AI draft RFIs, change orders and notices from your notes and photos
Give AI the issue, the drawing reference and a photo; it drafts a clear, properly worded RFI or change order description. You check facts and send.
- 1Note the issue, location, drawing or spec reference and what you need decided.
- 2Attach a photo if it helps.
- 3Use the prompt below in an approved AI assistant (or the AI built into your site app).
- 4Check every reference and number, then submit through your normal system.
Draft a [RFI / CHANGE ORDER DESCRIPTION / DELAY NOTICE] for [PROJECT]. Issue: [WHAT IS WRONG OR UNCLEAR]. Location: [LEVEL, GRID, ROOM]. Reference: [DRAWING / SPEC SECTION]. What we need: [DECISION OR APPROVAL]. Cost and time impact if known: [DETAILS]. Keep it factual and short, suggest one possible solution, and state the date we need an answer by: [DATE]. Do not invent references.
Tools: ChatGPT, Claude, Gemini or Microsoft Copilot · Procore, Autodesk Build, Fieldwire, Buildertrend or Raken
One more way to fix itHide the other fixes
Run RFIs, change orders and pay apps through the project software's workflows
Procore, Autodesk Build and Buildertrend track who owes what, send reminders, collect e-signatures and build pay apps from the schedule of values. You stop chasing by email and rebuilding spreadsheets.
- 1Check which of these modules your company already pays for: RFIs, submittals, change events, invoicing.
- 2Set up ball-in-court and due-date reminders.
- 3Use e-signature on change orders so they get signed on a phone.
- 4Build pay apps from the schedule of values in the system instead of a separate spreadsheet.
Tools: Procore · Autodesk Build · Buildertrend · Siteline or GCPay for pay apps