Long projects create
long commercial memories.
Programs run for years. Scope moves, notice clocks run, and the people who agreed the change have moved on long before the final account.
Where it bites
on a civil or infrastructure project.
Three places the commercial record slips on this kind of job, and the page that goes deeper on each.
Time bars are written into the contract years before anyone needs them.
Read moreThe proof for a change agreed in year one sits with people who left in year two.
Read moreThe final account is where a long program's loose ends are counted.
Read moreOne clause.
One clock.
From a public 2026 bid package: the claim notice that waives the claim if it is late, with the trigger and the cut-off cited to the page.
- Day 0Event, or first recognition of the condition§50-17 · Whichever comes first starts the clockTriggerTrigger
- Before workWritten notice before beginning the claimed work§50-17 · "in all cases"Notice requiredNotice required
- Day 10Written notice of intention to claim, to the Engineer§50-17 · Within ten (10) calendar daysDeadlineDeadline
- Work doneUpdate the written claim within 5 calendar days§50-17 · Failure to do so is a waiverDeadlineDeadline
- CloseoutNo differing-site-conditions request after Substantial Completion or final payment§50-17 · Whichever comes firstCut-offCut-off
What your team should be able to see.
- 01Every notice requirement, with its trigger
What starts each clock, cited to the clause, before the event happens.
- 02Each change tied to what it amended
The clause, the replacement and the document it came from.
- 03Evidence filed against a stated test
What would prove each requirement, written down while the job is live.
- 04Closeout conditions known from day one
Not discovered in the last month of a five-year program.
What teams run into on a civil or infrastructure project.
The pressure is familiar. The details are what decide whether the record holds up at final account.
- Programs that run for years across phased handovers
- Notice clauses with strict time bars
- Differing site conditions
- Directed work and quantity movement
- Layers of subcontractors between you and the work
- A final account argued from records nobody kept together
Common questions
What commercial risks are common on civil and infrastructure projects?
Long programs, strict notice time bars, differing site conditions, directed work and quantity movement, and final accounts argued from records nobody kept together.
Does Halozen review civil and infrastructure contracts?
Yes. Halozen reads the contract and project documents for civil and infrastructure work and lists every requirement, notice clock and payment term, cited to clause and page.
Show us the project
that’s giving you trouble.
Scope and fee agreed up front. Findings in two weeks. NDA first.
No implementation. Start with the records you already have.