Programme architecture
Keeping event agenda versions under control
Three people hold three different agendas, and the printed programme matches none of them.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Keep one master agenda with one owner, a version number and a date on every copy, and a change log that records each change, who approved it and who was told. Everything else, including slides, printed programmes and supplier cue sheets, is built from the master and marked with the version it came from.
Add freeze points: dates after which a change needs a named approver and a re-issue to everyone who holds an older version.
What the master agenda is
The master is the single document the programme owner updates. Others read it and request changes, but they do not edit their own copies and circulate them.
Keep it where all editors see the same file, and make sure the file name, the footer or the header shows the version and date.
Who touches the agenda
| Role | Can do | Cannot do |
|---|---|---|
| Programme owner | Edit master, issue new versions, approve small timing changes within the agreed limit. | Approve a change to a speaker, session topic or ceremonial item without the named approver. |
| Committee chair or programme approver | Approve changes to speakers, topics and order after the freeze point. | Edit copies held by suppliers. |
| Project lead or coordinator | Log changes, issue versions, chase acknowledgements. | Decide content. |
| Venue, audio-visual and other suppliers | Raise timing and technical conflicts. | Change times on their own cue sheets without a new issue. |
| Speakers and moderators | Request a change through the liaison. | Agree swaps with each other. |
Setting up the controls
- Choose a numbering style the whole team can read, for example a version number plus date, and put it on every copy.
- Name the approver for each type of change: timing, speaker, topic, order, room.
- Set freeze points, such as when printing starts, when slides are due and the day before the event, and write down what a change costs after each.
- Keep a distribution list with the version each party last acknowledged.
- Record every change in a decision log or the change log below, and link it to the run-of-show.
Common ways versions drift
- A speaker emails the venue directly and the venue updates its own sheet.
- A timing change is made in the run-of-show and not in the printed programme.
- Screens show an older agenda from a file saved earlier.
- The master is updated after the meeting, but nobody is told.
- Small changes pile up and the total no longer fits. Check with the duration checker at each issue.
Worked example · Fictional example
A two-track forum that kept three agendas
Fictional organisation and figures, for illustration only.
A fictional professional forum had a master spreadsheet, a venue sheet and a draft printed programme. A session moved by 15 minutes in the master and nobody told the venue.
After the miss, the programme owner named one master, set a freeze date three weeks before the event, and sent every issue to a distribution list with a reply-to-acknowledge line. In the next cycle a speaker swap was requested after freeze, the chair approved it in writing, and version 7 went to all parties within the same day with the change highlighted.
Use this yourself
Agenda change log
Copy into a shared spreadsheet. Add one row per change and keep older rows.
| Version and date | What changed | Reason | Requested by | Approved by | Parties told | Acknowledged (date) |
|---|---|---|---|---|---|---|
| v1 and date | First issue | |||||
| v2 and date | ||||||
| v3 and date |
Handle it in-house, or bring in help?
Your team can usually handle this when
- One person owns the agenda and has time to log changes.
- Few suppliers and few speakers hold copies.
- Changes rarely happen after the programme is published.
Outside planning help earns its fee when
- Many parties hold copies and changes are frequent near the date.
- Several committees approve different parts of the programme.
- Printed materials, screens and cue sheets must all match on the day.
Need the agenda controlled through to the day?
An Event Blueprint can set the master agenda, the version and approval rules and the freeze dates with your committee. A conference project lead can run the change log and re-issues through the final weeks if your team wants that workstream handled. Send your current agenda and who holds copies.
Questions organisers ask
Do we need special software for agenda version control?
No. A shared document or spreadsheet with a clear owner, version number and change log is enough. The discipline matters more than the tool.
When should the agenda be frozen?
Pick freeze dates from your own print, slide and supplier deadlines. After each freeze, require a named approver and a re-issue.
Who should be told about every change?
Anyone who builds something from the agenda: venue, audio-visual, catering, printers, stage manager, moderators and the speaker liaison.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.