Case Study 33-2 — The Claim That Was Never Made

Kestrel had the records, ran the analysis properly, and found out the delay was its own. What the decision not to file bought — with Meridian, with Caldwell Structural, and with Ironbridge Steel

⚠️ This case study is a framework for recognizing and preparing issues. It is not legal advice. Entitlement, concurrency doctrine, damages recoverability, and notice requirements vary enormously by jurisdiction and by contract, and they change. Nothing here tells you whether a claim on similar facts would succeed where you work. Every person, firm, and project in this story is a composite. Involve counsel early.

Setup

Project: Northgate Outpatient Pavilion — 132,000 SF, four stories, CM at Risk with a $47,500,000 guaranteed maximum price for Meridian Health System. 565 calendar days, notice to proceed March 3, Year 1, contract substantial completion September 18, Year 2.

The rates: extended general conditions $5,150 per calendar day, liquidated damages $5,500 per calendar day, combined exposure $10,650 per calendar day.

The people: Ray Alvarez, senior project manager, narrating. Wei Chen, project controls manager, who runs the analysis. Nadia Haddad, vice president of operations, who decides. Hank Duffy at Ironbridge Steel, the structural steel subcontractor — 985 tons erected. Ruth Caldwell at Caldwell Structural, the structural engineer of record, engaged by Meridian. Pri Sethi, Meridian's owner's representative.

The event, in one sentence: the anchor-bolt and embed submittal sat 11 days in Kestrel's own office before it went to Caldwell Structural, Caldwell then took its full 14-day contractual review, Ironbridge missed its mill rolling slot, the next mill opening was five weeks out, and steel erection start slipped 23 calendar days — August 4 to August 27, Year 1 — on a chain that was squarely on the critical path.

At that point Kestrel has a documented 23-day slip, a $244,950 exposure, and a project executive asking whether there is a claim here. So we ran one.

What Happens

The analysis

Wei Chen built the submittal chain against Kestrel's own document control procedure, which allows three calendar days in-house to log, review, and transmit, and two calendar days to return an approved package to the subcontractor.

Two things in that table deserve a second look.

The mill slip was 35 days and the erection slip was 23. Hank Duffy's shop swallowed twelve of them — resequenced detailing, the first two erection sequences run out of order, a second shift on the shop floor. That is twelve calendar days Kestrel did not pay $10,650 apiece for, performed by a subcontractor who had every reason to be unhelpful.

The planned chain held the mill slot by one day. Not eight. One. Which is a separate lesson about the review durations Kestrel accepted at buyout, and a genuinely uncomfortable one.

The two but-for tests

This is a collapsed as-built in miniature: build what actually happened, then remove one event at a time and see whether the outcome changes.

Test 1 — remove Kestrel's eight excess days. Transmit on March 31 as the procedure requires. Caldwell's full 14 days returns it April 14. Kestrel returns it April 16. Ironbridge releases the mill order April 16 — one day inside the cutoff. The slot holds. The slip is zero.

Test 2 — remove Caldwell's speed instead. Leave Kestrel's 11 days in place and give Caldwell a review faster than the contract requires. At 10 calendar days — quick by any standard — the order releases April 20, still three days past the cutoff. Caldwell would have had to return a 985-ton frame's anchor-bolt package in seven days, exactly half its contractual review, to land on the cutoff with zero margin.

Kestrel's eight days are both necessary and sufficient. Caldwell's review speed is neither.

The three proofs, run against ourselves

The damages were never the weak part. They never are.

The arithmetic says acceleration saves $13,050 against doing nothing — nearly a wash. What actually decided it was that Meridian's leased interim clinic space expires October 1, Year 2. Six days late is survivable. Twenty-three is not. Kestrel accelerated, and paid the non-monetary bill for it too: trade stacking, a rework event on deck-edge detailing, and a spike in near-misses in weeks 34 through 36, including the scaffold incident on the north elevation.

The argument in Nadia's office

It was not a short meeting, and it should not have been.

The contracts manager, for pursuing anyway: "Fourteen days on an anchor-bolt package for a 985-ton frame is slow, contractual or not. We don't have to win it. We file, Meridian doesn't want an open claim while their clinic lease is running out, and it settles for something. We just spent $168,000. Owen is going to ask me why none of it is coming back."

Wei Chen: "Then the first thing their consultant does is pull our submittal log, because we gave it to them — it's in the document control portal they have access to. The eleven days are date-stamped. It takes an hour."

Nadia: "That's the whole answer, but say the rest of it out loud."

Ray: "The rest of it is that we're going to be asking Meridian for time in about ten months. Every job does. If the first thing they learn about how we build a delay claim is that we filed one we knew failed causation, then when we bring them a real one they discount it by the same percentage they discounted this one. I'd rather spend the credibility on the claim that's true."

Nadia: "Price it anyway. I don't want to make this decision on principle. I want to make it on principle and arithmetic, and if the arithmetic disagreed I'd want to know that too."

It loses on the spreadsheet before anybody gets to the part about credibility. That is the ordinary case, and it is worth noticing how ordinary it is.

Decision: no claim. And then the second half of the decision, which is the half that mattered.

Analysis — What the Decision Bought

A decision not to file is worth nothing if it is silent. Kestrel spent the position rather than banking it, and spent it in three directions in the same week.

