Chapter 33 — Claims, Disputes, and Delay Analysis: When the Project Goes Sideways

The Hook: "I Believe You. I Can't Prove You."

Eleven months after substantial completion at Rivermont Elementary School #12, Curtis Boone is sitting in a conference room on the fourteenth floor of a building he has never been in before, and there is a box of his own documents on the table that he did not pack.

Across from him is Kestrel's outside counsel. Beside her is a schedule consultant named Ilse Brandt, who has spent six weeks with the project record and has a Gantt chart open on a laptop that Curtis does not recognize as his own job. Curtis is here because Kestrel filed a claim against the Rivermont Unified School District for $1,375,800 and 74 calendar days, and today is the day somebody tells him what it is worth.

He is not nervous. He is, in fact, certain — and here is the thing you need to understand before this chapter can do anything for you: he is right.

The district was slow. The technology racks the district furnished arrived weeks after the date the contract schedule showed, and the classroom wing's low-voltage cabling and ceiling closeout waited on them. The kitchen equipment package went through three rounds of district committee review while Curtis held a hood opening in a roof. There was a stretch in month nine when the district's facilities director was out on medical leave and nobody had authority to approve anything, and the job idled around a decision that never came. Curtis lived it. He was there at 6:00 a.m. on the mornings when there was nothing for the electricians to do and he sent them home.

Ilse turns the laptop around.

"Your monthly schedule updates stop at month four," she says. "There are two more after that, both dated inside a nine-day span in month fourteen, both prepared after the fact. So I have a baseline, I have an as-built I assembled out of your daily reports and pay applications, and I have nothing in between."

"I know where the delays were."

"I believe you. Your daily reports for days 208 through 288 — eighty-one consecutive working days — say worked on site. Three words. No crew counts by trade after month five, no areas, no delays noted, no visitors, no weather except on the days it rained hard enough that somebody wrote rain." She scrolls. "Your notice letters are dated inside a four-day window in month thirteen. Nine letters. They reference events from months six, seven, eight, nine, and eleven."

Curtis says: "We told them constantly. Every OAC meeting."

"The architect's minutes say contractor noted coordination concerns. Fourteen times, in essentially those words." Ilse closes the laptop halfway. "Curtis, I want to be precise, because I think you are going to hear this as an accusation and it is not one. I am not telling you the delays didn't happen. I believe you. I can't prove you. Those are different problems, and only one of them was ever fixable, and it stopped being fixable about fourteen months ago."

That is the chapter.

Somewhere out there is a version of this book that would tell you claims are what happens when construction management fails. That version would be wrong, and it would leave you defenseless. Claims are a normal, expected, structural feature of an industry in which thousands of decisions get made under time pressure by parties with different interests, working from documents that were never complete. A project that produces no claims is not automatically a well-run project — sometimes it is a contractor who absorbed everything and did not know they were allowed to ask.

What this chapter gives you is the machinery: how a claim is actually built, how delay is actually analyzed, how damages are actually proven, and — the half almost nobody teaches — how to evaluate a claim somebody else is making against you, honestly, so that you negotiate from arithmetic instead of from indignation.

⚠️ This chapter is not legal advice, and it cannot be. Claims procedure, notice requirements, the treatment of concurrent delay, the recoverability of specific damage categories, the enforceability of no-damage-for-delay clauses, and the availability of interest vary enormously by jurisdiction, by contract form, and over time. Two contractors on two sides of a state line, with identical facts and identical records, can get opposite results. What follows is a framework for recognizing issues, preserving your position, and preparing work product. Involve counsel early — long before you think you need to. I will say this again at the end, because people skip endings and I want it in both halves of your memory.

🏃 Fast Track: If you have prepared or defended a claim before, skim §33.1–33.3 for the three-proof framing and the notice checklist, then go straight to the worked windows analysis in §33.4.2, the concurrency treatment in §33.5, and the economics-of-claiming framework in §33.10.

🔬 Deep Dive: The scheduling mechanics underneath a windows analysis are in Chapter 14 and worked further in Appendix B. The clause-by-clause reading behind §33.2.1 is Appendix G. The productivity measurement that makes a measured mile possible at all is Chapter 20.

33.1 What a Claim Actually Is

A claim is a request for additional time, additional money, or both, that the other party has not agreed to.

That is the whole definition, and the last eight words are the entire content. Look at the three neighbors:

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. The transition is usually invisible from inside the job. Nobody rings a bell. What you have is a proposal that has been "in review" for ninety days, and one morning your project accountant asks whether it should still be in the forecast, and the honest answer is that it stopped being a change and became a claim sometime back in month seven.

⚖️ What the contract says. In most standard forms, "Claim" is a defined term with its own procedure and its own deadlines, and those are different from the change-order procedure. Typically the contract will define what constitutes a claim, require written notice of the claim within a stated period after the event or after the claimant recognized the condition, require submission of supporting data within a further period, designate somebody — the architect, an initial decision maker, an owner's representative, an engineer — to render an initial decision, and then make that decision a condition precedent to any further step. Miss the initial-decision step and your arbitration demand can be dismissed as premature. Miss the notice period and, depending on jurisdiction and clause language, you may have nothing at all.

Three questions to answer from your own contract, in writing, at buyout — before there is anything to argue about:

1. What starts the clock, and does it start at the event, at your knowledge of the event, or at the impact? Those are three different dates and they are sometimes weeks apart.
2. Who must receive the notice, in what form, by what delivery method, with copies to whom?
3. What is the consequence of late notice as the clause is actually written — waiver of the claim, or merely an obligation to show the other party was not prejudiced? That single distinction is worth more than any argument you will ever make about the merits.

The definition matters more than it sounds like it should. I have watched two competent people argue for forty minutes about whether something was "a claim" while meaning completely different things by the word. To the field, a claim is an accusation. To a contract administrator, a claim is a filing. To an owner's board, a claim is a headline. Use the contract's definition, say which meaning you intend, and never let the emotional meaning drive the procedural one.

Claims are not a moral failure. I want to be blunt about this, because the industry is squeamish about it. Owners describe contractors who file claims as "claims-oriented," and they mean it as an insult. Contractors describe owners who deny claims as acting in bad faith, which is usually wrong. Most claims arise because a risk that looked cleanly allocated on paper turned out to be ambiguous in the field, or because something happened that nobody priced. Somebody has to pay for it, and the mechanism this industry built for deciding who is the claim process. Using it correctly is professional. Declining to use it when you are genuinely entitled is not nobility; it is an unfunded donation — and if you work for a company with a bonding line and a payroll, it is not your donation to make.

There is a line, and it is not where people think it is. The line is not do you file claims. The line is do you file claims you believe in, supported by records you made at the time. We get to the other kind in §33.12.

33.2 🚪 The Three Proofs

🚪 Threshold concept. Entitlement, causation, and damages are three separate proofs, and you must win all three. Being right is not the same as being able to prove it. Most claims that fail are not wrong about what happened — they fail because the contractor proved that something bad occurred and never proved that the other party owed them for it, or proved entitlement and could not tie the dollars to the event.

Before: you think a claim is an argument about facts. Something went wrong, it was not your fault, it cost you money, and if you can just get the right people in a room and lay out the sequence clearly enough, a reasonable person will agree and you will be made whole. Under this model, the work of a claim is narrative work — telling the story well.

After: you understand that a claim is three independent gates in series, each with its own evidence, and that clearing two of them is worth exactly nothing. You start asking, on the day the event happens, three questions that never used to occur to you: Which clause makes this theirs? What record will show it drove the completion date? What document will substantiate the dollars? And then you go create the missing one before the day ends.

The change is not in what you know. It is in when you act. The "before" contractor builds a claim after the job. The "after" contractor builds it during the job, in fifteen-minute increments, and mostly never has to file it — because a position documented well enough to win is usually settled at the field level for less than it would cost to fight.

Here is the structure. Three doors, and you need a different key for each.

   ┌───────────────┐    ┌───────────────┐    ┌───────────────┐
   │ 1 ENTITLEMENT │ →  │  2 CAUSATION  │ →  │  3 DAMAGES    │
   │               │    │               │    │               │
   │ Does the      │    │ Did THAT      │    │ How much, and │
   │ contract or   │    │ event cause   │    │ can I sub-    │
   │ law give me   │    │ THIS harm --  │    │ stantiate it  │
   │ a right to    │    │ and can I     │    │ from records  │
   │ recover for   │    │ rule out      │    │ made at the   │
   │ this?         │    │ other causes? │    │ time?         │
   │               │    │               │    │               │
   │ KEY: clause + │    │ KEY: contem-  │    │ KEY: cost     │
   │ timely notice │    │ poraneous CPM │    │ codes+tickets │
   └───────────────┘    └───────────────┘    └───────────────┘
        ↓ fail               ↓ fail               ↓ fail
    Waived. Zero.       "Something bad        "You lost money.
    The facts never      happened, and         Now prove THIS
    get a hearing.       something else        event caused
                         may have caused       THIS dollar."
                         it."

