How to create a corporate meetings policy

This guide is about drafting. Meetings policy covers what a policy is for, what belongs in it and why most of them quietly fail; read that first if you have not decided whether you need one. What follows takes you through producing the document: who writes it, the scoping decision that shapes everything else, how to set thresholds, what each section should say, and how to get it published without it being rewritten into uselessness.

One expectation to set at the outset. A meetings policy is a few pages, and most of the work is not writing. It is making a small number of decisions the organisation has been avoiding, and getting the right people to agree to them. If drafting is taking weeks, the problem is almost certainly an unmade decision rather than a wording difficulty.

There is no boilerplate here to copy. A policy assembled from someone else’s thresholds and someone else’s scope is precisely the document that ends up unenforced, because nobody internally ever agreed to any of it. The value is in the decisions, and the guide below is how to make them.

These are two different jobs and conflating them slows everything down.

The owner is accountable for the policy existing, being current, being interpreted when it is ambiguous and being enforced when it is ignored. Usually procurement, holding meetings as a category alongside others, sometimes jointly with whoever runs events. What matters is that a single named person holds it — a policy owned by a committee is a policy nobody updates, and meetings governance makes the wider argument for naming an owner before writing any rules.

The drafter should be someone who knows how meetings are commissioned in practice. Often that is not the procurement lead — it is the person in executive support or the events function who receives the requests and can tell you immediately which rules will be ignored.

The productive pairing is the category owner and the person closest to the activity, drafting together. Procurement supplies the commercial requirements; the operational person supplies the reality check. A policy drafted only by procurement tends to be unworkable in ways nobody notices until publication; one drafted only by the events team tends to codify the current process rather than improve it.

Everything in the policy follows from what counts as a meeting or event it governs. Get this wrong and the rest is either unenforceable or absurd, and you will find out from the first person who asks whether their nine-person lunch meeting needs a purchase requisition.

“All meetings and events” is not a scope. Nobody can apply it, so people apply their own judgement, and the policy is advisory from day one. A workable scope is built from characteristics. Work through each of the following and write an explicit answer.

Then write the scope as two short lists: what is covered, and what is explicitly not. The exclusions matter as much as the inclusions, because they stop the policy being read as applying to every internal catch-up — being generous with exclusions is what makes the inclusions enforceable.

Test the draft against a dozen real bookings from the last quarter. The scope should give an unambiguous answer in one reading. If you deliberate, the person organising a training day will deliberate too, and then do whatever seems reasonable.

Thresholds are where policies most often fail, in both directions. Set too high and a long tail of routine bookings never touches any control — in aggregate frequently the largest part of the category. Set too low and every small training day queues behind a signature, which teaches people that compliance is expensive and non-compliance is not.

The only sound way to set them is against your actual booking distribution. Plot the last twelve months by value and see where the volume sits. That distribution — not a figure borrowed from another organisation — tells you where a threshold captures meaningful value without pulling in hundreds of routine items. How to measure meetings spend is the method for getting it.

Three bands is usually enough. Below the lowest, the requirement goes through the route and gets recorded, with budget-holder approval only. In the middle, the category owner is involved and competitive sourcing is expected. In the top, senior sign-off and contract review apply. More bands and people cannot remember the rule, which means they do not follow it.

This is the refinement most policies miss. A £9,000 venue booking carrying a 90 per cent cancellation charge inside eight weeks is not a £9,000 decision in the way a £9,000 equipment order is: the organisation is exposed to the contracted value, not the deposit, from signature.

Write the thresholds against total committed exposure. It requires whoever raises the requirement to know the contracted value and cancellation position — a useful discipline in itself — and it puts the right bookings in front of the right people.

Some characteristics warrant attention regardless of value: overseas destinations, external client attendance, regulated audiences, anything where the organisation is publicly named, and any event where personal data beyond a delegate list is collected. State these as triggers in their own right so a low-value but sensitive event is not waved through on the number alone.

And watch for gaming once the policy is live. A cluster of bookings sitting just below a threshold is not a coincidence; it is a threshold being managed around, and it is one of the specific patterns worth looking for in meetings compliance reporting.

