The situation
The programme goes to the printer weeks before the congress. After that, changes still come: cancellations, room swaps, a late keynote. The printed programme cannot follow them, so you need two things: protection against accidental changes, and a precise list of what moved since the print, for an insert or for the signs on site.
run.events has no "final" state for the programme. What it offers are locks, pinned versions and the changes report.
Step 1: Publish the version that goes to print
In the Agenda Builder, choose Publish with a note such as "Printed programme". Remember its version number in Published versions.
Step 2: Lock the layout
Under More in the bar above the grid, choose Lock everything scheduled. Every placed entry is now locked against accidental moves.
A lock guards against accidents, not against decisions: anyone who may edit the agenda can unlock, and a withdrawn or cancelled talk leaves the agenda even when it is locked.
Step 3: Pin the printed programme to its version
Make the printed programme from that version, and pin it:
- On Publications, open the programme document, or create it with Add new.
- On its tab General, under Agenda version, choose the version you published for print. The card then reads "Version n (pinned)".
- Choose Generate.
A pinned document does not change when you publish again. Under the card's menu, Runs lists every run, with its date and the agenda version it used, so you can always find the file that went to print.
Step 4: List what moved since the print
When changes have come in:
- Publish the current state of the agenda.
- On Publications, choose Add new and Changes report.
- Choose the Newer version (the current one) and the Older version (the one that went to print).
- Choose Generate. You get the report as PDF, Word and Excel.
What the changes report lists
- entries added, removed and moved, with their old and new day, time and room;
- renamed session blocks, breaks and placeholders;
- changed chairs;
- cancellations, withdrawals and declined participations;
- people who have not confirmed.
What it does not list: corrected session titles, abstracts and speaker names. These are not part of a version; they go public at once and are not tracked. If such a correction matters for print, note it yourself. For abstracts, the card of the Book of Abstracts shows how many sessions were changed since its last run, without naming them.
Good to know: the changes report compares two published versions. Publish before you make it, or the latest changes are not included.
Related articles