Assemble a delay evidence pack for qualified review

Identify the event, location, affected activities, relevant period and the decision sought. Is the team investigating a possible delay, preparing a notice, supporting an extension request or responding to a client's assessment? These tasks may need different records and deadlines under the actual contract.

Have the responsible commercial or legal specialist identify applicable notice and procedural requirements. Do not infer them from a generic template or this article. Record the relevant clause, source version, required action and authorised owner so administrative preparation does not miss a contract-specific step.

Keep the evidence scope wider than the preferred argument. A pack that includes only supportive emails may make it harder for a qualified reviewer to identify the actual cause and prepare a credible position.

In this fictional example, access is restricted from Monday through Wednesday. The contractor's equipment is unavailable on Tuesday and Wednesday. The chronology shows both events on their actual dates, linked to access records, daily logs and equipment evidence.

The observed periods span three calendar days, not five days obtained by adding three and two. Even three observed days are not automatically three days of delay to project completion. A qualified planner needs to assess the affected activities, logic, float, alternatives and contemporaneous programme position.

The commercial or legal reviewer then assesses the contract consequences using that analysis and the actual terms. The overlap must not be hidden simply because it complicates the claim. Record disputed facts and alternative interpretations explicitly rather than choosing the version that yields the largest number.

Retain the relevant approved baseline, contemporaneous updates, data dates, activity logic and supporting progress records. Identify who produced each version and whether it was submitted, reviewed or accepted for the relevant purpose. A programme file labelled approved needs its approval evidence.

Oracle's P6 baseline documentation describes snapshots used for comparison. That product capability does not establish contractual acceptance or determine the correct delay-analysis method. Qualified specialists select and apply the method appropriate to the facts and contract.

Do not modify historical programme files to make the event fit a later narrative. Work on controlled analysis copies, identify changes and preserve the originals. If an earlier update is missing or unreliable, state the limitation and its effect on the analysis.

For each event entry, record date and time where known, location, activity, description, source reference and whether the fact is agreed, reported or disputed. Distinguish an event date from the date an email described it. A later recollection may be useful but should not appear as a contemporaneous observation.

Link daily records, instructions, access logs, correspondence, photographs, resource records and relevant approvals. Procore's Daily Log documentation illustrates the types of manpower, equipment and productivity records that can support a chronology. Their evidential weight depends on the actual records and context.

Keep contradictions visible. If a daily log says the area was accessible while correspondence says it was restricted, assign the discrepancy for review. Do not silently choose one source or rewrite the chronology to remove the conflict.

Record what the team did to reduce or avoid the effect: resequencing proposals, alternative fronts, resource changes and requests for decisions. Preserve who proposed the action, whether it was approved, when it occurred and what evidence supports the result.

An alternative work front may matter to the schedule assessment, but its mere existence does not prove that it was usable. Check access, materials, approvals and resources. Equally, an assertion that no alternative existed needs evidence rather than repetition.

Separate actual mitigation from proposals that were never implemented. If a proposed measure carried cost, risk or contractual implications, record the decision and authority. The evidence pack should explain the operating choices without declaring their legal effect in advance.

The factual chronology answers what the records show. Schedule analysis assesses the effect on activities and milestones. Commercial and legal review considers the applicable contractual position. Combining these layers into one automatically generated narrative can make an inference look like an established fact.

The Works Manual, section 7.4.5, discusses delay categories and overlapping events within its public-works framework. It is useful background for why the distinctions matter, not a universal entitlement rule for private EPC contracts.

Use clear labels for facts, assumptions and specialist conclusions. Where a value or period is disputed, show the alternative and its source. A reviewer should be able to trace a conclusion back through the analysis to the underlying record without relying on the author's memory.

Provide an index, chronology, source register, programme inventory, notice register, mitigation records and a list of unresolved questions. Preserve original documents and use controlled copies for annotation. Avoid broad access to privileged or confidential material; the responsible advisers should direct its handling.

Test retrieval by asking a reviewer to follow the access event and the equipment failure independently. The pack is ready for assessment when both can be traced, contradictions are visible and missing evidence has an owner. It is not a promise that the proposed claim will succeed.

1. Define the event and contract-specific review question with the responsible specialists.
2. Assemble a chronology containing both supportive and adverse evidence.
3. Preserve programme versions, notices and mitigation records without rewriting history.
4. Route causation, concurrency and entitlement to qualified review before submitting a claim position.