Tracking owner-caused costs as they happen: a code per event from the day it starts
Owner-supplied pool equipment arrives without the control panel. The superintendent redirects the plumber and changes the crane booking. By Friday, the associated hours are mixed into general installation and nobody can reconstruct the event's cost clearly.
Open a traceable event code when the observed disruption begins, allocate the associated records to it and reconcile the amount regularly. Describe the owner-controlled input and its actual effect without treating the label as a liability decision. Keep observed facts, estimates and the recovery position distinct. The SCL Protocol supports linking cost records to events, but its UK guidance is subordinate to the applicable contract and law.
Keep the cost connected to the event
- Name the event factually. Use the input, location and start date, such as missing control-panel delivery, rather than a conclusion about blame. Have the project manager confirm the code and commercial review path. Preserve alternative explanations if responsibility is uncertain.
- Set the allocation boundary. Tell the foreman and coordinator which directly associated work, waiting or rearrangement belongs on the code. Keep unaffected planned installation on its normal code. Record shared-resource allocations on a stated basis instead of moving a whole crew's day.
- Attach contemporaneous support. Link timesheet entries, equipment records, delivery discrepancies, instructions and relevant report lines. Show what was planned, what occurred and the affected work. A photograph supports a condition or location; it does not calculate hours by itself.
- Reconcile the total weekly. Match charged hours and purchases to the event evidence, identify late records and separate estimates from posted cost. Check that the same charge is not also in a standby claim, replacement price or extended-overheads allowance.
- Maintain the notice path separately. Have the authorized project manager check and follow the actual contractual requirements as the event develops. A monthly cost summary should not become a reason to delay notice or to bypass the required recipient.
- Communicate the current position clearly. Give the owner the factual period, supported amount, unresolved assumptions and next update under the agreed process. Carry known cost in the forecast under the company's method while keeping proposed recovery identified as unresolved.
Common mistakes
- Moving all activity costs into the event code after a disagreement begins.
- Using the same invoice in several recovery totals.
- Reporting an internal charge rate as a contractually agreed billing rate.
Action list
Start the event folder
- Neutral event name and start date.
- Allocation boundary communicated.
- Source records linked to each charge.
- Posted cost and estimate distinguished.
- Overlaps checked.
- Notice and recovery reviewer identified.
Check your understanding
A delay is associated with an owner delivery, but another cause may also affect the work. Should every cost go to the owner event code?
