Liquidated Damages Clause: Workflow & Checklist约定损害赔偿条款：商业评估流程与清单

A commercial workflow, not a number copied from precedent这是一套商业流程，不是从范本复制一个数字

A liquidated damages clause sets an agreed amount or formula for a defined breach. Its practical value is predictability: the parties can price a known consequence, reduce arguments about measuring loss, and give delivery teams a visible performance signal. Its practical risk is false precision. A percentage that looks simple may be disconnected from the expected harm, triggered by the wrong event, duplicated by another remedy, or impossible to administer with available data.

约定损害赔偿条款针对明确违约预先约定金额或公式。它的商业价值在于可预测性：双方可以为已知后果定价，减少损失计量争议，并给交付团队清晰的履约信号。它的商业风险在于“虚假精确”：看似简单的比例可能脱离预期损失、由错误事件触发、与其他救济重复，或者因缺少数据而无法执行。

Treat the clause as a cross-functional design decision. Business owners define the protected outcome; finance builds the loss model; operations validates measurement; procurement or sales tests market acceptability; insurance specialists check coverage; and qualified legal reviewers assess the wording under the chosen law. The output should be a traceable decision record, not merely a redlined paragraph.

应把该条款视为跨职能设计决策。业务负责人定义需要保护的结果，财务建立损失模型，运营验证计量方式，采购或销售测试市场可接受性，保险人员核对保障范围，具备资质的法律人员则依据适用法律审核文字。最终产物应是可追溯的决策记录，而不只是修订过的一段条文。

Decide whether the mechanism fits the deal先判断该机制是否适合这笔交易

The mechanism is most useful when a specific failure could cause real loss that is difficult or expensive to calculate after the event, while the parties can still make a reasonable pre-contract estimate. Typical candidates include late completion of a revenue-producing facility, missed migration milestones, failure to meet a measurable service level, delayed delivery that disrupts a production line, or failure to close a time-sensitive transaction.

当特定失败会造成真实损失，事后计算又困难或成本高，而双方在签约前仍能作出合理估计时，该机制最有价值。常见场景包括产生收入的设施延期完工、迁移里程碑未完成、可衡量服务水平未达到、延迟交付导致生产线中断，或具有严格时效的交易未按期交割。

It may be a poor fit when the protected harm is easy to prove through ordinary records, the trigger depends mainly on subjective dissatisfaction, the amount is designed only to pressure performance, or one formula is expected to cover several unrelated failures. Before drafting, record the business objective, the uncertainty being reduced, why another remedy is insufficient, and which party can control the triggering risk.

如果损失很容易通过普通记录证明、触发主要依赖主观不满、金额只是为了施加履约压力，或者一个公式被要求覆盖多个无关失败，该机制可能并不合适。起草前应记录商业目标、希望减少的不确定性、其他救济为何不足，以及哪一方能够控制触发风险。

Collect the evidence behind the commercial position收集支持商业立场的证据

Start with the full agreement set and the operating plan, not the clause in isolation. Gather scope, milestones, acceptance criteria, dependencies, assumptions, price, margin, forecast revenue, replacement cost, financing cost, staffing, inventory exposure, downstream commitments, insurance, historical incidents, and mitigation options. Separate facts from estimates and identify the owner, date, and source for every material input.

应从完整协议和运营计划开始，而不是孤立看条款。收集范围、里程碑、验收标准、依赖、假设、价格、利润、预测收入、替代成本、融资成本、人员、库存风险、下游承诺、保险、历史事件与减损方案。把事实与估计分开，并为每项重要输入记录负责人、日期和来源。

Build at least three scenarios: expected, credible downside, and severe but plausible. For each, identify the sequence from breach to operational disruption to financial consequence. Remove losses that would occur anyway, could be avoided through reasonable mitigation, are already compensated elsewhere, or have no reliable connection to the trigger. This disciplined input pack makes negotiation faster because the team can explain why the mechanism exists.

至少建立预期、可信下行和严重但合理三种情景。逐一识别从违约到运营中断再到财务后果的链条。剔除本来就会发生、可通过合理减损避免、已经由其他机制补偿或与触发没有可靠联系的损失。规范的输入资料包能让谈判更高效，因为团队可以解释该机制为何存在。

