Using local delivery teams without losing central control
A central team owns the programme, but each city is run by a different local team with its own habits.
The short answer
Central control does not mean central doing. Decide which decisions stay central (content, budget limits, brand, data, safety escalation), which pass to local teams (room, welcome, local suppliers), and which need both, then write them down before the first stop.
Check each local team against the same short list at set points: before the stop, on the day and after it.
Decide decision rights, not just tasks
A task list says who does the work. Decision rights say who can say yes, who must be asked and who only needs to know. Disputes between central and local teams usually arise on the second and third.
Use one accountable person per decision. Where two roles are marked accountable, resolve it before the programme starts. The responsibility matrix builder shows duplicate or missing owners.
A starting split
| Decision | Central | Local | Both |
|---|---|---|---|
| Programme content and speakers | Decides | Informed | |
| Total budget and spending limit per stop | Decides | Informed | |
| Choice of local venue or supplier | Local proposes, central approves above agreed limit | ||
| Registration data and who sees it | Decides | Uses as instructed | |
| Room layout, refreshments, welcome | Decides | ||
| Incident or complaint escalation | Local first response, central informed at once | ||
| Changes to date or location | Local raises, central decides |
Control without micromanaging
- A single stop brief for every local team, with the same headings.
- A pre-stop check call, a day-of contact route and a short after-stop report in one format.
- A spending limit and a rule for what needs approval above it.
- Written supplier requirements, so local suppliers are asked the same questions.
When a local team goes off plan
- Ask what changed and why, before judging it.
- Check whether it touches a fixed item or a central decision right.
- If it does, decide centrally and tell the other stops. If it does not, record it and carry on.
- Add the lesson to the next stop brief.
Worked example · Fictional example
Three local hosts, one central programme lead
Fictional organisation and figures, for illustration only.
A fictional regional HQ, Kumpulan Fiktif Serantau, runs customer briefings in Kuala Lumpur, Shah Alam and Seremban. Local branch teams host. Each team has a spending limit of RM 3,000 per stop, an illustrative figure, with anything above it needing central approval.
In Seremban the branch books a different caterer without asking. The matrix shows refreshments as a local decision, so the programme lead notes it and only asks for the invoice. The same branch also changes the start time, which is a central decision, so the lead agrees a new time with the content owner and informs the other stops.
Use this yourself
Central and local decision rights table
Copy this and list every decision for your circuit. Mark one accountable role per row.
| Decision | Accountable (one role) | Must be consulted | Informed | Limit or condition |
|---|---|---|---|---|
| Example: refreshments per stop | Local host lead | Programme lead | Finance | Up to the agreed stop budget |
| Add your decision here |
Open the tool: KL-Selangor-Seremban briefing circuit planner
Handle it in-house, or bring in help?
Your team can usually handle this when
- The local teams already work with you and the stops are few.
- One person at the centre has time to review every stop brief.
- Spending limits and escalation routes are already agreed.
Outside planning help earns its fee when
- Local teams are from different organisations or agencies.
- Central staff are stretched across the stops.
- Past circuits have ended with disputes over who approved what.
Want a central lead who keeps the local teams in step?
Recurring programme management can set the decision rights with you, issue one brief to every local team, run the pre-stop checks and gather the after-stop reports in one format. Send the stop list and who the local teams are. A conference project lead covers the same ground if recurring support is not available.
Questions organisers ask
How much should a local team be allowed to decide?
Whatever does not change content, brand, budget limit, data handling or safety escalation. Write the list and review it after the first stop.
Who handles an incident at one stop?
Agree this in advance. Usually the local team gives the first response and the central lead is informed at once. Ask the venue and your own safety lead for the right route.
Do local teams need the full programme?
They need the part that affects them, in one brief. Share the rest only if they need it.
Related resources
- Regional multi-city corporate briefing planning guide
- Choosing which parts of a briefing must stay consistent across cities
- Managing one registration system for several briefing locations
- Event responsibility matrix builder
- KL-Selangor-Seremban briefing circuit planner
- Recurring member-event programme management
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.