📊 Diagram (described). Three boxes in a horizontal chain, connected left to right by arrows, with a downward "fail" arrow beneath each and the consequence written under it. The reason to draw this as a series rather than as a checklist is that failure at any single gate ends the claim. There is no partial credit for two out of three, and the money does not flow at 67 percent. A contractor with airtight damages and no notice recovers nothing. A contractor with perfect entitlement and no schedule records recovers a time extension, if that, and no money.

33.2.1 Proof one — entitlement: does the contract or law give me a right to recover?

Entitlement is a contract question first and a fact question second. Before you argue about what happened, find the provision that turns what happened into somebody else's obligation. If no clause and no legal doctrine gives you a right, then you had a bad month, and the bad month is yours.

⚖️ What the contract says — the entitlement categories. Every row below is a typical structure. Your contract governs, standard forms differ from each other, and the underlying law differs by jurisdiction. Read yours, and read it before you need it.

Look at the pattern running down the whole right-hand column: nearly every row demands a date the obligation was owed and a date it was performed, and several demand notice. Those come from documents that exist only if somebody made them at the time. That is not an accident. The contract is written on the assumption that you are keeping records (Chapter 25, Chapter 26).

Two entitlement-killers live in the contract rather than in the facts, and you need to find them before you sign:

• No-damage-for-delay clauses, which purport to make a time extension your sole remedy for delay. Their enforceability is highly jurisdiction-dependent, and courts in a number of states recognize exceptions — commonly for active interference, bad faith, delay of a kind not contemplated by the parties, or abandonment of the contract. Never assume the clause is a force field. Never assume it is a nullity. Ask counsel about your jurisdiction, in advance, in writing.
• Waivers and releases — including the release language buried inside a change order form or a pay application. That is §33.3.3, and it destroys more entitlement than any courtroom ever has.

33.2.2 Proof two — causation: did that event actually cause this harm?

Causation is the hardest of the three, it is where most substantial claims are actually lost, and it is the only one that genuinely cannot be fixed later.

For time, causation runs through the schedule. You must show that the event affected the critical path — that it delayed the project's completion, not merely an activity. An activity carrying 20 days of float that gets delayed 12 days has cost the project nothing in time. (It may have cost real money in disruption. That is a different claim, proved a different way, in §33.6.4.) A delay to a non-critical activity produces frustration, not entitlement.

For money, causation runs through the cost records. You must connect the dollars to the event, which in practice means the cost was captured against a code, a ticket, or a work order that identifies it as belonging to this event rather than to the ordinary work.

And then there is the part people forget. You must survive the argument that the harm had another cause. The other side does not have to prove that something else caused it. In most settings they need only make the alternative explanation credible enough that yours no longer stands alone. That is what a defense consultant is hired to do, and they are very good at it.

🔍 Why this works — why contemporaneous schedule updates carry so much more weight than a reconstruction.

There are three mechanisms, and it is worth understanding all three, because together they tell you exactly what to protect.

First, incentive. A schedule update prepared in month six, when nobody knows there will be a dispute, was made with no motive to shade anything. A schedule prepared in month twenty by a party who now needs a particular answer was made with one. Tribunals of every kind — judges, arbitrators, dispute boards, and experienced owner's reps in a negotiation — weight evidence heavily by whether it was created before or after the incentive to distort came into existence. This is the intuition behind the special status that records made in the ordinary course of business hold in most legal systems.

Second, information. A contemporaneous update captures what the project team actually believed the critical path was at that moment — including logic that has since been lost, resources that have since moved, and constraints everyone has since forgotten. Reconstruction cannot recover belief. It can only recover outcome, and outcome is precisely what is in dispute.

Third, hindsight contamination. When you rebuild a schedule knowing how the job ended, you unconsciously build the logic that produces that ending. Every forensic analyst on both sides of this work has caught themselves doing it. The contemporaneous update is the only version of the schedule that could not possibly have been shaped by knowing the answer.

That is the mechanism behind Theme 5 of this book. Records made contemporaneously are worth ten times records made after the dispute — and now you know that is not a slogan. It is three specific properties that a reconstruction cannot manufacture at any price.

33.2.3 Proof three — damages: how much, and can I substantiate it?

Damages — often called quantum — is where the claim meets your accounting system. The categories are in §33.6. Here I want to establish only the standard, because it surprises people in both directions.

You do not need mathematical certainty. The general standard, stated at a level of generality that survives crossing a border, is that damages must be proven with reasonable certainty: the fact of damage established clearly, and the amount supported by a reasonable basis for calculation rather than by speculation. What that means on a construction claim:

• A number without a source is worth zero. Not discounted — zero. And worse than zero, because an unsupported line contaminates the credibility of every supported line sitting next to it.
• An allocation is perfectly acceptable if the method is disclosed and defensible. "We allocated the superintendent's time 60/40 between base work and changed work based on the activity descriptions in his daily reports" is a real answer that a reviewer can test. "We allocated 60/40" is not an answer at all.
• The decision-maker is allowed to award less than you ask, and routinely does. Getting greedy on one line does not raise the average. It lowers the credibility of everything else on the page.

💰 Money check — what Curtis Boone's claim was worth in fact versus what he could prove.

This is the arithmetic Ilse Brandt put on the table: the claim as filed, then an honest element-by-element evaluation. All figures are illustrative; Rivermont Elementary School #12, Kestrel, the district, and everyone in this story are composites. Rivermont's canonical daily rates: Kestrel's field general conditions on that job run $2,100 per calendar day and the district's liquidated damages are $2,500 per calendar day, a combined exposure of $4,600/CD.

Element	Claimed	Which proof failed	Realistic value
Direct cost of changed work — 9 unresolved change proposals	$268,400	Damages, partly. Six of the nine carry genuine entitlement ($191,000); only $142,000 of that is backed by tickets or coded cost	$137,000
Extended field overhead, 74 CD × $2,100/CD | $155,400	Causation. Only 19 CD of owner-caused critical delay can be established; 21 more are arguably concurrent	$36,860
Unabsorbed home-office overhead	$118,600	Entitlement. No owner suspension, no standby, and Kestrel took on replacement work	$0
Lost productivity / disruption, on a total cost method	$604,000	Causation and damages. No measured mile, two labor cost codes for the entire job, and no way to separate owner-caused loss from self-caused	$74,000
Idle equipment and standby	$41,500	Causation. Six of the fourteen claimed standby days tie to an identifiable owner act in the record	$11,300
Material escalation on two late-released packages	$28,900	Survives all three gates — vendor quotes and invoices exist and are dated	$21,600
Interest and finance cost	$63,000	Entitlement. Contract silent; availability is jurisdiction-dependent and contested	$0
Claim preparation cost	$96,000	Entitlement. Generally not recoverable absent a contract provision or statute that says otherwise	$0
Totals	$1,375,800		$280,760

Then the time. Nineteen calendar days compensable plus twenty-one excusable-but-not-compensable equals a 40-day extension, which releases the 13 calendar days of liquidated damages the district had assessed: 13 CD × $2,500/CD = $32,500 back.

Gross realistic recovery: $280,760 + $32,500 = $313,260.

Now subtract what getting there costs. Consultant $58,000. Counsel to date $71,000. Roughly 400 hours of Curtis's and his field engineer's time at a loaded $85/hour = $34,000. Total pursuit cost: $163,000.

$313,260 − $163,000 = $150,260 — against a claim filed at $1,375,800. Eleven cents on the dollar, arriving somewhere between eighteen and thirty months after that meeting.

And here is the number that should keep you awake. A consultant who has now read the entire record puts Kestrel's genuine, actually-incurred, owner-attributable loss at roughly $780,000. The gap between $780,000 and $313,260 is not a legal outcome. It is a documentation outcome. It is the price of eighty-one daily reports that said worked on site.

🔄 Check your understanding. A contractor establishes that the owner's late delivery of owner-furnished equipment delayed a critical activity by 18 calendar days, and produces invoices proving $94,000 of extended field overhead during that period. The claim is denied in full. Give the most likely single reason, and name which of the three proofs it belongs to.

Answer

Late or absent notice — a failure at the entitlement gate. Nothing in the stated facts addresses whether written notice was given within the contractual period, and the notice provision is the single most common reason a factually sound claim recovers nothing. It sits at entitlement because a conditional notice clause makes notice a condition precedent to the right to recover, no matter how strong the causation and damages proofs are behind it.

Two runners-up worth naming. Concurrency: the owner may show that the contractor's own work was independently delaying the same period, which attacks causation. A no-damage-for-delay clause: depending on the jurisdiction, that can leave the contractor holding the 18-day extension and none of the $94,000.

Notice that all three failure modes happen upstream of the invoices. The $94,000 was never the weak part of this claim.

33.2.4 A table of claims that failed, and which gate they failed at

Nothing teaches this faster than autopsies. Every row below is drawn from this book's own composite projects, or is a pattern I have watched play out more than once.

Sit with that last row. The three proofs are not a contractor's framework. They are the framework, and they apply identically to the owner assessing liquidated damages against you, to you backcharging a subcontractor, and to a subcontractor claiming against you.

33.3 Notice — The Fourth and Final Time

