Site & field
Run the site day
Close the day out properly: record the diary, book the labour and plant hours, upload the p…
4 steps9 minOpen
Cases / Site & field
Site & field
Answer an RFI
Turn a question from the working face into a tracked request, drive it to the party who owns the answer, and file the response so it becomes part of the record.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
1
Raise the request
RFIsOpen the RFI with the actual question, the location and drawing reference it affects, and a needed-by date set from when the crew reaches that work, not an arbitrary week away.
Why: A woolly question buys a woolly answer and a week of delay. A tight RFI carrying a real date is also what lets a slow reply be tied back to lost time if it comes to that.
InSite questionDrawing referenceOutLogged RFINeeded-by date
2
Route and chase it
CorrespondenceRoute it to the designer or consultant who owns the response and keep the correspondence in one thread, with the open item and its due date sitting where everyone can see the clock.
Why: RFIs die quietly at the bottom of an inbox. Keeping the routing, the reminders and the reply in a single visible trail is what keeps the answer moving and the history defensible.
InOpen RFIResponsible partyOutCorrespondence threadResponse received
3
File the answer
DocumentsAttach the answer and any superseded or revised drawing to the project files, link it back to the affected work, and close the RFI so the loop is shut.
Why: An answer buried in a single inbox helps nobody at the trowel. A filed, closed RFI is what stops the same question being asked again next month by the next trade.
InRFI responseRevised drawingOutFiled answerClosed RFI
Modules in this playbook
3 / 184 platform modules
