Pre-Work and Invitation
When To Use
People arrive not knowing why they are there, and the pre-read nobody opened is never used anyway. Use this once the date and the plan are firm enough to announce. It answers two questions: what do participants need to read to walk in ready, and what does the facilitation team need to hear before the day?
When Not To Use
If you are still collecting what the group knows or wants, that is a design input and Pre-Session Survey fits. Messages to participants' managers belong in Manager Briefing Note, and anything sent after the session in Post-Session Follow-Up Sequence. Recording and consent wording comes from Session Agreements and Consent.
Inputs
- The session purpose and the agreed plan or agenda, with block names and the date, time, length and place or link.
- One message you have already sent to these people, any material for a pre-read, and the facilitation team's names and roles.
If you have none of this, I start from the session title, the date and one sentence on why it exists, and mark the output as a first draft.
Approach
This rests on Salas, Tannenbaum, Kraiger and Smith-Jentsch's 2012 review of the science of training, which found that what happens before a session matters alongside the session itself, including the expectations people arrive with and how the session was framed to them. So the invitation is treated as part of the design and kept honest. The failure it prevents: a room promised an inspiring day arrives sceptical, and the pre-work nobody mentions in the room teaches the group to skip the next one.
Workflow
- Ask at most three questions: who sends this and through which channel, what word cap do you want on the invitation, and do you want a pre-read at all?
- Write the invitation under your cap, in this order: why this session and why now, what we will have by the end, the practical facts, the "come with" ask, and a line that a calendar invite follows. I cut any sentence that oversells. If the room advises on a decision made elsewhere, the invitation says so.
- Set the "come with" ask: one small, specific thing, tied to a named block and doable in the few minutes you set. If I cannot point to the block that uses it, the ask goes and the invitation says "no preparation needed" plainly. An ask that does the session's work in advance is refused, because then the room is a readout.
- Build the pre-read only if you want one, and only by condensing the material you paste, with two or three focusing questions at the end so reading becomes preparation. With no material, I draft a two-line framing note for a document you already have. Gaps stay marked as gaps.
- Write the reminder: two sentences, the ask repeated, logistics confirmed, no guilt.
- Write the facilitation team's messages: each person's role in one line, the day-before sync with its short agenda, and the debrief hold right after the session so the slot exists before everyone leaves.
- Sweep every draft: dates, times and promises match the agenda, internal shorthand is gone from anything outsiders read, and no message singles out a participant. Then I hand over the invitation for you to read aloud once.
Output Format
# Pre-Work and Invitation Set
Session: [title] | Date: [date] | Sender: [name] | Channel: [channel] | Invitation cap: [word cap]
## To participants
### Invitation ([word count] of [word cap] words)
Subject: [subject line]
[Why this session and why now] [What we will have by the end] [Date, time, length, place or link] [The "come with" ask, or "No preparation needed"] [A calendar invite follows]
The "come with" ask: [one ask, or "none"] | Block where it is used: [block name] | Time it takes: [minutes]
### Pre-read (only if wanted)
Built from: [your source material] | Length: [pages] | [Condensed content, with gaps marked]
As you read: [focusing question] / [focusing question]
### Reminder (send [days] before)
[Sentence one: the ask repeated] [Sentence two: logistics confirmed]
## To the facilitation team
| Message | Send when | Content |
|---|---|---|
| Roles | [date] | [name]: [role in one line] |
| Day-before sync | [date, time, minutes] | Walk the run sheet, confirm roles, review the wobble moves, check materials, agree the signal for "we are behind" |
| Debrief hold | [right after the session, minutes] | Calendar hold only |
## Decision
[Sender] approves the wording and sends the invitation by [date]; [session lead] decides whether a pre-read goes out by [date].
Done When
- The invitation is under the cap you set and carries all five parts in order.
- There is one ask tied to a named block, or the words "no preparation needed".
- Every line of the pre-read traces to material you pasted.
- The team messages name roles, the day-before sync and the debrief hold.
Quality Bar
- No overselling: nothing the session cannot deliver is promised in the invitation.
- Every duration and word cap is yours; I supply no norm for either.
- Facilitation team messages never go to participants, and they describe roles, not people in the room.
- If the session may be recorded, the invitation says only that the wording will be shared beforehand; what consent applies is a point to check with a qualified adviser.
- Claude drafts and you send; the pre-read uses only your material, and nothing in any message singles out a participant.
Next
Run fac-workshop-run-sheet (Workshop Run Sheet) to make the agreed agenda runnable by the clock.
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-pre-work-invitation3description: Drafts everything sent before a session, producing a short invitation, one small "come with" ask or an honest "no preparation needed", a pre-read condensed from your own material, a reminder and the facilitation team's messages. Use for "run fac-pre-work-invitation", "workshop invitation email", "training invitation", "pre-work for a workshop", "write the pre-read", "reminder before the training", "nobody opens the pre-read", "brief my co-facilitators", part of the Claude for Trainers and Facilitators Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/fac-pre-work-invitation6---78# Pre-Work and Invitation910## When To Use11People arrive not knowing why they are there, and the pre-read nobody opened is never used anyway. Use this once the date and the plan are firm enough to announce. It answers two questions: what do participants need to read to walk in ready, and what does the facilitation team need to hear before the day?1213## When Not To Use14If you are still collecting what the group knows or wants, that is a design input and Pre-Session Survey fits. Messages to participants' managers belong in Manager Briefing Note, and anything sent after the session in Post-Session Follow-Up Sequence. Recording and consent wording comes from Session Agreements and Consent.1516## Inputs17- The session purpose and the agreed plan or agenda, with block names and the date, time, length and place or link.18- One message you have already sent to these people, any material for a pre-read, and the facilitation team's names and roles.19If you have none of this, I start from the session title, the date and one sentence on why it exists, and mark the output as a first draft.2021## Approach22This rests on Salas, Tannenbaum, Kraiger and Smith-Jentsch's 2012 review of the science of training, which found that what happens before a session matters alongside the session itself, including the expectations people arrive with and how the session was framed to them. So the invitation is treated as part of the design and kept honest. The failure it prevents: a room promised an inspiring day arrives sceptical, and the pre-work nobody mentions in the room teaches the group to skip the next one.2324## Workflow251. Ask at most three questions: who sends this and through which channel, what word cap do you want on the invitation, and do you want a pre-read at all?262. Write the invitation under your cap, in this order: why this session and why now, what we will have by the end, the practical facts, the "come with" ask, and a line that a calendar invite follows. I cut any sentence that oversells. If the room advises on a decision made elsewhere, the invitation says so.273. Set the "come with" ask: one small, specific thing, tied to a named block and doable in the few minutes you set. If I cannot point to the block that uses it, the ask goes and the invitation says "no preparation needed" plainly. An ask that does the session's work in advance is refused, because then the room is a readout.284. Build the pre-read only if you want one, and only by condensing the material you paste, with two or three focusing questions at the end so reading becomes preparation. With no material, I draft a two-line framing note for a document you already have. Gaps stay marked as gaps.295. Write the reminder: two sentences, the ask repeated, logistics confirmed, no guilt.306. Write the facilitation team's messages: each person's role in one line, the day-before sync with its short agenda, and the debrief hold right after the session so the slot exists before everyone leaves.317. Sweep every draft: dates, times and promises match the agenda, internal shorthand is gone from anything outsiders read, and no message singles out a participant. Then I hand over the invitation for you to read aloud once.3233## Output Format34```markdown35# Pre-Work and Invitation Set36Session: [title] | Date: [date] | Sender: [name] | Channel: [channel] | Invitation cap: [word cap]37## To participants38### Invitation ([word count] of [word cap] words)39Subject: [subject line]40[Why this session and why now] [What we will have by the end] [Date, time, length, place or link] [The "come with" ask, or "No preparation needed"] [A calendar invite follows]41The "come with" ask: [one ask, or "none"] | Block where it is used: [block name] | Time it takes: [minutes]42### Pre-read (only if wanted)43Built from: [your source material] | Length: [pages] | [Condensed content, with gaps marked]44As you read: [focusing question] / [focusing question]45### Reminder (send [days] before)46[Sentence one: the ask repeated] [Sentence two: logistics confirmed]47## To the facilitation team48| Message | Send when | Content |49|---|---|---|50| Roles | [date] | [name]: [role in one line] |51| Day-before sync | [date, time, minutes] | Walk the run sheet, confirm roles, review the wobble moves, check materials, agree the signal for "we are behind" |52| Debrief hold | [right after the session, minutes] | Calendar hold only |53## Decision54[Sender] approves the wording and sends the invitation by [date]; [session lead] decides whether a pre-read goes out by [date].55```5657## Done When58- The invitation is under the cap you set and carries all five parts in order.59- There is one ask tied to a named block, or the words "no preparation needed".60- Every line of the pre-read traces to material you pasted.61- The team messages name roles, the day-before sync and the debrief hold.6263## Quality Bar64- No overselling: nothing the session cannot deliver is promised in the invitation.65- Every duration and word cap is yours; I supply no norm for either.66- Facilitation team messages never go to participants, and they describe roles, not people in the room.67- If the session may be recorded, the invitation says only that the wording will be shared beforehand; what consent applies is a point to check with a qualified adviser.68- Claude drafts and you send; the pre-read uses only your material, and nothing in any message singles out a participant.6970## Next71Run fac-workshop-run-sheet (Workshop Run Sheet) to make the agreed agenda runnable by the clock.7273## About the makers7475This 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).