The gradient of obligation: mapping ‘efforts’ standards across our 2026 benchmark
How our small model evaluates the hierarchy of 'efforts' clauses, and what we observe about their distribution in cross-border agreements.
An absolute obligation is a strict allocation of risk. A contract stating that a party “shall secure regulatory approval” places the entire burden of failure on that party, regardless of external events or market conditions. To manage this, drafters use qualifiers. The “efforts” standard creates a gradient of obligation, allowing parties to commit to a goal without guaranteeing its completion.
This gradient is a frequent source of friction in early-stage negotiations. A reviewer must determine exactly where the counterparty’s proposed phrasing sits on the spectrum, whether it meets the firm’s baseline, and how it translates across jurisdictions.
Observations from the benchmark
Across the 2.4 million contracts indexed in our active accounts, we track how these qualifiers are distributed and negotiated. The terminology follows clear patterns based on practice area and governing law.
In North American commercial agreements—particularly MSAs and DPAs—”commercially reasonable efforts” is the dominant standard. It appears as the baseline obligation in 68% of the commercial contracts processed through Review this year.
“Best efforts,” which carries a heavier burden, appears in less than 12% of our benchmark. It is rarely used as a general standard. Instead, drafters isolate it for specific, high-priority covenants. We see it most frequently applied to confidentiality obligations, intellectual property registrations, and specific regulatory filings in biotech SPAs.
We also track the use of hybrid standards. “Reasonable best efforts” is a common compromise in Delaware M&A transactions, but it frequently causes confusion when exported to other jurisdictions. Counterparties often attempt to invent new variations, such as “commercially reasonable best efforts” or “good faith reasonable efforts.” These combinations lack clear judicial precedent and typically result in a more protracted negotiation.
Evaluating the hierarchy with ZAAN-7B Counsel
String matching is insufficient for reviewing efforts clauses. A counterparty might embed the qualifier deep within a nested conditional, or apply different standards to different sub-clauses.
ZAAN-7B Counsel, our in-house model, is trained to evaluate clause-level reasoning and categorise these qualifiers into a strict hierarchy. When Review 4.2 reads a draft against a firm’s playbook, it maps the text to this hierarchy.
If a playbook requires “commercially reasonable efforts” for an SLA uptime guarantee, and the counterparty draft offers “reasonable efforts,” the model registers the downgrade. Review 4.2 flags this as a Medium severity issue. It then proposes an inline redline in Word to restore the required standard, appending a citation to the firm’s playbook rule.
The model is also trained to detect when a standard is disproportionate to the transaction size. If a counterparty demands “best efforts” for routine reporting requirements in a low-value vendor agreement, Review can flag this as a High severity issue, noting that it exceeds the playbook floor for that specific clause type.
Cross-border translation and functional equivalents
The vocabulary of obligation changes at the border. Under English law, the terminology shifts from “efforts” to “endeavours.”
When a playbook is written using US terminology, but the governing law of the draft is English, a rigid review process creates false positives. Review 4.2 recognises that “reasonable endeavours” is the functional equivalent of “reasonable efforts.” Instead of generating a High severity flag for a missing term, it leaves a Note, explaining the jurisdictional shift and advising the reviewer to accept the local phrasing.
This parity extends across the 38 languages we support. If a Mandarin draft uses “尽最大努力” (best efforts), Review maps this against the English playbook. If the playbook sets a ceiling of “commercially reasonable efforts,” the system flags the Mandarin text as an over-commitment and proposes the narrower “商业上合理的努力” in the redline. The parity guarantee ensures that the strictness of the obligation is not lost in translation.
Drafting from precedent
The most reliable way to manage the efforts gradient is to define it explicitly. We observe a steady increase in master agreements that include a distinct definition for “commercially reasonable efforts,” often capping the financial expenditure required or explicitly stating that a party is not required to initiate litigation to satisfy the standard.
When a lawyer uses Draft 3.9 to compose a new agreement, the system looks at the firm’s matter history. If the firm consistently includes an expenditure cap in its definitions of “commercially reasonable efforts” for tech acquisitions, Draft inserts that specific carve-out, applying the firm’s house style and providing a citation to the last three closed deals where it was used.
For older matters, Recall 2.7 allows legal teams to trace how these standards were negotiated. A user can run a plain-language search for “definitions of commercially reasonable efforts in European biotech deals from 2024,” and Recall will isolate the definitions sections, showing the exact precedents and the trace view of how the clause evolved from the first draft to execution.
A gradient of obligation is only useful if both sides agree on the slope. Defining the standard clearly in the draft prevents a tribunal from having to measure it later.