# Facilitator kit: session checklist

<!-- ASSURED Methodology by Timothy Zilber, © Block, Inc., CC BY 4.0
     (https://creativecommons.org/licenses/by/4.0/). Reuse and adapt freely
     with attribution; note any changes you make.
     Template version: 2.0
     ASSURED facilitator kit, printable run sheet
     (https://assured-methodology.vercel.app/docs/teaching/kit). The session
     plans themselves live on the teaching page; where this sheet and the page
     differ, the page wins. -->

**For the facilitator. Print one copy per session.** The plans, prep
estimates and debrief questions are on the teaching page:
https://assured-methodology.vercel.app/docs/teaching

Timings are for 90-minute sessions. When a session runs long, cut the quiz
debate before you cut the exercise.

## Before every session

- [ ] Participants told the prep load (full and minimum path) at least three
      working days ahead.
- [ ] Facilitator prep done (about 2 hours): the session's chapters, the
      relevant answer keys, and the kit files listed below.
- [ ] Pairs assigned (4-12 participants; keep Session 3 pairs for Session 4).
- [ ] Remote: breakout rooms set up, one shared document per pair, keys kept
      out of the main room until the debrief.
- [ ] Answer keys stay with the facilitator. Participants write before they
      see any key.

## Session 1 · The shape of the work (A)

Kit files: `depth-ladder-alert-set.md` (one per participant), unless you
have five sanitized alerts from your own queue.

| Minutes | Block |
| --- | --- |
| 0-5 | Open: the seven questions, and why the record is the deliverable |
| 5-25 | Case A's Alert example, one person per step, "what would you do next" before each reveal |
| 25-55 | Alert quiz as argued discussion: answer alone, defend splits, then explanations |
| 55-80 | Depth ladder: assign a level to each alert, one-line justification, then the key |
| 80-90 | Close: when should IR have been paged in Case A, and what did the wait cost |

- [ ] Collected: each participant's level assignments with justifications.
- [ ] Noted: the quiz item that split the room, and the alert most people
      mis-levelled.

## Session 2 · Who and how much (S · S)

Kit files: Exercise 1 learner packet (`exercise-print-server.md`).

| Minutes | Block |
| --- | --- |
| 0-5 | Open: "who before where" |
| 5-45 | Exercise 1 tasks 1-3 (Alert, Subject, Scope) in pairs, written |
| 45-65 | Debrief against the key: who treated the service account as the subject |
| 65-90 | Subject and Scope quizzes: discuss only the items the room split on |

- [ ] Collected: pair-written subject determinations and scope boundaries.

## Session 3 · Evidence and verdict (U · R)

Kit files: `ai-draft-exercise-1-uncover.md` (one per pair), and the
Exercise 1 anchors (`anchors-exercise-1.md`) for your own calibration
beforehand.

| Minutes | Block |
| --- | --- |
| 0-30 | Exercise 1 tasks 4-5 (Uncover, Risk), pairs keep a visible hypothesis ledger |
| 30-50 | Debrief with the Cognitive traps page open: which trap came closest |
| 50-70 | Risk framing drill: half the room scores impact, half scores likelihood, then combine |
| 70-90 | "Verify the draft": mark the two planted errors, fill the Material AI use field |

- [ ] Collected: Exercise 1 write-ups through Risk (this is the calibration
      set for grading), and each pair's marked-up AI draft.

## Session 4 · The decision and the record (E · D)

Kit files: Exercise 2 and Exercise 3 learner packets; the Exercise 2 and
Exercise 3 anchors for your own calibration beforehand.

| Minutes | Block |
| --- | --- |
| 0-20 | Exercise 1 tasks 6-7 (Escalation decision, Documentation) in the Session 3 pairs |
| 20-50 | Exercise 2 solo, in writing, strictly 30 minutes |
| 50-65 | Debrief: who verified the change ticket, and who deferred to it |
| 65-75 | Exercise 3 as a literal five-minute timed drill, plus the timer-off part |
| 75-90 | Revise one or two volunteer close notes against the rubric, as a group |

- [ ] Collected: each participant's Exercise 2 Risk paragraph and verdict.
- [ ] Post-test (Form B, about 20 minutes) scheduled, if you ran Form A.

## Optional Session 5 · The capstone (2 hours)

Kit files: `capstone-packet.md` (one per candidate, coded, no names),
`capstone-scoring-guide.md` (facilitator only, holds the inject), and
`capstone-score-sheet.md` (two per script).

| Minutes | Block |
| --- | --- |
| 0-10 | Briefing: rules (solo, written, open book, no AI assistant, no conferring), codes handed out |
| 10-55 | Capstone, first part |
| 55 | Hand out the inject to each candidate who has recorded an Escalation decision and its time; the rest receive it at minute 70 |
| 55-100 | Capstone, second part: post-inject update |
| 100-120 | Scripts collected under their codes. No debrief until both raters have scored |

- [ ] Coordinator (not a rater) holds the code-to-name list.
- [ ] Two raters booked, at least one who did not teach the cohort.
- [ ] Raters ran the 15-minute calibration on the anchors before scoring.
- [ ] Raw scores from both raters recorded before any discussion.
- [ ] Debrief scheduled after reconciliation.

## After the course

- [ ] Sign-off on two real cases per participant (a lead reviews two of
      their own queue records; both pass all five rubric checks).
- [ ] Results reported in aggregate only, never used in performance
      evaluation.
