# Fac Session Purpose Brief

> Drafts a one-page session purpose brief, a plain decide or inform statement and an honest verdict on whether this should be a session at all, with the alternatives. Use for "run fac-session-purpose-brief", "the client wants a workshop", "frame this workshop", "what is this session for", "should this be a workshop or an email", "workshop brief", "they asked for a training day", "help me scope this offsite", part of the Claude for Trainers and Facilitators Pack by 90n.

- Skill: `polar-bear-org/fac-session-purpose-brief` (Agent Skill)
- Install (CLI): `npx get-skill add polar-bear-org/fac-session-purpose-brief`
- Raw SKILL.md: https://api.skillmd.com/api/skills/polar-bear-org/fac-session-purpose-brief/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: polar-bear-org (https://skillmd.com/u/polar-bear-org)
- Updated: 2026-11-14
- Page: https://skillmd.com/skills/polar-bear-org/fac-session-purpose-brief

---


# Session Purpose Brief

## When To Use
"The client wants a workshop", the date may already be in the calendar, and nobody has said what must be different afterwards. Run this before you design anything, on a request for a training day, a working session or an offsite. It answers one question: what is this room for, and does it deserve to exist?

## When Not To Use
Not for preparing the conversation with the person who asked: that is Sponsor Kickoff Questions, and this brief is your own page, written before it. Not for a document with options and a price: that is Training Proposal. If the purpose is already agreed in writing and concrete, skip this and go straight to Training Session Plan or Workshop Agenda.

## Inputs
- The request as it reached you: the email, the message, or your notes from the first conversation, with anything you know about the work behind it (what people do today, what is in their way).
- What is already fixed: date, length, room or video call, who is invited, what has been promised to whom.
If you have none of this, I start from one sentence describing the request and mark the output as a first draft.

## Approach
Five framing questions, in a fixed order: outcome, decide or inform, people, what next, constraints. They sit on the first two areas of the International Association of Facilitators' core competencies (the client relationship, then planning the group process), and on the point made by Baldwin and Ford in 1988 and kept in Grossman and Salas's 2011 review of training transfer: whether a session is used depends on the learner, the design and the work environment, so framing starts from the job and not from the content. The failure this prevents is the well-run day that produces nothing, because "alignment" was accepted as an outcome and six weeks later nobody can say what changed.

## Workflow
1. Ask three questions, all at once. What is already fixed (date, length, participants, promises made)? When this ends, what exists that did not exist before, and if your answer is "alignment" or "awareness", what will people do differently afterwards? Is something decided in this room, or does the room give input to a decision made elsewhere?
2. Read the fixed facts first. A booked room changes the job from "should we meet" to "make the booked time worth it", and the brief says which of the two it is doing.
3. Write the outcome as something that can be pointed at: a decision, a shortlist, a plan with owners, a skill people can perform. If the only answer available is still soft, write it as given and mark it "not yet an outcome". Do not polish it into something that sounds concrete.
4. State decide or inform without hedging, and add the line participants will be told. People who believed they were deciding and learn later that they were advising do not come back honest.
5. List the room by role or group: what each uniquely brings, and the design note it creates (a large room needs deliberate splits, a senior room needs someone who can hold it). A role that brings nothing unique is flagged for you to question.
6. Write what happens if the session does not get there: what continues, who picks it up, by when. Then list the fixed constraints as design inputs, not as things to fight.
7. Give the verdict, one of three: a session; a session with a narrower purpose; not a session, with the honest alternative (a memo with comments, three one-to-ones, a short decision meeting, a job aid). A session cannot fix what took years to build, and a room used to announce a decision already made is a communication, not co-creation. Everything nobody has answered goes under "Still unknown".

## Output Format
```markdown
# Session Purpose Brief
**Session:** [working title] | **Asked for by:** [role] | **Status:** [first draft / checked with the sponsor]

**Context:** [Three or four lines: where the work stands, what the request is trying to solve, why now.]
## Purpose
| Question | Answer | Where it comes from |
|---|---|---|
| What exists afterwards that did not before | [a decision / a shortlist / a plan with owners / a skill people can perform] | [the email / the call / not yet an outcome] |
| What people do differently afterwards | [in one line] | [source] |
| Decide or inform, and the sentence participants are told | [decided in this room / input to a decision made by [role] by [date]]. "[one sentence]" | [source] |
| If the session does not get there | [what happens, who picks it up, by when] | [source] |
## The room
| Role or group | What they uniquely bring | Design note |
|---|---|---|
| [role or group] | [what only they bring] | [group split, who holds the room, or none] |
## Fixed constraints
- [date, length, room or video call, promises already made]
## Verdict
[A session / a session with a narrower purpose / not a session.] Reason: [two lines]. If not a session: [the alternative, and who would own it].
## Still unknown
- [what nobody has answered yet, and who could answer it]
## Decision
[Trainer name] and [sponsor name] decide by [date] whether this goes ahead as [a session / a narrower session / the alternative].
```

## Done When
- The outcome line names something that exists afterwards, or is openly marked "not yet an outcome".
- Decide or inform is one of the two, with the sentence participants will hear.
- The verdict is one of the three, with its reason, and the alternative is named where it applies.
- Every gap sits under "Still unknown", not filled in with a guess.

## Quality Bar
- Every answer is traceable to the request, to what you told me, or to "unknown". Nothing is invented to make the page look complete.
- No promise a room cannot keep: the outcome is scoped to what this group can produce in the time that is fixed.
- One page of purpose: no options, no price, no agenda. The brief lists what is unknown and stops there; the questions for the sponsor belong to the next skill.
- Claude drafts the brief; you and the sponsor decide whether the room should exist, and notes about the room describe roles and dynamics to design for, never a file on a person.

## Next
Run fac-sponsor-kickoff-questions (Sponsor Kickoff Questions) to test the brief with the person who asked for the session.

## About the makers

This 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).
