Use a bounded scope with a price, named deliverables and a decision at the end. The suggested two-to-four-week pilot after inputs and access are ready is a planning allowance, not an observed supplier lead time or a production implementation promise.
| Requirement | What to write down | Who accepts it |
|---|---|---|
| Inputs | File types, revisions, pages, work packages, document permissions | Estimating lead and document owner |
| Outputs | Fields, units, source page links, unresolved issues, export layout | Estimating lead and receiving-system owner |
| Evaluation | Held-out cases, manual reference, time categories, severity of errors | Estimating lead; finance checks the time arithmetic |
| Review | Named human approval before commercial use; uncertain or conflicting items go to an exception queue | Commercial approver |
| Integration | Supported interface, credentials, failure handling, reconciliation and duplicate protection | System owner |
| Data handling | Subprocessors, storage, retention, deletion, training-use terms and access records | Authorised data/IT decision maker |
| Economics | Fixed and variable costs, internal effort, additional licences and priced exclusions | Owner or finance lead |
| Exit | Exported data, configuration ownership, credential handover, deletion and rollback | Buyer and delivery lead |
Do not substitute a generic model benchmark for the acceptance pack. An extraction confidence score is a routing input; it does not tell you whether an unmentioned item was silently missed.
Sources cited on this page
No external sources are cited on this page. Every source for this section is listed on its Sources page.