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
Track a design change through to the site record
Follow a design change from the drawing that carries it, through the site instruction, to the record that proves the right version was actually built.
How it works, step by step
3 steps across the platform - what you do at each one, and why it matters.
1
Issue the revised drawing
DocumentsRegister the revised drawing carrying the design change, mark the previous version superseded and note plainly what moved and why.
Why: A change that only exists as a verbal instruction on site has no paper trail behind it if the cost or the time is ever questioned.
InDesign changePrevious drawing versionOutRegistered drawing revisionSuperseded version marked
2
Log the site instruction
Change ordersLog the instruction that authorises the change on site, tied to the drawing revision that carries it, with the likely cost and time impact noted.
Why: Tying the instruction to the exact revision is what stops a dispute later over which version of the change was actually agreed.
InDrawing revisionChanged work scopeOutLogged site instructionCost & time impact
3
Verify it was built as changed
InspectionsInspect the affected work against the revised drawing and record that what went in matches the change, not the superseded detail.
Why: A change is only real once it is confirmed built. Verifying it on site is what closes the loop between the drawing, the instruction and the finished work.
InSite instructionRevised drawingAffected workOutVerified inspection recordAs-built confirmation
Modules in this playbook
3 / 184 platform modules
