Writing final joining instructions for your event
Registration is closed, the programme is settled, and every confirmed attendee now needs one message that tells them exactly what to do on the day.
The short answer
Final joining instructions are the single message a confirmed attendee reads before they travel. They say where to go, when to arrive, what to bring, how check-in works and who to contact, using only facts the venue and suppliers have confirmed in writing.
Send one version per audience, such as delegates, speakers and sponsors, so no one reads instructions meant for someone else.
What goes in, and who confirms each item
| Item | Detail to include | Confirm with |
|---|---|---|
| Place and entrance | Venue name, the entrance to use, the room or level for check-in. | Venue event contact |
| Times | Doors open, check-in window, programme start, scheduled finish. | Programme owner |
| Travel and parking | Only routes and parking arrangements the venue has confirmed in writing; otherwise link to the venue's own page. | Venue |
| Check-in | What to show, for example confirmation or ID, and where badges are collected. | Registration lead |
| Dress and what to bring | Dress expectation, any pre-reading, items to carry. | Organiser |
| Access and dietary needs | How to update needs already given, and a named contact. | Registration lead |
| Contact on the day | A role and a channel monitored on the day, not a person's personal number. | Project lead or secretariat |
Split by audience
Delegates need arrival, check-in and programme information. Speakers also need their session time, room, technical check arrangement and who meets them. Sponsors and exhibitors need load-in details from the venue and supplier, which you should take from their written confirmation.
Keep the speaker and sponsor versions separate from the delegate message, and link each to the audience's own detail rather than overloading one email.
Plan arrival so the message matches the desk
If you ask everyone to arrive at the same time, check-in becomes the first complaint. Use the check-in throughput estimator with your own desk count and observed service time to see how long an arrival window needs to be, and stagger arrival slots or categories if it does not fit.
Treat the estimate as a planning aid only. It is not a queue-time promise or a crowd safety assessment, so ask the venue about any limits on entry and queueing space.
Check it before sending
- Read it against the venue's latest written confirmation, line by line.
- Send it to two people who have not seen the plans and ask where they would go and when.
- Check the links, the entrance name and the times in every language you send.
- Fix the send date in the invitation and reminder sequence so it does not collide with another reminder.
Worked example · Fictional example
A one-day association conference
Fictional organisation and figures, for illustration only.
The fictional Malaysian Society of Event Planners sends final instructions to 310 confirmed delegates and 24 speakers five working days before the conference. Delegates are asked to arrive in one of three half-hour check-in slots by surname band.
The speaker message adds room, session time and a technical check slot confirmed by the AV supplier. A reviewer who had not seen the plans tests the delegate version and finds the entrance name differs from the venue's own signage, so it is corrected before sending.
Use this yourself
Final joining instructions template
Copy this structure. Replace each bracket with a fact confirmed in writing, and delete anything you cannot confirm.
- Subject: [Event name], joining instructions for [date]
- Where: [Venue], enter via [entrance], check-in at [location].
- When: check-in [window], programme starts [time], finishes [time].
- Your check-in slot: [slot], and what to show: [confirmation / ID].
- Getting there and parking: [venue-confirmed details or the venue's own link].
- What to bring and what to wear: [details].
- Access, dietary or other needs: reply to [role] by [date] to update what you gave us.
- On the day, contact: [role and channel monitored on the day].
- Question to confirm with venue: any limits on entry, queueing space or access routes that should appear here?
Handle it in-house, or bring in help?
Your team can usually handle this when
- One audience, one venue contact and a simple arrival pattern.
- The venue has confirmed every logistical detail in writing.
- Your team has run a similar check-in before.
Outside planning help earns its fee when
- Several audiences with different arrival, load-in and access needs.
- Arrival is concentrated and check-in capacity is uncertain.
- Details are still changing between the venue, the registration system and suppliers.
Want the last message checked against the real plan?
A conference project lead can assemble the confirmed facts from the venue and suppliers, draft one version for each audience and test them before they are sent. You still approve and send. Send your programme and the venue's latest written confirmation.
Questions organisers ask
How early should final instructions go out?
Set the date from your own check-in, badge and catering cut-offs. Ask the venue when it needs final numbers and plan the send for after those are settled.
Should we include directions and parking?
Only what the venue has confirmed in writing. Otherwise link to the venue's own travel page and ask the venue what it is happy for you to say.
What if details change after the message is sent?
Send a short correction to the same list, say what changed and what has not, and record the time it went out.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.