A venue arrival information request sheet helps an organiser identify what the venue still needs to confirm before visitor directions are written. After this guide, you can prepare six focused question topics and save a file you can reopen in a planned fifteen-minute session, without claiming that any venue answers have arrived.
Last updated: 19 October 2026.
What does a venue arrival information request sheet achieve?
A venue address is not an arrival route. A guest can reach the right building and still be unable to identify the event entrance or find the room. Before writing directions, an organiser needs specific information from the person responsible for the venue. This guide helps you prepare that request, not send it.
Your deliverable is a small working document that separates questions from confirmed answers. It does not rate a building, certify accessibility or promise that a particular route will meet every person's requirements. Step-free means a route without steps; the label alone does not establish whether every part of a journey suits someone.
Imagine a local business association arranging an evening discussion in a hired room. This is a fictional planning situation, not a report of an event. The organiser knows the building name but has no confirmed entrance description. The right next action is to record that gap, rather than turn a map pin into confident visitor instructions. Keep booking arrangements separate; the meeting scheduling guide addresses a different job.
Build the request around six information gaps
W3C's event checklist includes building entrances, meeting rooms, bathrooms and information about routes. Use those categories to decide what to ask. The source cannot tell you anything about an uninspected venue you might hire.
| Topic | Request to prepare | Honest starting status |
|---|---|---|
| Entrance | Which entrance is intended for this event, and how can it be recognised from outside? | Awaiting venue information |
| Step-free route | Is there a step-free route from that entrance to the room, and where does it run? | Route unconfirmed |
| Lift | If the route depends on a lift, which lift and destination floor are involved? | Lift details unconfirmed |
| Toilets | Where are the relevant toilets, and what route leads to them? | Location and route unconfirmed |
| Wayfinding | What signs will identify the route, especially where visitors could take a wrong turn? | Signs unconfirmed |
| Arrival contact | Who will handle arrival questions, and through which agreed contact channel? | Contact unconfirmed |
Wayfinding simply means helping people locate their destination. Do not turn that heading into a requirement for an elaborate signage system. You are asking what will actually exist, not describing what you wish the venue provided.
Copy a record that preserves uncertainty
Start with a new document rather than editing an old attendee email. That reduces the chance of carrying over another room's entrance, telephone number or access statement. Give the request an internal reference so later answers can be tied to the right event.
Venue arrival request V1 Event reference: Room and event date: confirmed / not yet confirmed Prepared by: Document status: unsent question sheet Item number: Information topic: Specific question for the venue: Information already confirmed: Person or team expected to answer: Reply date and source: Remaining uncertainty: Status: unsent / sent, awaiting reply / clarification needed / confirmation recorded
Repeat the item fields for the six topics. If the venue contact has not been appointed, write “venue contact to be identified”. Do not invent a name to make the document look complete. An empty reply field is useful evidence that the question remains open.
Keep commercial negotiation elsewhere. The business proposal guide deals with scope and a proposed commercial agreement. This sheet collects information for a visitor's physical arrival. Mixing the two can bury an unanswered route question beneath a long discussion about price.
Replace reassuring labels with answerable questions
“The building is easy to access” may sound helpful but does not identify an entrance. Preserve that wording as the reply you received, then ask the next factual question. Do not silently rewrite it as a confirmed route.
- Instead of “Is access fine?”, ask which entrance will be used and whether that route includes steps.
- Instead of copying “There is a lift”, ask whether the intended room is reached by that lift and which floor is involved.
- Instead of “Someone will help”, ask who the arrival contact will be and how visitors should reach them.
These are suggested questions, not claims about an actual building. If a photograph is supplied later, distinguish what it shows from what remains unknown. A photograph of an entrance does not establish the whole route to a room or confirm that the entrance will be in use.
Keep the original reply alongside your clarification. That lets a colleague see why another answer is needed. The same distinction between discussion and confirmation appears in the meeting notes workflow, although you do not need recording software or AI to complete this request.
Use real organising context without inventing a case study
A 17 October 2022 APA TV report identifies Anar Rustamli as one of the people who helped organise MeasureCamp with Kamal and other professionals. That is the real organising context used here. The report does not establish that he used this request sheet, inspected a venue's access arrangements or measured an improvement in arrivals.
This worksheet is a new recommendation for the reader. It is not a recovered historical document or an official event manual. No venue has been selected for this exercise, and none of the unanswered fields has been checked on site. Keep those limits visible when adapting the document.
UCL's accessible-event tips draw attention to route information, locating toilets and an arrival contact point. Those ideas support asking specific questions rather than repeating a broad access label. They do not transfer facts about UCL facilities to another organiser's building.
For an international team, also avoid assuming a local date or familiar building nickname is enough to identify the event. The meeting time clarification exercise handles an ambiguous instant. This request handles physical arrival information. Neither task can substitute for the other.
Create, save and reopen one useful file
Use a plain text editor you already have. On Windows, open Start, search for Notepad and launch it. Create a new blank document and paste the headings above. Write the six questions before attempting to supply any answers. You do not need an account, an integration or a venue reply for this first output.
- Spend about three minutes identifying the event reference and marking unknown room or date details. Expected result: a clear document header without invented facts.
- Allow five minutes for the six question topics. Expected result: a visible request covering the entrance through to the arrival contact.
- Use three minutes to replace vague language and separate assumptions from confirmed information. Expected result: questions a venue representative could actually answer.
- Reserve four minutes for saving and checking. Press Ctrl+S, choose Documents and save venue-arrival-request-V1.txt. Close the editor, find the file in Documents and open it again. Expected result: the questions and unresolved statuses remain intact.
This allocation is a planning suggestion, not a measured completion-time claim. Another editor may use different menu labels. If you cannot reopen the saved document, the file task is not finished. Sending it, receiving an answer and inspecting the venue are separate actions with their own timing.
A training activity worksheet can help organise a wider learning exercise, but this task has a narrower finish line: one readable request file. Stop once the questions are specific and the saved version is recoverable.
What should stay unresolved after the first session?
Leave every unsupported venue fact unresolved. Preparing a question is not obtaining permission to publish an answer. A document can be complete as a request while remaining incomplete as a source of arrival directions. Name that distinction in the status field.
When someone later records a reply, preserve its date, author or team and the event or room it concerns. A reply about a previous event is not automatically current information. If answers conflict, keep both and identify the conflict instead of choosing the more reassuring one. Requesting clarification would be a later, separately managed step.
Do not copy a private telephone number into an attendee message simply because it appeared in correspondence. An agreed public contact channel is a separate field to confirm. This exercise does not ask you to collect a participant's medical history or record personal access requirements in the venue sheet.
The request is one preparation tool, not a complete access assessment or safety plan. Different people may need different information. Its modest value is that an organiser can see which venue questions remain unanswered before writing confident directions. A finished first version contains the six topics, honest statuses and a file you can reopen.
Frequently asked questions
Does the sheet certify that a venue is accessible?
No. It prepares questions for the venue contact. It is not a certification, an on-site assessment or a guarantee that a route suits every participant.
Can I finish the task without a venue reply?
You can finish and save the question sheet. Confirmed arrival information still requires replies and appropriate checks; unresolved fields must stay unresolved.
What if I have no information about the lift?
Keep the lift question open and record that the details are unconfirmed. Do not infer a usable route merely from a building photograph or address.
Should I send the request during this exercise?
No. The exercise ends with a saved, reopened question file. Sending it, receiving replies and inspecting a venue are separate activities.


