Esc

↑↓ move↵ openIndex · Pagefind

How to calculate liquidated damages exposure and carry it in your forecast

Liquidated damages exposure is the days between your forecast finish and the adjusted contract date, times the daily rate, for each milestone that carries LDs, limited by any cap. The hard part is using honest inputs: approved extensions only, a forecast from the current schedule, pending requests and risk shown as separate scenarios. Here is the method and a worked example with two milestones.

Charley Forey7 min readSchedulingContractsProject controls
On this page
  1. Step 1: Read the LD clause properly
  2. Step 2: Work out the adjusted contract date for each milestone
  3. Step 3: Take the forecast finish from the current schedule
  4. Step 4: Count the days and apply the rate and cap
  5. Step 5: Show pending extensions, recoveries and risk as scenarios
  6. Step 6: Put it in the forecast and the WIP
  7. Step 7: Recalculate every update and act on it
  8. Worked example: two milestones, a cap and a pending request
  9. Common mistakes
  10. How os.construction handles it
  11. FAQ

Liquidated damages exposure is the number of days between your forecast finish and the adjusted contract date, times the daily rate, for each milestone that carries LDs, capped at any limit in the contract. Use approved time extensions only, take the forecast from the current schedule update, and show pending extension requests, subcontractor recoveries and schedule risk as separate scenarios beside the main number.

Liquidated damages are easy to calculate once a job is late and hard to forecast while there’s still time to act. That’s backwards. The exposure number is most useful months before completion, when it can justify a recovery schedule, push a time extension request up the priority list, or put an honest number into the margin forecast. This post covers the forecast. For whether an LD clause is enforceable, the glossary entry has the general rules, and the contract and your lawyer have the specific ones.

Step 1: Read the LD clause properly

Before calculating anything, get these from the contract:

  • The milestones. Usually substantial completion; some contracts add interim milestones, phases or final completion, each with its own rate.
  • The rate for each milestone, and whether it changes over time.
  • Calendar days or working days. This changes the count a lot over a holiday period.
  • The cap, if any, and what it’s measured against.
  • What starts and stops the count. The commencement date, how the completion date is fixed, and what certifies the milestone.
  • How extensions are requested: notice periods and the required analysis.
  • Whether LDs are the owner’s only remedy for delay, or whether other damages can be claimed too.

The notice to proceed template is a good place to record the commencement date, contract time and LD rate on day one.

Step 2: Work out the adjusted contract date for each milestone

adjusted date = contract milestone date + approved extension days

Only extensions granted by change order or another written instrument count. Requests you’ve submitted, however good, go in Step 5. If the contract uses working days, add extensions on the contract’s calendar.

Step 3: Take the forecast finish from the current schedule

Use the forecast milestone dates from the latest schedule update, with progress and logic current to the data date. If you know the update is optimistic, say because remaining durations haven’t been revised since a crew change, fix the schedule rather than adjusting the exposure by hand. The exposure number can only be as honest as the schedule behind it; how to run a cost-to-complete review makes the same point about cost forecasts.

Step 4: Count the days and apply the rate and cap

For each milestone:

days late = forecast date − adjusted date (in the contract’s day type, never below zero) exposure = days late × daily rate

Add the milestones together and apply the cap. Check whether milestones overlap: some contracts say interim LDs stop when a later milestone’s LDs start, or that interim LDs are credited against final ones. Follow the contract’s wording.

Step 5: Show pending extensions, recoveries and risk as scenarios

Keep the main number clean and put the uncertainty next to it:

  • Pending extension requests. Recalculate with each request granted, supported by a time impact analysis. The difference is what the request is worth, which tells you how hard to push it.
  • Subcontractor pass-through. If a subcontract flows LDs down for sub-caused delay and the delay can be traced to the sub, show the possible recovery separately. Don’t net it until it’s been assessed and you’re confident it can be collected.
  • Schedule risk. If you run a schedule risk analysis, calculate exposure at the P80 finish dates as well as the deterministic ones. A small deterministic number with a large P80 number is telling you the schedule has no margin.

