For organizers whose speakers have said yes
Speaker CareEverything an accepted speaker needs, collected on time, and the day run without surprises.
Enter what each accepted speaker was promised, the last usable date for every material, the session formats and recording intent, and who is travelling or speaking for the first time, and get - free in your browser, in the order the skill sets - the one named point of contact, the dated collection ladder pinned to each last usable date, never the event date, the care depth and the pre-event cadence per speaker, recording consent per format with its opt-out, the first-timers' care, the promised terms and the travel items, then the day-of tech check and green-room sheet. A run writes the care plan, or the speaker packet to send. It starts after acceptance: promised terms are delivered, never renegotiated or added to. It never invents a perk, a fee, a date, a person, a room or a piece of equipment, routes anything legal or financial to whoever handles the event's money and contracts, never reads anyone's identity, gender or experience from a name - first-time status is asked - and labels every number of its own self-set. The speakers came from Speaker Scout and Speaker Ask.
The event free
Blank means today.
The interview free
The skill's thirteen questions, word for word
- Where are you in the sequence: acceptance emails just went out, the event is weeks away, or it is next week? This fixes what is still changeable and what is now a communication problem.
- How many speakers, across how many session formats, and how many are travelling - domestically or internationally?
- What exactly was promised, and where: in the call, in the acceptance email, in any individual invitation? List each term. You deliver those. You never re-open them here.
- For each material you need, what is the last date it can still be used - programme print, badge print, slide upload, venue equipment order? Work the deadlines back from those dates rather than from the event date.
- One-off edition, or a recurring event where this year's speakers are next year's referrals and returning names?
- What is the effort ceiling: who is the speaker contact, how many hours a week do they have, and is there a budget line for speaker expenses at all?
- What is your recording and publication intent per session format, and where exactly were speakers told about it?
- Who is speaking for the first time, or for the first time at this scale? Ask rather than assume - a senior engineer's first conference talk is still a first talk.
- What does the venue actually give you: a green room or not, a house A/V technician or a volunteer with an adapter, a confidence monitor or not?
- Is any speaker presenting material their employer restricts, or otherwise sensitive?
- How mixed is the room: developers only, or developers alongside non-technical attendees? A mixed room changes the brief (depth gradient, jargon) and the question format.
- Does the event promise a recurring moment every edition, and who on the team has hours to coach speakers toward it? (See Talk coaching.)
- Is the event outside the region's main hub, so most invited speakers travel in from elsewhere?
Q2, Q3, Q8 and Q10 are answered per speaker in card 4, Q4 per material and Q7 per format.
For example: ticket; travel; lodging. The page compares every promised term against this.
The venue, the slides, after the event free
A reserved table, a quiet corner, a locked cupboard for bags.
Be honest: "nothing" is a fine answer.
Your own promise; blank means unset.
Formats, speakers and materials free
For example: Lightning talk | recorded and published | recorded and published | the call for papers | none. A lightning block recorded as one stream may offer no opt-out - say so before anyone submits.
First-time status is asked, never inferred - leave it blank when you have not asked yet. A promised term is copied as it was stated, and is never re-opened here.
Pin each to the last date it can still be used - programme print, badge print, slide upload, the venue's equipment order - never to the event date.
The care plan, worked out free
What the page flags
Where you are (Q1) and the one named contact
The collection ladder - pinned to each last usable date, never the event date
The status grid - per speaker, per material
What each speaker still owes - a note to send each one
Care depth and the pre-event cadence - re-ranked, deleted rungs struck
Every speaker's own dated touches - never one broadcast
Recording consent per format, with its opt-out
First-time speakers - asked, never inferred
Promised terms - delivered, never renegotiated or added to
Travel
On site - host, tech check, green room, slide deadline
After the event
The files free
The ladder as a spreadsheet and a calendar, the status grid, the day-of sheet, a packet draft and everything the page worked out.
The care plan metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
The page's check of this reply
Saved care plans
How it works - and what is sourced
The order is the skill's: read the acceptance packet and escalate anything promised that cannot be delivered; name the point of contact before the first message; turn "what we need next" into a dated ladder pinned to each material's last usable date; send one speaker packet; collect A/V needs by the venue's own ordering deadline; brief at the depth the care menu sets; hold the slide deadline as a real checkpoint; run the cadence per speaker; host, tech check and green room on site; close the loop with the thank-you, the feedback, the recording link and the retention pass. Recording consent is decided per format, and where a format offers no opt-out - a lightning block recorded as one stream - it is said before anyone submits.
Sourced from the skill and its references: the thirteen questions, the three menus with their rankings and deletions, the five-speaker line, the two reminders (at roughly half the remaining time and at the deadline), the 48-hour note, the week out, the check-in call two to three weeks out, the tech check steps, the green room and its substitutes, the consent record and the follow-up sequence. Self-set, and said so wherever used: the 21-day ask lead, the 7-day tight window, the 2-hour low-effort line, the 3-day thank-you, the 7-day retention default and the word caps. Never set at all: a visa lead time, a fee or its figure, a perk nobody promised.