1. Confirm the change before editing
Record what changes, who approved it and when the message should take effect. A request for another room is different from a confirmed booking. If information remains uncertain, the responsible organiser needs to decide what can be published.
Rehearse with a fictional example: the start moves from 09:00 to 10:00 and entrance A changes to B. Make a list of the old value, new value, responsible person and affected languages. It should be understandable without reconstructing a long email conversation.
2. Find every potentially conflicting reference
Check the homepage, programme, practical information, registration link and downloadable files. Include captions and reused event cards. Find the actual language equivalents; changing English does not establish that other languages update automatically.
Calendar files and external booking pages may have their own data and owners. Record who can change them and what has actually been updated. A downloaded file or previously sent message is not replaced simply because the website changes.
3. Publish a comprehensible message
Place the current information where attendees need it. A substantial change may warrant a short, dated notice explaining what has changed. Do not leave old and new times side by side without making their status clear.
Check the preview on mobile and with a keyboard. Use meaningful link names. If a PDF remains necessary, update it too and identify its version. Essential times and the address should also appear as ordinary text on the page.
| Information | Owner | Check |
|---|---|---|
| Programme | Programme lead | Time and room agree |
| Registration | Booking lead | The button describes the actual next step |
| Venue | Organiser | Address and entrance are confirmed |
| Change | Assigned editor | Languages and references are reviewed |
4. Follow the published attendee journey
Open the site in a fresh session. Go from the event entry point to the programme, practical information and registration. Compare the result with the change list in every language and follow actual links rather than relying on the editing view.
Ask another person to find when it starts, where to enter and whom to contact. Save the result and any unresolved external dependencies. Retain the change list so the next editor understands which message replaced the previous one.