A draft and published versions
Building a programme takes weeks, with many changes on the way. Attendees should not watch every one of them. That is why the agenda in run.events has a draft and published versions.
- The draft is your work in progress. Everything you change in the Agenda Builder stays in the draft.
- A published version is what the public sees. Each time you publish, the draft as it stands becomes a new version, and the public pages, the widgets on your website and the app show that version.
While the draft differs from the last published version, a yellow notice over the grid says so, with What changed? and Publish.
What a publication contains, and what goes public at once
A version holds the layout of the programme: which entry sits in which room at which time, and the session blocks, breaks and placeholders with their titles and chairs. Changes to the layout reach the public only when you publish.
A session's own details are not part of the version. Its title, its abstract, its people, and the names of the rooms reach the public at once, without a publication. If you correct the spelling of a speaker's name, the public sees the correction straight away.
Good to know: a correction to a session's title alone gives nothing to publish. Publish then says "There is nothing to publish.", because the title is already public.
Publishing
- In the yellow notice over the grid, choose Publish.
- Publish the agenda lists every change by day: what was added, removed and moved, with the old and the new day, time and room.
- Write a Note, for example "Friday afternoon rearranged after two cancellations".
- Publish.
Publish always publishes the whole draft. You cannot publish only some of the changes. If part of the draft is not ready, hide it first (see below) or finish it before you publish.
Publishing tells nobody. Speakers see their new slot on their speaker dashboard, with "Moved: was …" until they open the session, but no mail goes out. Write to them yourself if they should know.
Before your event is public
While your event itself is not published, its programme pages show nothing to anyone outside your event team. You can publish the agenda as often as you like; only your team sees it. This is a good way to show the committee a draft before the programme goes public.
Keeping parts of the programme out of view
- A session block, a break or a placeholder: clear Public on the entry. It disappears from the public agenda at once, without a publication. To show it again later, tick Public and publish.
- A whole room: clear Show in Agenda on the room in Room Management. This takes effect at once.
- Single sessions: a session has no Public tick. Give it a session label whose Visible on has the channels cleared where it should not appear: Web, App, Print, Poster gallery. This takes effect at once. Use it, for example, to show a session in the app only, or to keep a staff briefing off every channel.
Keep in mind that the draft hides only the layout. An accepted session with a confirmed speaker appears on the event portal's sessions page and in the sessions widget, whether it is on the agenda or not. To keep the content of a session hidden, use an embargo.
Published versions
Every publication is kept. In the Agenda Builder's menu, under Tools, Published versions lists them: each with its number, its date, who published it and the note. The version the public sees is marked Public.
On each version:
- Compare with draft shows what you have changed since that version.
- Compare with version… shows the differences between two versions.
- Revert to this version makes that version the draft again. The public sees it only after your next publication.
What changed?, in the bar above the grid, shows what the last publication changed compared with the version before it.
Good to know: Revert to this version brings back the layout only. Titles, abstracts and people stay as they are now. A revert is refused while a locked entry, room or day is in the way.
Who changed what
Published versions shows who published each version and why. The tab Lock history in Agenda Settings shows who locked and unlocked what. run.events does not record who moved which entry in the draft between two publications. If several people edit, agree on who publishes, and write a clear note each time.
Versions and the printed programme
The programme documents, such as the printed programme and the room timetables, are made from a published version. A document can be pinned to one version, so that it does not change when you publish again, and the Changes report lists what moved between two versions, for the print shop or the signage team. See Publications: the Book of Abstracts and the Programme Documents.
Related articles