Multi-office meetings management

An organisation operating from several offices, regions or countries has the standard meetings problem in a particular shape. Each location has its own relationships with venues near it, and knows which rooms are the size advertised and which supplier answers the phone on a Friday afternoon.

That knowledge is real. It is not sentiment and it is not resistance to change. It is operational information held nowhere but in the heads of the people who booked those venues before.

Meanwhile the organisation buys the same categories in several places at once without ever presenting itself to a supplier as one customer. Both things are true at once, which is why heavy-handed answers to meetings procurement across sites fail so reliably.

The instinctive fix is to appoint one central function, select preferred venues and require every office to use them. It fails for practical rather than political reasons.

The arrangement that holds across geographies separates framework from execution. The framework is common to every office; execution stays where the knowledge is.

Read down the central column and it is mostly standards, not decisions. That is the point: a common data standard and contract position produce a consolidated view and a consistent commercial floor without anyone centrally choosing a meeting room in a city they have never visited. See meetings governance and centralising meetings and events.

A single national or global preferred list rarely works across a dispersed organisation. Regional arrangements do — a small set of agreed venues per region or major city, negotiated against the volume that region generates, on common contractual terms.

That keeps the commercial benefit without pretending geography does not exist, and gives local teams a reason to use the list: the venues on it are ones they would plausibly have chosen anyway, now on better terms. Where volume is genuinely low, a formal arrangement is not worth negotiating — handle those ad hoc against the standard position. See preferred venue programme and supplier management.

Once offices sit in different countries, several complications arrive attached to meetings without being meetings problems.

The most consistently recoverable value in a multi-site organisation comes from requirements that are similar, close together in time, and invisible to each other.

A hypothetical illustration: three offices each run a two-day training event for thirty people in the same quarter, two in the same city, sourced separately at different rates. Nobody did anything wrong. The organisation simply never had the chance to present the three as one.

A consolidated forward view creates that chance. Not a mandate or an approval gate — a shared calendar of known requirements far enough ahead to act on, built from a common data standard and dependent on meetings spend visibility existing first.

Where offices are genuinely international, two realities have to be designed around rather than wished away.

Response time decides whether a central route gets used. A booker eight hours ahead who waits overnight for a reply will stop sending requirements through it, and no policy changes that. Either coverage matches the operating hours that matter, or the local team keeps authority to act and reports afterwards.

Language matters for the same reason. A form or policy existing in one language only will be worked around elsewhere. Keeping the mandatory elements short makes them translatable without becoming a project.