This is the fourth time this book has told you about notice. Chapter 5 introduced it as a legal framework. Chapter 25 put it in the document-control system. Chapter 31 attached it to the change process. Here it is one last time, because it is the single most common claim-killer in construction, and it is entirely preventable in about ten minutes per event.

I am repeating it on purpose. Spaced repetition is why you will remember it. That is not an accident of how this book was written; it is the point.

33.3.1 What a notice clause actually requires

A notice provision typically has five moving parts, and you need all five right:

The clock starts earlier than you think. In my experience the most expensive misunderstanding in this whole area is a contractor who believes the clock starts when they have quantified the impact. It usually does not. It usually starts when the event occurred or when a reasonable contractor would have recognized the condition — which can be weeks before you know what it costs. You give notice of the event, not of the number. You do not need a price to give notice. Saying "we do not yet know the cost or time impact and will supplement" is a complete and professional notice.

33.3.2 What a proper notice contains, and why it helps the owner too

A good notice is short, factual, unemotional, and complete. Six elements:

1. The contract provision you are giving notice under, cited by article number.
2. The event or condition, described factually — what, where, when discovered.
3. The date of the event and the date of your knowledge, stated separately if they differ.
4. The anticipated effect on cost and time, expressly stated as preliminary if you do not yet know it. Reserve both — cost and time frequently run on different clocks and different clauses.
5. What you are doing about it — including that you are proceeding to protect the schedule, if you are.
6. A request, if you have one: a direction, a decision, information, or access.

Nothing accusatory. Nothing speculative about dollars you cannot support. Nothing you would be uncomfortable having read aloud in a hearing three years later.

🔍 Why this works — notice is a benefit to the owner, which is why the clause exists.

Contractors experience notice as a hoop. Understand what it is actually for and you will send them more willingly and write them better.

A notice clause exists to give the party who owns the risk a chance to mitigate while mitigation is still cheap. If the district learns on day 2 that its technology racks are going to hold up the classroom ceilings, it can expedite the order, authorize a substitution, resequence with you, or accept the delay knowingly. If it learns on day 210, all of those options are gone and it is being handed a bill for a decision it never got to make.

That is exactly why the consequence of late notice is so harsh, and why "but they knew anyway" is a weaker argument than it feels like. The clause is not protecting a formality. It is protecting the owner's opportunity to do something. Which also means: an owner with actual knowledge who could not have mitigated anyway is in a materially weaker position to complain about your late notice — a point worth raising with counsel, and a reason the two questions "did they know?" and "were they prejudiced?" are asked separately.

The relationship consequence runs the same direction. Owners who build regularly expect notices, and they are quietly suspicious of contractors who never send any — because the claim always arrives eventually, and when it arrives with no notice history it arrives as an ambush. A steady, boring, well-written stream of notices is a marker of a professional organization, not an adversarial one.

33.3.3 Continuing notice, and the release you sign without reading

Two traps that cost real money.

Continuing notice for ongoing impacts. Many contracts require notice not only of the event but of its continuing effect — periodic updates while the impact persists, sometimes with a requirement to submit costs at stated intervals. A single notice on day 1 of a 90-day condition may not preserve days 30 through 90. Build the follow-up into your log the same day you send the first letter.

Reservation of rights on change orders and pay applications. Here is the trap, and it catches sophisticated people.

You negotiate the direct cost of a change. Everyone agrees on $46,000 for the added work. The change order form the owner sends over contains a sentence like: the adjustment stated herein constitutes full and final settlement of all costs, expenses, and time associated with the change, including all direct, indirect, impact, delay, disruption, and acceleration costs, whether known or unknown.

You sign it, because the $46,000 is correct.

You have just given away the impact claim — the disruption to the trades working around that change, the resequencing, the productivity loss, the schedule impact you had not yet quantified. That is Theme 1 in its purest form: a risk transferred by a sentence, at a moment when nobody was paying attention to risk. And it is exactly the kind of thing Chapter 31 warns about when it says the cost of a change is rarely the cost of the work.

⚖️ What the contract says — reservation of rights, conceptually. The remedy is a reservation: language added to the change order (or to the pay application, or to a transmittal accompanying either) stating that the agreed amount covers the identified direct scope only, and that rights are reserved with respect to identified impacts not yet quantified.

Conceptually, an effective reservation does four things:

1. Identifies what is being settled — the specific direct scope, by reference to the proposal, drawing, or directive number.
2. Identifies what is not being settled — cumulative impact, disruption, productivity loss, extended performance, or acceleration arising from this change and from the aggregate of changes.
3. States that the reservation is a condition of the signature, rather than a wish appended to it.
4. Is delivered in the manner the contract requires for notices, not scrawled in a margin.

The same logic applies to pay applications, many of which contain conditional or unconditional waiver language covering everything through the period of the application. Read the waiver on your own G-702-style certification form and on your lien waiver form (Chapter 32). Know which one you are signing every month.

Whether a reservation is effective, whether it must be accepted by the other party, and whether a unilateral reservation on a signed release preserves anything at all are questions of law that vary by jurisdiction and by contract. Have your counsel draft your standard reservation language once, and then use it consistently. Do not draft it yourself on a Friday afternoon.

🏗️ From the field. Margo Deacon has a rule I stole years ago and have never improved on. When a superintendent hands her a change order to sign in the field, she says: "Read me the last sentence." Nine times out of ten there is no last sentence and it is fine. The tenth time, the last sentence is a full-and-final release, and the ten seconds it took to read it out loud just saved a claim nobody had filed yet.

🔄 Check your understanding. Your contract requires written notice of a claim within 14 days of the event, and your change order form contains a full-and-final release. You are 60 days into an owner-caused delay that is still ongoing, and last week you signed a change order for a separate, unrelated scope addition. Name the three notice-related things you should already have done, and the one you need to check immediately.

Answer

Should already be done: (1) written notice of the delay event within 14 days of the event or your knowledge of it — not within 14 days of quantifying it; (2) continuing notice covering the ongoing 60-day impact, if your contract requires periodic updates while a condition persists; (3) a running contemporaneous record — schedule updates, daily reports identifying idle or redeployed crews, and cost captured to a code tied to the delay.

Check immediately: the release language on the change order you signed last week. Even though the scope was unrelated, many release sentences are drafted broadly enough to cover all claims through the date of execution, not just claims arising from that change. If that is what it says, you may have released a delay claim you were actively pursuing, on a form you signed for a completely different reason. Call counsel today, not next month.

33.4 Delay Analysis — The Technical Core

Now the engineering. A delay analysis answers one question: which party's actions moved the project completion date, and by how much? Everything else in a delay claim is commentary on the answer.

There is no single correct method. There is a family of methods with genuinely different strengths, data requirements, costs, and levels of acceptance, and the honest practitioner picks the best method the available records will support — then discloses the choice and its limitations, rather than pretending the choice was free.

33.4.1 The five methods

Two things about that table that matter more than the table.

First: the contract may choose for you. Many contracts specify a method — commonly a time impact analysis — as the required form of an extension request. Using a different method can get your submission rejected on procedure without anybody reading the analysis. Read the scheduling specification at buyout (Chapter 14).

Second, and this is the one that decides everything: every method in that table except impacted as-planned requires schedule updates that were made contemporaneously. Collapsed as-built needs a defensible as-built with logic, which in practice comes from updates. TIA needs the update that was in effect at the time. Windows needs a regular series of them. As-planned vs. as-built technically needs only a baseline and an as-built record, but it proves so little on its own that it is rarely enough by itself.

Curtis Boone stopped updating his schedule in month four.

Four of the five methods are therefore unavailable to him. Not weakened — unavailable. He is left with the weakest method in the table, the one most frequently rejected, plus an as-planned-versus-as-built comparison that shows the job finished late without showing whose fault that was. His consultant is not being difficult. She is describing a shelf with one item on it.

🧩 Productive struggle. Before you read the next section, try this yourself. Give it five minutes and a piece of paper.

Two consecutive monthly schedule updates on a job. At the first data date, the projected substantial completion is September 18. At the second, thirty days later, the projected substantial completion is October 7. In the intervening month, three things happened: the owner released a required equipment approval 11 days after the date on the accepted schedule; a subcontractor's crew ran 6 days behind the dates in the first update; and it rained for 4 days.

How many days did the project slip, and how much of that slip belongs to the owner?

Write down your answer and — this is the actual exercise — write down the one piece of information you would need that I have not given you. That missing piece is the entire subject of the next four pages.

What you needed

The slip is 19 calendar days (September 18 to October 7). The missing information is float — specifically, whether the subcontractor's 6-day slip and the 4 rain days were on the critical path, and how much total float those activities carried at the first data date.

If the subcontractor's activity carried 9 days of float and used 6, it consumed float but drove nothing, and it is not concurrent with anything. If it carried zero float, you have a genuine concurrency problem and the money answer changes completely. The same 6-day slip is worth $0 or is worth an owner's entire compensable claim depending on a number that exists only in a schedule update somebody had to run at the time.

That is why §33.4.2 is the most valuable technical artifact in this chapter, and why §33.4.3 is the most expensive lesson in it.

33.4.2 A windows analysis, worked