With Meridian

Ray took Pri Sethi a one-page memo in week 22 — before she asked, which is the entire point. It said: here is the 23-day slip, here is the submittal chain that produced it, eleven of those days are ours in the most literal sense — the package sat on a desk in our office — here is the recovery plan, here is the $168,000 we are spending on it, and we are not asking you for any of it.

Ten months later, in April of Year 2, Meridian rejected Kestrel's request for a time extension on the imaging suite. Wei Chen ran the three-window analysis at the May 1 data date: 29 days of slip, 11 compensable, 7 concurrent, 11 non-excusable and ours. Kestrel submitted all three columns on the same page as the ask.

Meridian granted 18 calendar days in about three weeks — no consultant on either side, no lawyer in the room. Pri told me afterward what actually moved it internally, and it was not the windows analysis. It was that Kestrel handed over eleven non-excusable days it had not been asked about. Nobody believes a party that has never conceded anything. That is §33.7.2's "include the bad facts," and week 22 of Year 1 is where Kestrel bought the right to be believed.

With Caldwell Structural

Ray called Ruth Caldwell, told her what the analysis found, told her Kestrel was not pursuing it — and then told her the uncomfortable half too: that fourteen days on a critical-path anchor-bolt package hurt, even though it was entirely within her rights.

Ruth's answer was better than a claim would have been. Caldwell and Kestrel put in a flagged-package protocol: Kestrel marks a submittal on the transmittal with the driving schedule activity, the date the response is needed to protect it, and a one-line reason; Caldwell targets five business days on those and calls before returning anything that will miss. Across the several hundred packages left in the log, flagged reviews ran near that target for the rest of the job.

None of that was contractually available to Kestrel. All of it was available for the price of a phone call that did not contain a claim.

With Ironbridge Steel

Ironbridge's shop resequencing — the twelve days Duffy absorbed — produced a documented premium of $38,400. Whether the subcontract obliged Kestrel to pay it was genuinely arguable. Kestrel paid it on a change order in eleven days without arguing, because Kestrel had caused the problem and knew it. (That figure sits outside the accelerate-or-absorb comparison above; it was spent before that decision was framed.)

Six weeks later, when the acceleration needed a second erection crew on eleven days' notice, Hank Duffy found one. He did not have to. And Ironbridge's numbers on Kestrel's next two pursuits came in sharp — not as a favor, but because a subcontractor who expects to be paid when something goes sideways prices less risk into the bid. That is Chapter 16's argument arriving eighteen months later with a dollar sign on it.

The uncomfortable part, said plainly

This decision was expensive. Kestrel spent $231,900 on the accelerate-and-absorb path plus $38,400 to Ironbridge, recovered none of it, and absorbed the safety consequences of an acceleration it caused. I would make the same call again — and "I would do it again" is not the same sentence as "it was free."

And here is the thing worth carrying out of both case studies at once. Curtis Boone's bad records let him believe for eleven months that he was owed $1,375,800. Kestrel's good records told it, in about four hours, that it was owed nothing. Documentation is not a weapon you point at the other side. It is an instrument, and an instrument reports the truth whichever direction the truth happens to run. Good claims discipline includes knowing when you do not have one — and the only way to know that is to have kept the records that could have told you either answer.

Discussion Questions

1. Test 1 shows the mill slot would have held by one day if Kestrel had followed its own three-day in-house procedure. Is a one-day margin a defense, an indictment, or both? What would you have changed at buyout, and what would that change have cost?

2. The contracts manager's argument — we don't have to win, we have to make it expensive enough to settle — is not stupid and it is not rare. Argue it as strongly as you can, then say precisely where it fails on these facts. Would it fail on a job where Kestrel expected never to work for the owner again?

3. Kestrel disclosed eleven non-excusable days it had not been asked about. Name the mechanism by which that increased what Meridian granted, and describe a situation in which that disclosure would have been a mistake.

4. The Caldwell flagged-package protocol was not contractually available. Write the clause you would put in a scheduling specification to make something like it contractual — then argue the other side: why an engineer would refuse it, and what they would want in return.

5. Kestrel paid Ironbridge $38,400 it arguably did not owe. Evaluate that as a business decision rather than a moral one: what is the return, over what horizon, and how would you defend it to a CFO reading only this job's cost report?

Your Turn

Take an issue on a project you know — live or finished — where you believe you were owed something and never pursued it.

Do four things.

1. Build the chain. One row per step, with the planned date, the actual date, and the variance, running from the triggering document to the impact. Use only records that existed at the time.
2. Run two but-for tests. Remove your own contribution and recompute the outcome. Then remove the other party's contribution and recompute. State which removals change the answer, and be prepared for the possibility that only yours does.
3. Run the three gates against yourself — entitlement, causation, damages — and write the finding for each in one sentence, as though you were the party being asked to pay.
4. Price the pursuit. Expected value against consultant, counsel, and internal hours at a loaded rate, netted out.

Then write the one-page memo you would have delivered in the week it happened — the week-22 memo, not the year-three claim. If the analysis says the issue was yours, the memo says so in the first paragraph and states what you are doing about it.

Deliver it, if the project is still live. The version that stays in your notebook teaches you the analysis. The version you hand to somebody teaches you what it is worth.