Two versions of the same problem
A long lead item that has not been ordered is, in month four, a procurement decision with several answers: order it, substitute it, or resequence around it. The same item, discovered missing in month eleven, is a delay with a cost attached and a dispute about who caused it.
Nothing about the underlying fact changed. What changed is that the options closed while nobody was looking.
That is what notice provisions exist to prevent. They are not administrative courtesy and they are not a paper trail for lawyers. They are a mechanism for getting information to the people who can still act on it.
The provision has a second function that gets less attention. It fixes a date. Once a matter has been notified, both parties know when it became known, which removes an entire category of later argument about whether somebody sat on information while the cost grew.
Why they get ignored
Raising a problem feels like reporting failure, and on projects where problems are received badly, people stop raising them. That is a management issue rather than a contractual one, and it is the root of most late notice.
There is also a practical disincentive. A contractor who gives notice of every possible issue is accused of building a claim. One who gives none is accused of concealment. The line between those is a matter of judgement and it is drawn differently by different commercial teams.
The developer’s interest is unambiguous, though: more notice, earlier. Information you did not want is still information you can use.
What the contract usually requires
Most standard forms require notice of matters likely to affect time or cost, within a stated period of the party becoming aware, and in a stated form. The consequences of failing to give it vary from a reduction in what can be recovered to the loss of entitlement altogether. [VERIFY: the notice provisions, periods and consequences in the contract edition and amendments in use.]
Bespoke amendments frequently tighten those provisions, sometimes considerably, and a developer whose solicitor has added condition precedent wording should understand what it does. It strengthens the employer’s position and it also means a genuine entitlement can be lost on a technicality, which is not always the outcome anybody wanted.
The practical reading is that both parties are better served by notice being given than by either side winning an argument about whether it was.
Making it work in practice
Three things help. A standing item on the monthly agenda where open risks are listed and either closed or carried, so raising something is routine rather than an event. A single register both parties can see. And a response discipline, meaning that notice given gets an answer, because notices that disappear stop being sent.
The register is the important one. Where each party keeps its own list, the first time they are compared is at the final account, and they will not agree.
None of this requires additional meetings. It requires the existing meeting to produce a written output that both parties accept.
What early warning is worth
The value is not in the notice, it is in the decision it enables. A design coordination problem raised at the right moment gets resolved by the designers. Raised late it gets resolved on site, at a different order of cost, by people improvising.
It also changes the character of the eventual account. Items that were flagged, discussed and decided are hard to dispute later, because the record shows both parties dealing with them at the time.
That is why we treat the risk register as a commercial document rather than a project management one, and why it belongs alongside the cost report rather than in a separate pack.
What this means for you
Read the notice provisions in your contract once, at the start, and make sure whoever runs the site meeting knows what they say. Most breaches are ignorance rather than tactics.
Then make it easy to raise things. A project where bad news travels quickly is not a project with more problems. It is a project where the problems are still cheap.
Running that register and reconciling it monthly is part of cost control and variations, and where we hold the contractual authority it sits inside the employer’s agent appointment.
One habit is worth adopting regardless of what the contract says. Where something is raised verbally in a meeting and it might affect time or cost, somebody sends two lines confirming it the same day. That single note frequently turns out to be the document that settles the question, and it costs almost nothing to produce.