Map the trigger before modeling the amount在计算金额前先绘制触发与归责图

A workable trigger answers six operational questions: what must happen, how performance is measured, when measurement occurs, who confirms the result, which exclusions apply, and when the amount starts and stops accruing. Tie the trigger to defined milestones, objective service data, acceptance records, or another auditable event. Avoid circular definitions and phrases that leave the decision entirely to one party without a measurement method.

可执行的触发应回答六个运营问题：发生什么、如何衡量、何时衡量、谁确认结果、适用哪些排除，以及金额何时开始和停止累计。应把触发关联到明确里程碑、客观服务数据、验收记录或其他可审计事件，避免循环定义以及没有衡量方法却完全由一方决定的表述。

Create a responsibility map for customer delay, supplier delay, shared dependencies, third-party systems, regulatory action, force majeure, change requests, inaccurate inputs, and prevention of access. State whether time is extended, performance is rebaselined, or accrual is paused when an excluded cause occurs. A clause that ignores shared responsibility can create disputes precisely when the project needs recovery decisions.

应为客户延误、供应商延误、共同依赖、第三方系统、监管行为、不可抗力、变更请求、错误输入和访问受阻建立归责图。出现排除原因时，应说明期限是否延长、基线是否调整或累计是否暂停。忽略共同责任的条款会在项目最需要恢复决策时制造争议。

Translate the loss pathway into a transparent formula把损失路径转换为透明公式

Choose the simplest structure that matches the loss pattern. A fixed amount can suit one discrete event. A daily or weekly rate can reflect delay. A percentage may fit value that changes with the affected portion of the work. A service-credit style schedule may fit repeated performance bands. Define the calculation base, currency, tax treatment, rounding, partial periods, affected units, commencement, cessation, and evidence needed for an invoice or deduction.

选择与损失模式匹配的最简单结构。固定金额适合一次性事件；按日或按周费率可反映延误；比例适合随受影响工作部分变化的价值；服务抵扣式阶梯则适合重复出现的绩效区间。应定义计算基数、币种、税务处理、四舍五入、不完整期间、受影响单元、开始与停止以及开票或扣款所需证据。

Document the assumptions behind the rate. Show expected revenue or cost impact, duration, probability, mitigation, avoided cost, insurance recovery, and any uncertainty range. The model does not need to predict the future perfectly; it needs to show a reasoned connection between the protected interest and the proposed consequence at the time of contracting. Preserve the model with version history and approval evidence.

记录费率背后的假设，包括预期收入或成本影响、持续时间、概率、减损、避免的成本、保险赔付和不确定性区间。模型不必完美预测未来，但应显示签约时受保护利益与拟定后果之间经过推理的联系。保留模型版本历史和审批证据。

Test the formula against real operating scenarios用真实运营情景测试公式

Run the formula through short, medium, and long failures; partial and complete failures; one site and multiple sites; low-value and high-value orders; and events near the overall cap. Compare the result with the modeled loss and total contract value. Watch for cliffs where one additional hour creates a disproportionate jump, flat amounts that overcompensate small failures, or caps that eliminate the signal before the most important harm occurs.

应测试短期、中期和长期失败，部分与完全失败，单站点与多站点，低价值与高价值订单，以及接近总体上限的事件。把结果与模型损失和合同总价值比较，关注额外一小时却造成不成比例跃升的“悬崖”、对小型失败补偿过高的固定金额，以及在最重要损失出现前就耗尽的上限。

Record sensitivity to assumptions such as demand, price, recovery time, substitute availability, and mitigation cost. Ask a reviewer who did not build the model to reproduce the result from the clause. If two informed readers obtain different answers, improve the formula, definitions, examples, or data hierarchy before signature.

记录需求、价格、恢复时间、替代供应和减损成本等假设变化的敏感性。让未参与建模的审核人员仅依据条款重复计算。如果两位知情读者得到不同答案，应在签署前改进公式、定义、示例或数据优先顺序。

Connect the clause to the rest of the agreement把该条款与协议其他部分衔接

