For organizers receiving a minister, a funder or a visiting executive
Guest ProtocolThe few guests who need special handling, qualified by obligation and received with discretion.
Name the guests you think need special handling and what each arrives with, and get - free in your browser, in the order the skill sets - speakers, sponsor staff and press routed out first, the rest qualified by obligation rather than status, the roster with its holder, viewers and deletion date, the program, visibility and escort postures set against what each guest actually said; then the greeter brief, the liaison intake for any protective detail, and who decides on the day. Four siblings own most of what people call a VIP, and the most common correct outcome is that nobody is left in scope. It never infers anyone's importance, identity, gender, nationality or visibility from a name or a title, leaves every security decision to the guest's own detail, treats the roster as personal data with a named holder and a deletion date, and labels every number of its own self-set.
The event free
Blank means today.
The interview free
The skill's nine questions, word for word
- Which mode: set a posture before an edition, or handle one named guest already confirmed for a date?
- Who owns the event and which pole is it on - community-run (volunteer, CFP-driven, cost-recovery sponsors) or vendor/corporate-run (marketing-funded)? And does its register say anything about status: flat and explicitly anti-hierarchy, or comfortable recognizing who is in the room? (This one answer flips Menu B end to end.)
- Name each guest and say what makes them a guest rather than something else. Anyone on the program is a speaker; anyone covered by a signed sponsorship is a sponsor; anyone filing copy is press - route each out. For whoever is left: what obligation do they carry, in one sentence, and is there one at all, or only status?
- Does any guest arrive with obligations you do not control: a protective detail, a protocol or advance officer, a stated institutional security requirement, a fixed arrival or departure window? Has their office actually contacted you, or are you assuming they will?
- Has the guest or their office said how visible they want to be: introduced, or moving through the day unremarked? Never infer this. Both answers are common, and this is the fact that decides the whole visibility posture.
- How long until doors, and are the badge print run, the seating plan and the run of show still open? (A closed print run deletes every badge-marking rung on its own, without any argument about culture.)
- Is this a one-off visit, or a relationship that recurs edition after edition?
- What is the effort ceiling: organizer-hours, how many people can be pulled off another post on the day, and who is willing to own this? Note that reversibility is not symmetric here: a badge colour can be dropped next edition; a stage announcement and a published photograph cannot be unsaid.
- How many named guests in total, who compiles the list, who else sees it, and on what date is it deleted? Which assets re-rank the defaults: an organizer who already knows the guest, a venue with a second entrance, a team member with protocol experience?
Q3 and Q5 are answered per guest in card 3; Q4's obligations too, as "arrives with".
By need, never by seniority - write "nobody else" if nobody does.
The named guests free
Write the title exactly as the guest's office gives it - it never qualifies anyone. Visibility is only what the guest or their office said; "not said" stays not said. A need is a provision (a step-free route, a seat near an exit), never a diagnosis.
The day and the notes free
One name with a number that will be answered - not a team address, not a shared inbox.
The guest posture, worked out free
What the page flags
Questions to send their office - copy, then send from your own mail
Routed out first, then qualified by obligation - never by title
Identification breadth and the roster - holder, viewers, deletion date
The program posture - re-ranked, deleted rungs struck
Visibility and discretion - against the pole and only what each guest said
Escort depth and the greeter brief's items
The liaison intake - receiving a guest's own detail's plan
The two day-of decisions and the hand-offs
The files free
The roster (only the fields its breadth allows, with its deletion date in the first line), every named guest's routing, the greeter brief's skeleton, and everything the page worked out.
The posture 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 guest postures
How it works - and what is sourced
The order is the skill's: run the interview and route out speakers (event-speaker-experience), sponsor personnel (event-sponsor-fulfillment) and press (event-press-relations) first, and stop when nobody remains; apply the qualification test - an obligation, never status - with its four types (external protocol, security, discretion, dependency exposure, the last only when the relationship recurs); set the identification breadth and build the roster with its fields, holder, viewers and deletion date; set the program posture; set the visibility posture against the pole and only what each guest said, asking rather than deciding while there is time; set the escort depth and write the greeter brief; run the liaison intake where a guest arrives with their own detail or advance team; name who decides on a photograph and who says no on the guest's behalf; hand off seating, the check-in desk, access needs and any crowd, medical or threat question. Security decisions belong to the guest's own detail, never to the organizer.
Sourced from the skill and its references: the nine questions, the four menus with their rankings, promotions and deletions (a closed print run and seating plan delete both marker rungs; a flat register deletes the broad notability list, and the formal program when no external obligation exists; an unremarked guest at a flat register deletes the full-visit escort), the qualification test, the roster's fields and rules, the greeter brief, the what-not-to-say list, the photograph lines and the liaison intake. The page's own, said wherever used: the per-guest posture rule (a marker only where that guest asked for one), the roster kept by the page whenever anyone qualifies, the reading of the Q9 assets, and these self-set lines - a handful is at most 5 qualified guests, asking needs at least 3 days before doors, a roster kept more than 90 days after the event is flagged, at most 30 rows of each list go to the run, a 40-word summary and at most 5 caveats. Never stated at all: anyone's importance, identity, gender, nationality or visibility from a name or a title.