A claim is often thought to begin with an event — a delay, an instruction, a change in scope, or a disruption to progress. In practice, it begins earlier than that. It begins with whether anyone recorded, at the time, what actually happened.
Most claims that fail do not fail because the underlying entitlement was weak. They fail because the documentation needed to prove it was never created — or was created too late, after memory had already started replacing fact.
THE GAP BETWEEN WHAT HAPPENED AND WHAT CAN BE PROVEN
An event occurs on a project. Work is disrupted, an instruction changes scope, a delay begins to affect completion. At the time, everyone involved understands roughly what happened — the sequence, the cause, the immediate impact. That understanding feels solid. It doesn’t feel like something that needs to be written down, because it’s obvious to everyone present.
Months later, when the claim is actually prepared, that shared understanding has usually dissolved. People have moved to other projects. Memories have blurred into a general impression rather than a specific sequence of events. The site diary has a one-line entry where a detailed record was needed. The photographs that would have shown site conditions were never taken, or were taken without a date, a location, or a clear purpose.
What remains is not the event. It’s a reconstruction of the event, built from fragments and assumptions — prepared by someone under commercial pressure to make the strongest case possible, which is exactly the condition under which reconstructed memory becomes least reliable.
ENTITLEMENT IS RARELY THE ACTUAL PROBLEM
In many cases, the contractual mechanism is sufficiently clear. The dispute is not whether the contract contains an entitlement mechanism, but whether the facts support its application.
Was the instruction given on the date claimed? Was the delay caused by the event alleged, or by something else happening in parallel? Was the additional work genuinely outside scope, or could it be read as already included? Did the disruption affect the critical path, or a sequence with float?
These are factual questions. They cannot be resolved by a well-written narrative alone. They are resolved by records that were created at the time — correspondence, site diaries, progress photographs, meeting minutes, programme updates — that show what was actually happening, independent of how anyone later chooses to characterise it.
Contemporaneous records don’t need to be persuasive. They need to exist.
WHY CONTEMPORANEOUS RECORDS ARE DIFFERENT FROM RECONSTRUCTED ONES
A record made at the time of an event carries a kind of credibility that no later account can replicate — not because it’s better written, but because it was created before anyone had a commercial interest in how it would be read.
A site diary entry written the day an instruction was issued reflects what was understood in that moment, without the benefit — or the distortion — of hindsight. A progress photograph taken because it was routine practice, not because someone anticipated a future dispute, shows conditions as they actually were.
Reconstructed records carry the opposite problem. They are created specifically because a claim is being prepared, which means they are shaped, consciously or not, by what the claim needs to show. A tribunal or an opposing party reading them knows this — and weighs them accordingly.
The distinction isn’t about honesty. It’s about the structural difference between a record created as a byproduct of doing the work, and a record created as a byproduct of arguing about the work.
Documentation is not a claims activity. It is a contract administration activity. Claims simply reveal the quality of the administration that has already taken place.
HOW THE GAP USUALLY FORMS
The gap rarely appears because people ignore documentation. More often, it appears because documenting today’s event never feels as urgent as solving today’s problem.
The absence of contemporaneous records is rarely a deliberate choice. It develops through a familiar sequence of reasonable-sounding decisions. Recording the event in detail feels unnecessary because everyone present already understands what happened. Raising a formal record feels like it might signal distrust, or create friction in a relationship that is otherwise working. There’s an assumption that if a dispute ever arises, the facts can be reconstructed later from memory, from emails, from whoever is still around.
Each of these assumptions is individually plausible. Together, they produce a project with no reliable record of the events most likely to matter later — because the moments most likely to become disputed are, by definition, the moments where different parties have different interests in how the story is told.
WHAT DISCIPLINED DOCUMENTATION ACTUALLY REQUIRES
Strong claims documentation isn’t about generating paperwork for its own sake. It’s about capturing specific, verifiable facts at the moment they occur, in a form that will still be usable months or years later.
This means site diaries that record what actually happened each day, not just that work continued. It means instructions confirmed in writing close to the time they were given, even when they arrived verbally. It means photographs that are dated, located, and taken with enough regularity to show a genuine record of conditions, not just isolated snapshots. It means programme updates that reflect actual progress and actual delay, not an optimistic projection maintained to avoid difficult conversations.
It also means capturing context, not just events — who was present, what was discussed, what was agreed, and what remained open. A record that shows only that a meeting happened is far less useful than one that shows what was decided in it. And it means preserving version history — of programmes, drawings, instructions and key correspondence — so that the evolution of the project can still be understood months or even years later.
THE PRACTICAL LESSON
The strength of a claim is usually determined long before anyone starts preparing it — at the moment the underlying event occurred, and in the weeks that followed, when the decision to document it properly or to let it pass unrecorded was actually made.
By the time a claim is being drafted, the opportunity to create contemporaneous evidence has already closed. What remains is the work of finding whatever records do exist, and building the strongest possible account around them — which is a fundamentally weaker position than having built the record as the project went along.
Claims are not won by good arguments made later. They are won by good records made at the time.
How ACC TRUST Supports Stronger Claims
ACC TRUST supports contractors, subcontractors and project owners in strengthening the contemporaneous record on live projects, including reviewing current site diary, correspondence and reporting practice against what claims actually require, establishing structured processes for recording instructions, delays and disruption as they occur, developing photographic and progress-recording protocols that hold up under later scrutiny, identifying events on live projects that require immediate documentation before the opportunity closes, reviewing existing records to assess the strength of a potential claim before it is prepared, and supporting the preparation of claims where the underlying documentation is incomplete.
For support with claims documentation, notice management or contemporaneous record-keeping:
Explore ACC TRUST services:
→ https://acctrust.ro/en/services
Discuss a specific project:
→ office@acctrust.ro
About ACC Trust Insights
ACC Trust Insights is the knowledge centre for Commercial & Contract Governance, Project Delivery and Risk Management in complex projects. Each article combines practical project experience with structured analysis of commercial, contractual and governance issues affecting construction, infrastructure and energy projects.
Explore ACC Trust Insights:
→ https://insights.acctrust.ro
ACC TRUST
Commercial & Contract Governance Advisory
Property · Infrastructure · Energy
office@acctrust.ro