Paralegals and legal operations staff who review an agent's contract work need onboarding that ties every approval to the legal playbook. This checklist sets access, privilege and red lines first, then shadowing on held drafts, reviewer training and exam, a practicum with real deviations and deadlines, a drill and sign-off scoped to contract types.
What does a legal operations reviewer check?
A legal operations agent triages incoming contracts, drafts standard agreements such as NDAs from approved templates, compares a counterparty's paper against the playbook, flags deviations and tracks renewal and notice dates. Triage and comparison are depth 1; drafting is depth 2. Sending a marked-up draft to a counterparty is held. Accepting a deviation from the playbook is held for a lawyer. Signing is never the agent's.
Three risks matter. A missed deadline: a notice period recorded wrongly means a renewal nobody wanted. A deviation accepted because the counterparty called its clause "standard", which is an external claim, not a fact. And privilege: an agent draft that mixes privileged advice into a document going outside the business. A reviewer must catch all three without becoming the bottleneck the agent was meant to remove. The case that review capacity, not agent capability, limits scale is made in legal services will not scale AI agents without trained reviewers.
How should the checklist be used?
The legal operations manager owns it, with a lawyer signing the red lines. Work in order. No approval rights until stage 5. The teaching method is in how to train the legal operations team to review AI agent decisions, and the general training order in the guide to training teams for AI agents.
The checklist
| Stage | Item | Signed by |
|---|---|---|
| 1. Set-up | Read-only access to the matter workspace and contract repository | Manager |
| 1 | Privilege and confidentiality briefing | Lawyer |
| 1 | Agent capabilities read: triage (1), playbook comparison (1), template drafting (2), outbound mark-ups (held), deviation acceptance (held), deadline entries (3, checked) | Reviewer |
| 1 | Red lines signed: never send to a counterparty a draft that departs from the playbook without a lawyer's approval; never accept a clause because the counterparty calls it standard; always check notice and renewal dates against the signed contract | Reviewer and lawyer |
| 2. Shadowing | Two days with a certified reviewer | Buddy |
| 2 | Seen a deviation escalated to a lawyer | Buddy |
| 2 | Seen a deadline corrected against the source document | Buddy |
| 3. Training | Shared foundation complete | Learning lead |
| 3 | Reviewer modules complete; written exam passed | Learning lead |
| 4. Practicum | Two weeks of real held drafts and entries, confirmed by a buddy | Buddy |
| 4 | Coverage: an NDA with a non-standard term, a supplier contract with an auto-renewal, a draft containing privileged comment, a counterparty insisting on its paper | Manager |
| 4 | Incident drill completed | Manager |
| 5. Sign-off | Assessor sign-off; no missed red line | Assessor |
| 5 | Approval rights by contract type and value | Manager |
| 5 | Renewal date set | Manager |
Worked example
An illustrative in-house legal team at a logistics company brings in Sample Paralegal X. The agent drafts NDAs and low-value supplier agreements from templates and compares inbound contracts to the playbook.
While shadowing, Sample Paralegal X sees the agent flag a counterparty's liability cap at one month's fees against a playbook minimum of twelve months. The counterparty's covering email called it "our standard position". The buddy escalates to a lawyer, who rejects it. Later, the agent records a renewal notice date of 30 days; the buddy opens the signed contract and finds 90.
Her practicum covers 70 held items. She catches a draft where an internal comment, "legal view: we would lose on this clause", had been left in a version marked for sending, and removes it before anything goes out. She escalates a governing-law change she could not assess. Her drill follows how to run an AI agent incident drill for the legal operations team. She is signed off in week 7 with rights to approve NDAs and template supplier agreements below a set value.
Where the Academy fits
Pryme Intelligence Academy provides the shared foundation, reviewer modules and assessor sign-off in stages 3 and 5. Operator certification requires a written exam and a two-week practicum of real review decisions with no missed red line, signed off by a Pryme assessor, and is valid 12 months. Anyone can check the certificate at source, which helps when external counsel asks who approved a draft.
Questions people ask
Should paralegals approve anything without a lawyer?
Within the playbook, yes, once certified and within their rights. Outside it, no. The checklist makes that boundary explicit in the red lines and in stage 5.
How does this differ from the operations checklist?
General operations reviewers handle process exceptions; legal operations reviewers handle documents with legal effect. See the reviewer onboarding checklist for the operations team.
Do payments operations teams face similar deadline risks?
Yes, around cut-off times rather than notice periods. The reviewer onboarding checklist for the payments operations team covers that.