Inputs
- A representative, permissioned document set
- Field definitions
- Expected source-span format
- A legal reviewer
Control points
- No silent field guessing
- Source span for every value
- Missing is allowed
- Human approval before system-of-record updates
Human approval gate
A qualified legal or contract owner approves meaning-dependent fields and every system-of-record write.
The workflow
Every step includes a check that can stop the process before risk moves downstream.
- 01
Define each field
Specify the field meaning, accepted formats, and how to represent missing or ambiguous values.
Gate: The schema does not force the model to invent a value. - 02
Preserve document coordinates
Request page or section references and the minimal supporting excerpt for each candidate value.
Gate: A reviewer can locate the original wording. - 03
Validate mechanically
Check dates, currencies, required keys, and cross-field rules before review.
Gate: Schema failures are rejected, not repaired invisibly. - 04
Review legal meaning
A qualified person confirms clauses whose meaning depends on context or jurisdiction.
Gate: The workflow distinguishes extraction from interpretation. - 05
Audit the write-back
Only approved values enter a contract or procurement system, with document and reviewer references.
Gate: Every system-of-record change has an audit event.
Candidates to pilot
Inclusion means relevant product shape, not measured superiority.
Sources checked
Open the original pages before relying on a time-sensitive product decision.