Systems and records
Who could approve that contract change? A legal ops delegation dataset
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
To establish who had authority to approve a contract change, rebuild the chain as it stood on the approval date: the board or committee grant, the delegation policy version then in effect, the approver's role that day, the limit for that change type, and the approval and signature records. Compare the change with that limit and label it within authority, outside authority or indeterminate.
Provenance trail
Legal ops approval
Key takeaways
- Authority is a chain: board grant, policy version, role on the date, limit for the change type, then the approval event.
- Signatures and approval logs record who acted, not whether they were allowed to.
- Apply the delegation policy version effective on the approval date and a written precedence rule when records conflict.
- Build cases from administrative records; counsel screens out legal advice and logs exclusions.
- Label cases indeterminate or exclude them when a link is missing rather than forcing an answer.
How do you establish who had authority to approve a contract change?
Establish authority by rebuilding the chain as it stood on the approval date: the governing grant (bylaws or a board resolution), the delegation of authority policy version then in effect, the role the approver actually held that day, the limits attached to that role, and the approval and signature records for the specific change. Then compare the change against those limits and record whether it was within authority, outside it, or cannot be determined.
For a legal operations team, that comparison is a repeatable task with a clear input packet and a defensible answer, which is why it makes a useful evaluation case for AI systems that review contracts. A model that reads a redline well can still miss that the person who clicked approve had lost that authority a week earlier.
The same packet serves people too. Auditors testing approval controls, a general counsel answering a counterparty challenge, and a contract team checking that a new CLM routing rule matches the policy all need the same joined record. Building it once, with a fixed specification, means the dataset is a by-product of work the company already has reasons to do.
This page specifies that task: the fields, the sources each field comes from, the precedence rules when records conflict, and the screen that keeps privileged legal advice out. It is general information, and counsel decides authority questions on the specific facts.
Why a signature and an approval stamp do not answer the authority question
A signature proves that a person signed; it does not prove they were allowed to. Under the federal E-SIGN Act, a signature or contract may not be denied legal effect solely because it is electronic, but that rule addresses form, not whether the signer had authority to bind the company.
The systems legal teams use record events, not entitlement. Docusign's Certificate of Completion lists each recipient's events with timestamps and identifying details, and adds an Envelope Updated entry for every correction. Salesforce's Approval History list shows statuses such as Submitted, Approved, Reassigned and Recalled, and for a step assigned to a queue it shows both the queue and the actual approver. Those records tell you who acted and when.
Neither tells you whether the actor's role carried authority for that contract type, amount and term on that date. That answer lives in governance documents and HR records that sit outside the contract system, which is exactly why a case that joins them is harder, and more valuable, than a clause extraction task.
Where approval authority comes from, document by document
Authority flows downward from the board through written delegations, so each case needs the specific link that reached the approver. In a Delaware corporation, for example, section 141(c) of the General Corporation Law lets the board create committees that exercise board powers only to the extent the resolution or bylaws provide, and committees can delegate further to subcommittees.
Below the board, most companies publish a delegation of authority matrix that assigns approval limits by role, contract type and value. Public companies also have a regulatory reason to keep these records: SEC Rule 13a-15(f) describes internal control over financial reporting as including procedures that give reasonable assurance that expenditures are made only in accordance with the authorizations of management and directors.
| Level | Typical document | What it settles | Common gap |
|---|---|---|---|
| Board | Bylaws, board resolutions, committee charters | Which powers were delegated and to whom | Resolutions stored as minutes PDFs with no structured dates |
| Committee or executive | Committee resolution, CEO delegation memo | Further delegation to officers or roles | Memo superseded without a recorded end date |
| Policy | Delegation of authority matrix, versioned | Limits by role, contract type, value and term | Only the current version kept |
| Person | HR role history, acting appointments | Who held the role on the approval date | Acting or interim roles not recorded |
| Event | CLM or CRM approval log, e-signature certificate | Who approved and signed, and when | Approvals given by email outside the system |
Which record wins when the policy, the system and the contract disagree?
Set a precedence rule before labeling any case and apply it the same way every time. A sensible default is that the governing grant beats the policy, the policy version effective on the approval date beats any later version, and the HR role record beats the job title typed into the approval system.
Amendments need special care. The change being approved is the amendment, not the original agreement, so the limits to apply are the ones that cover the amendment's effect: a term extension, a price change or a new license scope may sit in different rows of the matrix than the original deal. Record which row you applied and why.
Reassignments and delegations during absence are where most conflicts appear. When an approval system shows a reassigned step, the case must include the reassignment record and confirm the new approver's own authority; a reassignment inside a tool does not transfer authority the policy did not grant.
Dates need the same discipline. Record every timestamp with its time zone, and decide whether authority is tested at the moment of approval, at signature, or at both. When an approval and the signature fall on different sides of a policy change, keep both events in the packet and state which one the label rests on, so a second reviewer applying the same rule reaches the same answer.
The delegation and approval evidence task specification
The specification below is the asset. Each row is one field of the case, where it comes from, and what a reviewer checks before accepting it. A case is complete only when every required field is filled or carries a documented reason for its absence.
At a glance
The delegation and approval evidence task specification
- Within authority: every link of the chain is documented and the change sits inside the applied limit.
- Outside authority: the chain is documented and the change exceeds the limit or the approver lacked the role.
- Indeterminate: a required link is missing or the records conflict in a way the precedence rule cannot resolve.
| Field | Content | Source | Reviewer check |
|---|---|---|---|
| Case and change ID | Contract ID, amendment or change-order ID, change type | CLM or contract repository | Change is a single, identifiable amendment |
| Change effect | What the change does: term, price, scope, liability, termination | Executed amendment text and redline | Effect described in plain words and mapped to a policy row |
| Approval events | Each approver, action, status and timestamp | Approval history export from CLM or CRM | Reassignments and recalls included, time zone stated |
| Signature events | Signers, order, timestamps, corrections | E-signature certificate of completion | Signed version matches the approved version |
| Policy version | Delegation matrix version and effective dates | Policy repository or governance site | Version effective on the approval date, not today |
| Grant chain | Board or committee resolution supporting the policy | Corporate secretary records | Resolution date precedes the policy version |
| Role on date | Approver's role, acting appointments, leave | HR system role history | Role held on the approval date |
| Applicable limit | The matrix row and limit applied | Derived from the fields above | Row choice explained in one sentence |
| Label | Within authority, outside authority, indeterminate | Reviewer decision | Second reviewer agrees or disagreement is logged |
| Exclusion record | What was withheld and why | Counsel privilege screen | No privileged content in the case packet |
How many cases, and which ones, make a useful set?
Sample on purpose rather than exporting every amendment. A set dominated by routine renewals approved well inside their limits teaches a model that the answer is almost always within authority, which is not a useful skill to measure.
Stratify by change type (term, price, scope, liability), by label, and by distance from the limit, and deliberately include cases that sit just above or just below a threshold, cases that straddle a policy version change, and reassigned approvals. Those are the cases where a careless reviewer, human or model, gets the answer wrong.
Have two reviewers label each case independently from the packet alone and record their agreement. Cases where trained reviewers disagree are either indeterminate by nature or signal a gap in the specification; fix the specification before adding more cases.
Keeping privileged advice out of an authority case
Build authority cases from process records, not from legal advice. The approval log, the policy, the resolution and the role history are administrative records; the email in which in-house counsel analyzed whether an approval was valid is not, and it stays out.
The reasons are both ethical and evidentiary. ABA Model Rule 1.6 bars a lawyer from revealing information relating to a client representation without consent or another listed basis, and it reaches more than privileged communications. Federal Rule of Evidence 502 governs when a disclosure waives privilege, which is why disclosure decisions belong to counsel rather than to the data team.
In practice, counsel screens each candidate case, removes advice, flags matters under hold or dispute, and signs an exclusion record. Cases that only make sense with the legal analysis attached are dropped, not redacted into something misleading.
Illustrative case: a term extension approved during a policy change
The company and dates in this case are invented to illustrate the method. A software company extends a reseller agreement by 24 months. The amendment is approved in the CLM by a regional sales director and signed eleven days later by the same person.
The company's delegation matrix had two versions in the relevant window. Version 4 allowed directors to approve term extensions up to 12 months; version 5, effective three days after the approval, raised the limit to 36 months. The HR record confirms the approver held the director role on the approval date.
Applying the precedence rule, version 4 governs, and a 24-month extension exceeds its limit, so the case is labeled outside authority. The case packet records both versions, their effective dates, the approval and signature timestamps, and the one-sentence reason. Whether the company later ratified the extension is a separate legal question that the label does not decide; the packet notes that counsel reviewed the case and that any ratification record was excluded.
When the honest label is indeterminate
Label a case indeterminate, or drop it, when a missing or conflicting record means a reasonable reviewer could reach either answer. Forcing a label teaches a model to guess at authority, which is the failure you are trying to measure.
Typical causes are approvals given in meetings or by email that never reached the system, policy versions that were overwritten rather than archived, acting appointments with no HR record, and approvals later ratified by a higher authority. Doctrines such as ratification and apparent authority can change the legal outcome even when the internal policy was breached, so these cases go to counsel and are usually kept out of training sets.
| Situation | Decision | Record to keep |
|---|---|---|
| Policy version for the date cannot be found | Indeterminate or exclude | Search performed and versions found |
| Approval given outside any system | Exclude unless a contemporaneous written record exists | Where the record was found |
| Later ratification by a higher authority | Counsel review; usually exclude | Counsel sign-off, no advice content |
| Contract in dispute or under legal hold | Exclude | Hold or dispute reference only |
| Records conflict beyond the precedence rule | Indeterminate | Both records and the conflict |
Why contract datasets rarely capture authority, and what that means for licensing
Public contract datasets mostly label what a contract says, not how it was approved. The Contract Understanding Atticus Dataset, a widely used benchmark, defines clause categories such as parties, agreement date, anti-assignment, change of control and license grants; none of its categories asks who approved the contract or under what delegation. Authority cases built from real approval histories fill a gap that clause labels cannot.
Four questions need separate answers before approval records go anywhere: whether you can access and export them, whether privacy rules permit their use, who owns them, and whether you hold the contractual right to license them. Counterparty agreements often carry confidentiality terms, so the case packet may need counterparty details removed even when the approval facts are the company's own.
If a legal department chooses to license its approval histories to AI developers, SourceX handles the rights review, the contract, the preparation and the delivery. The company signs off on scope and terms, and signs the agreement, before a single case packet moves. A brief company assessment, with no records uploaded, decides whether the company qualifies.
Frequently asked questions
What should a delegation and approval evidence task specification include?
It should include the change and its effect, every approval and signature event with timestamps, the delegation policy version effective on the approval date, the board or committee grant behind it, the approver's role on that date, the limit applied, the label and an exclusion record. Each field names its source system and the check a reviewer performs.
Does an electronic signature prove the signer had authority?
No. Federal law says a signature cannot be denied effect solely because it is electronic, which addresses form only. Whether the signer could bind the company depends on the delegation in effect and the signer's role, which come from governance and HR records.
Which delegation policy version applies to an approval?
The version in effect on the date of the approval, not the current one. Keep every version with its effective dates, and if the approval and signature fall on different sides of a policy change, record both and apply your written precedence rule.
Can in-house counsel emails about an approval go into the dataset?
Generally no. Legal analysis of whether an approval was valid is the kind of material confidentiality and privilege rules protect, so counsel screens it out and the case is built from administrative records only.
What if the approval happened by email outside the contract system?
Include it only when a contemporaneous written record exists and counsel clears it; otherwise exclude the case or label it indeterminate. Note where the record was found so a reviewer can trace it.
Sources
- Section 141(c) of the Delaware General Corporation Law lets a board designate committees of directors that exercise board powers only to the extent the board resolution or bylaws provide, with some matters reserved, and lets committees form subcommittees. Source
- SEC Rule 13a-15(f) defines internal control over financial reporting to include policies and procedures that provide reasonable assurance that receipts and expenditures are made only in accordance with authorizations of management and directors. Source
- Federal Rule of Evidence 502 limits when a disclosure waives attorney-client privilege or work-product protection, including a rule that an inadvertent disclosure does not waive protection when the holder took reasonable steps to prevent and correct it. Source
- ABA Model Rule 1.6 bars a lawyer from revealing information relating to the representation of a client without informed consent or another listed basis, and requires reasonable efforts to prevent unauthorized disclosure. Source
- The E-SIGN Act, 15 U.S.C. 7001, says a signature, contract or record in interstate commerce may not be denied legal effect solely because it is in electronic form. Source
- Salesforce's Approval History related list tracks a record through a classic approval process with statuses such as Submitted, Pending, Approved, Rejected, Reassigned and Recalled, and for queue steps distinguishes the assigned queue from the actual approver. Source
- Docusign's Certificate of Completion records envelope details, each recipient's events with timestamps and identifying information, and summary events including an Envelope Updated entry for each correction. Source
- The Contract Understanding Atticus Dataset labels clause categories such as parties, agreement and effective dates, anti-assignment, change of control and license grants; none of its categories records who approved the contract or under what authority. Source
See if your company qualifies
A short company assessment. No data uploads are needed.