How to price a late-delivery penalty into a quote
A $600-a-day delay clause added $3,063 to the quote that keeps 80% margin confidence. How to price the clause, and which negotiating lever moves it most.
Short answer Apply the clause to every simulated finish, add the penalty to that run’s cost, and read your quoting percentile off the combined total. Adding the average penalty to the P80 cost underprices it, because the late runs are also the expensive ones. Then negotiate in this order: the date, the grace period, the rate, the cap.
- Chance of owing a penalty
- 45.5%date at day 42
- Expected penalty
- $1,161cap $8,500
- Penalty in a bad run (P95)
- $4,800P90: $3,600
- Added to the P80 quote
- +$3,063$85,041 → $88,104
What a delay clause costs you
A late-delivery clause turns a finish date into a cost. The usual shape has three parts: a grace period before anything is owed, a rate per day after it, and a cap on the total. In symbols, with days counted in whole days:
penalty = min(cap, rate × max(0, days late − grace))
So the clause is not a fixed cost. It is zero in most good runs, grows steadily in the late ones, and flattens at the cap. That shape, a lump of probability at zero and a tail to the right, is exactly what an average hides. (This note is about pricing the exposure as written. Whether a clause is enforceable, and how it should be drafted, depends on the jurisdiction and the contract; have a lawyer review it.)
A worked example: a rollout with a client date
A five-task rollout for a client who wants it live on day 42. The contract carries a clause of $600 a day after a 3-day grace period, capped at 10% of an $85,000 price, so the most you can owe is $8,500.
| Task | Days (low / likely / high) | Cost a day | Starts after |
|---|---|---|---|
| Discovery & design | 5 / 7 / 12 | $900 | – |
| Core build | 14 / 20 / 34 | $1,000 | Discovery |
| Data migration | 6 / 10 / 22 | $850 | Discovery |
| Integration & UAT | 7 / 10 / 20 | $900 | Build, migration |
| Training & go-live | 3 / 4 / 9 | $800 | Integration |
Inputs. Project fixed costs $3,000 and overhead $5,000. Beta-PERT (λ = 4), 100,000 runs, fixed seed, durations in calendar days. Quote = P80 cost ÷ 0.75 (25% margin). Illustrative figures. Figures are rounded for display, so recomputing from the rounded values can differ by a dollar or two.
Simulated, the project finishes in a median of 44.5 days, with a P80 of 48.6 and a P90 of 50.8. A client date of day 42 sits near the 30th percentile, which is what you get when the date comes from the client rather than from your schedule.
Figure 1. Top: when the project finishes, split by what the clause does about it. Bottom: what the clause costs at each finish day, on the same axis.
Only 29.9% of runs finish on time. A further 24.7% are late but inside the grace period, so they cost nothing. The other 45.5% owe $600 a day, and the cap is reached in about 0.1% of runs.
| Measure | Value |
|---|---|
| Chance of finishing late at all | 70.1% |
| Chance of owing a penalty (late beyond grace) | 45.5% |
| Expected penalty, averaged over all runs | $1,161 |
| Penalty in a bad run: P90 / P95 | $3,600 / $4,800 |
| Chance of reaching the cap | 0.13% |
Add it to each run, not to the average
The expected penalty is $1,161, so it is tempting to add that to the P80 cost and quote. The result is $86,589. The correct way is to apply the clause to each simulated run, add the penalty to that run’s cost, and then take the P80 of the combined total: $88,104. The difference is $1,515, and it exists because late runs are also expensive runs. A project that overruns its schedule burns more days of cost, so the penalty lands in the same runs that already sit at the top of the cost distribution.
Against the quote you would have given without the clause, $85,041, the clause adds $3,063 (3.6%). Ignore it and send $85,041 anyway, and the chance of earning your 25% margin falls from 80% to 71.2%. The same thinking, applied to the deadline alone, is in deadline confidence without padding.
Negotiate in this order
Each lever attacks a different part of the exposure, which is why they are not equally useful.
| Clause | Chance of owing | Expected penalty | P95 penalty | Quote increase |
|---|---|---|---|---|
| As written | 45.5% | $1,161 | $4,800 | +$3,063 |
| Client date + 5 days | 13.1% | $237 | $1,800 | +$266 |
| Grace period 10 days | 6.4% | $102 | $600 | +$37 |
| Rate halved to $300 | 45.5% | $581 | $2,400 | +$1,506 |
| Cap cut to 5% ($4,250) | 45.5% | $1,064 | $4,250 | +$3,062 |
Figure 2. How much the clause adds to the P80 quote under each change. The grey note at the right is the chance of owing anything.
The date and the grace period remove most of the cost because they attack the probability of owing. The rate halves the cost because it attacks the size. The cap barely moves the P80 quote because it only bites in the far tail.
That last point matters. A cap does not make the quote cheaper, but it halves the worst case, from $8,500 to $4,250. A date or grace concession is price insurance; a cap is survival insurance. Ask for the date first, because moving it five days removed 91% of the quote impact here, and then for a cap you can live with.
When the clause is a reason to walk away
Two questions decide it. Is the capped worst case survivable? Here $8,500 is 40% of the $21,260 margin in the quote. And is the chance of owing something acceptable? 45% is nearly one project in two. If the date cannot move and the answer to either question is no, the right price may be a lot more than $88,104, or no bid at all; the death spiral shows what one badly priced commitment does to the rest of the work.
Doing it in BidVariance
BidVariance reports deadline confidence and the finish-date percentiles; it does not apply penalty clauses itself. A workable approximation: set the promised date to the end of the grace period (day 45 here) and read the deadline confidence, which is the chance of owing nothing, 54.5%. Then add a project-level risk with a probability of 45.5% and a cost range of $600 / $2,400 / $8,500 (the first day owed, the typical penalty when one is owed, and the cap) and read the P80 again.
That gives $87,236 here: closer than ignoring the clause ($85,041) or averaging it ($86,589), and a little below the exact $88,104, because a risk event does not know its penalty arrives in the expensive runs. It is good for the order of magnitude, not for the last dollar. The free deadline confidence calculator gives the on-time chance for a single block of work, and the app does it for the whole task network.
Frequently asked questions
How do you price a late-delivery penalty into a fixed-price quote?
Simulate the finish date, apply the clause (grace period, daily rate, cap) to each run, add that penalty to the run’s cost, and read your usual percentile off the combined total. In the worked example the clause raised the P80-based quote from $85,041 to $88,104.
Can I just add the expected penalty to my price?
It underprices the clause. Late runs are also the expensive runs, so the penalty and the cost overrun arrive together. Adding the average penalty to the P80 cost gave $86,589 in the example, against $88,104 when the clause was applied run by run.
Does a cap on the penalty reduce my quote?
Barely. A cap only bites in the far tail, so cutting it to 5% left the quote increase at $3,062 instead of $3,063. It does cut the worst case in half, from $8,500 to $4,250, which is what protects you from a ruinous outcome.
Which part of a delay clause is worth negotiating first?
The date. Moving the client date by five days cut the chance of owing from 45.5% to 13.1% and removed about 91% of the quote impact. A longer grace period is the next most effective lever.
Are delay penalties and liquidated damages enforceable?
That depends on the jurisdiction and on how the clause is drafted, so it is a question for a lawyer. This note covers only how to price the exposure as written; it is not legal advice.