# Fac Sponsor Kickoff Questions

> Prepares a question guide for the kickoff call with the sponsor and turns your notes into a one-page call note with success at work in their words and dated commitments on both sides. Use for "run fac-sponsor-kickoff-questions", "questions to ask the sponsor", "kickoff call with the client", "what should I ask before the workshop", "the sponsor booked the room and disappeared", "get the managers involved", "client discovery call for training", "write up the kickoff call", part of the Claude for Trainers and Facilitators Pack by 90n.

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

---


# Sponsor Kickoff Questions

## When To Use
The sponsor books the room and disappears, then asks three months later why nothing changed. Run this before the call with the person who asked for the session, and again right after it with your notes. It answers: what will the sponsor and the participants' managers do before and after, and what will we look at later to know?

## When Not To Use
Not for your own framing of the request: Session Purpose Brief does that from an email alone, and comes first. Not for the call after delivery (Sponsor Debrief), and not for writing to managers (Manager Briefing Note). If there is no sponsor because people sign up for themselves, skip the call and ask the participants through Pre-Session Survey.

## Inputs
- Your purpose brief, or the request as it reached you.
- Who the sponsor is by role, how long the call is, and what has already been said to participants and their managers, if you know.
- After the call: your own typed notes, with the sponsor's words kept as they said them where you caught them.
If you have none of this, I start from the session topic and the sponsor's role and mark the output as a first draft.

## Approach
The guide follows the before, during and after of Salas, Tannenbaum, Kraiger and Smith-Jentsch's 2012 review of the science of training, which holds that what happens around a session matters alongside the session itself. The questions about the sponsor's part come from Grossman and Salas's 2011 review of training transfer, where support, opportunity to perform and follow-up in the work environment show the most consistent links to use at work. Agreeing who does what before the work starts is ordinary contracting practice. The failure this prevents: a call spent on catering and dates, so the only thing agreed is your part, and the sponsor's part is discovered missing when the debrief arrives.

## Workflow
1. Ask three questions, all at once. Has the call happened yet (guide, or note from your notes)? What did the sponsor ask for, in their words? What has already been told to participants and their managers?
2. Build the "before" band: why now, what people have been told about why they are invited, what would make them want to come. Keep it short. A sponsor who cannot say why now is telling you something about the day.
3. Build the "after, at work" band around one question asked plainly: what would you see people doing that you do not see today? Leave space under it for the answer in the sponsor's own words. Your paraphrase is not a substitute, and it is what the debrief will be read against.
4. Build "the sponsor's part": what will you say to people before the session, what will their managers do before and after, what gets in the way back at work. This band only gets agreement that managers have a part. The message to them is a separate piece of work.
5. Add the two single questions. Scope test: what is this session not expected to fix? Look-back: what will be looked at afterwards, by whom, and when? Put a date on the debrief before the call ends. Then order the guide for the time available and mark the questions to keep if the call is cut short: the "see people doing" question, the sponsor's part and the look-back survive every cut.
6. After the call, turn your notes into the call note: success in the sponsor's words, verbatim; the two columns of commitments, each with a date; anything left open marked as open. If the sponsor spoke about a particular participant, that stays out of the note and out of the design.

## Output Format
```markdown
# Sponsor Kickoff Guide and Call Note
**Session:** [working title] | **Sponsor:** [role] | **Call:** [date, length]
## Question guide
| Band | Question | Keep if the call is cut short | What you heard |
|---|---|---|---|
| Before | Why this session, and why now? | [yes / no] | [notes] |
| Before | What have people been told about why they are invited? | [yes / no] | [notes] |
| After, at work | What would you see people doing that you do not see today? | yes | [the sponsor's words, verbatim] |
| The sponsor's part | What will you say to people before the session? | yes | [notes] |
| The sponsor's part | What will their managers do before and after? | yes | [notes] |
| The sponsor's part | What gets in the way back at work? | [yes / no] | [notes] |
| Scope | What is this session not expected to fix? | [yes / no] | [notes] |
| Look-back | What will we look at afterwards, who looks, and when? | yes | [notes] |
## Call note
**Success at work, in the sponsor's words:** "[verbatim]"
**Not expected of this session:** [in one or two lines] | **What will be looked at afterwards:** [what], by [role], on [date]
| The trainer will | By | The sponsor and managers will | By |
|---|---|---|---|
| [commitment] | [date] | [commitment] | [date] |
## Open questions
- [what was not answered, and who will answer it by when]
## Decision
[Sponsor name] confirms the call note, the managers' part and the debrief date by [date]. [Trainer name] decides whether the design starts before that confirmation.
```

## Done When
- The guide has the three bands, the scope test and the look-back question, with the must-keep questions marked.
- The call note carries the sponsor's description of success in their own words, or says plainly that none was given.
- Both commitment columns have at least one line with a date, or the empty column is shown as empty.
- The debrief date is on the page, and open items are listed with who answers them.

## Quality Bar
- Questions are plain enough to say aloud once. No double questions, no jargon the sponsor would have to translate.
- Verbatim means verbatim: I do not tidy the sponsor's words into training language.
- Nothing is promised about results at work. The note records what each side will do and what will be looked at, on one page that goes to both sides, so neither holds a private version.
- Claude prepares the questions and the note; you hold the conversation, and nothing the sponsor says about an individual participant goes into the design.

## Next
Run fac-pre-session-survey (Pre-Session Survey) to hear from the people who will be in the room.

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