Where owner and contractor delays overlap, the result depends on the contract and the law; concurrent delay covers the common approaches.

Step 6: Put it in the forecast and the WIP

LD exposure affects margin twice: the LDs themselves, and the extra general conditions for every week the job runs past the date the budget assumed. The general conditions calculator gives you the weekly cost of a delay.

For revenue recognition, expected liquidated damages are generally treated as variable consideration that reduces the contract price, not as a cost. That reduces revenue and margin on the WIP schedule. How much to record is a judgment for your accountant, so send them the calculation, the scenarios and the schedule update it came from.

Step 7: Recalculate every update and act on it

Recalculate with every schedule update and track the trend. If exposure is growing, the options are a recovery schedule, better-supported extension requests, or both. On calendar-day LDs, every week of delay recovered is worth the daily rate times seven, plus a week of general conditions, which is a useful number to have when deciding whether overtime or an extra crew pays for itself.

Worked example: two milestones, a cap and a pending request

Illustrative numbersA made-up contract. Rates, dates and amounts are examples, not typical values.

A $12,000,000 contract has two LD milestones, both counted in calendar days, with total LDs capped at 5% of the contract sum, $600,000:

  • Milestone A, parking deck substantially complete: $1,500 per day, contract date March 31, 2027.
  • Milestone B, building substantially complete: $4,000 per day, contract date August 31, 2027.

Approved change orders have granted 5 days on A and 12 days on B. The November schedule update forecasts A on April 19, 2027 and B on October 10, 2027.

Milestone Contract date Approved days Adjusted date Forecast Days late Rate Exposure
A Mar 31, 2027 5 Apr 5, 2027 Apr 19, 2027 14 $1,500 $21,000
B Aug 31, 2027 12 Sep 12, 2027 Oct 10, 2027 28 $4,000 $112,000
Total $133,000

$133,000 is under the $600,000 cap, so the cap doesn’t bite.

Scenarios. The GC has a pending request for 15 days on B for a late owner design change to the curtain wall, supported by a time impact analysis. The schedule risk analysis puts A at April 26 and B at October 24 at P80. And the precast supplier’s late deliveries caused 6 of A’s 14 days, under a subcontract that flows LDs down for sub-caused delay.

Scenario A days A exposure B days B exposure Total
Current forecast, approved extensions only 14 $21,000 28 $112,000 $133,000
Pending 15-day request on B granted 14 $21,000 13 $52,000 $73,000
P80 finish dates, approved extensions only 21 $31,500 42 $168,000 $199,500

The pending request is worth $133,000 − $73,000 = $60,000, which is why it goes to the top of the PM’s list. The possible pass-through from the precast sub is 6 × $1,500 = $9,000, shown as a note, not deducted.

Milestone B: from contract date to forecast and P80A timeline for milestone B. The contract date is August 31. Twelve approved days move the adjusted date to September 12. The forecast is October 10, 28 days late, an exposure of 112,000 dollars. The P80 date is October 24, 42 days late, an exposure of 168,000 dollars.AUG 31CONTRACTSEP 12ADJUSTEDOCT 10FORECASTOCT 24P80+12 DAYS28 DAYS: $112,00042 DAYS: $168KONLY THE DAYS AFTER THE ADJUSTED DATE COST LDs
Exposure runs from the adjusted date, not the original one. Not to scale. Illustrative.

What it does to margin. The budget carried $11,040,000 of cost, an 8% margin on $12,000,000. On the current forecast, LDs reduce the contract price to $12,000,000 − $133,000 = $11,867,000, and four extra weeks of general conditions at $14,000 a week add $56,000 of cost, for $11,096,000. Profit falls from $960,000 to $11,867,000 − $11,096,000 = $771,000, a margin of about 6.5%. The delay costs $189,000 of profit, $133,000 in LDs and $56,000 in time-related cost.

