The invisible teammate: Solving the contract risks nobody is monitoring on site
Laura Earnshaw
Business Development Director
NEC4 Accredited Project Manager
Several months into a project, a compensation event lands and the site team is certain the issue was raised with the project manager back in spring. There was a discussion, there may have been an email – but nobody can find it.
The claim is not weak because the contractor was wrong, but it’s weak because the record doesn’t exist.
Not only can these contract risks creep up and hurt main contractors but they can lead into more large-scale and dramatic disputes. A slow issue, built out of conversations that were never written down and notices that were raised a fortnight too late, can often create the most difficult outcomes.
Why good teams still miss things
Contract administration is rarely anyone’s only job.
The project manager is running a programme, the quantity surveyor is chasing valuations and the site manager is dealing with whatever arrived that morning. The NEC4 clock keeps running throughout all of it and the programme passes very quickly when nobody owns the diary.
Add a supply chain of dozens of subcontractors, each with their own notices and their own idea of what counts as an early warning.
A necessity for NEC
This is where contractors feel it most sharply because NEC is built on the assumption that both parties are managing the contract actively rather than reading it at the end.
The early warning mechanism only works if issues go on the register while there’s still time to do something about them. The compensation event process runs to fixed timescales, and under NEC4 a contractor who notifies late can find the entitlement gone entirely. Quotations, assessments and programme updates all carry their own timelines.
An NEC job punishes a team that treats contract administration as an afterthought.
Sypro builds those timescales in rather than leaving them to memory. The early warning register stays live and the deadline is visible so it can be addressed before it becomes a problem. The same applies to JCT, FIDIC and bespoke forms, each with their own workflows.
You spot a risk before it becomes a dispute?
Early warnings only work if they’re raised early. That sounds obvious until you’re the one deciding whether a two-day delay to a delivery is worth a formal notice.
Sypro tracks every contractual obligation against its deadline and flags the moment something drifts. The commercial lead sees the drift while it’s still a scheduling problem, rather than after it’s become a compensation event with a contested start date.
Do you know what’s happening across your whole supply chain?
Subcontractor visibility is where most contractor risk actually lives.
If a package contractor raises an issue on their own system, or in a WhatsApp group, or not at all – it reaches you when it’s already expensive. Real-time visibility across every workstream means nothing happens in the dark, and that your own notices to the client are based on what’s happening rather than what you were told last Thursday.
Could you evidence every conversation if it went to adjudication?
A fully auditable, searchable record of every communication is worth very little on the day you create it and worth an enormous amount the day you need it. Contractors who win adjudications are rarely the ones with the better argument. They’re the ones who can produce the correspondence, in sequence, without multiple people spending a week in an email archive.
What story does the project data tell?
Most contractors have the data but very few have the time and resource to pull it into a shape that supports a decision.
Real-time insight across live projects shows where notices are running late, where there is the most change and which project managers are carrying more risk than the programme suggests. That’s useful at project level and across a framework, providing the knowledge to help you price the next scheme effectively.
The invisible teammate
There’s no notification celebrating the dispute that didn’t happen and no line on the final account for the compensation event that got resolved at week three instead of month nine. The value shows up as absence. That’s what an invisible teammate looks like: Quietly reliable, super consistent and usually only noticed when it isn’t there.
So what’s it actually worth?
One avoided compensation event dispute, or one final account that closes two months earlier, will typically cover the cost of the software across a whole programme. That’s before the hours your project team stops losing to administration.
In practical terms, it depends on your portfolio, your contract forms and how much change your projects carry. To help show how much Sypro could save, check out our handy ROI calculator.
Meet the author Laura Earnshaw
Business Development Director