Jurisdiction playbook — the process guidance ("how do we handle X") the case assistant grounds its answers on, scoped by legal authority
Last updated: July 29, 2026 by Steve
Jurisdiction Playbook
The Jurisdiction playbook is your office's written process guidance — short, plain-language entries that answer "how do we handle X" for your jurisdiction. It is the complement to the exemption/statute grounding the case assistant (Ask AccessPoint) already uses: where the statute grounding answers "what can I withhold," the playbook answers "what's our process for transferring a request," "how do we handle a fee waiver," or "who signs off on an extension." When AI Assist is deployed, the assistant reads your enabled playbook entries directly, so its how-to answers reflect your procedures rather than generic advice.
The playbook is part of the optional AI Assist capability. Entries are stored and editable whether or not AI Assist is deployed, but they only influence the assistant when it is. See the Features page.
Where to Find It
Open Settings from the app toolbar and choose Jurisdiction playbook in the Foundations group.
An Entry
Each playbook entry is a single topic and its guidance:
| Field | What it holds |
|---|---|
| Topic | The short title of the procedure — for example, "Transferring a request (ATIA s.8)". |
| Content | The plain-language process guidance itself — the text the assistant grounds on. Write it the way you'd explain the step to a new coordinator. |
| Legal authority (scope) | The legal authority this guidance applies to — so a rule that only applies under one Act is offered only on cases under that Act. Leave it unset for general guidance that applies everywhere. |
| Keywords | Optional comma-separated retrieval hints to help the assistant find the entry. |
| Enabled | Only enabled entries are used for grounding; disable one to retire it without deleting the history. |
Scoping to a Legal Authority
Scoping keeps guidance relevant. An entry scoped to a specific legal authority is only used when the assistant is answering about a case governed by that Act; an entry with no authority set is treated as general and applies across every case. This mirrors how the rest of the platform hangs off the legal-authority spine.
Seeded by Configuration Packs
Jurisdiction packs can seed playbook entries for their regime, so a freshly imported jurisdiction arrives with sensible starting guidance. Pack-seeded entries are safe to edit: once an administrator changes an entry, a later pack re-import will not overwrite your version. See Configuration Packs.
Tips
- Keep each entry to one topic and a few sentences — short, specific guidance grounds better than long policy prose.
- Scope narrowly. If a step only applies under one Act, set that authority so it isn't offered on unrelated cases.
- Disable rather than delete when a procedure changes, so you keep the history.