That’s the number that goes to the recovery discussion. If a second crew on the curtain wall for six weeks costs less than the LDs and general conditions it saves, it’s worth doing whether or not the pending request is granted.

Common mistakes

  • Counting pending requests as approved. The contract date moves when the change order is signed.
  • Using the original contract date and forgetting the approved extensions, which overstates exposure.
  • Calendar days and working days mixed up. Check the clause and count the right way.
  • Forgetting interim milestones, which can run LDs long before substantial completion.
  • Ignoring the cap, or applying it to the wrong base.
  • Netting sub pass-through before it’s been assessed and can be collected.
  • Leaving out time-related cost. Extended general conditions are often as large as the LDs.
  • Missing notice deadlines for extensions while waiting to see whether the delay matters. See extension of time and how to document weather delays.

This is general information, not legal advice. Enforceability of liquidated damages, time extension rules and the treatment of concurrent delay vary by contract and jurisdiction.

How os.construction handles it

In the Schedule, contract milestones can carry contract-date constraints and baselines keep the original dates, so each update shows how far a milestone has moved. Risk analysis runs a Monte Carlo simulation from three-point durations and a risk register and reports finish percentiles from P10 to P95, including P80, for up to 20 key dates. The LD calculation itself, rates, caps and scenarios, is spreadsheet work today. For the wider tool, see construction scheduling software.

FAQ

How do you calculate liquidated damages?

Take the milestone date in the contract, add any approved time extensions to get the adjusted date, and count the days from the adjusted date to the actual or forecast completion, in calendar or working days as the contract specifies. Multiply by the daily rate, repeat for each milestone that carries LDs, and limit the total to any cap in the contract.

What is LD exposure?

LD exposure is the amount of liquidated damages you would owe if the job finishes on your current forecast. It's a forecast, not an assessment, and it changes with every schedule update, every approved extension and every recovery.

Should pending time extension requests reduce LD exposure?

Not in the main number. Carry exposure on approved extensions only, and show the effect of pending requests as a separate scenario. A request that's well supported may well be granted, but until it is, the contract date hasn't moved.

How do liquidated damages affect the WIP schedule?

Under ASC 606, liquidated damages are generally treated as variable consideration that reduces the contract price, rather than as a job cost. That lowers revenue and margin on the WIP. How much to record and when is a judgment for your accountant, so share the exposure calculation with them each month.

Can liquidated damages be passed down to subcontractors?

Often, if the subcontract says so and the delay can be traced to the sub. Treat that as a possible recovery shown separately, not as an offset you can count on, because it depends on the subcontract's terms, the evidence and the sub's ability to pay.

Share this article

Written by

Charley Forey

Founder of os.construction. We're building the operating system for construction. Project Financials follows job money, and company Accounting covers the books and controls. AI agents remain planned. We write about how money and data actually move on a job, and we build in public.

Apply to the founding program →Start a free trial →
Keep readingAll articles →
Project controls

Earned value vs percent complete: one measures progress, the other tells you what it means

Percent complete says how much of the work is done. Earned value turns that progress into the budgeted value of the work done, so it can be compared with the plan and with what was spent. Here is how the two relate, when to use each, a worked example and the mistakes that make every job look on budget.

5 min read

Scheduling

How to create a work breakdown structure for a construction project

A work breakdown structure splits the whole scope of a job into pieces you can schedule, budget and measure. Choose the split that matches how the job will be built, decompose to work packages one party can own, check the 100% rule, write a WBS dictionary, then tie the WBS to cost codes and schedule activities. Here is the method and a worked example for a three-story office building.

6 min read

Subcontracts

How to track subcontractor certificates of insurance: collect, review, renew, hold

Collecting a COI once at award isn't tracking. Here is a routine for subcontractor insurance: set the requirements in the subcontract, review certificates and endorsements against them, log every policy's dates, chase renewals before they lapse, and connect it all to payment, with a worked renewal calendar.

5 min read

Open file