Lesson objective
Run an AI-assisted legal task through the seven stages of the Level 2 workflow, stopping at each gate before the next stage begins.
Plain-language explanation
Why this matters now
Triage tells you whether a task belongs with a tool. The workflow tells you how to run it. Every remaining module in this level — prompting, drafting, contract review, research, citation checking, client communication, billing — is one part of the same seven-stage sequence, taught in depth. Learn the sequence once here and the rest of the level becomes variations on a shape you already know.
The reason to insist on a fixed sequence is that ad-hoc use produces ad-hoc results. Adoption is no longer the problem: Clio's 2025 Legal Trends Report, published October 16, 2025, describes adoption plateauing at 79%. The Thomson Reuters Institute's 2026 report, published February 9, 2026, found only 18% of respondents saying they knew their organisation tracked return on investment. A profession that has largely adopted the tools and largely cannot say what they produced is a profession working without a defined process. The workflow is that process at the level of a single task.
A question to sit with
Two paralegals at the fictional firm Ashgrove Partners produce the same document summary on the same day using the same tool. One takes eleven minutes and one takes fifty. Both summaries are accurate. Which one would you rather defend to a supervising attorney six weeks later?
The honest answer is: the one that can show its stages. Accuracy that cannot be demonstrated is indistinguishable from luck.
What goes wrong
The failures here are all failures of sequence — a stage skipped, or two stages collapsed into one.
- Starting at the prompt. No triage, no source material assembled, no idea what "done" looks like. The prompt becomes a wish.
- Unverified inputs. The tool is given a fact packet nobody checked. Everything downstream inherits the error, and it now carries the authority of a polished document.
- Verification merged into review. The person reading for quality is the same person, in the same pass, supposedly checking every fact and citation. In practice one of the two jobs gets done.
- Review by fluency. The output reads well, so it reads as correct. Level 1 named this; it does not stop being true because you are now more experienced.
- No named approver. "The team reviewed it." Six weeks later nobody knows who read what.
- No record. The work is fine and the file cannot show it. Stage 7 is the only stage that survives the matter.
- Reverse-engineered verification. Checking after the document has gone out, so that every problem found is now a correction to something already delivered.
The practical answer
Seven stages. Each one has a gate: a question you answer yes to before moving on.
| # | Stage | What you do | The gate |
|---|---|---|---|
| 1 | Triage | Consequence, verifiability, data class, mode | Is the mode written down? |
| 2 | Assemble | Gather and verify the source material the task will rest on | Has every input been checked against its origin? |
| 3 | Instruct | Write the prompt: role, task, source, constraints, format, refusal rule | Does the instruction say what to do when the source does not answer? |
| 4 | Generate | Run it; capture the tool, version, date and the output as received | Is the raw output saved before anyone edits it? |
| 5 | Verify | Check facts, quotations, citations, figures and dates at source, as a separate pass | Was every checkable claim checked by someone, against something? |
| 6 | Review and approve | A named licensed attorney reads for judgment, strategy and fitness, then approves | Is there a name and a date on the approval? |
| 7 | Record | Write the matter entry: task, tool, mode, verification, approver | Could a stranger reconstruct this in two minutes? |
Stage 3 has a shape you will reuse all level. Module 02 takes it apart properly; here is the skeleton:
- Role — who the tool is acting as, and for what audience.
- Task — one verb, one deliverable.
- Source — what material to use, and that it may use nothing else.
- Constraints — length, tone, what must not appear, jurisdictional limits.
- Format — the structure you want back, including a citation format that makes checking mechanical.
- Refusal rule — what to output when the source does not answer. "Write NOT IN SOURCE" beats a confident guess every time.
Why 5 and 6 are separate stages. Verification asks "is this true." Review asks "is this right." They use different mental gears and they can be done by different people. In many firms a paralegal or legal assistant performs stage 5 under supervision and an attorney performs stage 6. Collapsing them means the reviewer skims for accuracy while reading for judgment and does neither well.
Where each Level 2 module sits in the workflow
Modules 2 and 3 are stage 3. Module 4 is stages 2 to 4 for drafting. Modules 5 and 6 are stages 3 to 6 for contract review. Modules 7 and 8 are stages 3 to 5 for research. Module 9 is stage 6 in a court context. Modules 10 to 12 are what leaves the firm. Modules 13 and 14 are stages 1 and 7. Nothing in this level sits outside the sequence.
Remember this
- Seven stages: triage, assemble, instruct, generate, verify, review and approve, record. Each has a gate.
- Verify and review are different jobs. Do not run them in one pass.
- The refusal rule in the instruction turns silent invention into a visible gap.
- Save the raw output before you edit it.
- The approval carries a name and a date, or it did not happen.
Legal example
Tomás Ferreira, a senior paralegal at the fictional firm Ashgrove Partners, must produce an issues-and-dates summary of a fictional 60-page supply agreement between the fictional parties Brightwater Mutual and Del Rio Fabrication, for the attorney Nadia Blankenship.
Stage 1, triage. Consequence: moderate — it feeds Nadia's advice, which is high. Verification: the agreement itself, which he holds as a text-searchable PDF. Data class: client confidential; the firm's tool is approved for it. Mode: assistive. Ninety seconds.
Stage 2, assemble. He confirms the PDF is the executed version by checking the signature page and the execution date against the closing index, and he notices that Schedule 3 is referenced but missing. He requests it first: a summary built on an incomplete agreement is an incomplete summary that looks complete.
Stage 3, instruct. His prompt names the role (a paralegal preparing an internal issues list), the task (extract obligations, dates and termination triggers), the source (only the attached agreement and its schedules), the constraints (no legal conclusions), the format (a table with a clause reference and page number on every row) and the refusal rule (write NOT IN SOURCE where the agreement is silent).
Stage 4, generate. He runs it, notes the tool name, the version shown and the date, and saves the raw output before touching it.
Stage 5, verify. Separate pass, separate sitting. He checks every row's clause reference and page number against the agreement. Thirty-one rows check out. Two do not: one cites a clause that exists but says something narrower than the summary states, and one confidently fills in a notice period the agreement never specifies — precisely the gap the refusal rule was meant to catch, missed on that row. He corrects the first, replaces the second with NOT IN SOURCE, and flags it.
Stage 6, review and approve. Nadia reads for judgment, not for typos. She sees the flagged notice-period gap and recognises it as the commercially important point in the whole agreement. She approves with her name and the date.
Stage 7, record. Four lines: task and mode, tool and version and date, verification by Tomás against the executed agreement with its two corrections, and Nadia's approval.
The summary took Tomás about an hour, against perhaps three unaided. The hour includes the verification pass that found the invented notice period — which is the whole argument for the workflow.
Responsible-use warning
Never merge stage 5 into stage 6. When one person reads once, for quality and accuracy at the same time, fluent prose wins and the fact-checking quietly does not happen. The second most common failure is generating before assembling: if the source material has not been confirmed as complete and current, every downstream stage inherits the gap and dresses it in confident formatting. And never let stage 7 wait until the matter closes; a record written from memory weeks later is a reconstruction, not a record.
Human-review requirement
A named licensed attorney performs stage 6 and owns the deliverable. The reviewer confirms that stage 2 inputs were verified and complete, that the instruction carried a refusal rule, that the raw output was preserved, and that stage 5 was performed as a separate pass by an identified person against an identified source. The reviewer then does the work only a lawyer can do: judging fitness for the client, strategy, tone, what is missing, and whether any legal conclusion in the document is one the lawyer actually holds. Approval is recorded with a name and a date. Supervision of assistance under the applicable rules of the reviewer's jurisdiction is not satisfied by the tool having been approved.
Practical exercise
Use only tools your firm permits, and only fictional material you create.
- Build a fictional source document of at least eight pages: a services agreement, a set of board minutes, or a witness statement for an invented matter. Include three specific dates, two dollar figures, and one deliberate silence — a topic a reader would expect it to address but which it does not.
- Stage 1: write the four-line triage card.
- Stage 2: list the inputs, and write one sentence on how you confirmed each is complete and current.
- Stage 3: write the instruction with all six elements — role, task, source, constraints, format, refusal rule. The format must require a page or clause reference on every item.
- Stage 4: run it. Record the tool, the version shown, and the date. Save the raw output unedited.
- Stage 5: on a separate pass, check every dated item, every figure and every reference against your document. Mark each row verified, corrected, or unsupported.
- Check specifically whether the output invented an answer to your deliberate silence, or correctly wrote NOT IN SOURCE. Record which.
- Stage 6: write the review note a supervising attorney would write — what they checked, what they changed, what they would want to know.
- Stage 7: write the four-line matter record entry.
- Paste the triage card, the instruction, the verification table and the record entry into the submission box. Do not paste the fictional document itself.
Record in the workbook: how many items were corrected at stage 5, and whether the deliberate silence was invented or flagged. Workbook: Module 01 worksheet, Seven-stage workflow log.
Knowledge check
-
Name the seven stages of the assisted task workflow in order.
Answer guidance: Triage, assemble, instruct, generate, verify, review and approve, record. Each stage has a gate that must be answered yes before the next begins.
-
Why are verification and review separate stages rather than one careful read?
Answer guidance: They are different jobs. Verification asks whether each checkable claim is true, against a source. Review asks whether the document is right for the client, the strategy and the audience, which only a lawyer can judge. Done in one pass, fluent writing crowds out the fact-checking, and the accuracy work is the part that silently does not get done.
-
What is a refusal rule and why does it belong in every legal prompt?
Answer guidance: It is the instruction telling the tool what to output when the supplied source does not answer — for example, to write NOT IN SOURCE. Without it, a tool asked to complete a structure will complete it, turning a gap into an invented answer that looks identical to a supported one. With it, the gap becomes visible and you can go and close it.
-
A deliverable is accurate but the file contains no record of who approved it. Which stage failed, and why does it matter?
Answer guidance: Stage 7, supported by stage 6. It matters because accuracy that cannot be demonstrated is indistinguishable from luck when someone asks six weeks later. Under the AI Coalition Network educational standard the approval carries a named licensed attorney and a date; recording it is what makes the supervision visible.
Sources and further reading
- American Bar Association Standing Committee on Ethics and Professional Responsibility — Formal Opinion 512: Generative Artificial Intelligence Tools (2024-07-29). Accessed 2026-09-14.
- American Bar Association — Model Rules of Professional Conduct. Accessed 2026-09-14.
- AI Coalition Network — Certification Educational Standard: Human Review of AI-Assisted Professional Work. Accessed 2026-09-14.
- Clio (Themis Solutions) — 2025 Legal Trends Report (2025-10-16). Accessed 2026-09-14.
- Thomson Reuters Institute — 2026 AI in Professional Services Report (2026-02-09). Accessed 2026-09-14.
- 2025 Legal Trends Report — Clio (Themis Solutions) (October 16, 2025).
- 2026 AI in Professional Services Report — Thomson Reuters Institute (February 9, 2026).