What Is a Liquidated Damages Clause?

What the clause actually does

Normally, when someone breaks a contract, the other side has to prove what the breach cost them. That means producing records, sometimes expert testimony, and arguing about which losses really flowed from the breach. It is slow, and on smaller deals the proving can cost more than the loss.

A liquidated damages clause skips that step for one named obligation. It says: if this particular thing happens, the amount owed is this figure. No proof of loss, no argument about the calculation, just the number the parties wrote down in advance. That is the whole mechanism. Everything else about these clauses is detail stacked on top of it.

Why parties use one

Three reasons, worth separating because they pull in different directions.

The loss is real but hard to measure. A retail center that opens two months late, a confidential formula that leaks, a key person poached the week before a launch. Everyone agrees there is damage. Nobody can put a defensible number on it afterwards without a fight. Fixing it up front removes the fight.

Both sides can price the risk. A builder who knows the exposure is a stated daily rate can put that in the bid and decide what to spend on protecting the schedule. An unknown, unbounded exposure cannot be priced at all, so it gets either ignored or padded.

It can work as a ceiling. This is the part people miss. When the clause says the amount is the sole and exclusive remedy for that breach, it is written to close off the open-ended version of that exposure rather than to add to it. That is why a liquidated damages clause is not automatically a term to resist.

Why the number is written the way it is

These clauses are drafted as a forecast, not as a fine. The drafter is trying to write down what the loss would plausibly be, estimated at the time of signing, for a loss that would be difficult to calculate later. That is why the figure is usually tied to something the other side can point at: carrying costs per day of delay, the monthly fee for a service that was not delivered, the cost of replacing a person.

You will often see a recital sitting right next to the number, saying something like: the parties acknowledge that actual damages would be difficult or impossible to determine, and agree this sum is a reasonable estimate of them. That sentence tells you how the number was framed and what the drafter was aiming at. It is a statement of intent rather than a guarantee of anything, and what a court would eventually make of any particular figure depends on state law and on facts specific to the deal. That question belongs to a lawyer, not to a web page.

The practical version: a number that traces back to a real cost the other side can explain is a number you can negotiate about. A number nobody can explain is worth asking about directly. “How did you arrive at the daily figure?” is a completely ordinary question, and the answer tells you a lot about whether the clause is movable.

Where you run into them

They rarely carry the label. Look for a fixed sum attached to one specific failure.

• Construction and build contracts. A per-day rate for finishing past the completion date. This is the most explicit version you will see.
• Service level agreements. Service credits for downtime, very often written as the sole and exclusive remedy for the outage.
• Early termination fees. A set amount for ending a lease, a subscription or an equipment agreement before the term runs out.
• Training repayment agreements. A fixed sum an employee repays for leaving within a set window after paid training or a certification.
• Non-solicit and placement fees. A stated fee if a client hires a contractor or a staff member directly instead of through the agreement.
• Confidentiality agreements. A fixed amount per disclosure, which is one of the classic hard-to-measure losses.
• Property purchases. Forfeited deposits and earnest money, where the deposit itself is the pre-agreed figure.

Eight things to check about the number

This is the part you can act on. Work through these against the clause in front of you, in this order. The first four decide how big the risk is. The last four decide how easily it can be applied to you.

What to ask for before signing

Asking for the clause to be deleted usually fails, because the other side put it there for a reason they can defend. Asking for boundaries around it usually works. In rough order of how often they are granted: a grace period before the amount starts running, an aggregate cap on the total, an extension of time when the delay traces to something on their side, and language making the amount the exclusive remedy for that breach so it works as a ceiling rather than a floor. Each of those is a one-sentence edit, which is a large part of why they get approved.

If you have already signed

Work from the document rather than from the worry. Read the trigger literally and check whether the event it describes has actually happened as defined, because these clauses often turn on a milestone date or a notice step that nobody completed. Find the cap, so you are working with the outside number instead of imagining it. Check whether the clause is exclusive. Then keep a dated written record of every dependency you are waiting on from the other side, and follow any notice requirement in the clause exactly, since a deadline missed inside the clause can cost more than the facts underneath it.

If the sum is real money, this is a good use of an hour with a lawyer. Bring the clause, a timeline, and your specific question. That is a much cheaper hour than handing over the whole agreement and asking what they think of it.

Where we fit

StraightTerms runs a fixed pass over the whole document and reports what it finds, including fixed-sum clauses like this one and the surrounding terms that change their size, such as the limitation of liability and its list of exclusions. Every finding quotes the exact clause it refers to, so you can hold it against your own copy rather than taking it on trust.

Your first review is free with no signup, and after that an email unlocks three a month. This is AI analysis and not legal advice, and on anything with real money attached the point is to arrive at a lawyer with specific questions rather than to skip one.

Common questions

What is the difference between liquidated damages and a penalty?

In ordinary speech people call anything a penalty if it costs money when something goes wrong. In contract law the word is a term of art, and whether a particular figure falls on one side of that line is a state-specific, fact-specific question that turns on what the parties knew when they signed. No web page can tell you where your number lands. What you can do is look at how the amount relates to the loss it stands in for, and if the sum is meaningful, put the clause itself in front of a lawyer.

Why would I agree to a fixed amount instead of actual damages?

Because a known number is easier to plan around than an unknown one, and because proving actual damages is slow and expensive for whoever has to do it. A clause written as the sole and exclusive remedy for that breach is drafted so the fixed amount is the ceiling as well as the exposure, which is why the structure is not automatically bad for the paying side. If it is written to sit on top of every other remedy, you get the certainty of the number without the ceiling, and that version is worth pushing back on.

Does a liquidated damages clause mean I cannot be sued for more?

That turns on the wording rather than on the label. The words to look for are sole and exclusive remedy, usually sitting right there in the same clause. Without them, the fixed sum reads as one recovery among several rather than as the end of the conversation. This is the most commonly missed detail in the whole clause, because the number is what draws the eye.

Is there a normal amount for liquidated damages?

There is no single figure, because the amount is meant to track the specific loss it stands in for. Construction paper often uses a daily rate tied to what the owner spends while the building sits unfinished. Software agreements often use service credits set as a share of the monthly fee. The useful test is not whether your number matches an industry benchmark but whether the other side can explain how they arrived at it.

What if the delay was caused by the other side?

Check the clause for excusable delay or extension of time language, which is how a well-drafted version handles exactly that. If your contract has it, follow its notice requirements precisely, because those provisions usually require you to raise the delay in writing within a set window. If it does not have it, that is the edit to ask for before signing, and in the meantime keep a dated written record every time you are waiting on them.

I already signed one and I think it might get triggered. What now?

Start with the text rather than the dread. Read the trigger literally and check whether the event it describes has actually happened as defined, find any cap so you know the outside number, check whether the clause is exclusive, and gather dated evidence of anything on their side that contributed. Follow any notice provision in the clause exactly, since a deadline missed inside the clause can cost you more than the facts underneath it. If the amount is real money, this is the point to spend an hour with a lawyer, and arriving with the clause and a timeline makes that hour far cheaper.