Strategic Meetings Management checklist

Visibility and data

• There is an agreed written definition of what counts as a meeting or event. Good looks like a one-page scope statement that a department head could read and apply without ringing anyone. Without it, every number you produce means something different to each person who reads it, and your second year is not comparable with your first.
• Someone can state total meetings and events spend for the last twelve months. Good is an approximate figure with its limitations written down beside it. A precise-looking number that turns out to have excluded accommodation or catering does more damage than an honest estimate, because it collapses at the first challenge.
• Activity can be counted, not just costed. Good is knowing how many meetings happened, of what type, in which departments. Counts persuade internally where values invite methodological argument, and they are usually easier to establish.
• Spend can be broken down by department or cost centre. Good means you can say where demand originates rather than only what it totalled. Without this, you cannot target where a programme would help most, and you cannot have a useful conversation with any individual budget holder.
• You know how many separate people commit the organisation to a venue or supplier. Good is a specific number. This is the single most persuasive structural fact in most first data exercises, and it is a fact about your own systems rather than an estimate.
• Data is captured when a meeting is briefed, not reconstructed from invoices. Good is information arriving at the point somebody still cares about the meeting. Retrospective reconstruction tells you what happened; captured data lets you influence what happens next.
• The same fields are recorded for every meeting, defined once. Good means “contracted value” has a written definition that says whether it includes VAT and accommodation. Definitions that drift mid-year quietly destroy the comparison you were building.
• Committed but uninvoiced spend is visible. Good is knowing what the organisation is contractually on the hook for before the invoice arrives. Cancellation exposure is real money and it is invisible in any system that only sees payments.

Sourcing and procurement

• There is one defined route by which a requirement enters the process. Good is a route everyone can name, with a published response commitment that is met. Multiple routes are not a route; they are a description of what people were already doing.
• Procurement sees requirements before a supplier is selected. Good means procurement can still influence competition, terms and cancellation exposure. Seeing the invoice is not involvement — by then every commercially meaningful decision has been taken by somebody trying to book a room quickly.
• More than one option is compared for meetings above an agreed value. Good is a documented comparison, however brief. The point is not bureaucracy; it is that a single quotation cannot be evaluated because there is nothing to evaluate it against.
• Date flexibility is asked about at brief stage. Good is knowing how movable the dates are before you go to market. It is the largest single commercial lever in venue sourcing and requesters almost never volunteer it.
• Sourcing follows a method rather than a personality. Good means a new joiner could run a sourcing exercise from the written process and produce a comparable result. Where the method lives in one capable person’s head, the capability is borrowed rather than held.
• Requirements are aggregated where they can be. Good is noticing that three departments need similar venues in the same quarter and going to market once. This is the benefit that fragmented buying structurally cannot produce, and it is covered on reducing fragmented event spend.
• Formal [RFP](/glossary/rfp/) processes are used where they are proportionate, and not where they are not. Good is a stated view on which requirements warrant one. Running a full tender for a twelve-person training day is as much a failure of judgement as not running one for a three-day conference.
• Someone knows what the organisation last paid the same supplier. Good is being able to check before negotiating. Without it you are re-establishing a price position you already held.

Suppliers

• You can name your most frequently used venues and suppliers. Good is a ranked list by both frequency and value, because they are different lists. If you cannot produce this, you are almost certainly paying transactional rates to suppliers you use often enough to have negotiated with.
• Any preferred list was built from your own usage data. Good means it contains the venues departments already chose. A list assembled centrally that excludes somebody’s favourite venue without explanation gets ignored, and takes the rest of the list with it.
• Preferred suppliers carry negotiated terms, not just approval. Good is agreed rates, inclusions and cancellation positions. A preferred list with no commercial advantage is an instruction rather than an offer, and instructions in this category are hard to enforce.
• You know your group-level volume, not just property-level. Good is recognising that six separate hotels belong to two groups. Group-level aggregation is frequently the strongest negotiating position an organisation has and it is invisible if you look property by property.
• Preferred supplier usage is measured. Good is a number you report quarterly, including where bookings went off-list and why. Leakage you do not measure is leakage you will discover at renewal, when the volume you promised did not appear.
• There is a defined and documented route for going off-list. Good is an exception that stays inside the programme. Without one, the requirement does not disappear — it leaves your visibility entirely.
• Supplier performance is recorded, not just remembered. Good is a short note after each event that survives the departure of the person who ran it. Institutional memory about venues is otherwise held entirely in individual heads.
• Supplier arrangements have a review date. Good is a scheduled reopening whether or not anyone has complained. Rates agreed two years ago and never revisited stop being competitive quietly.

Policy and governance

• A meetings policy exists and is findable. Good is a document someone could locate in under a minute without asking. A policy that exists in a folder nobody can name has the practical status of not existing.
• It is short enough to be read. Good is a couple of pages covering scope, route, thresholds, supplier expectations and who to ask. Comprehensive policies are written to survive audit and read by nobody, which means they govern nothing.
• It has been cited in a real decision. Good is evidence that someone used it to settle a question. If nobody can recall an occasion, the policy is documentation rather than governance.
• The policy was written after the service existed, not before. Good means it describes something that already works. A policy mandating a route that cannot yet answer a venue question within a day teaches people that the route is slower than ringing a hotel.
• A named person owns the category day to day. Good is a name known outside their own team. Not a committee, not a function — a person who answers questions and is accountable when it drifts.
• A sponsor exists above the owner. Good is someone senior enough that a department head cannot simply decline to participate. An owner without a sponsor is running a suggestion.
• A governance forum meets on a cycle and can change the rules. Good is quarterly, with authority to alter scope, thresholds and supplier arrangements without escalating. A forum that can only observe produces minutes rather than decisions.
• Scope disputes have a named adjudicator. Good is one person who can rule immediately. Edge cases that require a meeting to resolve are what make a programme feel bureaucratic.
• There is an annual review date in the calendar. Good is a scheduled reopening of policy, thresholds and supplier terms whether or not anybody has complained. Frameworks that are only revisited under pressure are revisited too late.

