Delay Analyst: Mastering Forensic Scheduling & Claims

Most planners spend their careers trying to stop projects from running late. A delay analyst spends theirs explaining, after the fact, exactly why a project ran late, who was responsible, and how much time and money that responsibility is worth. It is one of the most specialised and best‑paid corners of project controls, and it sits at an unusual intersection: part scheduling expert, part detective, part expert witness. When a dispute over a major project reaches the tens of millions, the delay analyst’s report is often the single document that decides who pays. That is why the role is demanding and the bar is high.

A delay analysis that is technically sloppy, methodologically inconsistent, or visibly partisan gets torn apart by the other side’s expert — and a torn-apart analysis can lose a winnable claim. This article maps how to get there from a planning background: the recognised methods you must master, the skills that separate a credible analyst from a planner with opinions, the certifications worth holding, and the experience that earns you a seat at the table.

What a delay analyst actually does: Strip away the jargon and the job is this: prove, to an evidentiary standard, that a specific event caused a specific amount of delay to the project's completion — and that the responsibility for that event sits with one party rather than another. The output is usually a formal delay report that will be scrutinised by opposing experts, lawyers, and possibly an adjudicator, arbitrator or court. Everything about how you work is shaped by that scrutiny. Crucially, a delay analyst must be able to demonstrate cause and effect, not merely correlation.

The methods you must master: There is no single “correct” method of delay analysis; there are several recognised techniques, each with strengths, weaknesses, data requirements and appropriate use cases. A credible analyst knows all of them, can justify why they chose the one they used, and understands the criticisms the other side will level at it. The SCL Delay and Disruption Protocol is essential reading here. The four you must understand deeply are below.

• Time Impact Analysis (TIA): Insert delay events into the schedule at the point they occurred and measure the push. Best used when you have a good baseline and contemporaneous updates. Prospective; sensitive to schedule quality.
• As‑Planned vs As‑Built: Compare the planned programme directly against what actually happened. Records are good but the schedule logic is weak. Doesn’t isolate causation on its own.
• Windows / Time‑Slice: Divide the project into periods and analyse delay within each window. Appropriate for long projects with multiple, shifting delays. Data‑hungry and labour‑intensive.
• Collapsed As‑Built: Remove delay events from the as‑built to model what would have happened. Strong as‑built records, weak baseline. “But‑for” logic is contestable.

These four core delay‑analysis methods are essential to master; knowing which to use, and why, is itself a senior skill.

Why method choice is a battleground: In a real dispute, the choice of method is rarely neutral — different methods can produce materially different answers from the same facts, which is exactly why the opposing expert will attack your choice before they attack your numbers. The credible analyst selects the method that best fits the available records, documents why, and is honest about its limits. An analyst who picks the method that gives the biggest number, rather than the one the evidence supports, loses under cross‑examination.

The skills that separate credible analysts: A delay analyst needs everything a senior planner has — and then a second, distinct layer on top. The planning skills are necessary but nowhere near sufficient. What actually makes an analyst credible when their work is challenged is the combination below.

• Forensic rigour: every conclusion traced to evidence; no gaps an opposing expert can exploit.
• Contract and entitlement literacy: understanding extension‑of‑time clauses, notice requirements, and concurrency — delay analysis lives inside contract law.
• Records discipline: knowing what contemporaneous evidence exists, what it proves, and where the gaps are.
• Clear written argument: a report a non‑technical adjudicator can follow and believe. Brilliance nobody can follow is worthless.
• Independence and objectivity: even when engaged by one party, the credible analyst’s opinion must be defensible, not partisan.

Planner vs delay analyst — the gap to close: If you are a senior planner, you already hold one axis of this role — the scheduling depth. The gap to close is forensic method, contract and claims literacy, evidence discipline, written advocacy, and the hard‑won posture of independence. None of these are bolt‑ons; they are a second profession layered onto the first, and most planners underestimate how long the second profession takes to build.

Certifications And Qualifications Worth Holding: Delay analysis is a field where credibility is currency, and the right credentials signal it. None are strictly mandatory, but in a discipline where your authority can be challenged, they help establish that you know the recognised methods and standards.

• AACE PSP — Demonstrates planning & scheduling rigour — the foundation.
• AACE CFCC — Forensic schedule / claims focus — directly relevant.
• SCL Delay & Disruption Protocol — The industry reference for method and good practice.
• Primavera P6 mastery — The tool most forensic analysis is performed in.
• Contract knowledge (FIDIC, NEC, etc.) — Delay sits inside the contract — you must read it fluently.

Credibility is assembled from method, tool, and contract literacy — not from any single certificate.

How To Build The Experience: You cannot shortcut your way into delay analysis; you build toward it. The most natural route is through senior planning on projects that actually experience disputes — because the best education in delay analysis is maintaining the records and schedules that later become the evidence. Volunteer for the extension‑of‑time submissions on your project. Work alongside the commercial team when a claim is being prepared. Get exposure to how a real delay argument is constructed and, ideally, how it is attacked.

Common Mistake — Treating delay analysis as a schedule exercise: The commonest error planners make moving into this field is treating it as pure scheduling — running the numbers, producing the impacted programme, and stopping there. But a delay analysis with no command of the contract, no grasp of notice and concurrency, and no evidence trail is a technical artefact that collapses the moment it meets a lawyer. Delay analysis is a legal‑technical discipline. The schedule is half of it; the contract and the evidence are the other half. Master all three or you remain a planner who builds impacted schedules for someone else to argue.

The expert‑witness dimension: As you become senior, delay analysis increasingly leads toward the role of expert witness — the person who signs a report and may have to defend it under oath. This changes how you work in a profound way: every opinion you express has to be one you can stand behind when a skilled barrister is trying to dismantle it. The independence requirement becomes absolute. An expert’s first duty is to the tribunal, not to the party paying the fee, and an analyst who forgets that — who shades the analysis toward their client — is an analyst whose credibility, once broken, never recovers.

Even if you never enter a witness box, working as if you might makes you a better analyst. It forces you to ask, of every conclusion: would this survive a hostile, expert cross‑examination? That discipline — anticipating the attack and closing the gap before it is found — is what elevates a competent analysis into a winning one. The best delay analysts I have known build their reports backwards from the cross‑examination they imagine facing.

Expert Tip — Build the report your opponent would attack: Before you finalise any delay analysis, spend an hour as the opposing expert. Where is your weakest link? Which assumption is least supported by the records? Which method criticism applies to your choice? Then strengthen or honestly caveat each one. The analyst who finds their own weaknesses first controls the argument; the one who waits for the other side to find them is always on the defensive.