Map the clause against service credits, price reductions, refunds, indemnity, limitation of liability, termination rights, performance security, warranties, insurance, and ordinary damages. Decide whether amounts are exclusive, cumulative, credited against another recovery, or subject to a shared cap. Also check whether the clause applies before termination, survives termination, or changes after a maximum period.

把该条款与服务抵扣、降价、退款、赔偿、责任限制、终止权、履约担保、保证、保险和普通损害赔偿进行映射。确定金额是排他、累计、抵扣其他赔偿还是受共同上限约束，并核对条款是否在终止前适用、终止后存续，或在最长期间后发生变化。

The internal links matter operationally. Review the limitation of liability clause to confirm the cap and exclusions, and the termination clause to understand when accrual ends and what survives. Use a complete contract review checklist to find definitions, priority rules, notices, and schedules that may change the result.

内部链接对执行同样重要。审核责任限制条款以确认上限和排除，审核终止条款以了解累计何时结束以及哪些义务存续，并使用完整的合同审查清单查找可能改变结果的定义、优先顺序、通知和附表。

Adapt the workflow to the business scenario根据商业场景调整流程

Do not reuse one scenario’s rate in another. Even when the percentage looks familiar, the protected interest, duration, mitigation, contract value, market practice, and governing law may differ. Rebuild the evidence chain for each transaction.

不要把一个场景的费率直接用于另一个场景。即使比例看起来熟悉，受保护利益、持续时间、减损、合同价值、市场惯例和适用法律也可能不同。每笔交易都应重新建立证据链。

Create an approval path with named owners建立具有明确负责人的审批路径

1. Business owner confirms purpose.业务负责人确认目的。 Define the protected outcome, trigger, priority, and acceptable commercial range.定义受保护结果、触发、优先级和可接受商业区间。
2. Finance validates the model.财务验证模型。 Check assumptions, double counting, mitigation, tax, currency, sensitivity, and total exposure.核对假设、重复计算、减损、税务、币种、敏感性与总风险。
3. Operations validates measurement.运营验证计量。 Confirm data sources, clocks, exclusions, incident records, acceptance, and dispute escalation.确认数据来源、计时、排除、事件记录、验收与争议升级。
4. Commercial and legal reviewers align the contract.商业和法律审核人员统一合同。 Coordinate caps, credits, termination, insurance, law, notices, evidence, and authority.协调上限、抵扣、终止、保险、法律、通知、证据与权限。
5. Authorized approver records the decision.授权审批人记录决定。 Store the approved wording, model version, deviations, rationale, owners, and monitoring plan.保存批准文字、模型版本、偏差、理由、负责人和监控计划。

Make the signed commitment operational让签署后的承诺真正可以执行

After signature, translate the clause into the contract management system. Capture the affected obligation, measurement source, baseline, exclusions, notice address, claim window, calculation rule, cap, invoice or credit process, dispute route, and owner. Link the clause to project milestones, service dashboards, incident tickets, acceptance records, and renewal or termination calendars.

签署后，把条款转换到合同管理系统中。记录受影响义务、计量来源、基线、排除、通知地址、主张窗口、计算规则、上限、开票或抵扣流程、争议路径与负责人，并关联项目里程碑、服务仪表板、事件工单、验收记录以及续签或终止日历。

Run periodic checks before an incident occurs. Confirm that source data remains available, system names have not changed, owners still have authority, caps have not been exhausted, and amendments have not replaced the formula. When a potential trigger occurs, preserve evidence, apply exclusions, calculate independently, obtain approval, issue any required notice, and record settlement or dispute status.

应在事件发生前定期检查：源数据仍可获得、系统名称未变、负责人仍有权限、上限尚未用尽、修订没有替换公式。潜在触发发生时，应保存证据、应用排除、独立计算、取得批准、发送必要通知，并记录结算或争议状态。

Liquidated damages commercial review checklist约定损害赔偿商业审查清单

