Systems and records
Legal signature completion dataset: when is an agreement fully executed?
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Label an agreement fully executed only when every required signer has completed the same document version, the signing request is closed as complete, and nothing later voided or replaced it. Derive that state from the signing platform's request and recipient records, not from file names, CLM stages or a single signer's status, and keep partially signed, declined, voided, expired and unresolved cases as separate labels.
License terms
Legal signature completion
Key takeaways
- Execution is a state derived from signing evidence, not a field copied from the contract repository.
- Read the request status and every required signer's status; one recipient marked signed proves nothing about the agreement.
- A version hash on every signer event exposes deals where each party signed a different draft.
- Rank evidence by closeness to the act of signing and record conflicts instead of hiding them.
- Score calling a partially signed agreement executed as a critical error, and reward abstention on unresolved cases.
- The dataset labels documentary state; whether a contract binds anyone is a question for counsel.
How should legal operations data tell a partially signed agreement from an executed one?
Treat execution as a state you derive from evidence, not a label you copy. A legal signature completion dataset should mark an agreement fully executed only when every required signatory has signed the same final version, the signing request is closed as complete, and nothing later voided, declined or replaced it. Anything short of that is partially signed, pending, declined, voided or expired, and the case records which.
The distinction matters because the cheapest signals in a contract repository point the wrong way. A PDF named with the word signed, a CLM stage called Signed, or an email that says signed copy attached can all describe a document that only one party has signed. A model trained on those signals learns to call half-finished agreements executed, which is exactly the error a legal team cannot tolerate.
One boundary applies throughout. The dataset labels the documentary state of the signing process. Whether a contract was formed, or binds a party that never signed, is a question of substantive law and the parties' conduct, and it belongs to counsel, not to a label.
Why a signed flag, a file name or a CLM status is not proof of execution
Each common shortcut fails in a predictable way, so the task pack has to read the underlying signing records. E-signature platforms keep separate status at two levels: the request as a whole and each recipient inside it.
Docusign's published eSignature API specification shows why the levels matter. A recipient's status of signed is described as a temporary processing state after which the recipient moves to completed, while the envelope's completed status means the recipients have finished and the documents are signed with all required fields filled in. A voided envelope is no longer valid and recipients cannot sign it. Reading one recipient's status as the agreement's status is the most common labeling mistake.
Dropbox Sign's API makes the same split explicit. Its signature request carries an is_complete flag described as whether the request has been fully executed by all signers, plus an is_declined flag, while each signature has its own status code such as awaiting_signature, signed or declined. Adobe Acrobat Sign documents that a canceled agreement cannot be completed and that expiration is terminal, with agreements that have no set date expiring automatically after 365 days.
Repository fields are weaker still. A CLM stage is usually set by a person or an automation rule, a file name is typed by whoever saved the copy, and a scan can contain one signature block filled and one blank. Use these as hints that point to a case, never as the label.
The execution states every case in the task pack must carry
Use a closed list of states so that every case resolves to exactly one, and keep the separate question of which version is current out of this label. The table below is the state vocabulary for the task pack; the platform terms in the second column are examples of where the evidence comes from.
| State | Evidence that establishes it | False signal to reject | Labeling rule |
|---|---|---|---|
| Not sent | Request exists as a draft; no recipient has been notified | A template or unsent draft stored in the signed folder | Exclude from execution tasks or keep as a negative example |
| Out for signature, none signed | Request sent; every required signer still pending | Email to the counterparty saying here is the agreement to sign | Label pending; record the send timestamp |
| Partially signed | At least one required signer completed; at least one still pending | File saved as signed after the first signature | Label partially signed; list each missing role |
| Fully executed in platform | Request closed as complete and every required signer completed on one document version | A single recipient status of signed | Label executed; execution timestamp is the last required completion |
| Executed outside a platform | Wet-ink or separate counterpart pages for every required party, all on the same version | One party's signature page with no counterpart | Label executed only if counsel confirms the counterpart evidence; otherwise unresolved |
| Declined | A required signer declined, with a reason where the platform stores one | Silence from a signer treated as refusal | Label declined; keep the reason text only after privilege review |
| Voided or canceled | Sender voided or canceled the request; the platform blocks further signing | A later reminder email that implies the request is live | Label voided, and also record whether any signatures preceded the void |
| Expired | Signing deadline passed without completion | A request still listed as in progress during processing | Label expired; note the deadline and the last signer event |
| Unresolved | Records missing, contradictory or unreadable | Guessing from the CLM stage | Keep the case and score abstention as the correct answer |
Field-level schema for one document execution case
Each case needs enough fields to recompute its state without the label. If a reviewer cannot rebuild the answer from the evidence references, the case is not ready. The schema below is a field-level packet a legal operations team can fill as is; the example values are illustrative.
At a glance
Field-level schema for one document execution case
| Field | Illustrative value | Where it comes from | Rule |
|---|---|---|---|
| case_id | EXE-0042 | Assigned by the preparer | Stable across versions of the pack |
| document_version_hash | SHA-256 of the PDF each signer saw | Computed from the signed document | Every signer event must reference the same hash for an executed label |
| required_signers | Role A (vendor), Role B (customer), routing order 1 and 2 | Request recipient list and the signature blocks in the document | Roles, not names; optional recipients and copy-only recipients excluded |
| signer_events | Role A sent, viewed, completed; Role B sent | Platform recipient history | Keep timestamps in UTC with the event type as the platform names it |
| request_status | Voided, with status change time | Request-level status in the platform | Never inferred from a recipient status |
| void_or_decline_reason | Terms changed before countersignature | Platform reason field | Privilege screen before inclusion; truncate or drop if it quotes advice |
| outside_platform_evidence | None, or counterpart pages A and B | Scanned signature pages | Each page linked to the same version hash |
| dates | Signature completion date and effective date clause, kept separately | Platform events and contract text | Never merge the two into one date |
| related_documents | Amendment 1 links to this case as parent | CLM relationships or the documents themselves | Execution of an amendment does not change the parent's state |
| label and evidence_refs | Voided after partial signature; refs to events 3 and 5 | Reviewer decision | Every label cites the event or page that proves it |
Which record controls when the evidence disagrees?
Platform event records beat everything typed by a person. When sources conflict, rank them by how close they sit to the act of signing, and record the conflict in the case instead of silently picking a winner.
A workable order is: first, the signing platform's request and recipient history; second, the executed document itself with every signature block inspected; third, counterpart pages for agreements signed outside a platform; fourth, the CLM status or matter record; fifth, email statements and file names. A lower source can add context, such as why a request was voided, but it cannot overrule a higher one on whether a signature happened.
Version is the conflict that catches teams most often. If the vendor signed version three and the customer signed version four after a late edit, both parties signed something, but no single version carries both signatures. The case is partially signed on each version unless counsel decides otherwise, and the version hash field is what makes the problem visible.
The legal frame explains why the dataset should not decide more than this. Under the federal E-SIGN Act, a signature or contract may not be denied legal effect solely because it is electronic, and the Uniform Electronic Transactions Act states the same rule for records and signatures in adopting states. The UETA drafters note that this does not establish whether any given record, signature or contract is effective; that remains substantive law. A completed request proves the signing process finished, not that the agreement is enforceable.
Worked case (illustrative): the vendor agreement only the vendor signed
This case is illustrative and invented for teaching; no real parties or documents are described. It shows the starting state, the linked evidence, the decision and the outcome check in the order a reviewer works through them.
Starting state: the contract repository lists a vendor services agreement at stage Signed, and the stored file is named with the word signed. The signing platform shows one request with two required signers, the vendor at routing order one and the customer's authorized signer at routing order two.
Evidence: the vendor's recipient record shows sent, viewed and completed on day one. The customer signer shows sent on day one and nothing after. On day nine the sender voided the request with the reason that commercial terms changed. On day twelve a second request went out with a revised version; both required signers completed it by day fourteen, and its document hash differs from the first.
Decision: the first request is labeled voided after partial signature, with the vendor listed as the only completed signer. The second request is labeled fully executed, with the execution timestamp set to the customer signer's completion on day fourteen. The CLM stage was right only by accident, because it pointed at the wrong file.
Outcome check: the reviewer confirms that later records reference the revised version, for example a purchase order citing the new agreement date. The counterexample to include in the same pack is a paper deal where each party signed a separate counterpart page of the same version. It is labeled executed outside a platform only after counsel confirms the counterpart evidence, and unresolved if one page is missing.
Turning the cases into evaluation tasks a model can fail
A task pack earns its keep when it contains the cases a model is tempted to get wrong. Build each task so the correct answer requires reading the evidence references, and include abstention as a valid answer.
At a glance
Turning the cases into evaluation tasks a model can fail
- State classification: given the evidence packet, return one state from the closed list. Score confusion between partially signed and executed as a critical error, separately from other mistakes.
- Missing signer identification: return the roles that have not completed. Score exact set match.
- Execution dating: return the last required completion timestamp and, separately, the effective date clause. Score each independently.
- Version mismatch detection: flag cases where signers completed different document hashes.
- Superseded request handling: given two requests for the same agreement, identify which one controls and why.
- Abstention: for unresolved cases, the correct output is that the evidence is insufficient, with the missing item named.
- Report per-state precision and recall, the critical error count, and the abstention rate on unresolved cases, and publish the state distribution of the pack so readers can see how many hard cases it holds.
Privilege, confidentiality and counterparty screens before cases leave legal
Signing metadata is usually less sensitive than the contract text, but it is not automatically safe to share. Counsel should screen every case before it leaves the legal department, and the screen result belongs in the case record.
Three screens matter most. The privilege screen removes decline reasons, void reasons, comments and email excerpts that carry legal advice or reflect counsel's strategy. The confidentiality screen checks whether the counterparty agreement restricts disclosure of its existence or terms; a metadata-only packet that keeps roles, events and hashes may fit where full text cannot. The personal data screen replaces signer names, emails and IP details with consistent role-based pseudonyms so that the same signer stays the same placeholder across cases.
Scope out matters under a litigation hold, agreements whose confidentiality terms forbid any disclosure, and cases where the only evidence is privileged correspondence. Holding access to a document, or the right to process signer data, is not the same as the right to license it; each needs its own answer.
Offering signature workflow history for AI licensing
Contract signing histories with clean event records are the kind of operational evidence legal AI teams find hard to obtain from public filings, which rarely show the failed or abandoned paths. If you are weighing whether your agreement workflow records could be licensed, SourceX can help: it runs sourcing, rights review, contracting, preparation and delivery for companies licensing operational records to AI developers.
A legal team can learn whether its company qualifies from a short assessment, with no signing records uploaded. Nothing is delivered until your company has approved the scope and terms and signed the agreement, so a counsel-screened sample like the one described above can shape that scope before any records move.
Frequently asked questions
Is a contract signed by only one party binding?
Sometimes, depending on the law that applies, the contract's own terms and how the parties behaved, which is why the dataset should not decide it. Label the documentary state as partially signed and leave enforceability to counsel reviewing the specific facts.
Does an electronic signature count the same as a handwritten one?
In the United States, the E-SIGN Act and state UETA laws say a signature or contract cannot be denied legal effect solely because it is electronic. Those rules validate the medium; they do not make any particular agreement effective, so the execution state still has to be proven from the records.
What should a document execution state evaluation task pack include?
A closed list of states, one evidence packet per case with signer events, request status, version hashes and dates, a label that cites its evidence, and counterexamples such as voided and version-mismatched requests. It also needs unresolved cases where the right answer is to abstain.
Which date should the dataset record as the execution date?
Record the timestamp of the last required signer's completion as the execution date, and record the effective date stated in the contract as a separate field. They often differ, and merging them teaches a model the wrong rule.
Can CLM status fields be used as labels?
Only as a pointer to cases worth checking. A CLM stage is often set manually or by automation and can say signed when only one party has signed, so the label should come from the signing platform's records or the executed document.
Sources
- Docusign's eSignature API specification defines envelope statuses (completed, declined, voided and others) and notes that a recipient status of signed is a temporary processing state before completed. Source
- Dropbox Sign's API specification describes is_complete as whether a signature request has been fully executed by all signers and lists per-signature status codes. Source
- Adobe Acrobat Sign documents that a canceled agreement cannot be completed and can only be copied and sent as a new agreement. Source
- Adobe Acrobat Sign documents that expiration is terminal and that agreements without a set date expire after 365 days. Source
- 15 U.S.C. 7001(a) provides that a signature, contract or record may not be denied legal effect solely because it is in electronic form. Source
- The Uniform Electronic Transactions Act gives electronic records and signatures legal recognition, and its comments say this does not establish the effectiveness of any given record, signature or contract. Source
See if your company qualifies
A short company assessment. No data uploads are needed.