Managing the handover from conference chair to operations team
The chair has shaped the programme, and now the secretariat has to run the event without calling the chair about every detail.
The short answer
The handover works when the chair and the operations team agree, in writing, which decisions stay with the chair, which pass to the operations team, and which need both.
Pick a handover date, hand over a decision-rights table and a brief rather than a conversation, and agree how the chair will be reached when something truly needs them.
Why the handover goes wrong
- The chair stays involved in details out of habit, so operations decisions wait for a reply.
- The operations team makes decisions that the chair considers programme matters, such as moving a speaker's slot.
- Promises made by the chair to speakers, sponsors or members never reach the secretariat.
- Nobody agrees when the chair stops being the first call and becomes the escalation point.
Three kinds of decision
| Kind | Examples | Who decides |
|---|---|---|
| Chair keeps | Programme changes that alter content, speaker line-up, the theme, public statements on behalf of the conference. | Chair, recorded in the decision log |
| Operations decides | Room set-up, supplier timings, registration queries, catering counts within agreed limits, volunteer rosters. | Operations lead, reported to the chair in the weekly summary |
| Both agree | Last-minute session swaps, speaker substitutions, anything that changes cost beyond a set limit. | Chair and operations lead, within an agreed response time |
A sequence for the handover
- Agree the handover date, usually when the programme and speaker list are confirmed.
- The chair writes a handover brief: what has been promised, to whom, and what is still open.
- Both sign off the decision-rights table, including financial limits for operations decisions.
- Agree a response time for escalations and a named alternate if the chair is unreachable.
- Schedule a short weekly check-in so the chair stays informed without being involved in details.
- Record all promises and changes in the decision log.
What the handover brief should contain
The brief is not a full plan. It is the part of the chair's head that nobody else has: informal commitments, relationships and judgement calls.
Examples are the speaker who was promised the opening slot, the sponsor who was told a particular room would be used, and the member who asked for a reserved seat. Anything promised that is not written down will be broken by accident.
Where authority sits
Elected chairs often hold both programme authority and, by habit, operational authority. The council or committee should confirm which authority the chair hands over. See separating elected committee decisions from conference operations and the committee terms of reference for how to write this down.
If the operations team is a single secretariat person, check that the person has authority to commit supplier spend up to the agreed limit without waiting for a committee meeting.
Worked example · Fictional example
A fictional chair hands over at six weeks
Fictional organisation and figures, for illustration only.
The chair of the Persatuan Fiktif Juruukur Bahan hands over the conference to a two-person secretariat team six weeks before the event. The handover brief lists three informal promises: the opening slot to a visiting speaker, a reserved table for a past president, and a sponsor's request to display a banner near the registration desk.
The decision-rights table allows operations to approve catering and set-up changes up to a stated amount and to swap two breakout rooms without asking the chair. Any change to a speaker or session title needs the chair's reply within one working day, and a named deputy chair covers if the chair is travelling.
Use this yourself
Handover brief and decision-rights table
Complete this together and keep it with the decision log. Anything the chair has promised that is not on the list needs to be added before handover.
- Handover date and who is present:
- Programme status: confirmed, pending and still open items:
- Informal promises made by the chair, to whom, and the agreed response:
- Decisions the chair keeps:
- Decisions operations makes, with financial limits:
- Decisions needing both, with the agreed response time:
- Escalation route and named alternate if the chair is unreachable:
- Weekly check-in day and format:
- Where the decision log and supplier contracts are held:
- Date the arrangement will be reviewed:
Handle it in-house, or bring in help?
Your team can usually handle this when
- The chair and the operations lead already work well together.
- Authority limits are accepted by the committee.
- The event has one clear operations owner.
Outside planning help earns its fee when
- The chair is also managing the programme, the sponsors and the budget.
- The operations team is a part-time secretariat and has not run this event before.
- There is disagreement over who may commit spending or change the programme.
Need the handover run to a date?
If the chair and the secretariat both want a clean handover but nobody has time to write it, a conference project lead can draft the decision-rights table, collect the chair's open promises and run the weekly check-in until the event. Authority limits and programme decisions stay with the chair and your committee.
Questions organisers ask
When should the chair hand over to operations?
Usually once the programme, speakers and venue are confirmed. Pick a date, write it in the plan and make it visible to the committee.
Can the chair still change the programme after handover?
Yes, but through the agreed route. Programme changes go in the decision log and the operations lead adjusts suppliers and communications.
What if the chair is also the operations lead?
The distinction matters less, but still write the decisions down. If workload is the problem, see event committee workload planning for a way to see it.
How does this differ from continuity across years?
This page covers the within-year handover. Continuity when leadership changes between editions is covered in retaining useful continuity.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.