Record the event once, then reuse it
Good project records should support operations, commercial administration and reporting without requiring three separate entries. A site event can begin in the diary, link to an instruction or delay, and then support a notice, variation, claim or forecast action.
The record should preserve the date, author, project location, affected work, people involved, supporting files and next action.
Use specific descriptions
Avoid entries such as “delay on site” or “extra work completed.” Record what happened, where, when it started, who directed or caused it, what resources were affected and what the immediate consequence was.
Specific records are easier for someone outside the event to understand months later.
Make photos evidentiary
A useful photo has context. Link it to the project, area, date, issue and description. Capture wide context and close detail where required. Photograph the condition before work, during the affected activity and after completion.
Do not rely on an unstructured phone gallery that must be searched after a dispute begins.
Connect correspondence and instruction
Link the email, RFI response, site instruction or meeting action to the same issue record. Record whether the direction is formal, whether clarification is required and whether a contractual notice or price is due.
This prevents the variation register from becoming a list with no clear source.
Create a minimum daily standard
Record labour by activity or work front, progress achieved, access, deliveries, instructions, delays, disruptions, visitors, quality events and photos. Keep the standard short enough to complete consistently.
Supervisors should capture facts. Project and commercial teams can then classify the impact and required action.
Review records while they are fresh
A weekly review should identify diary events without a commercial disposition, instructions without notices, photos without issue links and delays without programme assessment.
The best time to improve a weak record is the same week—not when the final claim is being prepared.
What happened, where and when did it happen, who was involved, what work or cost was affected, and what action followed?
Turn the guidance into a repeatable workflow
SubbieTRAC is designed to keep the tender baseline, project records and commercial actions connected so these controls can happen as part of normal work rather than through another disconnected register.