Trainer and Facilitator Guide
When To Use
A colleague delivers your session next month and all they have is your slides. Use this when a timed plan exists and the person who designed it will not be in the room. It answers: what is each segment for, how does it start, what do I ask, and what goes first when I am running late?
When Not To Use
If you and your team run the session this week, you need clock times, owners and kit, which is the Workshop Run Sheet. If several trainers must learn the programme by practising it, this guide is what they are handed and Train-the-Trainer Handover is the skill. If there is no timed flow yet, write the Training Session Plan first.
Inputs
- The session plan or agenda with timings, the objectives and the slides.
- Your own notes on where people usually struggle and what each segment is really for.
- Who will deliver, and how well they know the topic and the group.
If you have none of this, I start from the objectives and a rough order of segments, and mark the output as a first draft.
Approach
A practice standard for delivery guides, built on Gagné's nine events of instruction (Northern Illinois University's teaching centre page). Each segment names the event it serves, so the colleague knows why it exists and can adapt it without breaking it. What gets written down is the part slides never hold: the designer's knowledge of where it goes wrong. The failure it prevents: a new trainer reads the speaker notes word for word, runs late, and cuts the practice because it came last on the page.
Workflow
- Ask at most three questions: who delivers it and how well do they know the topic, which segment worries you most and why, and what must stay as designed against what they are free to change?
- Per segment, write its purpose, the event it serves, the time, the cue to start (what the trainer says or shows first) and three to five key points as short prompts. Prompts, never a script.
- Add the questions to ask, each with what a good answer sounds like and a follow-up if the answer is thin, so the trainer knows when to move on. Questions about people's work beat questions about the slide.
- Write word for word only the activity setup: the task, the group size, the time, what to bring back. A muddled setup costs more minutes than any content.
- Add the timing flex per segment: what to cut if late, never the practice, and what to add if early.
- Write the "what the designer knows" note per segment from your notes: where people usually struggle, what the segment is really for. Where your notes say nothing, I leave a marked gap for you to fill and do not guess.
- Check the guide: timings match the plan, no line asks the trainer to judge attendance or keep notes on anyone, and difficult situations point to the Difficult Moments Plan. The guide can be made as a document in Claude Docs (beta).
Output Format
# Trainer and Facilitator Guide
Session: [title] | Length: [minutes] | Room or video call: [format] | Written by: [designer] | Delivered by: [trainer]
## Before you start
Must stay as designed: [what] | Free to change: [what] | For difficult situations, see: [where the plan is kept]
## Segment [n]: [name]
| Purpose | Event it serves | Time | Cue to start |
|---|---|---|---|
| [why this segment exists] | [one of the nine events] | [minutes] | [what you say or show first] |
Key points (prompts, not a script): [prompt] / [prompt] / [prompt]
| Question to ask | A good answer sounds like | If the answer is thin |
|---|---|---|
| [question about their work] | [what you are listening for] | [follow-up] |
Activity setup, word for word: "[The task]. [Group size]. [Time]. [What to bring back]."
| If late, cut | If early, add | What the designer knows |
|---|---|---|
| [content, never the practice] | [extension] | [where people usually struggle; what this segment is really for] |
## Open questions
- [gap the designer still has to fill]
## Decision
[Designer] and [delivering trainer] walk the guide together and agree changes by [date]; [delivering trainer] decides how to adapt it on the day.
Done When
- Every segment names its purpose, the event it serves and its cue to start.
- Key points are prompts; only activity setups are word for word.
- Every segment has a cut if late, and no cut removes practice.
- Each "what the designer knows" note is yours or is marked as a gap.
Quality Bar
- A trainer who was not in the design can run the session from the guide and the plan, and every question tells them what a good answer sounds like.
- Timings match the plan; any change is flagged, not silent.
- Nothing is invented about the group, the job or past sessions; a gap stays a gap.
- Claude drafts the guide; the trainer who delivers adapts it to the room, and it carries no notes on any participant.
Next
Run fac-training-slide-outline (Training Slide Outline) to make the slides serve the guide, not the other way round.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: fac-trainer-facilitator-guide3description: Writes the guide a colleague delivers your session from, producing for each segment its purpose and cue to start, key points as prompts, questions with what a good answer sounds like, activity setup word for word and what to cut if late. Use for "run fac-trainer-facilitator-guide", "facilitator guide", "trainer guide", "leader guide for a workshop", "instructor guide", "trainer notes for this session", "someone else is delivering my session", "all they have is my slides", part of the Claude for Trainers and Facilitators Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/fac-trainer-facilitator-guide6---78# Trainer and Facilitator Guide910## When To Use11A colleague delivers your session next month and all they have is your slides. Use this when a timed plan exists and the person who designed it will not be in the room. It answers: what is each segment for, how does it start, what do I ask, and what goes first when I am running late?1213## When Not To Use14If you and your team run the session this week, you need clock times, owners and kit, which is the Workshop Run Sheet. If several trainers must learn the programme by practising it, this guide is what they are handed and Train-the-Trainer Handover is the skill. If there is no timed flow yet, write the Training Session Plan first.1516## Inputs17- The session plan or agenda with timings, the objectives and the slides.18- Your own notes on where people usually struggle and what each segment is really for.19- Who will deliver, and how well they know the topic and the group.20If you have none of this, I start from the objectives and a rough order of segments, and mark the output as a first draft.2122## Approach23A practice standard for delivery guides, built on Gagné's nine events of instruction (Northern Illinois University's teaching centre page). Each segment names the event it serves, so the colleague knows why it exists and can adapt it without breaking it. What gets written down is the part slides never hold: the designer's knowledge of where it goes wrong. The failure it prevents: a new trainer reads the speaker notes word for word, runs late, and cuts the practice because it came last on the page.2425## Workflow261. Ask at most three questions: who delivers it and how well do they know the topic, which segment worries you most and why, and what must stay as designed against what they are free to change?272. Per segment, write its purpose, the event it serves, the time, the cue to start (what the trainer says or shows first) and three to five key points as short prompts. Prompts, never a script.283. Add the questions to ask, each with what a good answer sounds like and a follow-up if the answer is thin, so the trainer knows when to move on. Questions about people's work beat questions about the slide.294. Write word for word only the activity setup: the task, the group size, the time, what to bring back. A muddled setup costs more minutes than any content.305. Add the timing flex per segment: what to cut if late, never the practice, and what to add if early.316. Write the "what the designer knows" note per segment from your notes: where people usually struggle, what the segment is really for. Where your notes say nothing, I leave a marked gap for you to fill and do not guess.327. Check the guide: timings match the plan, no line asks the trainer to judge attendance or keep notes on anyone, and difficult situations point to the Difficult Moments Plan. The guide can be made as a document in Claude Docs (beta).3334## Output Format35```markdown36# Trainer and Facilitator Guide37Session: [title] | Length: [minutes] | Room or video call: [format] | Written by: [designer] | Delivered by: [trainer]38## Before you start39Must stay as designed: [what] | Free to change: [what] | For difficult situations, see: [where the plan is kept]40## Segment [n]: [name]41| Purpose | Event it serves | Time | Cue to start |42|---|---|---|---|43| [why this segment exists] | [one of the nine events] | [minutes] | [what you say or show first] |4445Key points (prompts, not a script): [prompt] / [prompt] / [prompt]46| Question to ask | A good answer sounds like | If the answer is thin |47|---|---|---|48| [question about their work] | [what you are listening for] | [follow-up] |4950Activity setup, word for word: "[The task]. [Group size]. [Time]. [What to bring back]."51| If late, cut | If early, add | What the designer knows |52|---|---|---|53| [content, never the practice] | [extension] | [where people usually struggle; what this segment is really for] |54## Open questions55- [gap the designer still has to fill]56## Decision57[Designer] and [delivering trainer] walk the guide together and agree changes by [date]; [delivering trainer] decides how to adapt it on the day.58```5960## Done When61- Every segment names its purpose, the event it serves and its cue to start.62- Key points are prompts; only activity setups are word for word.63- Every segment has a cut if late, and no cut removes practice.64- Each "what the designer knows" note is yours or is marked as a gap.6566## Quality Bar67- A trainer who was not in the design can run the session from the guide and the plan, and every question tells them what a good answer sounds like.68- Timings match the plan; any change is flagged, not silent.69- Nothing is invented about the group, the job or past sessions; a gap stays a gap.70- Claude drafts the guide; the trainer who delivers adapts it to the room, and it carries no notes on any participant.7172## Next73Run fac-training-slide-outline (Training Slide Outline) to make the slides serve the guide, not the other way round.7475## About the makers7677This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).