Destination and multi-day
Make access needs part of the operational plan
Editorial team · Reviewed
Access planning works best when it is a normal part of asking what people need to participate. Translate confirmed requirements into practical routes, timing and responsibilities without sharing unnecessary personal details.
A practical sequence
- Ask the relevant person how they would like the team to support their participation.
- Confirm venue routes, transport and seating with the responsible providers.
- Allow the actual time needed for transitions.
- Give the on-site lead the operational instruction and a respectful way to check it.
Work through an example
A guest needs a step-free route that takes longer than the main staircase. The planner confirms the route, adjusts the arrival instruction and names the person available to help if requested. The public guest list does not need a medical explanation.
Where judgement matters
A software label cannot certify accessibility. Confirm the actual venue and equipment with the person using them and the responsible professionals. Avoid assuming that one solution works for everyone with a similar stated need.
Make it usable
Open the working tool and work through the decision with your own inputs. Adapt the structured template to preserve the choices and responsibilities. Keep an original copy so later changes remain understandable.
Work the decision
A practice case
An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.
A guest asks for help with the final approach from vehicle drop-off to the ceremony. The venue’s photograph shows a wide path, but the actual route includes a threshold and a change of surface. Ask the guest about their needs and obtain a specific venue plan rather than marking the whole event accessible from an image.
| Decision | Why it matters |
|---|---|
| Discuss assistance privately and respectfully. | The person should decide what information needs to be shared and with whom. |
| Confirm the entire route with the venue. | Transport, entrance, seating, toilets and departure are connected parts of the experience. |
| Assign the agreed assistance to a named person. | A general note in a large runbook does not establish that someone will be present. |
Make one usable artifact
Create a restricted handoff with the requested arrangement, route, responsible contact, confirmation date and backup. Keep unnecessary personal detail out of public schedules.
Then test the difficult case
The rain plan changes the entrance. Reconfirm the agreed route and assistance before publishing the relocation as ready for guests.
Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.