How to build a construction dispute chronology that is actually useful

Why a chronology matters

Construction projects generate large quantities of information. The legal problem is rarely the absence of documents; it is finding the small number that establish what happened, what the contract required and what consequence followed.

A chronology creates the bridge between project records and the legal/commercial issues. It is particularly useful for adjudication because the timetable makes late document organisation expensive and risky.

The eight columns to start with

1. Date and time. Use exact dates where possible and mark uncertain dates clearly.
2. Actor. Identify the party/person who issued the instruction, notice, programme or response.
3. Event. Describe the event neutrally in one sentence.
4. Source. Link to the email, notice, drawing, site record or programme that proves the event.
5. Contract clause. Identify the provision engaged, if known.
6. Significance. Explain why the event matters to entitlement, jurisdiction, valuation, delay or defects.
7. Time/quantum effect. Record any claimed or apparent effect without overstating causation.
8. Status. Note whether the event or its significance is agreed, disputed or unknown.

Build separate issue chronologies where necessary

A master chronology can become unusable on a large project. If the dispute concerns delay, create a delay chronology focused on programme events, notices and critical activities. If the dispute concerns payment notices, create a payment-cycle chronology showing due dates, notices, service and the final date for payment.

Those issue chronologies can later be combined or cross-referenced.

Do not turn argument into “fact”

A chronology should distinguish between the event and the party's interpretation. For example, “Architect issued Instruction 24” is an event; “Instruction 24 caused a 17-day critical delay” is an analytical conclusion that may require programme/expert support.

Keeping those layers separate makes the chronology more credible and helps identify where evidence is missing.

Use the chronology to expose missing evidence

If a row says “verbal instruction given on site” but there is no confirming email, drawing revision, diary entry or witness, that gap becomes visible. If a delay claim jumps from an event to a completion date without intermediate programme evidence, the chronology exposes the causation gap.

For adjudication: start earlier than you think

Once a Notice is served, the response period is short. A chronology built during the project or at the first sign of a dispute can therefore materially improve the quality of the later referral or response.