Chapter 33 — Key Takeaways

A one-page reference card. Self-contained: if you come back to this in two years having forgotten the chapter, this page should re-ground you.

⚠️ This is a framework for recognizing and preparing issues. It is not legal advice, and it cannot be. Entitlement, the doctrine governing concurrent delay, the recoverability of particular damage categories, the enforceability of no-damage-for-delay and liquidated-damages clauses, and notice requirements all vary enormously by jurisdiction and by contract, and they change over time. Two contractors with identical facts and identical records can get opposite results on two sides of a state line. Read your own contract, verify against current primary sources, and involve counsel early — the cheapest legal advice you will ever buy is the advice you get before you need it.

Key Takeaways

• A claim is a request for additional time, money, or both that the other party has not agreed to. That is the whole definition, and "has not agreed" is the entire content. A change order request becomes a claim the moment the other side says no — or, under many contracts, the moment they say nothing for long enough. In most standard forms "Claim" is a defined term with its own procedure and its own deadlines, different from the change-order procedure.

• Entitlement, causation, and damages are three separate proofs, and you must win all three. They are gates in series, not a scorecard. Clearing two is worth exactly nothing. Airtight damages with no notice recovers zero; perfect entitlement with no schedule records recovers a time extension, if that.

• Being right is not the same as being able to prove it. Most claims that fail are not wrong about what happened. Curtis Boone's genuine, owner-attributable loss was roughly $780,000; his net recovery on a $1,375,800 filing was $150,260 after $163,000 of pursuit cost. The gap is not a legal outcome. It is a documentation outcome.

• Notice is the single most common claim-killer, and it is entirely preventable in about ten minutes per event. The clock usually starts at the event or at the point a reasonable contractor would have recognized the condition — not when you quantify it. You give notice of the event, not of the number.

• Every delay-analysis method except impacted as-planned requires contemporaneous schedule updates. Windows needs a regular series. Time impact analysis needs the update in effect when the event occurred. Collapsed as-built needs a defensible as-built with logic, which in practice comes from updates. A contractor who stopped updating has eliminated four of its five options — not weakened them, eliminated them, permanently, for any amount of money.

• Contemporaneous records beat reconstructions for three specific reasons, not because of a slogan: incentive (made before anyone had a motive to shade), information (they capture what the team actually believed the critical path was), and hindsight contamination (a schedule rebuilt knowing the ending unconsciously produces that ending).

• The critical path moves, and only a windows analysis follows it. On Northgate the driving chain was curtain wall in February, the imaging suite in March, and the elevator in April. As-planned versus as-built has no mechanism for that.

• Float consumed is not delay caused. A delay to an activity carrying float is not concurrent with anything. That one test — the total-float column of the update in effect at the start of the period — disposes of most alleged concurrency and was worth $56,650 in Window 2 on Northgate.

• True concurrency typically yields time but not money — and it also bars the owner's liquidated damages for the same period. Neither party can show its counterparty's conduct was the operative cause. This is a default, not a law, and its treatment varies substantially.

• Time is money at a knowable rate, and you should know yours to the dollar. Northgate: $5,150/CD extended general conditions, $5,500/CD liquidated damages, $10,650/CD total exposure. Willow Street: $1,600 + $1,200 = $2,800/CD.

• Disruption is not delay, and the measured mile is the only strong proof of it. Your own unimpacted performance against your own impacted performance, on the same job — because it removes the attack that kills every other method: your estimate was optimistic. Factor tables are negotiating references. The total cost method is last, disfavored, and carries four predicates.

• A single unsupported number damages every supported number next to it. Reviewers who find one line they cannot trace stop believing the lines they can.

• Evaluating a claim honestly negotiates better than evaluating it optimistically — measured in dollars, not manners. You know your walkaway, your credibility becomes an asset, and you spend your consultant budget on the elements that can actually win.

• Whether a claim is valid and whether it is worth pursuing are entirely different questions. Value it, apply a probability, discount it for time, subtract the cost to pursue. Many valid claims lose money.

• Good claims discipline includes knowing when you do not have one. Kestrel's records told it in four hours that the 23-day steel slip was its own. Documentation is not a weapon; it is an instrument, and it reports the truth whichever direction the truth runs.

• Above all: settle it while the people who know what happened are still on the project. Everything expensive about a dispute is a function of elapsed time. The facts do not get better with age. Only the legal bill does.

Action Items — this week, on your job

1. Answer three questions from your own contract, in writing, today: what starts the notice clock, who must receive it and how, and what the consequence of late notice is as the clause is actually written — waiver, or an obligation to show absence of prejudice.
2. Confirm your schedule update actually ran this month, and put a recurring calendar entry on it. Tie it to the pay application so the two live or die together. Four hours a month is the whole cost.
3. Read yesterday's daily reports. If any of them could be summarized as worked on site, you have found your exposure. Crew counts by trade, area, delays, idle time, visitors.
4. Pick your single strongest open issue and name which of the three proofs it is weakest on. Then go create the missing record before the day ends.
5. Read the last sentence of the next change order anybody hands you — out loud, if that is what it takes. Full-and-final release language destroys more entitlement than any courtroom ever has.
6. Ask counsel once, in advance, in writing: in this jurisdiction, on this contract, is unabsorbed home-office overhead available at all, and how are no-damage-for-delay clauses treated?
7. Open a cost code for any impact event on the day the decision is made — acceleration, standby, rework. Payroll that cannot distinguish acceleration overtime from ordinary overtime proves nothing.
8. If you have a claim you believe in, price the pursuit before you file it. Expected value, discounted, less consultant, counsel, and internal hours at a loaded rate.

Common Mistakes and the Fix

Decision Framework

The three gates, in order

1. ENTITLEMENT   Which clause or doctrine makes this theirs?
                 Was notice given, in time, in form, to the right people?
                 |  FAIL -> waived. The facts never get a hearing.
                 v
2. CAUSATION     Did it drive the CRITICAL PATH, in a contemporaneous update?
                 Can I rule out the alternative explanation?
                 |  FAIL -> "something bad happened, and something else
                 |          may have caused it."
                 v
3. DAMAGES       Is every dollar traceable to a code, a ticket, an invoice?
                 Is the method disclosed and defensible?
                    FAIL -> "you lost money. Now prove THIS event
                            caused THIS dollar."

Classifying any delay — three labels, in this order

1. Critical or non-critical? Non-critical usually ends the analysis. Float consumed is not delay caused.
2. Excusable or non-excusable? Does it extend the contract time and bar liquidated damages?
3. Compensable or non-compensable? Does it also carry money?

Concurrent delay is normally excusable and non-compensable: time, no money, no liquidated damages. Assess it period by period, never once for the whole job.

Picking a delay-analysis method

Check the contract first: it may specify the method, and using another can get your submission rejected on procedure without anyone reading the analysis.

Evaluating a claim made against you — run in this order

Notice and procedure → entitlement, read as though you were the claimant → causation, against the contemporaneous updates → damages audit, hunting the double-count → concurrency → your own exposure if you are wrong → a written settlement range with a walkaway, before the first meeting.

Pursue, negotiate, or absorb

The Three Sentences

1. Entitlement, causation, and damages are three separate proofs, and you must win all three.
2. Every delay-analysis method except the weakest one requires schedule updates somebody ran at the time.
3. The facts do not get better with age — only the legal bill does, so settle it while the people who know what happened are still on the job.