The Early Warning Habit: How Site Engineers Earn Commercial Credibility
Photo: The Builder, Public domain, via Wikimedia Commons
Commercial awareness is often described as if it begins at a desk, with a spreadsheet and a set of bills of quantities. On a live site it begins earlier. It begins when an early-career engineer notices that the ground is not as the drawing promised, that a service has appeared where none was shown, or that a delivery sequence has changed the order of work. Under NEC4, those observations may become compensation events. The engineer’s job is not to decide entitlement. It is to notice, record and escalate clearly enough that the commercial team can act while the facts are still fresh.
Why the site engineer matters to the commercial process
A quantity surveyor can price an event. They cannot invent a contemporaneous record of what the site looked like at 07:30, which plant was standing, or what the supervisor said when the trench was opened. That record comes from the site. NEC4 expects early warning and timely communication, and the site engineer is often the first person in the chain. In 2026, with UK infrastructure programmes under pressure to demonstrate value, that first link matters more than ever. Commercial awareness is not a separate skill reserved for the commercial manager. It is part of competent site practice.
Spot, record, escalate
Three verbs keep the role boundary clear.
Spot means noticing a change against the contract baseline: the accepted programme, the scope, the site information or a previous instruction. You do not need to memorise the contract to spot a difference. You need to know what was planned and what is happening.
Record means writing down facts, not conclusions. ‘At 08:15 on 4 November, an unmapped 150 mm duct was found at chainage 2+340 during excavation for the north drainage run. Work in the trench stopped. Supervisor J. Patel informed. Photographs 2026-11-04-001 to 006 taken. Trench dimensions 12 m by 0.9 m by 1.2 m.’ That is useful. ‘The client has caused a delay’ is not.
Escalate means telling the right person through the right route, without delay and without drama. That may be the site manager, the project manager or the commercial team, depending on your organisation. The key is to send the record, not just the concern.
A one-page event log
Keep a single-page log for your section or package. It is not a formal contract record in itself, but it prevents events from living only in your memory or your phone. Review it at the end of each shift and send relevant lines to the commercial team weekly, or sooner if the event is live.
| Date and time | Location / chainage | What was observed (fact only) | Immediate action | People informed | Records attached | Follow-up owner and date |
|---|---|---|---|---|---|---|
| 04/11/2026 08:15 | North drainage, 2+340 | Unmapped 150 mm duct found during excavation | Work stopped in trench; area isolated | Supervisor; site manager | Photos 001–006; diary entry; sketch | Commercial team, 06/11/2026 |
Add a short note on programme effect only if you can state it factually. ‘Excavation in this run suspended for four hours’ is a fact. ‘Four weeks of delay to completion’ is a conclusion for others to reach.
Raising it with the commercial team
Use the project’s formal route first. Then follow up with a short, structured conversation. A script keeps you professional and prevents the discussion from becoming a complaint.
‘Morning [name]. I want to flag a potential compensation event on [package or area]. At [time] on [date] we observed [fact]. I have recorded it in the site diary, taken [photos or measurements] and issued [RFI or early warning] reference [number]. My concern is [programme, resource or sequence] impact. I am not asking you to accept entitlement now. I would like your advice on whether we need an early warning meeting and what further records you need. Can we agree a follow-up by [date]?’
That last question matters. It turns an alert into a tracked action. It also protects you: you have raised the issue, provided evidence and asked for guidance. You have not overstepped.
Common mistakes that weaken your position
- Deciding entitlement. Telling a subcontractor or colleague that ‘this is definitely a compensation event’ creates expectations you cannot satisfy.
- Waiting for certainty. Records made a week later are weaker than records made an hour later.
- Mixing fact and opinion. Keep the diary factual; put analysis in a separate note for the commercial team.
- Sending only a photograph. A photo without location, time, scale and context is easy to challenge.
- Bypassing the line manager. Escalation should follow the project route, not social media or a side message.
- Forgetting to close the loop. An event log without follow-up dates becomes a diary of unresolved issues.
Chartership evidence
Commercial awareness is credible evidence for professional review. ICE attributes expect engineers to understand the commercial and contractual context of their work, communicate with different disciplines and exercise professional judgement. A well-kept event log shows exactly that: you noticed a change, recorded it accurately, communicated it appropriately and understood why it mattered. It is stronger evidence than a claim to be ‘commercially aware’ because it shows a habit.
A habit, not a hat
You do not need to become a quantity surveyor. You need to be the engineer who makes the commercial team’s job possible. Keep the log short, the language factual and the escalation timely. Over a year, that habit will do two things: it will improve the project’s position, and it will give you a body of evidence that reads like a site engineer ready for the next step.
