Skip to content
EventConsultant

Recurring and cross-location professional programmes

Using one organising committee for several target-region events

One committee is organising events in KL, Selangor and Seremban, and every decision is being taken again at every stop.

Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

Optional: send a short event brief

Every field can stay as Not decided. You review the full message before WhatsApp opens.

Message preview

Hi, I'd like to discuss professional-event planning support.
Help needed: Not decided
Event type: Not decided
Event area: Not decided
Date: Not decided
Approx. attendees: Not decided
Reference: EV-1010 / en
Page: https://eventconsultant.com.my/guides/local-event-planning/using-one-organising-committee-for-several-target-region-events/

The short answer

Sort every decision into central, local or shared, and write the owner beside it. Central decisions are made once for all stops. Local decisions are delegated by name. Shared decisions state who proposes and who approves.

Build the matrix in the responsibility matrix builder. Where the committee will run the same programme repeatedly, recurring programme management can keep the matrix current.

Why decisions get duplicated

When ownership is unwritten, each stop re-opens decisions the committee already made, such as speaker fees policy, registration wording or sponsor rules. The matrix fixes who decides what, and what a stop may change without asking.

What to verify before delegating

Each check is a question with who answers it.

  • Which decisions must stay central because they bind every stop, such as budget limits and the core programme? Answered by the committee chair.
  • Which decisions depend on the stop's own venue or authority, so cannot be made centrally? Answered by the venue and the council for that address.
  • Who is the named local owner for each stop, and what authority do they have in writing? Answered by the committee.
  • What triggers an escalation back to the committee? Answered by the committee, recorded in the matrix.
  • Who holds the decision log, and where can every stop see it? Answered by the secretariat.

How the three areas differ for this decision

The verifiable difference is the local authority. DBKL, MBPJ and MBS each publish their own portals for Kuala Lumpur, Petaling Jaya and Seremban, and MBS public material includes Nilai. Any decision that depends on a council or building rule therefore has a different owner at each address, which is why it sits in the local column rather than the central one.

Worked example · Fictional example

A fictional regional committee

Fictional organisation and figures, for illustration only.

A fictional accounting association's committee lists twelve recurring decisions. Five become central, four local to the stop and three shared with the committee proposing and the stop host approving.

The stop hosts stop re-voting on the five central items, and each local owner records only the four items they own. All numbers are illustrative.

Use this yourself

Central-versus-local approval matrix

One row per decision. Mark exactly one owner type and name the person.

DecisionCentral, local or sharedNamed ownerWho approvesEscalate to committee whenLogged where

Open the tool: Event responsibility matrix builder

Handle it in-house, or bring in help?

Your team can usually handle this when

  • A small committee with clear roles and a few stops.
  • The secretariat can keep the decision log current.

Outside planning help earns its fee when

  • Stop hosts keep re-opening central decisions.
  • Several stops overlap in time and need a single coordinator.
  • The committee changes membership often and the matrix needs an owner.

Want the matrix built and maintained?

A project lead can run the committee through the matrix, name the local owners and keep the decision log across stops. If recurring programme management is unavailable for your dates, the same coordination can be scoped as an outsourced conference project lead. Share the stops and the current committee roles.

Discuss your committee matrixOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Recurring programme management

Questions organisers ask

Which decisions should stay central?

Those that bind every stop, such as the core programme and budget limits. Your committee decides the list.

What if a stop disagrees with a central decision?

Use the escalation trigger in the matrix rather than changing it locally.

Do local owners need written authority?

Yes. Record it so the venue and suppliers know who can decide.

Is there a local office?

No office is claimed. On-site arrangements are agreed for the particular brief.

Related resources

Sources and check dates

  1. Portal Rasmi DBKL, Dewan Bandaraya Kuala Lumpur (DBKL) (checked 2026-10-07). DBKL is the official portal of the Kuala Lumpur city authority, so a Kuala Lumpur address starts here
  2. Portal Rasmi Majlis Bandaraya Petaling Jaya (MBPJ), Majlis Bandaraya Petaling Jaya (MBPJ) (checked 2026-10-07). MBPJ is the official portal for Petaling Jaya; the full address decides whether it applies
  3. Portal Rasmi Majlis Bandaraya Seremban (MBS), Majlis Bandaraya Seremban (MBS) (checked 2026-10-07). MBS is the official portal for Seremban, which MBS public material says includes Nilai

Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.