If the policy says one thing clearly, it should be where a requirement goes first — and that it goes there before anyone contacts a supplier. That sequencing is the most commercially significant sentence in the document, because approval obtained after a venue has been held and a rate verbally agreed is administration rather than control.

Name the route specifically: a team, an inbox, a form, a person. “Contact procurement” is a suggestion, not a route. Include what information is needed to start, so the first exchange is productive rather than a request for basics.

Then be honest about whether the route can deliver. A mandated route taking nine days when ringing a hotel takes twenty minutes will lose, and the people bypassing it are responding rationally to the process you built. If you are not prepared to resource it so that it is the faster option, do not publish a policy claiming it is mandatory. The workflow itself is on meetings approval process.

The table below walks through the sections a meetings policy needs, what each should actually contain, and the mistake most commonly made in it. The right-hand column is the useful one: plenty of policies contain every heading here and say nothing under any of them.

A meetings policy competes for attention with the actual job of organising a meeting. It wins that competition by being short, findable and immediately useful, and it loses by being thorough.

Consultation separates a workable policy from one that gets ignored, and it is the step most often compressed because the draft already exists and feels finished.

Consult two groups for two reasons. The functions whose policies you touch — finance, HR, legal, compliance, data protection, and whoever owns the travel policy — are checking for conflicts and gaps. The people the policy constrains, particularly the individuals who actually do the booking, are checking whether it is workable.

The second group is the valuable one and the one most often skipped. Ask them directly: what would make you not use this route? The answers are usually specific and fixable. It does not handle short-notice requirements. It does not cover the one supplier they always use for a good reason. The form asks for information they do not have at that stage. Every one of those, fixed before publication, is a category of non-compliance that never happens.

Be clear about what is open and what is not. The existence of a mandated route is a decision, not a consultation topic. How the route works, where the thresholds sit and which situations need special handling genuinely are. And resist the bloat that follows: every reviewer adds a paragraph, and the aggregate is a twenty-page document nobody reads. The owner’s job at this stage is to say no to well-intentioned additions that belong in operational guidance.

Publishing a policy to the intranet and sending an all-staff email is not a launch. It is an archival act, and the effect on behaviour is close to nothing.

Go to the people who commission most of the meetings — usually a small number of teams and a smaller number of individuals — and walk them through the route in person. Fifteen minutes with the executive assistants, the L&D coordinators and the marketing team who between them place most of the activity does more than any communication campaign.

Lead with what the route does for them rather than what it requires of them: faster sourcing because someone else does the legwork, rates they could not have obtained alone, terms they would not have known to negotiate. That is an honest pitch where the route is properly resourced, and it is the only one that works.

Have the sponsor say publicly that this is the organisation’s position — one email, and it removes the most common objection, which is uncertainty about whether the policy has backing. Then make the first few requests work well. A policy is judged on the first experience people have of it, and a slow response in the first month is remembered long after the document is forgotten.

Annually suits most organisations, and the review should test the document against reality rather than re-reading it. The useful method is a sample: pull twenty bookings from the last quarter and check each one — did it go through the route, was the right approval obtained, were the standard terms applied, was it recorded. That tells you more in an hour than any amount of redrafting.

Read the results as a design signal rather than a compliance verdict. Where a rule is widely ignored, the first question is whether it is workable, not whether people are difficult. A rule bypassed by most of the organisation usually costs more to follow than it delivers, and the fix is to change the rule or the route behind it.

Two things should trigger a review outside the cycle: a material change in how the organisation is structured, and a change in any policy this one cross-refers to. The second is easy to miss, and it is how a meetings policy ends up contradicting an anti-bribery policy updated without anyone telling the category owner.

Finally, accept that the policy is only part of the answer. A document changes very little alone. It works when there is something behind it: a route that is genuinely quick, suppliers already on agreed terms, and reporting that shows whether it is being used. That combination is what Strategic Meetings Management describes — one route in, better visibility out — and the sequence for building it is in how to build an SMM programme.