Evidence-led executive learning · reviewed August 2026
Annotated safe-use boundary and escalation card
Fictional example: drafting internal meeting summaries.
| Field | Exemplar entry | Why it is decision-quality |
|---|---|---|
| Purpose | Draft decisions and actions for participant verification after internal project meetings. | Names a correctable support task. |
| Information | Approved meeting notes in the managed workspace. Exclude performance, health, disciplinary, customer-secret and legally privileged content. | Gives users recognisable permitted and prohibited classes. |
| Authority | Organiser opens the notes, verifies each decision, corrects owners/dates and sends a draft to participants. Project sponsor owns the final record. | Specifies evidence, timing and decision ownership. |
| Affected-person protection | Participants receive notice, may correct the draft and may request manual notes. | Makes correction and an alternative channel practical. |
| Escalation | If prohibited information enters the service or a summary is sent externally, stop distribution, notify the privacy/security channel and project sponsor, and record recipients and containment. | Trigger and first actions are observable. |
| Change rule | Performance assessment, external meetings, recording audio or a new provider requires new approval. | Approval cannot silently transfer to a new purpose or system. |
Weak counterexample
“Staff may use AI responsibly with human oversight. Avoid sensitive data.” Users cannot tell which environment, data, review, affected-person protection, escalation or owner applies.