Let me run one properly, on Northgate, using Kestrel's monthly updates. Wei Chen ran this at the May 1 data date in Year 2 because Meridian had rejected a time extension request and Nadia Haddad wanted to know what Kestrel's position actually was before anybody wrote another letter.

Setup. Northgate Outpatient Pavilion: 132,000 SF, CM at Risk with a $47,500,000 guaranteed maximum price, 565 calendar days, notice to proceed March 3 Year 1, contract substantial completion September 18, Year 2. Extended general conditions are contractually fixed at $5,150 per calendar day and liquidated damages are $5,500 per calendar day — a combined exposure of $10,650 per calendar day. Kestrel updates the CPM monthly with a data date on the first of the month.

Three windows, three updates, three months:

Total projected slip across the three windows: September 18 to October 17 is 29 calendar days. Now the actual work — finding out who owns each piece, window by window, and watching the critical path move.

Window 1 (Feb 1 → Mar 1, Year 2): the critical path runs through the enclosure.

At the February 1 data date the driving path is: curtain wall installation → building dried-in (March 28) → interior finishes → commissioning → substantial completion. Curtain wall is 38,500 SF of unitized aluminum and glass, delivered in shipments by elevation.

What happened in the window: the fabricator's third shipment arrived 8 days late. Kestrel's daily reports record the erection crew standing down on the north elevation for six of those days and being redeployed to punch out the south elevation for two.

Was anything else critical? Update 15 shows the next-nearest path — mechanical equipment set on the roof — carrying 12 days of total float at the March 1 data date. It moved, but it did not drive.

Apportionment: 8 CD, contractor-side (a supplier to Kestrel's subcontractor is Kestrel's responsibility to Meridian). Non-excusable. $0 compensable. Kestrel owns this.

Window 2 (Mar 1 → Apr 1, Year 2): the critical path moves to the imaging suite.

This is the window that teaches. Kestrel resequenced the enclosure by elevation and got curtain wall largely back under control, which means it is no longer the longest path. The critical path shifts to the imaging suite — the depressed slab, added structural framing, RF shielding, and larger electrical feed that came out of CO #14, the MRI change Meridian made after the GMP was set.

What happened: Meridian's imaging vendor released the final shielding shop drawings 11 days after the date shown on the accepted schedule. RF shielding cannot be installed without them, the shielding is a predecessor to closing the walls, and closing the walls is a predecessor to everything else in that suite.

And here is the complication — the one Meridian's consultant raised. In the same window, Kestrel's own medical-gas rough-in in that same suite ran 6 days behind its Update 15 dates. Meridian argued concurrency: you were late too; you get time, not money.

Run the test. It takes four minutes and it is worth $56,650.

Apportionment: 11 CD, owner-caused, excusable and compensable. The alleged concurrency fails because the contractor's own slip never touched the critical path — a fact that exists in exactly one place in the universe: the total-float column of a schedule update Wei Chen ran on March 1 and nobody thought was interesting at the time.

11 CD × $5,150/CD = $56,650 in extended general conditions.

Window 3 (Apr 1 → May 1, Year 2): the critical path moves again, and this one is genuinely concurrent.

With the imaging suite released, the driving path shifts a third time — now to elevator installation → elevator inspection → commissioning start (July 20) → substantial completion.

Two things happened, and they overlap:

• The elevator subcontractor pulled its field crew to another job from April 6 through April 15 — 10 calendar days. Contractor-side.
• Meridian suspended work in the ambulatory surgery suite from April 9 through April 15 — 7 calendar days — to accommodate an accreditation survey at the adjacent clinic that stays open. The suspension blocked the corridor that was the only route for elevator equipment and the only access for the commissioning walk. Owner-caused.

Both were on the critical path. They overlap on April 9–15: 7 calendar days of true concurrency.

Apportionment: 3 CD non-excusable, 7 CD excusable but non-compensable. $0 compensable in this window.

The result, assembled.

Time extension requested and supported: 18 calendar days (11 compensable + 7 excusable). Money supported: 11 CD × $5,150/CD = $56,650. Kestrel's own exposure on the 11 non-excusable days: 11 × $10,650/CD = $117,150 unless it recovers them.

