Annual professional association conferences
Planning the next edition without copying last year's programme
Last year's programme is open on your screen, and copying it would be the quickest way to a finished draft.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Treat last year's programme as evidence, not a template. Audit every session as keep, refresh or retire, and decide the new edition's purpose before you open the old running order.
A useful rule of thumb is to name what the programme committee wants delegates to do differently this year. Sessions earn a place by serving that, not by having been there before.
Why copying feels safe and what it costs
A repeated programme is easy to approve. Speakers, rooms and timings are known, and nobody has to argue about content.
The cost shows up in members who attended last year and see nothing new, in sponsors asking for the same slot, and in the committee never revisiting why a session exists. The association conference planning guide covers the whole annual cycle; this page covers only the programme decision.
Start with the audit, not the draft
- Collect last year's running order, session feedback and attendance by room, if you recorded it.
- List each session on one row with its owner, original purpose and whether the speaker is a returning or a new voice.
- Ask the programme committee to mark each row keep, refresh or retire before any new session is proposed.
- Count how many slots the retire and refresh decisions free up, and only then call for new ideas.
What each verdict means
| Verdict | Use it when | What changes |
|---|---|---|
| Keep | The session met its purpose and the audience still needs it. | Same format; confirm speaker and update examples. |
| Refresh | The topic still matters but the angle, speaker or format is stale. | New case, new speaker or a different format such as a clinic instead of a talk. |
| Retire | Purpose achieved, topic faded or feedback shows low value. | Slot goes to a new idea, or the time is returned to networking. |
Who has a stake in the old programme
- Returning speakers who assume they are invited back and need a clear, early answer either way.
- Long-serving committee members attached to sessions they created.
- Sponsors whose visibility was tied to a particular slot, which is a conversation for the sponsorship workstream, not for the programme audit.
- Members who attended and want continuity of a few signature items, such as an annual update or an awards session.
Keep a small fixed core
Most associations have two or three items that members expect every year. Name them as the fixed core and design the rest around them.
Anything outside the core is open to challenge. This keeps the decision from feeling like a rejection of the previous committee's work.
Check the draft before it is announced
Compare the new draft with last year's running order side by side. If more than a few sessions share title, speaker and slot, ask the committee whether that is intentional.
Pass the shape of the new programme to the secretariat early so venue and supplier briefs follow the new rooms and timings, not the old ones.
Worked example · Fictional example
A fictional association audits 14 sessions
Fictional organisation and figures, for illustration only.
The Persatuan Fiktif Jurutera Perunding ran a one-day conference with 14 sessions. Its programme committee marked 4 as keep, 6 as refresh and 4 as retire.
The 4 retired slots became two new sessions chosen from member feedback and one extended networking break. The secretariat told the two returning speakers whose sessions were retired before any announcement, and offered both a chance to propose a refreshed topic.
Use this yourself
Session audit table
Copy one row per session from last year. The committee fills the last two columns before any new session is proposed.
| Session | Original purpose | Feedback or attendance note | Verdict (keep / refresh / retire) | Reason and owner |
|---|---|---|---|---|
| Example: opening plenary | Set the year's agenda | Rated useful by most respondents | Keep | Chair to confirm speaker |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The programme committee meets regularly and decides quickly.
- Last year's feedback and running order are on file.
- Few sessions are contentious.
Outside planning help earns its fee when
- The committee has changed and nobody remembers why sessions were chosen.
- Keep or retire decisions are stalling on competing opinions.
- The secretariat has no time to collect feedback, brief speakers and run the decision dates.
Need someone to run the programme decisions to a date?
If the audit is clear but the committee keeps deferring the keep, refresh and retire calls, a conference project lead can set the decision dates, collect the evidence and brief speakers on the outcome. The programme itself stays with your committee.
Questions organisers ask
How much of last year's programme should we change?
There is no correct percentage. Set a fixed core the members expect, then judge everything else against this year's purpose. The audit shows how much needs to change.
What do we tell a returning speaker whose session is retired?
Tell them early and plainly, thank them, and say whether a refreshed proposal is welcome. Delay is usually worse for them than the answer.
Where do we find evidence if we did not collect session feedback?
Use registration choices by session, room headcounts from the volunteers, and a short member question. Record the gap and collect better evidence this year using the feedback objectives page.
Can we reuse last year's budget and timeline?
Use them as a starting point only. Changes in rooms, speakers or formats alter costs, so rebuild from the new programme shape in the event brief builder.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.