Keep the agreement, amendment and playbook together.
The example agreement has four short clauses. A separate amendment replaces the invoice review period in C1. The invented playbook defines three comparison checks and one missing-information rule. Each document has an identifier and date so the reviewer can identify the exact source.
These fixtures are educational document-comparison material. They are not a contract template, legal advice or professionally approved clause recommendations. No practitioner review or application run is represented here. Use the files to discuss the task and establish a reference method.
Inspect the reference findings clause by clause.
A useful finding names the criterion, the supplied text, any amending text and the issue for review. Keep the reviewer’s eventual decision in a separate column. A model should not silently replace a clause or decide whether the party should accept a term.
The table is a hand-authored illustrative reference key. A future product test should retain its own actual answers, citation references, errors and corrections separately.
| Check | Supplied evidence | Illustrative finding |
|---|---|---|
| P1: flag invoice periods over 30 days | C1 says 45; A1 replaces it with 30. | No flag under the invented P1 after applying A1. |
| P2: flag working-copy retention over 60 days | C2 says 90 days. | Flag the difference between C2 and the invented P2. |
| P3: confirm the draft label | C3 requires “For review”. | The requested label is present. |
| P4: report an absent renewal provision | C4 supplies no renewal provision. | Not found in the supplied fixture; no legal consequence determined. |
Test omission, amendment handling and abstention.
Begin with “Which clauses differ from this supplied playbook?” Then ask “Does C1 still contain the effective invoice period in this example?” A response that flags 45 days without considering A1 has failed the amendment check even if it quotes C1 accurately.
Ask for a renewal term and its source. The correct reference behavior for this fixture is to report that the term is not found. Do not fill the gap from a typical agreement or suggest that absence settles an interpretation. In a real evaluation, the practitioner decides whether the document set is complete and which conclusions it supports.
Make the review handoff inspectable.
A review table can carry a finding ID, playbook rule, agreement clause, amendment reference, stated difference, uncertainty and reviewer decision. Keep the agreement’s words separate from any suggested drafting. When an output is exported or saved, inspect the proposed action and confirm the permitted destination.
Test one added exception, one inconsistent defined term and one scanned page only when the candidate package supports the required extraction. Record failures in parsing or page references separately from errors in applying the rubric. A successful plain-text check would not establish competence on all contract files.
- Read every cited clause in context.
- Confirm whether supplied amendments change the comparison.
- Retain missing and ambiguous evidence.
- Record reviewer edits and accepted findings.
- Approve any proposed file change before applying it.
Measure the actual configuration.
Use a supported Apple Silicon Mac and record package, operating system, memory, model, settings and source files. Agree on selected-file access and any approved external provider path. Inspect all relevant processing layers with the legal IT reviewer before using confidential material.
Compare the ordinary review process and the candidate workflow against the same permitted files. Measure time to a reviewed result, omitted issues, false flags, citation correctness and corrections. A qualified practitioner must establish expected findings for a real matter-specific evaluation. No review-time saving or task accuracy is claimed by this example.
Scope one contract-document task.
Describe the document types, jurisdiction, review owner, device profile and intended output using nonsensitive details. Begin with a synthetic pack. Agree separately on authorization and handling before sharing actual agreements. The goal is a bounded acceptance decision with an accountable professional reviewer.
Sources and further reading
- Qwerty product and selected-file workflow · Reviewed 2026-10-16
- Qwerty deployment and supported environment · Reviewed 2026-10-16
- Qwerty evaluation methods · Reviewed 2026-10-16