Inviting External Guests to Company Travel

Every company event has people in it who do not work for the company. A customer telling the story the sales team needs to hear. A partner running a session. A facilitator. A board member. An analyst.

They are the reason the event is worth holding, and they are the part of it that is booked worst. The travel tool is for employees, so the organizer books the guest by hand — on a personal card, or a shared company card, or by asking the guest to book and claim it back. Then three things go wrong at once: the cost lands outside the event's budget, the booking is invisible to everyone who needs to see it, and somebody is left holding a personal expense claim for a stranger's flight.

Why "just book it yourself" is the expensive option

The cost goes missing. A guest's flight bought outside the event is not in the event's numbers. It shows up later as an expense claim against a department that has nothing to do with the event, or as a card charge nobody can attribute. The event's final cost is wrong by exactly the amount spent on the people who made the event worth attending.

Nobody can see the itinerary. The organizer knows when the guest lands because it is in their inbox. The person doing airport transfers does not. The person who needs to know whether the speaker will make the rehearsal does not.

The change is the hard part. A guest's flight moves. Now the person who booked it has to find the confirmation in their own email, call the airline on behalf of someone they do not represent, and pay the difference personally.

And the access problem, which is the one nobody plans for. The alternative — give the guest a normal account in the company travel tool — solves the booking and creates something worse: an external person with a standing account, in whatever directory that account lives in, until an access review finds it. Most of them are found late, if at all.

What scoped guest access means

The shape that works is an invitation to one event rather than an account in the company:

the guest is invited by email, not added to the employee directory;
their access is to the event — its dates, its city, its rules — and not to the company's travel more broadly;
they book inside the event's rules, which are the rules the organizer already set for everybody;
their bookings and spend appear in the event's booking list and budget like anyone else's;
and the access ends when the event does, on its own, rather than when someone remembers.

That last line is the one worth insisting on. An invitation that expires by itself is a control that does not depend on anybody's diligence. An account you have to remember to close is a control that depends on the one thing people are reliably bad at.

The rules a guest should and should not inherit

A guest is not an employee, and some of the event's rules fit them and some do not.

Fits: the travel window — a speaker who arrives after their own session is a problem regardless of who employs them. The allowed arrival airports. The hotel, especially when the group is in one block and the guest should be in it too. The service list, because an event that is not booking car rental does not want to be booking it for guests either.

Needs thought: the cabin class cap. A rule written for employees travelling on company policy may be the wrong rule for an invited speaker on a long-haul sector, and a guest's travel is not the place to discover your policy is embarrassing. Decide deliberately: raise the cap for the event, or handle the exception through approval rather than leaving the guest to ask.

Does not apply: anything that assumes a cost center, a manager or an expense workflow the guest is not part of. Their spend still needs an owner on your side — usually the event itself.

A sequence that works

Confirm the guest's role and their dates before the invitation. Their dates are often not the event's dates: a speaker may come for one morning.
Decide the exceptions up front — cabin class, an extra night, a hotel outside the block — and set them as part of the event's rules rather than approving them one at a time under time pressure.
Invite by email and track the answer. An invitation sent is not an invitation accepted, and a guest who has not answered is not a guest you can assign a room to.
Let them book inside the event, so the itinerary is visible to the organizer, the transfers are planned against real arrival times, and the cost lands in the event's budget.
Assign them a room from the block like everybody else, if the group is in one hotel.
Check the access closed after the event. If it closes by itself, this step is a verification rather than a task.

What to put in the invitation itself

A guest invitation is not an internal one, and the two differences are worth writing down. The guest does not know your travel rules, and they do not know what they are allowed to spend. Say both in the invitation rather than leaving them to discover it at the booking screen: the dates they may arrive and leave, what they may book, and who to ask when their case does not fit.

And say who pays. "We will arrange your travel" and "book it and we will cover it" are different promises, and a guest who guesses wrong either arrives having spent their own money or does not arrive at all.

How this works in Travel Code

In a company event in Travel Code, external guests are invited by email from the same participant list as employees, who come from the company directory. The list shows, per person, the invitation status with the date it was sent, whether they accepted or declined, their departure city, the planned estimate, what they have booked and spent, and a flag when their bookings fall outside the event's travel window — guests included.

Guests get their own access for the event, and it closes on its own after the event ends. While it is open, they book under the event's rules: the travel window with its arrive-by and leave-after times, the services that are turned on, the cabin class cap, the allowed arrival airports and the hotel rule. Bookings outside the window do what the organizer chose — get flagged, require approval, or be blocked — and approvals go to the event owner and to co-organizers holding the approval right.

Their bookings appear in the event's booking list with everyone else's, and their spend counts in the event's budget: booked and spent, paid, remaining, split by category, participant, cost center or department. If the group is in a room block, the organizer assigns guests to rooms from the same list.

The short version. Invite guests to the event, not to the company. Give them the rules that fit their role and decide the exceptions before you need them. Keep their bookings and their spend inside the event, so the cost of the people who make an event worth attending is counted in the event that invited them. And prefer access that expires by itself over access somebody has to remember to revoke.

More on running company events

The product these articles describe is Company Events in Travel Code: one workspace for the people, the travel rules, the room blocks and the budget of a company trip.

Inviting external guests to company travel