Build a delay and disruption claim with evidence

Open a claim against the contract, citing the specific clause that gives the entitlement and the event that triggered it, with the dates and notice requirements set out.

Why: A claim with no clause behind it is just a complaint. Anchoring it to the right provision, and to the notice the contract demands, is what makes it an entitlement the other side has to answer.

Pull the diary entries, labour and plant returns and photos that show the event happened, when it happened, and how it stopped or slowed the work on the ground.

Why: Delay argued from memory gets argued down. Contemporaneous site records are the difference between a claim that gets paid and an assertion the other side simply denies.

Tie in the changes and instructions that drove the delay, showing the chain from the event through the affected activities to the programme slip.

Why: A big number with nothing behind it invites a fight. Linking each day of delay back to the change that caused it is what turns a round figure into a substantiated cause and effect.

Pull the clause, the records and the change chain into one claim document that sets out the narrative, the entitlement and the time and money being sought.

Why: A claim scattered across emails and folders never gets read, let alone paid. One assembled, evidenced narrative is what a client, an adjudicator or a court can actually assess and agree.