Trainer kit — run Veil training for your team

Everything a facilitator needs: what to stage on the demo instance before each module, a 90-minute session plan for Foundation, and a printable completion sheet.

Before any session

• Demo instance readySeeded demo data; your Administrator can reset it between sessions.
• One login per trainee, in the right roleInvited by the Administrator; roles and visibility set before the session, not during it.
• A trainer account one tier upYou’ll need to send documents back (senior tier) or approve them (Final Approver) to demonstrate hand-offs.
• Point everyone at this siteEach trainee opens Start Here and their role’s first-hour checklist.

What to stage, per module

Module 00 — Foundation (everyone)

• A case whose Documents tab shows all four review states side by side — “Ready for Review”, “In Review”, “Reviewed (Initial)”, “Signed Off”
• At least three active cases at different lifecycle stages so “Home” and “Cases” look alive
• One document open in review with cards in each decision state — “to decide”, “redacted”, “kept visible”
• Remind trainees: this module is look, don’t touch — no decision, sign-off, or export buttons

Module 02 — The Reviewer

• Per trainee: one document at “Ready for Review”, assigned to them (an assigned document is read-only to everyone else)
• A detection spread on that document: several at ≥ 90% confidence, at least two below 90%, one flagged [REVIEW REQUIRED], and one obvious item the pipeline missed (for the manual-detection step)
• A trainer on the senior tier ready to “Request Changes” → “Send Back” with a written reason (exercise step 10)

Module 03 — The Senior Reviewer

• A case with documents at “Reviewed (Initial)”, including one planted mis-grounded redaction for the audit exercise
• A draft sign-off already made on the target document, so “Compare versions” (⋯ menu) has a “Draft (Submitted for Review)” snapshot to diff
• Recurring names and phone numbers across several documents, so the “Bulk review” page shows meaningful “Review by reach” groups
• On LGOIMA demo instances only: a document to “Mark as PE” (the public-excluded exercise; hidden on OIA instances)

Module 04 — The Final Approver

• Documents at “Reviewed (Initial)” reviewed by a different account than the trainee — separation of duties blocks approving your own review work
• A clean case that can be fully approved, attested (“Granted in part”), exported, and downloaded on camera-free demo data
• The blocked-export demonstration: either a case staged to fail verification or the failure screenshots from the guide — never “fix” it by bypassing

Module 01 — The Lead

• Departments configured, so “Log a new request” has real “Department(s)” options
• Sample synthetic files for the upload exercise (a PDF, a DOCX, an EML with an attachment)
• At least one reviewer and one approver account visible in the “Review Workflow Setup” palettes
• “Custom Rules” reachable with one Active rule already in the list

Module 05 — The Administrator

• An Administrator login for the trainee (and nothing else — the walls are the lesson)
• Organisation identity set, so the agency-name/export dependency can be shown rather than suffered
• Know your instance’s service status (OCR, AI detection, Microsoft 365) — §7 of the module briefs staff from configuration facts

Find & reuse past work (Foundation + Lead + Reviewer)

• An existing case whose request summary is close to the one trainees will type — so the “Similar requests” panel surfaces it live as they type
• That case holds at least two documents in the trainees’ scope, so “Attach documents…” has something to copy
• An identical file (byte-for-byte) already processed on a prior case, so upload or attach offers the import — a re-saved copy will not match
• Optional: a second similar case outside the trainees’ scope, to show the padlocked, link-less result

A 90-minute Foundation session that works

A 20-minute find-&-reuse walkthrough

One pass that demonstrates all three tiers — find, attach, imported analysis — and the guarantee behind them. Run it after Foundation, or as a standalone for Leads and Reviewers. Stage the demo per Find & reuse past work above.

1. Type a summary, don’t save yet on “Log a new request”, type a request summary close to the staged case and pause — the “Similar requests” panel surfaces the match.
2. Open the match and read it make the point: a match is a prompt to look, not an instruction to reuse. Decide it is the same territory, new request.
3. Create the case now finish creating it — attaching needs somewhere for the copies to land.
4. Find Similar → attach two documents on the case page, select “Find Similar”, then “Attach documents…”, tick two, and “Attach”. Show the “Attached” badge and that the source case is untouched.
5. Accept the import on the identical file, accept the offered import — the document carries an “Imported” badge and provenance chips.
6. Open one and see everything pending every detection is pending, including ones a previous reviewer had decided. This is the moment that lands hardest — slow down here.
7. Decide them and sign off decide each detection, then sign off — and if you skip one, let trainees meet Veil’s sign-off refusal deliberately.

The line to repeat until it sticks: you inherit the finding, never the decision.

Completion sign-off sheet (print me)

Site checklists and quiz passes are stored per browser, so keep the official record on paper or in your LMS.