• State the protected business outcome and why advance agreement creates value.说明受保护的业务结果以及预先约定为何有价值。
• Define an objective trigger, measurement source, clock, exclusions, and responsibility rules.定义客观触发、计量来源、时钟、排除与归责规则。
• Preserve a dated loss model with assumptions, mitigation, uncertainty, and supporting evidence.保存带日期的损失模型、假设、减损、不确定性与支持证据。
• Specify the amount or formula, base, currency, partial periods, affected units, start, stop, and cap.明确金额或公式、基数、币种、不完整期间、受影响单元、开始、停止和上限。
• Test normal, downside, severe, partial, prolonged, repeated, and shared-cause scenarios.测试正常、下行、严重、部分、长期、重复与共同原因情景。
• Map service credits, refunds, ordinary damages, indemnity, liability limits, termination, security, and insurance.映射服务抵扣、退款、普通赔偿、赔偿责任、责任限制、终止、担保与保险。
• Confirm claim, notice, invoice, deduction, evidence, approval, dispute, and record-retention processes.确认主张、通知、开票、扣款、证据、审批、争议和记录保存流程。
• Obtain commercial, finance, operations, insurance, and qualified legal review appropriate to the transaction.取得与交易相适应的商业、财务、运营、保险和具备资质的法律审核。

Escalate these commercial and process warning signs升级处理这些商业与流程风险信号

Warning signs include a number copied from an unrelated precedent, no contemporaneous model, one amount for different breaches, a subjective trigger, no customer-dependency relief, automatic deductions without evidence, an accrual period with no end, a formula that cannot be reproduced, and language that conflicts with credits, caps, termination, or insurance. Also escalate when the amount is materially disconnected from contract value or plausible harm.

风险信号包括：从无关范本复制数字；没有同期模型；不同违约共用一个金额；主观触发；没有客户依赖救济；无证据自动扣款；累计没有终点；公式无法复现；以及与抵扣、上限、终止或保险冲突。金额明显脱离合同价值或合理损失时也应升级。

Process failures can be equally serious: incomplete agreement sets, undocumented assumptions, no named data owner, approvals outside authority, confidential models shared without controls, and no post-signature handoff. A polished clause cannot repair missing evidence or an operating process that nobody owns.

流程失败同样严重，包括协议不完整、假设未记录、数据负责人不明、超权限审批、机密模型无控制共享以及签署后没有交接。文字精美的条款无法弥补证据缺失或无人负责的执行流程。

Use AI to organize a traceable first pass使用 AI 组织可追溯的第一轮初筛

AI can extract triggers, formulas, caps, exclusions, notices, cross-references, and remedy language from a complete contract set. It can compare wording across the main agreement, schedules, statements of work, amendments, and priority rules; create a dependency map; and flag missing fields for human review. Require exact citations and “not found” when information is absent.

AI 可以从完整合同集中提取触发、公式、上限、排除、通知、交叉引用和救济文字，比较主协议、附表、工作说明、修订与优先规则，建立依赖图，并标记缺失字段供人工审核。应要求准确引用，信息缺失时返回“未找到”。

AI should not invent a loss model, select governing law, decide whether an amount is enforceable, approve a claim, or replace transaction-specific professional judgment. Human reviewers must confirm the full agreement, current law, facts, model assumptions, data, responsibility, authority, notices, remedy interaction, and business decision. Protect confidential material and follow organizational data-handling controls.

AI 不应虚构损失模型、选择适用法律、决定金额是否可执行、批准主张或替代针对具体交易的专业判断。人工审核人员必须确认完整协议、现行法律、事实、模型假设、数据、归责、权限、通知、救济衔接与商业决定，并保护机密资料、遵守组织的数据处理控制。

Liquidated damages clause FAQ约定损害赔偿条款常见问题

Sources and Method来源与方法

• Cornell Legal Information Institute — UCC section 2-718 on liquidation or limitation of damages康奈尔法律信息研究所 — UCC 第 2-718 条关于约定或限制损害赔偿
• Cornell Legal Information Institute — Penalty clause overview康奈尔法律信息研究所 — 惩罚性条款概览
• California Legislative Information — Civil Code section 1671加利福尼亚州立法信息 — 《民法典》第 1671 条
• UK Supreme Court — Cavendish Square Holding BV v Makdessi case materials英国最高法院 — Cavendish Square Holding BV v Makdessi 案件资料