Ask a procurement director whether their organisation has a meetings and events policy and the answer is usually yes. Ask where it is, when it was last updated, and what happens when someone ignores it, and the answers get vaguer.
That gap is the subject of this page. Not how to write a policy — that is covered step by step in creating a corporate meetings policy — but what a meetings policy is, what belongs in it, and what separates one that shapes behaviour from one that exists so somebody can say it exists.
Definition
Meetings and events policy
The written rule set governing how an organisation commissions, sources, approves and contracts for meetings, conferences, training and related events. It defines the mandated route in, the limits of individual discretion, and the point at which someone else has to be involved.
It is not the same as meetings governance, the structure of ownership and decision rights that gives the policy force.
What a policy is for
A meetings policy does one useful job: it removes the need for people to invent a process. A department head who needs a venue should not have to work out whether to call three hotels, whether procurement wants to see it, or who can sign. It is a time-saving document as much as a control document, and organisations that write it purely as the latter produce something people route around.
The second job is consistency. A policy is the first structural fix for decentralised meetings management, and the foundation a strategic meetings management programme sits on.
What belongs in a meetings policy
The right-hand column matters more than the left: plenty of policies contain all these headings and say nothing under any of them.
- 01
Scope
Precisely what counts as a meeting or event — by activity type, attendee number, external attendance, overnight stay or spend. Not "all meetings and events", which nobody can apply.
- 02
Mandated route
Where a requirement goes first, and that it goes there before any supplier is contacted. One route in, named, with the contact point.
- 03
Thresholds
The value or characteristic triggering each additional approval or sourcing step — with the figures stated, not "significant expenditure".
- 04
Approved suppliers
Which venues are preferred, what using them obliges, and what has to happen to go outside the list. See preferred venue programme.
- 05
Sourcing requirements
When competitive sourcing is expected and who runs it. Cross-refer to meetings procurement rather than restating it.
- 06
Contracting and signature
Who is authorised to sign a venue contract. Usually a shorter list than people assume, and the clause most often missing.
- 07
Travel and accommodation
Which document governs delegate flights, rail and hotel rooms, and where the boundary with the travel policy sits.
- 08
Expenses boundary
What is an event cost and what is an individual expense claim. Ambiguity here is where spend disappears.
- 09
Hospitality and gifts
The organisation’s position on entertaining and supplier hospitality, cross-referenced to the anti-bribery policy rather than duplicated.
- 10
Duty of care
What the organisation needs to know about who is travelling and attending, and why. See duty of care.
- 11
Exceptions
How to request one, who decides, and how long it takes. If the exception route is slower than non-compliance, the policy is already lost.
- 12
Ownership and review
A named owner, a review date, and who to ask when the document does not cover the situation.
What does not belong in it
Policies bloat because every stakeholder who reviews the draft adds a paragraph. The result is a twenty-page document read by nobody. Keep the following out:
- Operational detail. How to brief a venue, or present a sourcing comparison, belongs in process documentation.
- Supplier terms. A policy that names rates is out of date within a quarter.
- Restated legal policy. Anti-bribery, data protection and health and safety have their own owners. Cross-refer; a paraphrase can conflict with the source.
- Aspiration. If it is not testable at the point of approval, it is strategy, not policy.
- Everything about travel. Where a travel policy exists, the meetings policy needs the boundary, not a second version of the rules — see SMM vs travel management.
Why most meetings policies fail
A policy fails in one of four recognisable ways, and only one is about people being difficult.
- 01
Nobody can find it
It sits three clicks below a menu nobody uses, under a title nobody would search for. The person organising a training day has no reason to look.
- 02
It does not answer the actual question
It states principles — value for money, appropriate authorisation — without saying what to do on a Tuesday with a room needed in six weeks. Principles are not instructions.
- 03
Compliance is slower than non-compliance
The mandated route takes nine days and a form; ringing a hotel takes twenty minutes. People are responding rationally to the process you built.
- 04
Nothing happens when it is ignored
The invoice still gets paid. Once that is established the policy is advisory, whatever it says. See meetings compliance.
Thresholds that work
Set too high and a long tail of £3,000–£8,000 bookings never touches procurement — in aggregate frequently the largest part of the category, as reducing fragmented event spend describes. Set too low and every twelve-person training day queues behind a director signature.
Two or three bands usually works, with the lowest requiring the route and the data capture but no senior approval, and the trigger being the commitment rather than the invoice. Thresholds should also catch characteristics: an overseas destination, external client attendance or a cancellation scale are material regardless of headline cost. See meetings approval process.
Lowest band
The mandated route and the data capture, but no senior approval.
Higher bands
Two or three bands in total, each adding an approval or sourcing step as committed value rises.
Characteristic triggers
An overseas destination, external client attendance or a cancellation scale — material regardless of headline cost.
The trigger is the commitment, not the invoice. The figures behind each band come from your own booking distribution rather than a standard table — see how to measure meetings spend.
Ownership and review
A policy with no named owner is a policy nobody updates. Ownership normally sits with procurement, or jointly with the function that runs events. What matters is less which name appears than that one does, with the authority to interpret it and to say no.
An annual review is the usual cycle. It should test the document against reality: pull a sample of last quarter’s bookings and check how many followed the route. That is more useful than reading the policy again. Where responsibility is spread across procurement, finance, events and budget holders, ownership is really a governance question — see meetings governance.
From policy to programme
A policy alone changes very little. It works when there is something behind it: a route that is genuinely quick, suppliers already under agreement, and reporting that shows whether it is being used. That combination is what Strategic Meetings Management describes — one route in, better visibility out.
Frequently asked questions
01How long should a meetings policy be?
Two to four pages is typical for organisations that want the document read. Anything longer tends to be operational process that would be better held separately and referenced.
02Should the meetings policy sit inside the travel policy?
It can, where most activity is small internal gatherings. It stops working once there is real event spend with contracted venues, cancellation terms and supplier negotiation — those are procurement questions, not travel-booking questions.
03What spend threshold should trigger procurement involvement?
There is no correct figure. Look at your actual booking distribution and set the threshold where it captures the bulk of committed value without pulling in a long tail of routine bookings. How to measure meetings spend covers getting that distribution.
04Does a policy need to mandate preferred venues?
Not necessarily. A policy can mandate the route without mandating the venue, which lets preferred arrangements build from real volume data rather than being imposed and then ignored.
05Who should sign venue contracts?
Whoever holds delegated authority under your own signature policy — the point is that this is stated. A common finding is that contracts carrying cancellation and attrition exposure have been signed by people with no authority to bind the organisation.
Related reading
- 01GuideCreating a corporate meetings policyThe step-by-step guide to writing one.
- 02GovernanceMeetings governanceThe ownership and decision-rights structure that gives a policy force.
- 03GovernanceMeetings approval processTurning thresholds into a workflow people can actually use.
- 04GovernanceMeetings complianceHow to measure whether the policy is being followed.