Here is the ASCII view of the same thing, which is how I actually explain it to an owner:

                Feb 1        Mar 1        Apr 1        May 1
                  |            |            |            |
 WINDOW           |<-- W1 -->  |<-- W2 -->  |<-- W3 -->  |
 SLIP             |    8 CD    |   11 CD    |   10 CD    |   = 29 CD
                  |            |            |            |
 CRITICAL PATH    | CURTAIN    | IMAGING    | ELEVATOR   |
 IN THE WINDOW    | WALL       | SUITE      | + CX       |
                  |            |            |            |
 DRIVING CAUSE    | late panel | late owner | crew pull  |
                  | shipment   | shielding  | + owner    |
                  |            | drawings   | suspension |
                  |            |            |            |
 OWNS IT          | KESTREL    | MERIDIAN   | BOTH       |
                  | [########] | [########] | [##|#####] |
                  |  8 non-exc |  11 comp   |  3  |  7   |
                  |            |            | n-exc concur

📊 Diagram (described). A three-panel timeline. Each panel is one monthly window, labeled with its slip in calendar days, the activity chain that was critical during that window, the driving cause, and which party owns it. The essential visual message is the middle row: the critical path is a different chain of work in each of the three panels. Nothing else in delay analysis matters as much as that.

Why the windows method beats every alternative here. An as-planned-versus-as-built comparison of this project would report 29 days of slip and a lot of activities that finished late. It could not tell you that curtain wall drove February, the imaging suite drove March, and the elevator drove April — because as-planned-versus-as-built has no mechanism for a critical path that moves. An impacted-as-planned analysis would insert the shielding delay into the baseline and produce a number that ignores the fact that curtain wall had already consumed the float the baseline showed. Windows follows the project the way the project actually happened, one month at a time, using the schedule the team was actually managing to.

What happened next on Northgate. Meridian granted the 18 calendar days, moving the adjusted substantial completion to October 6, Year 2. Kestrel built a recovery plan for the 11 days it owned — that is Chapter 29's territory — executed it, and achieved substantial completion on September 18, Year 2, the original contract date. The 18-day extension became genuine float, and Kestrel spent most of it later on two problems nobody had forecast. That is what a well-run job looks like: you fight for the extension you are entitled to, you fix the part that is yours, and you bank the difference against the next surprise.

33.4.3 What Curtis Boone cannot do, said plainly

Put the two projects side by side.

Four of the five delay-analysis methods are unavailable to Curtis, and they are unavailable for one reason: the updates do not exist. No amount of skill, money, or expert testimony creates them now. A consultant can reconstruct an as-built from daily reports and pay applications, and Ilse did — but a reconstructed as-built has no contemporaneous float data, so it cannot answer the question that Window 2 on Northgate answered in four minutes: was the contractor's own slip on the critical path or not? And when that question cannot be answered, the tie goes to the party defending.

That is the whole lesson, and it costs Curtis roughly $467,000 of a genuinely incurred $780,000 loss.

Wei Chen puts it in one sentence that I have since put on a wall: "A schedule update costs about four hours a month. Four hours a month for fourteen months is fifty-six hours. Curtis saved fifty-six hours."

⚠️ Safety alert — the claim posture that gets somebody hurt. There is a specific and genuinely dangerous failure mode here, and I have seen it twice. A contractor in a dispute becomes reluctant to fix a condition, because fixing it might look like accepting responsibility for it, or might make the impact harder to prove. Or a contractor accelerates hard to defeat an anticipated liquidated-damages assessment, and the acceleration produces exactly what acceleration produces — trade stacking, fatigue, and an unwritten "make it up" pressure on the crews. That is the mechanism behind the scaffold near-miss on Northgate in week 34, and it is Theme 4 of this book: schedule pressure is a hazard exactly like an unguarded edge.

The rule is not complicated. Fix the hazard today; document it today; argue about who pays for it later. Correcting an unsafe condition is never an admission of anything, and no claim strategy in the world justifies leaving a plank unsecured or a crew working a compressed schedule without a re-look at the job hazard analysis. If anyone on your team ever suggests otherwise, the answer is no, and the reason is not legal.

33.5 Concurrent Delay

Concurrent delay means two or more delays, caused by different parties, affecting the critical path during the same period.

It is the most contested single concept in construction claims. It decides enormous amounts of money, it is analyzed inconsistently across jurisdictions, and reasonable, expert, well-intentioned people disagree about it in good faith. What follows is a working framework, not a rule of law.

33.5.1 The general principle, and why it exists

The usual outcome of true concurrency: the contractor gets time but not money, and the owner does not get liquidated damages.

The logic is symmetrical and once you see it you will not forget it. The contractor cannot recover delay damages, because it would have been delayed anyway by its own conduct — the owner's delay did not cause the additional cost, since the contractor's own delay was independently sufficient to produce it. The owner cannot assess liquidated damages, because it would be collecting for a delay it also caused. Neither party can prove that its counterparty's conduct was the operative cause, so the day is excusable (no LDs) and non-compensable (no money).

Time, no money. That is the default in most treatments. It is a default, not a law.

33.5.2 Literal versus functional concurrency

This distinction settles a great many arguments, and most people have never heard it named.

Window 3 on Northgate was literal concurrency: April 9 through 15, both delays live, both on the critical path. That is the easy case and it is why I built the example that way.

Functional concurrency is where the arguments live, and it is also where the order of analysis starts to matter enormously — analyze the events chronologically and you can get a different answer than if you analyze them by magnitude. That is not a flaw in anybody's integrity. It is a genuine methodological question that reasonable experts resolve differently.

33.5.3 The tests that actually decide it

In practice, three questions decide most concurrency arguments, and you can answer all three from good records:

1. Was the second delay actually on the critical path during that period? This is the Window 2 test, and it disposes of a large share of alleged concurrency. A delay to an activity with float is not concurrent with anything. It consumed float. Float is not the same thing as delay.
2. Was the second delay of a different character? A "pacing" delay — where the contractor deliberately slows work because it is already delayed by the other party and there is no point burning money to arrive early at a wall — is treated differently from an independent delay in many analyses. Pacing generally must be a conscious, documented, contemporaneous decision, not one discovered after the fact by a consultant. Write it down when you do it, or it is not pacing, it is just being late.
3. Can the delays be separated in time or in effect? Window 3 separated cleanly: 3 days of contractor-only, then 7 days concurrent. That partition is only possible because both start and end dates were documented.

33.5.4 Apportionment

Where concurrency is found, tribunals take broadly three approaches, and which one you get depends on where you are and what your contract says:

⚖️ What the contract says. A growing number of contracts now address concurrency expressly, and some do so aggressively — for example, providing that the contractor receives no compensable delay for any period in which any contractor-caused delay exists, however small. That is a very large risk transfer executed in one sentence, and it is a clause worth pricing at bid time and negotiating before signature (Chapter 4, Chapter 6).

33.5.5 The honest statement, and where to read further

Treatment of concurrent delay varies substantially by jurisdiction and by contract, and it is one of the most contested areas in construction law. Definitions differ. The required degree of overlap differs. Whether a contractor-caused delay must be on the critical path to count as concurrent differs. Whether apportionment is permitted at all differs. I am not being cautious for form's sake; I am telling you that a confident, universal answer to a concurrency question is a warning sign about whoever is giving it.

Two bodies of work are the standard references, and you should know both by name and by function:

• The Society of Construction Law's Delay and Disruption Protocol. A widely referenced guidance document addressing delay analysis methodology, concurrency, float, and disruption. It is guidance rather than law, it has been revised over time, and it is not binding anywhere — but it is frequently cited in international practice and it gives a common vocabulary to people who would otherwise argue past each other. Read the current edition itself; do not rely on anyone's summary, including mine.
• AACE International's recommended practice on forensic schedule analysis (RP 29R-03). A comprehensive taxonomy and methodological framework for delay analysis techniques — it classifies the methods, describes their data requirements, and is candid about their limitations. AACE publishes a companion recommended practice addressing the estimation of lost labor productivity that surveys the available methods and ranks them by reliability. These are the closest things the industry has to methodological standards.

I am describing what those documents do, not quoting them. Neither is a statute, neither is binding, and both have been revised. Get the current versions and read them yourself before you rely on either in a dispute.

🔄 Check your understanding. An owner delays a critical activity by 12 days. During the same 12 days, the contractor's own painting subcontractor is 9 days behind — on an activity that carried 20 days of total float at the start of the period. The owner asserts concurrency and offers a time extension with no money. What is your response, and what single document do you need?

Answer

This is not concurrency. The painting activity carried 20 calendar days of total float and consumed 9. It was never on the critical path, so it never independently delayed project completion. Consuming float is not the same as causing delay. Absent something else, the 12 days should be excusable and compensable.

The single document: the contemporaneous schedule update in effect at the start of the period, showing 20 days of total float on the painting activity. Without it you are asserting a float value from memory against a consultant with a laptop, and you will lose — not because you are wrong, but because you cannot show it. This is exactly the Window 2 test from §33.4.2, and it is exactly what Curtis Boone cannot do.

One caution worth carrying: if the painting slip continued past 20 days, the activity becomes critical from that point forward and the analysis changes for the remainder of the period. Concurrency is assessed period by period, not once for the whole job.

33.6 Damages — The Categories and How Each Is Proven

Entitlement and causation get you through the door. Damages is what you actually collect, and this is where careful contractors separate themselves from hopeful ones.

33.6.1 Direct costs of changed or extra work

The straightforward category: labor, material, equipment, subcontract cost, and markup for work that was added or changed. This is the pricing machinery of Chapter 31, and the proof is the same: quantities, unit costs, quotes, invoices, time-and-material tickets signed by somebody, and a markup structure that matches what the contract allows.

The lesson from CO #14 on Northgate governs the whole category. Kestrel's actual cost on that MRI change was $186,400; the cost it could substantiate with contemporaneous records was $121,000; the negotiated settlement eight weeks later was $142,750; and Kestrel ate $43,650. The gap is not a negotiating failure. It is the four days at the beginning where nobody wrote a T&M ticket. The price of a change is set by what you can document, not by what it cost you.

33.6.2 Extended field overhead (extended general conditions)

When the project runs longer, your job-site overhead keeps burning: the project manager, the superintendent, the field engineer, the trailer, the temporary power and water, the dumpsters, the portable toilets, the safety supplies, the small tools, the cleanup labor. That is extended field overhead, usually called extended general conditions, and it is the most commonly recovered delay damage there is.

Worked, on Northgate. The GMP carried general conditions of $2,900,000 over a 565-calendar-day contract:

$2,900,000 ÷ 565 CD = $5,132.74/CD

Kestrel and Meridian negotiated a stipulated rate of $5,150 per calendar day in the contract. For the 11 compensable days from Window 2:

11 CD × $5,150/CD = $56,650

What it means for the job: every calendar day of compensable owner delay is worth $5,150 to Kestrel in overhead alone — and every calendar day of non-excusable delay costs Kestrel that same $5,150 plus $5,500 in liquidated damages, which is where the canonical $10,650/CD total exposure comes from. Time is money at a specific, knowable rate, and you should know yours to the dollar. That is Theme 2: the schedule and the budget are the same conversation.

When the rate is not contractually fixed, you have four approaches, in descending order of defensibility:

Note what happened in the Curtis Boone money check: his extended-overhead claim was filed at $2,100/CD, and the audited actual for the relevant period came in at $1,940/CD. The $160/day difference across 19 days is only $3,040 — small. But the credibility cost of a rate that could not be reconciled to the ledger was not small, and it colored how the district's consultant read every other line on the page.

33.6.3 Unabsorbed home-office overhead

This one is genuinely subtle and it is the category most often claimed badly.

The concept. Your company has fixed overhead that exists regardless of any single project: the executives, the accounting department, the estimating department, the office lease, the insurance, the IT. That overhead is implicitly allocated across the projects that are running. When a project is extended, the project keeps absorbing overhead but generates no additional revenue over the extension — the contract value did not grow, only the time did. The contractor's fixed overhead is now spread over a longer period on this job than it was priced to be, and if the contractor could not take on replacement work during the extension, some of that overhead genuinely went unrecovered.

That is a real economic harm. Whether and how you can recover it is a different question entirely.

Formula-based approaches exist. The best known is generally referred to as the Eichleay approach, which allocates home-office overhead to a delayed contract on a proportional basis and derives a daily rate for the delay period. It is jurisdiction-dependent, frequently contested, and carries strict predicate requirements. In the settings where it is most established, those predicates typically include some combination of: a government- or owner-caused suspension, delay, or disruption of uncertain duration; a requirement that the contractor remain on standby, ready to resume work; and an inability to take on replacement work during the period.

I am describing a concept, not handing you a formula to apply. Some jurisdictions accept the approach; some restrict it heavily; some reject formula-based home-office recovery outright; many private contracts disclaim it by name. The predicates are applied strictly where they are applied at all, and "we were busy and it was annoying" does not satisfy them.

That is exactly why Curtis's $118,600 went to zero. There was no suspension. Kestrel was never on standby — the job kept working the whole time. And Kestrel took on replacement work; the company bid and won two other projects during the period. Three predicates, three failures, before anybody looked at a number.

What to do instead, and do it early: ask counsel, in your jurisdiction, whether this category is available to you at all, before you spend money building the calculation. It is one of the few damage categories where the entitlement question genuinely should be answered before the arithmetic is started.

33.6.4 Lost productivity and disruption — the hardest one

Disruption is different from delay. Delay makes the project longer. Disruption makes the work less efficient — the same scope, done by the same people, at a worse rate, because of interference, out-of-sequence work, trade stacking, crew size changes, learning-curve loss from restarts, rework, dilution of supervision, or overtime fatigue.

You can be disrupted without being delayed. You can be delayed without being disrupted. They are separate claims with separate proofs and they are frequently confused, including by people who should know better.

Disruption is the hardest damage category to prove, and here are the methods in order of strength.

Method 1 — the measured mile. This is the preferred approach and it is not close.

You compare your own performance on the same work, on the same job, in an unimpacted period against an impacted period. Because the baseline is your own actual performance rather than your bid, it removes the single most effective attack on every other method: your estimate was optimistic.

Worked, on Northgate. Cardinal Mechanical (Sofia Marchetti's crew) installs overhead sheet-metal ductwork. Two periods:

Step by step:

1. Productivity loss: (38.0 − 24.0) ÷ 38.0 = 0.368 → 36.8 percent
2. Hours the impacted work should have taken at the unimpacted rate: 52,800 lbs ÷ 38.0 lbs/MH = 1,389 MH
3. Hours actually expended: 2,200 MH
4. Lost hours: 2,200 − 1,389 = 811 MH
5. At a fully burdened sheet-metal rate of $74.00/MH: 811 MH × $74.00 = $60,014

What it means for the job: roughly $60,000 of Cardinal's cost on that wing is attributable to working around the CO #14 rework and out-of-sequence access — and it is a number derived entirely from this project's own labor records, which is why it survives contact with an opposing consultant.

Now attack your own measured mile before somebody else does. The two periods must be genuinely comparable, and here they are not perfectly comparable:

A measured mile that you have already stress-tested, with its adjustments disclosed, is worth several times one you present as flawless. The credibility of the method is the damages.

Method 2 — earned value and baseline productivity comparisons. Where a clean unimpacted period does not exist, you can compare performance against the earned-value baseline (Chapter 30) or against a "baseline productivity" period constructed from the best-performing consecutive periods on the job. Weaker than a true measured mile, but grounded in actuals, and far stronger than the next two.

Method 3 — industry inefficiency factor studies. Published tables assign productivity-loss percentages to conditions like trade stacking, overtime, out-of-sequence work, or extreme temperature. Several respected organizations publish such material.

Use them honestly: as negotiating references, not as proof. A factor table describes what happened on other projects. It is a planning heuristic and a sanity check. Presented as the primary proof of your damages, it will be dismantled by any competent opposing consultant in about four minutes, and the dismantling will damage the rest of your claim. Chapter 20 makes the same point from the estimating side and it is worth repeating here: a number taken out of a book into a negotiation dies to the first competent question.

Method 4 — the total cost method, and why tribunals dislike it.

The total cost method says: my actual cost was X, my bid was Y, therefore my damages are X − Y.

It is enormously appealing when your records are bad, which is precisely why tribunals distrust it. It silently assumes three things that are frequently false: that the bid was accurate, that all the actual costs were reasonable, and that none of the overrun was the contractor's own fault. A bad bid is invisible inside a total cost claim, and so is bad management.

Where the method is entertained at all, four predicates are typically demanded:

1. The nature of the losses makes it impossible or highly impracticable to determine them with a reasonable degree of accuracy by any better method.
2. The bid or estimate was realistic.
3. The actual costs were reasonable.
4. The contractor was not responsible for the added expense.

The modified total cost method improves on it by adjusting both ends: correct the bid for identified estimating errors, and remove from the actual costs those amounts attributable to the contractor's own inefficiency, rework, or unrelated problems. That adjustment is often the difference between a claim that gets discussed and one that gets dismissed — but note what it requires. To subtract your own inefficiency, you must be able to identify it, which requires the very cost detail whose absence drove you to a total cost method in the first place. That circularity is the honest heart of the problem.

Curtis's $604,000 disruption claim was a straight total cost claim. It failed predicates 1, 3, and 4, and predicate 2 was never tested. It settled for $74,000 — which is not a valuation of his damages. It is the price of making a nuisance go away.

33.6.5 The remaining categories

33.6.6 Liquidated damages — the owner's claim, and your defenses

Everything in this chapter cuts both ways, and liquidated damages (LDs) are the owner's claim against you.

An LD clause fixes, in advance, a daily amount payable for late completion — $5,500/CD on Northgate, $2,500/CD at Rivermont Elementary, $1,200/CD at Willow Street. The purpose is to avoid litigating the owner's actual damages, which are often real but hard to quantify: lost revenue, extended financing, holdover rent, staff overtime, and in Meridian's case a leased interim clinic space with a hard expiration.

The owner's LD claim must clear the same three gates yours does:

At Rivermont, this is exactly how Kestrel got $32,500 back. The district assessed 13 calendar days. Kestrel established a 40-day extension from the delay analysis, which moved the adjusted completion date past the actual completion date and eliminated the assessment entirely. The claim and the defense were the same document. They almost always are, which is a good argument for doing the analysis even when you have decided not to file.

📋 Try It — Classify the Delay, Compute the Money

You are the project manager. Your contract has a standard changes and delay clause, an excusable-delay provision, and no no-damage-for-delay clause. Extended general conditions are contractually stipulated at $5,150 per calendar day.

Here is what happened, laid against a compact schedule. All activities below are on the critical path when they occur.

 DAY:  1    4    8   12   16   20   24
       |    |    |    |    |    |    |
 A: Owner-caused design delay (late response, RFI 214)
       [=========== 14 CD ===========]
       Day 1 ----------------- Day 14

 B: Subcontractor manpower shortfall (framing sub short 6 of 11 workers)
                      [=========== 14 CD ===========]
                      Day 9 ------------------ Day 22

 OVERLAP:              [## 6 CD ##]
                       Day 9 -- Day 14

 TOTAL PROJECT SLIP:  Day 1 ------------------- Day 22  =  22 CD

Answer five questions:

(a) Classify each of the two delays — excusable or non-excusable, compensable or non-compensable. (b) Determine the concurrent period. (c) State what time and what money the contractor is likely entitled to, and why. (d) Name the three documents you would need to prove it. (e) Compute the extended general conditions claim at $5,150/CD.

Work it before you open the answer. The classification in (a) is the easy part; (b) and (c) are where people go wrong.

33.7 Building the Claim Document

A claim document has one job: persuade a person who was not there.

Internalize that and the structure writes itself. The reader is an owner's representative who joined in month 14, a claims consultant, an insurance adjuster, a dispute board member, an arbitrator, or a judge. They do not know your job, your people, or your building. They have limited time and they are reading three other submissions the same week. They will decide how much of your document to believe in the first ten pages.

33.7.1 The structure

33.7.2 The rules that decide whether it works

A single unsupported number destroys the credibility of the document. This is not an exaggeration and it is not a moral point — it is how reviewers actually behave. When a reviewer finds one number they cannot trace, they stop believing the numbers they can trace and start looking for more. I have watched a well-built claim lose most of its value because of one $18,000 line that somebody could not source. The $18,000 was probably real. It cost more than $18,000.

Never assert a fact you cannot exhibit. If it is in the narrative, it is in the index. If it is not in the index, cut the sentence.

Write it so a hostile reader stays fair. The best claim documents I have read are almost boring: dates, documents, arithmetic, and a tone that assumes the reader is reasonable. The worst read like an argument you are losing.

Include the bad facts. Every claim has them. If you have three weeks of your own crew shortage inside the delay period, put it in the narrative, address it in the analysis, and explain why it does not change the result. If you omit it, the other side introduces it — and then the question is no longer whether the crew shortage mattered. The question is what else you left out.

33.8 Evaluating a Claim Made Against You

This is the other half of the skill and it is almost never taught. You will spend more of your career evaluating claims — from subcontractors, from the owner, from suppliers — than filing them.

The temptation when a claim lands on your desk is to look for the reason it is wrong. Resist it. Your first job is to find out what it is actually worth, because that number determines everything you do next.

33.8.1 The evaluation sequence

Run it in this order. The order matters because each step can end the analysis.

33.8.2 The professional reality nobody says out loud

A contractor who evaluates its own claims honestly negotiates far better than one that does not. Not more ethically — better, measured in dollars.

Three mechanisms, and they are worth understanding because they are counterintuitive.

You know your walkaway. A party that has honestly valued a claim at $280,000 to $340,000 can hold at $300,000 with total composure, because they know what happens if the deal fails. A party that has told itself the claim is worth $1.4 million has no walkaway, only hope, and hope negotiates terribly.

Your credibility becomes an asset. When you concede the two lines that are genuinely weak, the other side starts believing the six that are strong. Conceding nothing signals that nothing you say is calibrated, and the other side responds by discounting everything uniformly — including the parts you would have won.

You spend your money where it can win. Claim preparation is expensive. A party that knows which three of its nine elements are strong spends its consultant budget on those three. A party that believes all nine are excellent spreads the budget evenly and under-develops the ones that mattered.

The same is true in reverse when you are on the receiving end. When Sofia Marchetti brings me a disruption claim from Cardinal Mechanical, the fastest path to a resolution I can live with is to tell her honestly which part I think she is right about. It costs me nothing I was going to keep, and it converts a two-year argument into a three-week negotiation.

33.9 Dispute Resolution — The Ladder

Chapter 5 introduced the ladder. Here is how each rung actually behaves.

33.9.1 Field-level resolution — where almost everything gets solved

Two project people, the documents, and a conversation. By an enormous margin the cheapest and most common way construction disputes end, and the one that never appears in any statistic, because a dispute resolved at the field level never gets called a dispute.

Its power comes from a fact that expires: the people who know what happened are still on the project and still remember. That fact has a half-life measured in months.

33.9.2 Executive negotiation

Both parties elevate to people who were not in the fight — a vice president, an owner's facilities director. Most contracts require this step before formal proceedings, and it works more often than cynics expect, precisely because the participants have no ego invested in the disputed events and have a portfolio view: this project is one of eleven, and the relationship has a future.

33.9.3 Dispute review boards and standing neutrals

A dispute review board (DRB) is a panel — commonly three people, one selected by each party and a third selected by the first two — appointed at the start of the project, kept current through periodic site visits and document distribution, and available to hear issues as they arise and issue findings, usually non-binding.

A standing neutral is the same idea with one person.

They are used most on large, long infrastructure projects, and they are genuinely effective for a reason worth stating precisely: they resolve issues while memories are fresh and the people are still on the project. A DRB hearing in month nine gets testimony from the superintendent who was standing there. An arbitration in year four gets that same superintendent's recollection, three jobs later, refreshed from documents. The board also changes behavior even when it never sits — parties who know a knowledgeable neutral will read their correspondence write better correspondence.

The cost is real: retainers, per-visit fees, and document distribution across the whole project. On a large job it is a rounding error against a single avoided arbitration.

33.9.4 Mediation — where most construction disputes actually settle

A neutral mediator, with no power to decide anything, meets with both parties, usually shuttling between rooms, and works toward a negotiated settlement. It is confidential, non-binding, and typically fast: a day or two of session, plus preparation.

Mediation settles a large majority of construction disputes that reach it. The mechanisms are worth knowing:

• A neutral can say things the parties cannot. A mediator telling your executive privately that the notice problem is worse than counsel has admitted lands differently than opposing counsel saying it.
• It forces valuation. Preparing for mediation forces both sides to actually price the claim, and the pricing usually moves the parties closer than the argument ever did.
• It surfaces non-monetary trades. Release of retention, a change-order package resolved together, a warranty extension, an agreement on future work, or a schedule concession can bridge a gap that dollars alone cannot.
• Everyone in the room understands the cost of the alternative, and by the time you are in mediation both parties have seen a legal bill.

Preparation matters more than performance. Go in with your honest evaluation from §33.8, a settlement range approved by whoever can actually approve it, and the authority to sign. A mediation where the decision-maker is on a plane is a wasted day.

33.9.5 Arbitration

A private tribunal — one arbitrator or a panel of three — hears evidence and issues a binding award. Usually confidential. Usually with narrower discovery than litigation. Appeal rights are extremely limited: in most systems an award can be challenged only on narrow grounds such as fraud, arbitrator misconduct, or exceeding authority — not because the arbitrator got the facts or the law wrong.

Two honest observations:

Arbitrator selection is the most consequential decision in the process. You are choosing your judge. A construction-experienced arbitrator who has read a hundred schedule analyses will engage with your windows analysis. One who has not will fall back on impressions. Take the selection process seriously and use counsel who knows the field.

Arbitration is no longer necessarily cheap. Its original promise was speed and low cost. In practice, large construction arbitrations have grown to look a great deal like litigation: extensive document exchange, multiple experts, lengthy hearings, and arbitrator fees that a court does not charge. It remains generally faster and more private than litigation, and the decision-maker is generally more knowledgeable. It is not automatically cheaper, and anyone who tells you it is has not priced a three-arbitrator panel lately.

33.9.6 Litigation

Public courts, public record, broad discovery, formal rules of evidence, a judge or jury who may have no construction background, and a genuine right of appeal. Slowest and generally most expensive. It has real advantages: the broadest discovery tools, the ability to join multiple parties (which matters enormously in a multi-party construction dispute where the architect, the contractor, and three subcontractors all point at each other), enforceable subpoenas against non-parties, and appellate review of legal error.

33.9.7 The comparison

⚖️ What the contract says. The contract usually dictates the path, and often makes each rung a condition precedent to the next. Some forms let the owner elect the final method after the fact. Some specify the arbitration rules and the administering body. Some contain a fee-shifting provision that changes the economics of everything in this chapter. This is a clause worth negotiating before you sign, not a clause to read for the first time when you are angry. Ask three questions at contract review: What is the required sequence? Who bears the cost of each step? And is the final step binding arbitration or litigation, and in what venue?

33.10 The Economics of Claiming

Here is the section I wish somebody had given me at thirty. Whether a claim is valid and whether it is worth pursuing are entirely different questions, and many valid claims are not worth pursuing.

33.10.1 The five costs

1. Claim preparation cost. A schedule consultant on a mid-sized delay claim runs into the tens of thousands of dollars and can run well past that. Counsel is billed hourly, and the hours are not small. Neither is trivial against a mid-sized claim.

2. Internal cost — the one nobody budgets. Your project manager and field engineer will spend hundreds of hours retrieving documents, explaining the job, sitting for interviews, reviewing drafts, and preparing for depositions or hearings. At a loaded rate that is real money, and it appears on no invoice, which is exactly why it gets ignored.

3. Time value of money. A dispute that resolves in thirty months delivers dollars that are worth materially less than dollars today. Run it: $120,000 received in 2.5 years, at a 12 percent cost of capital, is worth about `$120,000 ÷ 1.12^2.5 ≈ $90,400` today. You just lost roughly $30,000 to the calendar — more than many claims' entire preparation budget.

4. The client relationship and future work. On a negotiated private job or a repeat public client, this can be the largest number on the page and it never appears in a spreadsheet. It is also frequently overstated by people who want to avoid a hard conversation: sophisticated owners generally do not blacklist a contractor for professionally pursuing a documented claim. What damages a relationship is a surprise claim, an inflated claim, or a claim delivered with theater.

5. Management distraction. This is the one that is genuinely underestimated. A claim consumes the attention of your best people — the same people you need running the next three jobs. There is no line item for a project executive spending 15 percent of a year on a closed project.

33.10.2 A decision framework, worked

Here is the arithmetic I actually run. A claim prepared at $400,000 on a completed project.

Step 1 — Value it honestly. Run §33.8's evaluation on your own claim as though you were the defendant. Suppose the realistic settlement range is $130,000 to $190,000; take the midpoint, $160,000.

Step 2 — Apply a probability of recovery. Not everything settles. Suppose 75 percent likelihood of a meaningful recovery: 0.75 × $160,000 = $120,000 expected value.

Step 3 — Discount it to today. Thirty months at 12 percent: ≈ $90,400.

Step 4 — Subtract the cost to pursue.

Read the table. Path A — the one that feels like justice — loses $52,600 and takes two and a half years. Path C, a well-prepared negotiation that settles for less money much sooner, nets the most. Path B is a reasonable fallback if C fails.

This is why experienced contractors settle. Not because they are soft, and not because their claims are weak. Because they did the arithmetic.

What would change the answer: a much larger claim (the fixed costs of pursuit stop dominating somewhere in the high six figures); a contractual fee-shifting provision; a claim so strong that the probability of recovery is near certain; an opponent with a track record of only paying at the courthouse steps; or a company-level need to signal that it does not roll over — which is a real business consideration and should be made consciously, at the executive level, not by a project manager who is angry.

33.10.3 The pursue / negotiate / absorb decision

🏗️ From the field. The best thing I ever did on a claim was not file one. We had roughly $210,000 of genuine exposure from an owner's slow decisions on a job that was otherwise going well. I put together the analysis anyway — six pages, three exhibits, honest — and took it to the owner's rep at the field level, in month nine, while everybody still remembered. We resolved it for $138,000 in eleven days, folded into a change order. Two years later that owner brought us a negotiated job worth twenty times the difference. I did not settle cheap. I settled early, which is a different thing, and the discount for early is smaller than the discount for late.

33.11 Avoiding Claims — This Entire Book in One List

Everything in the preceding thirty-two chapters points here.

And then the one that outranks all eight:

💡 Aha moment. The single best claims-avoidance practice in construction is settling issues while the people who know what happened are still on the project.

Everything expensive about a dispute is a function of elapsed time. Memories decay. People change companies. The superintendent who could have explained the sequence in ninety seconds is in another state. Documents get boxed. Positions harden, because after eighteen months of arguing, a person's identity gets attached to being right.

A disagreement resolved in month nine costs a conversation. The same disagreement resolved in year three costs six figures and buys the identical outcome. The facts do not get better with age. Only the legal bill does.

33.12 The Ethical Lines

Four of them, and each has a price attached.

1. The inflated claim. Take a genuine $300,000 claim and file it at $900,000 "to leave room." Every experienced evaluator recognizes it instantly, and the effect is the opposite of what is intended: the reviewer discounts your entire submission uniformly, including the $300,000 that was real. You do not create negotiating room. You destroy the credibility that would have gotten you the $300,000. File the number you can defend, defend it, and hold.

2. The claims-conscious contractor. Bid low, plan to litigate — win on price, then recover margin through claims. This is Curtis Boone's model, and I want to name it precisely because he does not think of it that way. Curtis does not sit down and decide to litigate. He bids sharp because he is confident, he staffs lean because staff is overhead, he documents little because he manages by relationship, and he assumes that when something goes wrong, he will work it out with the owner the way he always has. The claim strategy is not a plan; it is the residue of a business model, and it appears only when the model fails.

Two things to say about it. First, it is not illegal, and a contractor is entitled to bid its own number. Second, and more usefully: it does not work. Look at the ledger this book has kept on him — $153,000 unrecovered on the soils claim, $562,100 net on the coordination decision, and a final claim worth eleven cents on the dollar. Curtis is a skilled builder losing money on purpose, and he does not know it. The argument against the claims-conscious model is not primarily an ethical one. It is that it loses.

The deliberate version — a contractor who genuinely bids below cost intending to manufacture claims — is a different and worse thing. It is a fraud on the procurement process and it poisons the market for every honest bidder in the room.

3. Reconstructed documentation. Creating records after the fact and presenting them as contemporaneous. Backdating a daily report. Rebuilding a schedule update and dating it to the period it describes. Writing notice letters in month thirteen and letting them read as though they were sent in month six.

Do not do this, and understand exactly why beyond "it is wrong." It is discoverable — metadata, file creation dates, printer logs, email headers, the paper stock, the fact that a report references an event that had not happened yet. It converts a civil dispute over money into an allegation of fraud, which changes the insurance coverage, the bonding relationship, the licensing exposure, and in some circumstances the criminal exposure. And it destroys the entire claim, including every element that was legitimate. One fabricated document is worth more to your opponent than all of your genuine ones combined.

The honest alternative always exists and is always available: reconstruct openly. "Exhibit 14 is an as-built schedule prepared by the undersigned in March of Year 3 from daily reports and pay applications; it is a reconstruction and is identified as such." That is admissible, professional, weaker than a contemporaneous record, and infinitely better than the alternative. Curtis's nine notice letters, dated when they were actually written, are worth far more than nine backdated ones would have been — because the nine that exist are merely late, and the backdated ones would have been a fraud.

4. The owner who uses the cost of dispute as leverage. This one is on the other side of the table and it is real. An owner who knows a contractor cannot afford a two-year arbitration can deny a valid claim, offer thirty cents on the dollar, and be reasonably confident of the outcome. It is a rational strategy and it is an abuse of a structural power imbalance — and it is worse when directed at a small subcontractor with no working capital, where it shades into using nonpayment as a financing tool (Chapter 32).

If you work for an owner, this is your line to hold. If you work for a contractor facing it, your defenses are the ones this whole chapter has been building: documentation that makes the claim cheap to prove, notice that survives, remedies for nonpayment (Chapter 32), a dispute clause negotiated before you signed, and the honest evaluation that tells you whether their thirty cents is actually bad relative to your alternatives. Sometimes the answer is that thirty cents today beats sixty cents in three years, and knowing that is not weakness. It is arithmetic.

🪞 Learning check-in. Stop and take five minutes on this one. It is the halfway point of the project-controls part of this book and the material has gotten heavy.

First — a confidence calibration. Rate yourself 1 to 5 on each: (a) I could identify, on a live project today, which of the three proofs my strongest open issue is weakest on. (b) I could pick the right delay-analysis method given a described set of available records, and say why the others are unavailable. (c) I could tell a colleague what makes a delay concurrent, and what makes an alleged concurrency fail.

Second — the hard question. Everything in this chapter depends on records created before anybody knew they would matter. Think about a project you are on now or one you have worked on. If it went to a claim next month, what would you not be able to prove? Be specific. Name the document, the log, or the field that is missing or thin.

Third — notice how you felt about Curtis Boone. Most readers experience a flicker of contempt somewhere in this chapter. Sit with that for a second, because it is the most dangerous reaction available to you. Curtis is skilled, well liked, good in a crisis, and better in the field than most of the people reading this. He did not fail from laziness or dishonesty. He failed because a rational-looking economy — fifty-six hours of schedule updates — was invisible until the moment it was decisive. If you read this chapter and concluded "I would never be Curtis," you have learned nothing. The correct conclusion is "I need a system that makes it impossible for me to become Curtis on a busy month," and that system is a calendar reminder, a standing agenda item, and a one-page notice sheet taped inside your project notebook.

Now do one thing. Not seven. Pick the single weakest record on your current job and fix it this week.

Spaced Review

Answer these before you read the responses. Retrieval beats rereading, and this chapter's material only works if it is available under pressure.

From Chapter 32 — pending changes as a cash-flow problem. You are carrying $340,000 of pending change orders that the owner has neither approved nor rejected for ninety days. Name the two distinct harms this causes, and the remedies that exist for one of them but not the other.

From Chapter 29 — the delay taxonomy and time impact analysis. Without looking back: what are the three axes on which a delay is classified, and what does a time impact analysis insert, into what?

Deep callback to Chapter 5 — notice requirements are jurisdictional and unforgiving. Curtis Boone's differing-site-conditions claim at Rivermont Elementary was factually correct and recovered $61,000 of $214,000. What killed it, and what would ten minutes on day nine have been worth?

Project Checkpoint: The Willow Street Delay Analysis

In Chapter 32 you built pay application #6 with retention, the lien waiver package, and the cash-flow curve, and you saw the pending change orders sitting in your receivables like a stone. Now the schedule catches up with you.

The situation. Your month-6 schedule update from Chapter 29 shows the Willow Street Community Center — $6,800,000, 24,000 SF, 425 calendar days, liquidated damages $1,200 per calendar day, City of Rivermont Parks & Recreation — projecting 22 calendar days past the contract substantial completion date. Your general-conditions estimate from Chapter 13 was $680,000 over 425 calendar days, which is $1,600 per calendar day, giving a combined daily exposure of $2,800/CD. Build the delay analysis.

Deliverable — eight parts.

1. A windows analysis of the 22-day slip. Divide months 4, 5, and 6 into three windows using your monthly updates. For each window state: the projected substantial completion at the start and end, the slip in the window, which activity chain was critical during that window, the driving cause, and which party owns it. Make the critical path change at least once between windows — on a real job it always does, and the water-main relocation, the CMU-and-steel first floor, and the wood-framed second floor give you three genuinely different candidate paths.

2. Entitlement, clause by clause. For each delay event, name the contract provision you would rely on from the §33.2.1 categories, and state in one sentence what you would have to show under it. Where you are relying on an owner obligation, cite the specific obligation.

3. Causation. For each event, state the evidence that it drove the critical path — and state honestly where your evidence is thin.

4. Concurrency. Identify at least one period where two delays overlap, apply the three tests from §33.5.3, and reach a conclusion. Show the total-float figure you relied on and which update it came from. If your answer is "not concurrent because it had float," say how much float and where the number lives.

5. Damages. Compute extended general conditions at $1,600/CD for the compensable days only. Then add at least two other categories from §33.6 with their substantiation named. State the total, and state which liquidated-damages exposure your time extension eliminates: excusable days × $1,200/CD.

6. The exhibit index. Numbered, dated, described. Minimum fifteen exhibits. Every factual assertion in parts 1 through 5 must point at one. This is the part that will teach you the most, because you will find assertions you cannot exhibit — and each one is a hole in a real claim.

7. The executive summary. Two pages maximum, written for a Parks & Recreation director who has never read a CPM schedule. What happened, which clauses apply, how many days, how many dollars, and one sentence that makes it make sense.

8. The honest paragraph. One paragraph — the hardest thing in this notebook. What would you actually recover, and would you pursue it? Use the §33.10.2 framework: value it honestly, apply a probability, discount it, subtract the cost to pursue, and compare against negotiating early or absorbing it. Then say what you would do and why. If your answer is "settle it at the field level in month seven for less money," that is very likely the right answer, and saying so in writing is a mark of judgment rather than weakness.

Next chapter takes you up a level, from this project to the company that carries it: Chapter 34 puts Willow Street into a work-in-progress schedule, computes your over- and under-billing, and shows what this job does to Kestrel's bonding capacity. Your claim, unresolved, will show up there as a number that a surety underwriter reads very differently than you do.

Chapter Summary

The framework, in one table. This is the page to come back to.

The four numbers from this chapter worth memorizing:

⚠️ Once more, because it matters and because people skip endings. This chapter is a framework for recognizing issues and preparing work product. It is not legal advice. Notice requirements, claims procedure, the treatment of concurrent delay, the enforceability of no-damage-for-delay and liquidated-damages clauses, the recoverability of unabsorbed home-office overhead and interest, and the rules governing every forum in §33.9 vary enormously by jurisdiction and by contract, and they change. Read your own contract. Verify against current primary sources. Involve counsel early — the cheapest legal advice you will ever buy is the advice you get before you need it.

What's Next

Chapter 34 pulls the camera back from the project to the company. You will build a work-in-progress schedule, compute over- and under-billing, and see why a contractor can be profitable on every job and still run out of cash — which is the reason Owen Baptiste reads your cost report differently than you do, and the reason an unresolved claim on your balance sheet is a very different object to a surety underwriter than it is to you. Then Part VII takes you into specialized practice and technology, starting with what a coordinated model does to the RFI log that Curtis Boone never had.