Strategic Meetings Management vs travel management

A travel management company buys and controls individual business travel: flights, rail, hotel rooms, ground transport — one traveller at a time, at volume, inside a policy. Strategic Meetings Management covers what happens when people are brought together: a venue, a group contract carrying cancellation exposure, and a delegate list.

The overlap is real and narrower than it looks. Travel moves people; meetings commit the organisation to a venue months before anyone sets off, which is why they are managed as a discipline of their own.

None of this is a criticism of travel management. A well-run travel programme is one of the better-managed indirect categories in most organisations, and it does things a meetings programme cannot.

If your problem is transient travel — cost per trip, compliance at booking, traveller welfare — a TMC is the right answer and a meetings programme has nothing to add. Where an organisation’s meetings are genuinely a room and coffee near an office a few times a year, a travel programme with a small meetings desk may cover it comfortably.

Meetings behave differently from trips, and the differences are structural rather than a matter of effort:

The consequence is that a booking tool designed for trips will not hold a meeting, and policy enforced at booking arrives far too late for a commitment made when a contract was signed. Meetings governance has to sit earlier, at the point the requirement is approved — see meetings approval process and meetings governance.

On cancellation, attrition and liability terms, organisations should take their own specialist legal advice rather than relying on general guidance from any supplier.

The overlap concentrates in two places, and both are worth handling deliberately rather than by accident.

The first is group accommodation. A block of thirty rooms for a conference is a meetings requirement bought on meeting terms, but it lands in the hotel market your travel programme already negotiates in. Contracting it with no reference to those rates wastes a position you paid to build.

The second is delegate travel. Getting people there is transient travel, whoever organises it, and it should almost always be booked through the travel programme — so it stays in policy, in the tracking record and in the travel data.

A third, quieter overlap is data. Neither function can say where the organisation’s people are unless both feed the same picture. See duty of care and meetings spend visibility — and take specialist advice on the obligations.

Most organisations of any scale need both, working to an agreed boundary rather than competing for the same territory. Where nobody has defined that boundary, meetings default to whoever is closest — usually the person running the meeting, with no terms, no approval and no record. See decentralised meetings management.

Some travel management companies operate a meetings division, and that is a reasonable option to evaluate seriously: one supplier relationship, shared data, an existing contract. Ask whether the meetings capability is resourced as a specialism or carried as an add-on, how venue sourcing and group negotiation are done, whether delivery is available, and what the reporting covers. Put those questions to any provider, including us.

Built alongside an existing travel arrangement, a programme should be additive: travel keeps transient travel, the meetings programme takes the category travel was never designed for, and both report into the same view. See corporate meetings management.