← SkillSafe
Host Visit

For organizers taking an audience into someone else's building

Host VisitA host that withdraws does not cost you a room. It deletes the programme.

Plan a site visit, company tour or learning expedition where the host's floor and people are the programme. Free in your browser: how much of the day depends on a host you cannot direct, what attendees may see and repeat, the options that drop out and why, everything to route to someone else, and the four things that must exist in writing before attendees hear where they are going. A run writes the expedition brief, or the brief you send the host. No invented group sizes or lead times.

Try a sample:

1 The host, the audience and the terms free

2 The two decisions, worked out free

What the page flags

The pass threshold and the restriction list

Host dependency, then access

Routed out and handed off

3 Expedition brief or host brief

Pricing as soon as the session is ready...

NOT RUN YET

The page's check of this reply

    4 Saved visits

    How it works

    Everywhere else a third party supplies either the room or the content. A host supplies both, so a host that withdraws deletes the programme rather than a room you can re-book. That leaves two decisions: how much of the day depends on the host - their engineer in your own room, one site they lead, one site built to your agenda, or several hosts in a row - and what attendees may see and repeat afterwards.

    Each menu applies its delete rules before ranking: no talk when the audience comes for something no slide can show, no negotiated agenda without a counterpart who can commit colleagues' time, no open record over a restriction the host stated, no clearance queue without someone to run it. Transport, catering, filming, invitations and goals belong to other plans and are routed out. Before attendees hear where they are going, four things exist in writing: the host's yes, the counterpart, the restriction list and the person who clears what attendees publish.