Chapter 06
Building the claim file
How to assemble a claim file that survives external review: a numbered evidence index, a clear narrative, a defensible chain of custody, and a working definition of when the file is ready to release.
01
The numbered evidence index
A claim file with a numbered evidence index is qualitatively different from a claim file without one. The reviewer can move directly to the item being discussed. The narrative references the index. The cross-checks become navigable. Building the index is the discipline of taking each piece of evidence — clip, walk, weather record, programme extract, correspondence, certification, instruction — and giving it a stable reference. The reference does not change once it is assigned, even when items are added later; new items take new numbers rather than displacing the existing sequence. The index should record for each item the source, the capture date, the export date, the export operator, the file format, and the file hash. The index is a working document that grows through the life of the claim; it does not appear in finished form on the day the claim is submitted. The file is judged partly on this discipline because the discipline is what an external reviewer sees first. A reviewer who opens a file and finds a clean index forms a different first impression than the reviewer who finds a folder of files with timestamped names. The first impression is not determinative, but it sets the tone of the assessment.
02
The narrative
The narrative is the document that walks the reviewer from the event to the milestone. It is short — usually under ten pages — and structured around the four parts of a delay claim: event, activity, path, milestone. Each assertion is referenced to the index, with the reference inline rather than in a footnote so the reviewer can move from claim text to evidence in a single step. The narrative does not try to win the argument by force of language; it tries to make the reviewer agree because the references hold up. A narrative that runs longer than ten pages usually contains weaker assertions hiding among stronger ones. The discipline of writing short is the discipline of holding the strongest version of the case rather than every version. Where the claim involves multiple events, each event has its own narrative segment with its own four parts. The temptation to bundle is the temptation to weaken. A claim that bundles three events into one narrative invites the reviewer to reject the package on the weakest event; a claim that separates the three lets the reviewer accept the strong two and reject the third without affecting the rest. The structure is not cosmetic; it is the architecture of the assessment outcome.
03
The defensible chain
Each item in the index has a chain of custody from capture to inclusion in the file. The system records who captured, who exported, and how the item reached the file. The custody report is included with the file, not held separately. When the reviewer opens an item, the chain is visible. When the reviewer asks how the item arrived, the answer is on the page rather than in a follow-up email. The work to make this visible is small at the time and large at the moment of challenge. The chain should also be defensible against a hostile examination. A reviewer who is sympathetic will accept a chain with one or two informal links; a reviewer who is hostile will not. The discipline of building the chain as if a hostile reviewer will see it is the discipline that produces a chain that survives across both audiences. Practitioners who have given evidence in arbitration or court report that the questions almost always concentrate on the chain rather than on the underlying observation. The clip itself is rarely contested; the path the clip took to reach the bundle is. The project that has documented the path has answered most of the cross-examination before it begins.
04
Knowing when the file is ready
A claim file is never finished; it is released. The decision to release is a commercial decision that the team has to make against incomplete information. The working definition of ready that holds up across most claims has four conditions. The four parts of the claim are evidenced and indexed. The narrative is under ten pages and references the index inline. The chain of custody is intact for every cited item. The retention policy on the source evidence extends past the expected dispute window. When all four conditions are met, the file can be released; when any one of them is not, the release should wait until it is. The fifth informal condition that experienced commercial managers add is that the team has read the file in the form an opposing party would. A file that is read internally by the team that wrote it tends to feel stronger than it is. The team that has the file read by a colleague who was not involved in the underlying events catches the soft assertions before the opposing party does. The colleague´s questions are the questions the opposing party will ask. Answering them in advance is cheaper than answering them in adjudication. The file that has been pressure-tested before release is the file that holds.
Practice
01. Open the most recent claim file on your project. Apply the four ready conditions to it and identify which are met and which are not.
Look for: A strong response names each of the four conditions, identifies the gap on any unmet condition, and proposes a specific action to close the gap before release.
02. Ask a colleague who was not involved in the underlying events to read the narrative and list the three softest assertions. Note how you would harden each.
Look for: A strong response cites the three soft assertions in the colleague´s words, names the additional evidence or rephrasing that would harden each, and confirms whether the change has been incorporated.
Checkpoint
For a current or recent claim, can you produce a numbered evidence index, a ten-page narrative, and a custody report in under a working day?
Recommended reading