Approvals and contracting

• Approval thresholds exist and mirror existing delegated authority. Good means finance recognises the numbers because they are the same ones used elsewhere. A parallel authority scheme invented for meetings is one nobody can remember.
• Approval is triggered by commitment, not by payment. Good is authorisation before a contract is signed and a cancellation schedule starts running — typically months before an invoice exists. Approving at invoice stage is approving something already irreversible.
• A named list of people may sign venue contracts, and it is enforced. Good is a short list that suppliers could be told about. If anyone who happens to be organising an event can bind the organisation, you have no contracting control.
• There are minimum contract standards covering cancellation, attrition and deposits. Good is a written internal position on what is acceptable and what should be challenged. Most standard venue terms are more negotiable than non-specialists assume.
• Force majeure and postponement positions are understood before signing. Good is knowing whether the contract permits moving an event rather than only cancelling it. That distinction is worth a great deal when circumstances change.
• Signed contracts are held in one place, accessible to someone other than the signatory. Good is being able to produce the signed version on request. Contracts stored in individual inboxes are contracts you cannot rely on.
• Data protection obligations are addressed where delegate data is shared. Good is knowing what a venue or production supplier receives and on what basis, reviewed by your own compliance function. See meetings compliance, and take specialist advice.
• Retrospective approvals are logged and reported. Good is a small, visible number that the governance forum sees. They will happen; what matters is whether anyone knows how often.

Delivery

• There is a consistent standard for how a meeting is run. Good is a shared expectation of what attendees get regardless of which department organised it. Where every meeting reflects the individual who arranged it, quality is a matter of luck.
• Someone is named as responsible for each event in scope. Good is a single accountable person recorded against the meeting, which sounds obvious and is frequently ambiguous for internal events.
• Accessibility requirements are asked about at brief stage. Good is capturing them when the meeting is requested rather than discovering them after the venue is contracted, when the options are expensive or unavailable.
• Delegate information is handled to a known standard. Good is a consistent approach to what is collected, who receives it and how long it is kept — see delegate management and take your own data protection advice.
• Final numbers and final costs are recorded against the original brief. Good is a closed loop, so that next year’s estimate is informed by this year’s outcome. Most organisations capture the plan and never capture the result.
• Attrition and cancellation positions are tracked against actual attendance. Good is knowing whether you routinely over-commit on numbers. This is a recurring, quantifiable cost that is invisible unless somebody looks.
• A short post-event record exists. Good is a few lines on what worked and what did not, held centrally. It is what makes supplier performance a record rather than a recollection.
• Internal time spent organising meetings is at least acknowledged. Good is recognising that senior people spending days on venue logistics is a real cost. It rarely appears in any budget, and it is one of the more persuasive arguments for a programme.

Reporting and review

• Reporting goes out on a named date to named people. Good is a report that arrives whether or not anyone asks. Reporting produced on request answers questions; reporting produced on a cycle builds a trend, and only the second is useful for decisions.
• The pack is small enough to be read. Good is a page or two that someone actually reads monthly. A comprehensive pack delivered twice and then abandoned is worth less than a thin one delivered every month for two years.
• Every measure has a named audience and a decision attached. Good means you can say what someone would do differently if the number changed. Measures that fail that test are decoration.
• Adoption is measured and reported, including where it is poor. Good is knowing what proportion of identifiable activity came through the programme, by department. It is the uncomfortable number and the most useful one.
• Exceptions are visible. Good is reporting retrospective approvals, off-list bookings and contracts signed outside authority. A programme that only reports its successes cannot be corrected.
• Year-on-year comparison is possible. Good is unchanged definitions and a stable data set. Changing what a field means mid-year is the most common way organisations lose a comparison they had already paid for.
• Reporting has changed a decision at least once. Good is a specific example — a supplier arrangement altered, a threshold moved, an event reshaped. If nothing has ever changed because of the reporting, it is documentation.
• The programme itself is reviewed, not just the activity. Good is an annual look at whether the scope, thresholds and operating model still match how the organisation works. Frameworks describe the organisation that existed when they were written.

Duty of care

• You could say where your people are, for meetings in scope, on a given day. Good is being able to answer within an hour without ringing round departments. This is the question that gets asked when something happens, and the moment it is asked is the wrong time to start building the capability.
• Attendee records exist for events involving travel or overnight stays. Good is a record held somewhere other than the organiser’s inbox. The long tail of small events is usually where the gap sits, because nobody thinks of a twelve-person training day as a risk event.
• Venues and suppliers are subject to some proportionate due diligence. Good is a consistent minimum — insurance, licensing, and health and safety position — applied to suppliers you use repeatedly, even if lightly. Inconsistent diligence is hard to defend precisely because it is inconsistent.
• Insurance position is understood for events in scope. Good is knowing what your own policies cover and what a venue’s do not, before rather than after an incident.
• There is a known escalation route if something happens at an event. Good is a documented contact chain that an organiser could follow at nine in the evening. Most organisations have one for offices and have never extended it to offsite activity.
• Higher-risk activity is identified in advance. Good is a simple flag at brief stage for overseas events, unusual venues, physical activity or particularly senior attendees. It does not need to be elaborate; it needs to exist.
• Accessibility and individual needs are handled consistently. Good is a standard question at brief stage rather than a conversation that happens only when someone raises it.
• The duty of care position is reported to someone accountable. Good is a quarterly line to risk, HR or the sponsor. A capability nobody reports on is a capability nobody maintains.