Rights and contracts
Legal document authority benchmark: when newer is not controlling
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Check four tests before dates: whether the newer document's signer had authority to bind, whether it met the agreement's amendment formalities, how the order-of-precedence clause ranks its document type, and whether its scope reaches the term in question. Recency decides only among valid, in-scope documents of equal rank. A benchmark task should make a model show each test against counsel-approved, nonprivileged records.
Evaluation split
Legal document authority
Key takeaways
- A later contract document controls only if it passes authority, formality, precedence and scope tests.
- Order-of-precedence clauses often rank newer document types, such as specifications, below older ones.
- Terms that arrive by click-through, invoice or informal email are a distinct trap and belong in the task set.
- Each task needs the authority records and quoted clauses, so the answer can be checked document by document.
- Privileged material stays out entirely, and counterparty confidentiality is a separate rights question for counsel.
How do you identify the controlling document when it is not the newest one?
Check four things before looking at dates. Was the newer document signed by someone with authority to bind the party? Did it satisfy the amendment formalities the governing agreement requires? Does an order-of-precedence clause rank its document type above or below the older one? Does its scope actually reach the term in question? Date decides only among documents that pass all four and rank equally.
Legal operations teams do this every day when a renewal, a dispute or an audit asks which term applied on a given date. The newest file in the contract repository is usually the right answer, which is exactly why a model trained on recency alone looks accurate until the cases that matter: an unauthorized side letter, an informal email, a vendor form attached to an invoice, or an amendment limited to one statement of work.
A legal document authority benchmark tests that reasoning directly. Each task gives the model a set of related documents and an as-of date and asks for the controlling term, the document that supplies it and the chain of tests that rules the others out. Qualified counsel approves the answer before the task is used.
Why does the latest date fail as a rule for contract authority?
Because a document can be later and still have no legal effect. The four tests in the opening answer each defeat recency in a different way, and a good task set includes all four rather than one dramatic example. The table adds a fifth check, the effective date, which matters once a document passes the other four.
Authority is the clearest. Federal procurement rules give a public, citable illustration: under FAR 1.602-1, contracting officers bind the government only to the extent of the authority delegated to them, and FAR 43.102 says only contracting officers acting within that authority may execute contract modifications, with other personnel barred from acting as if they could. FAR 1.602-3 calls an agreement that fails solely for lack of that authority an unauthorized commitment, which an official with authority may later ratify. The FAR citations on this page, including the precedence clauses below, follow the FAR text published before the Revolutionary FAR Overhaul; agencies have since adopted overhaul class deviations that rewrite parts of the FAR, including Part 43 on contract modifications, so check the current section numbers and wording before relying on them.
Commercial contracts are not governed by the FAR, and their outcome depends on their own terms and the governing law. The pattern still transfers: signature authority policies, delegation matrices and amendment clauses that require a signed writing are the records that let a reviewer tell a valid change from a later document that only looks like one.
| Test | Question the task asks | Record that answers it | Typical trap |
|---|---|---|---|
| Authority | Could this signer bind the party for this kind of change? | Signature authority policy, delegation matrix, board or officer resolution | A project manager's email agreeing to new terms |
| Formality | Did the change meet the agreement's amendment clause? | Executed amendment, countersignature, amendment clause text | An unsigned redline circulated as final |
| Precedence | Does the document type rank above the conflicting one? | Order-of-precedence clause in the governing agreement | A later specification that contradicts the schedule |
| Scope | Does the change reach this term, product or engagement? | Amendment recitals, SOW references, defined terms | A one-project change read as a global change |
| Effective date | Was the change in force on the as-of date? | Effective date clause, execution dates, conditions | Signed after the date asked about but effective before it |
Which order-of-precedence rules settle conflicts between document types?
The governing agreement's own precedence clause settles them, and it often ranks newer document types lower. FAR 52.215-8 is a standard example: inconsistencies are resolved by giving precedence first to the schedule excluding specifications, then representations and other instructions, then contract clauses, then other documents, exhibits and attachments, and last the specifications. A specification issued last still loses to the schedule.
The commercial item clause takes the same approach with more layers. FAR 52.212-4 paragraph (s) puts the schedule of supplies or services first, places addenda including software license agreements in the middle, and puts other documents, exhibits, attachments and the specification at the end.
Commercial master agreements commonly carry their own version, such as the master agreement controlling over a statement of work unless the SOW expressly identifies the clause it overrides. That is a drafting pattern, not a rule of law, so the task must quote the actual clause from the agreement in the document set. Without the clause, the correct answer may be that precedence cannot be determined.
Can a later click-through or preprinted form change the deal?
Often it cannot, and the task set should include these cases because models tend to treat any document with terms as binding. FAR 52.212-4 paragraph (u) is an explicit example: when a supply or service is subject to an end user license agreement or terms of service containing certain indemnification clauses, those clauses are unenforceable against the government, clicking an I agree box does not bind the government to them, and they are deemed stricken.
Private agreements reach similar results in other ways, for example an entire agreement clause, a precedence clause that excludes preprinted purchase order or invoice terms, or a requirement that changes be signed by named officers. Whether any of these works in a given dispute is a question for counsel, and the benchmark should mark such tasks as counsel-decided rather than inferable from a general rule.
The useful skill for a model is narrower and testable: notice that a later document arrived through a channel the governing agreement does not recognize, flag it and route it, instead of quietly adopting its terms.
What does a counsel-reviewed authority and amendment task contain?
This is the asset: one record per question, built from nonprivileged contract records, with every step of the reasoning tied to a document a reviewer can open. Counsel signs off on the answer and on the exclusion record before the task is used.
- Authority defect: a later document signed by someone outside their delegation.
- Formality defect: an unsigned or one-sided change where the agreement requires a signed writing.
- Precedence override: a later document type that ranks below an earlier one.
- Scope limit: an amendment that changes one SOW or product line, not the master terms.
- Retroactive effect: a change signed after the as-of date but effective before it.
- Unrecognized channel: terms arriving through a click-through, invoice or order form.
- Cannot be determined: a missing signature page, exhibit or precedence clause, where abstaining is correct.
- Plain recency: a valid, in-scope, equally ranked later amendment, so the model does not overcorrect.
| Task field | What it contains | Where it comes from | How it is checked |
|---|---|---|---|
| Question and as-of date | One term and the date it must be determined for | Renewal, audit or dispute prompt, rewritten neutrally | Answerable from the document set alone |
| Document set | Agreement, amendments, SOWs, exhibits, side letters, relevant emails | Contract management system and repository | Each item carries version, execution and effective dates |
| Authority record | Signer roles and delegation limits in force on each date | Signature authority policy, delegation matrix | Signer checked against limit for that change type |
| Amendment formality | The agreement's change clause, quoted | Governing agreement | Each later document tested against it |
| Precedence rule | Order-of-precedence clause, quoted, or a note that none exists | Governing agreement | Ranking applied before dates |
| Controlling answer | The term in force, the document that supplies it, or cannot be determined | Counsel review | Exact match on term and source document |
| Reasoning chain | Why each other document does not control, test by test | Counsel review notes, nonprivileged summary | Each excluded document has a named failed test |
| Exclusion record | What was withheld for privilege or confidentiality and why | Counsel screen | Present and signed for every task |
Can a manager's email relax a contract's response time? An illustrative case
This case is illustrative and not drawn from any real matter. A facilities services company and a client signed a master services agreement with an amendment clause requiring changes to be in a writing signed by an officer of each party, and a precedence clause letting a statement of work set service levels for its own site.
The document set: the master agreement with a 24-hour response time for all sites; SOW 3 for one distribution center, signed by officers, setting a 4-hour response time for that site; and an email sent eight months later by the client's regional facilities manager agreeing that the vendor may respond within 24 hours at that site during a staffing shortage.
Question: what response time applied at the site on a date two weeks after the email? Controlling answer: 4 hours, from SOW 3. The email is later but fails authority, because the regional manager is not an officer under the client's delegation policy, and formality, because it is not signed by officers of both parties. The master agreement's 24 hours does not apply at that site because the precedence clause lets SOW 3 set the level for its own site.
Counterexample: the same email is countersigned by officers of both parties and expressly references SOW 3. Now it meets the amendment clause, and the correct answer becomes 24 hours from the amendment's effective date. A model that always picks the SOW is as wrong as one that always picks the newest file.
Where the reasoning stops: if the vendor relied on the email for months and the client said nothing, arguments such as waiver may arise. The task marks that as a question for counsel rather than giving the model a rule.
What does counsel screen out before legal records become task data?
Anything privileged, anything a counterparty's confidentiality clause protects, and anything outside the approved scope. The task needs executed documents, metadata and nonprivileged summaries; it does not need advice memos, outside counsel emails, negotiation strategy or litigation files.
Privilege is easier to lose than to restore. Federal Rule of Evidence 502 addresses when disclosing privileged communications or work product waives protection, and it notes that a party agreement on the effect of disclosure binds only the parties unless a court order incorporates it. That is one more reason the safe default is to keep privileged material out of the export entirely rather than rely on clawback.
Confidentiality is a separate screen. Many executed contracts restrict disclosure of their terms, so a company may control the file and still lack the right to license it. Removing party names reduces identification risk but does not by itself create that right; counsel decides whether masking, consent or exclusion applies to each agreement.
How do existing legal benchmarks differ from an authority task?
They mostly test reading one document or one rule, not choosing among documents. CUAD's category descriptions ask for clause-level answers inside a contract, such as the effective date, the expiration date, the renewal term and the governing law. Those are building blocks, but none asks whether a later document displaced the clause.
LegalBench describes itself as a collaborative benchmark of 162 legal reasoning tasks gathered from 40 contributors, each with a dataset of input-output pairs. Its tasks cover issues such as hearsay, definition extraction and rule questions. An authority task adds what single-input tasks cannot: several documents, an as-of date, and an answer that depends on authority, formality, precedence and scope together.
The practical consequence is that public benchmark scores say little about whether a model will pick the controlling document in a client's contract family. That gap is filled only by real, counsel-reviewed document sets with the authority records attached.
Getting contract records ready for a licensing conversation
Legal operations teams that keep executed agreements, amendment histories and signature authority policies in a contract management system already hold most of what these tasks need. The first decisions are internal: whether counterparty confidentiality allows licensing, which matters are excluded, and who signs the privilege screen.
Once those decisions are made, SourceX can take the selected contract records through rights review, contracting, preparation and delivery into a dataset licensed for AI. No contract record leaves before the company approves scope and terms and signs, and legal operations can learn whether the company qualifies from a short assessment, with no documents uploaded.
Frequently asked questions
Does the most recent version of a contract always control?
No. A later document controls only if it was signed by someone with authority, met the agreement's amendment requirements, ranks at least as high under any precedence clause and covers the term in question. Recency decides only among documents that pass those tests.
What is an order of precedence clause?
It is a clause that ranks the documents making up a contract, such as the schedule, clauses, exhibits and specifications, so conflicts are resolved by rank rather than by date. FAR 52.215-8 is a published example used in federal contracts.
Can an email amend a contract?
Sometimes, depending on the contract's amendment clause, who sent it and the governing law. Many agreements require a signed writing by authorized officers, in which case an email from someone else usually does not qualify. Counsel should decide specific cases.
What records are needed to build a legal document authority benchmark?
Executed agreements and amendments with dates, the precedence and amendment clauses, signature authority policies in force on each date, and counsel's nonprivileged reasoning for each answer. Privileged advice and negotiation files should be excluded.
Why should some tasks have no determinable answer?
Real contract files have missing signature pages, lost exhibits and agreements without precedence clauses. A model that always produces an answer will fabricate one in those cases, so abstaining with a stated reason should score as correct.
Sources
- FAR 1.602-1 says contracting officers may bind the government only to the extent of the authority delegated to them. Source
- FAR 43.102 says only contracting officers acting within their authority may execute contract modifications, and other personnel must not act as if they could bind the government. Source
- FAR 1.602-3 defines an unauthorized commitment as an agreement not binding solely because the representative lacked authority, and provides for ratification by an official with authority. Source
- FAR 52.215-8 resolves inconsistencies by precedence: the schedule excluding specifications, representations and instructions, contract clauses, other documents, then specifications. Source
- FAR 52.212-4 sets an order of precedence for commercial contracts in paragraph (s) and, in paragraph (u), makes certain indemnification clauses in EULAs or terms of service unenforceable, including through click-wrap. Source
- Federal Rule of Evidence 502 governs when disclosure waives privilege or work-product protection; a party agreement binds only the parties unless incorporated in a court order. Source
- CUAD's category descriptions include Effective Date, Expiration Date, Renewal Term and Governing Law as clause-level questions within a contract. Source
- LegalBench is a collaborative benchmark of 162 legal reasoning tasks from 40 contributors, each with input-output pairs. Source
- Agency class deviations under the Revolutionary FAR Overhaul rewrite FAR Part 43 on contract modifications to remove non-statutory language and fit a new FAR framework. Source
See if your company qualifies
A short company assessment. No data uploads are needed.