Law firms, accountancy practices and consultancies have a structural feature that changes how a meetings programme has to be designed: a large number of senior individuals each hold genuine budget authority, and each is accountable for the client relationships that budget serves.
That is not a governance failure to be corrected. It is how the business model works. A partner taking eight clients to dinner is exercising exactly the discretion the firm expects, and a process requiring them to justify it centrally will be treated as an obstacle to revenue.
Which is why the usual centralisation argument lands badly. Told that a single route in improves control, a partner hears that someone else will decide where they take their clients. Programmes that work here are built on a different premise: the partner keeps the decision and stops doing the administration.
Why autonomy produces the specific problems it does
Distributed decision-making with distributed administration produces a predictable set of consequences. None of them are dramatic individually, which is why they persist.
- The same venue is negotiated repeatedly. Several partners use the same venues, each securing an individual rate, none aware of the firm’s aggregate volume.
- Terms vary by whoever signed. Cancellation, attrition and payment terms differ across bookings at the same venue in the same year.
- Administrative time is expensive. Sourcing, chasing and reconciling is done by people with a chargeable rate, or by assistants with no buying leverage.
- Client events blur into marketing. A seminar with clients present sits between business development and marketing, which is why nobody owns it.
- Spend appears late. Commitments made months earlier arrive as invoices, after the budget conversation that should have included them.
- Practice groups do not see each other. Two groups commission similar events in the same quarter without either knowing.
What a programme should actually offer here
Framing
Programme that fights autonomy
Meetings spend must be controlled centrally.
Programme that removes friction
Send the requirement in; options come back within a day.
Venue choice
Programme that fights autonomy
Restricted to an approved list.
Programme that removes friction
Partner chooses; the list exists because its terms are better, not because it is mandatory.
Approval
Programme that fights autonomy
Central sign-off before anything is booked.
Programme that removes friction
Existing budget authority stands; thresholds apply only at the top end.
Administration
Programme that fights autonomy
A form to complete, then the same work as before.
Programme that removes friction
Sourcing, negotiation, contracting and reconciliation handled elsewhere.
Data
Programme that fights autonomy
Requested retrospectively from organisers.
Programme that removes friction
Captured as a by-product of the booking route.
Likely outcome
Programme that fights autonomy
Worked around within two quarters.
Programme that removes friction
Adopted because it is the path of least effort.
| Dimension | Programme that fights autonomy | Programme that removes friction |
|---|---|---|
| Framing | Meetings spend must be controlled centrally. | Send the requirement in; options come back within a day. |
| Venue choice | Restricted to an approved list. | Partner chooses; the list exists because its terms are better, not because it is mandatory. |
| Approval | Central sign-off before anything is booked. | Existing budget authority stands; thresholds apply only at the top end. |
| Administration | A form to complete, then the same work as before. | Sourcing, negotiation, contracting and reconciliation handled elsewhere. |
| Data | Requested retrospectively from organisers. | Captured as a by-product of the booking route. |
| Likely outcome | Worked around within two quarters. | Adopted because it is the path of least effort. |
The right-hand column produces more governance than the left, because it is the only one people use.
This is the argument for making the central route the easy route rather than the compulsory one. A preferred venue programme in a partnership is a set of pre-negotiated terms partners can draw on, not a restriction on where they may go, and a meetings policy here concerns itself with what must be recorded rather than what may be spent.
The visibility arrives anyway. If the sourcing route is genuinely faster than doing it yourself, requirements flow through it, and spend visibility follows rather than being separately enforced.
The client-event boundary
Client-facing events are where the marketing and business development boundary becomes genuinely unclear, and the ambiguity has commercial consequences. A client seminar may be budgeted by marketing, commissioned by a practice group, attended by clients a third group also serves, and evaluated by nobody.
The practical step is not to resolve ownership philosophically. It is to record the same fields for every client-facing event whichever budget pays — purpose, audience, attendees, cost and who commissioned it — so the firm can see the whole picture before deciding who should own it. Measuring meeting ROI becomes possible only once that baseline exists.
A realistic starting point
- 01
Find the aggregate
Twelve months of venue and catering spend across every practice group and office. Nobody has usually seen this number in one place, and it tends to be larger than expected. - 02
Identify the repeat venues
Where the same venue appears under several partners there is unused leverage, and it is the least contentious place to start — see meetings procurement. - 03
Offer a route, not a rule
One channel for briefs, not mandated. Measure adoption honestly after a quarter. - 04
Report what the route sees
Show what is now visible and what is still not. The gap is the argument for the next stage — see meetings data and reporting.
Frequently asked questions
01Will partners accept a central meetings process at all?
They will accept one that saves them time and costs them nothing in discretion. They will not accept one whose first visible effect is a request to justify a decision they are entitled to make. That distinction sounds like presentation. It is a design choice, and it determines whether the route gets used.
02Should we mandate the programme instead?
Mandates are enforceable only where someone is willing to enforce them against senior fee-earners, which in most partnerships is nobody. A voluntary route with high adoption produces more usable data than a compulsory one with widespread workarounds — see decentralised meetings management.
03Who should own this internally?
It varies more here than in most sectors. Practice management, operations, marketing and finance are all plausible, and the answer is usually whoever has credibility with partners rather than the closest job title. What matters is that one named person owns it — see meetings governance.
04Does this work for a firm with several UK offices?
Yes, and it is common. Each office builds its own venue relationships, which are worth keeping; the framework and data standard are what centralise. Multi-office meetings management sets out the hybrid model.
Related reading
- 01Structure and behaviourDecentralised meetings managementChanging behaviour where departments commission independently and mandates will not stick.
- 02GovernanceMeetings policyWhat a short, adoptable policy contains — and what it leaves out.
- 03The mechanismPreferred venue programmePre-negotiated terms as an offer rather than a restriction.
- 04Sector noteFinancial servicesThe opposite structural problem: strong central governance that meetings are not meeting.