A visitor cannot plan from a welcome statement alone. They may need to know which door is used, whether an exhibition needs booking, how long a seated activity runs or whether a particular facility is available during the session. When these details are scattered across announcements, the person has to reconstruct an operational picture the venue already knows.
A useful pre-visit page gathers the facts that change a practical decision and gives unresolved questions a clear contact route. It should describe the current visit rather than an idealised version of the building. The page does not need to answer every conceivable enquiry, but it should distinguish what is known, what varies and what must be confirmed for a particular programme or requirement.
Begin with questions that affect the decision to visit
Collect recurring enquiries from reception, booking messages and public programme staff. Remove unnecessary personal details before sharing the list for editorial work. Group questions by the decision they support: whether to attend, how to reach the entrance, what participation involves and what facilities are available. This produces a page based on actual information needs rather than a marketing team's guess about what a visitor might find reassuring.
Include questions that staff answer so routinely they no longer recognise them as missing information. A side door used after the main building closes may be obvious to regular visitors but decisive for a newcomer. Ask someone unfamiliar with the venue to explain what they would do using the existing pages. Their uncertainty can reveal assumptions hidden in otherwise accurate copy.
Prioritise details that would materially change a person's plan. These may include booking requirements, entry arrangements, significant route conditions or the format of an activity. A long history of the building can be linked elsewhere. Practical information should not be buried beneath promotional introductions simply because those introductions are more familiar to the organisation.
Describe the actual arrival point
Give the official venue name, useful address information and the entrance used by the relevant audience. If the public entrance differs from a delivery address or a map pin, explain the difference plainly. Describe a recognisable feature without relying on a temporary poster or a business that may close. Keep directions connected to legitimate public routes and avoid inventing a shortcut from an unverified map.
Where arrival arrangements change by programme or time, state the condition. An evening workshop may use a different door from a daytime gallery visit. Link the programme's specific guidance instead of expecting the visitor to infer the variation. Staff should confirm the description through the same procedure used to brief hosts, so the webpage and the operating plan do not drift apart.
For transport information, distinguish stable orientation from changing service details. Link the relevant official journey-planning source for current routes, disruption, fares or assistance arrangements rather than copying an indefinite timetable into the page. If a route has not been physically checked, do not describe it as a verified accessible walking route merely because it appears short.
Separate building access, exhibition access and activity registration
A venue can be open while a particular workshop requires booking, or an exhibition can have different entry arrangements from a talk in the same building. Explain these layers explicitly. A general admission statement should not cause someone to assume that every activity is included, nor should a ticketed event listing imply that the whole building is closed to ordinary visitors.
Describe what a participant is expected to do. A workshop, drop-in session, facilitated discussion and seated presentation involve different commitments. State whether someone can arrive during the activity, leave early or observe without participating, where the venue has a confirmed answer. Avoid broad labels such as suitable for everyone when the actual format has conditions the visitor needs to consider.
Identify the authoritative booking route and where current programme changes are announced. If capacity or access depends on a particular session, direct the reader to that information. Do not imply guaranteed entry from free admission alone. A pre-visit page remains useful when it clarifies the process without making promises the venue cannot control.
Explain the parts of the internal journey that matter
Describe where visitors first obtain orientation and how the relevant spaces relate. Use the official room names shown on signs and confirmations. If a map is offered, make it a verified visitor map rather than an unedited architectural drawing. Include the practical information a newcomer needs to choose a route and avoid presenting private staff spaces as public destinations.
Be specific about access conditions rather than using one undifferentiated accessible label. The entrance, changes of level, internal surfaces, activity position and facilities can each raise different questions. Confirm the facts with responsible venue staff and appropriate expertise. Where a condition varies or information is incomplete, explain that limit and provide a focused enquiry route.
Give alternatives accurately. If a person can shorten a route or access the same content in another format, describe what is actually available and how to obtain it. Do not invent equivalence between a partial alternative and the complete activity. A visitor should be able to make an informed decision about the offered option rather than discovering its limits only after arrival.
Write facilities information as usable descriptions
List relevant facilities with their actual location and conditions of use. Toilets, water points, seating, belongings storage and refreshments may affect whether a visit is practical. Confirm which are available during the programme, particularly when only part of a larger building is open. A symbol on a general floor plan does not establish that the facility can be used during every event.
Describe limitations without turning the page into a defensive document. If there is no staffed cloakroom, say what belongings arrangement is offered. If seating cannot be reserved, avoid promising it. If a visitor has a specific facility requirement, provide the appropriate contact route for clarification rather than asking them to infer suitability from a small photograph.
Keep external facilities clearly separate from the venue's own provision. A nearby cafe or public service may have different hours and conditions. Link current official information where useful, but do not promise another operator's availability. This distinction matters when a reader is relying on the page to plan around a requirement rather than simply browsing ideas for a day out.
Describe the activity's likely conditions
Explain relevant sound, lighting, movement and participation features in concrete language. A film may contain audio, a workshop may involve a demonstration and a foyer may become busy at changeover. Verify those descriptions with the people delivering the programme. Avoid speculative assurances about how every visitor will feel or blanket claims that a setting is calm throughout its opening hours.
Where a quieter or lower-activity option is offered, explain its location and limits. A rest corner in a shared corridor differs from a separate room with controlled conditions. Museum sensory guides provide examples of how practical descriptions can help visitors plan, but another institution's list of features is not a ready-made statement about this building.
If access services or alternative materials require advance contact, explain the actual process and relevant timing without inventing a universal notice period. Give the reader a direct route to the responsible team. Do not describe a service as routinely available if it depends on arrangements that have not been confirmed for the event.
Use current photographs to explain, not decorate
A useful arrival photograph shows the actual entrance and enough surroundings to recognise it. An interior photograph can explain a reception position, room arrangement or rest area. Choose images for the practical question they answer. An atmospheric stock image of an unrelated gallery should not be presented as evidence of the venue's layout or facilities.
Keep the images current and describe meaningful changes in the accompanying text. A tightly cropped photograph can conceal a step, an adjacent doorway or a busy shared use that matters to planning. Do not deliberately remove an inconvenient condition from the visual account. Seek appropriate image permissions and avoid including identifiable visitors or personal information without a suitable basis.
Provide descriptive alternative text and written information alongside images. A photograph cannot replace an accessible explanation of a route, and a map should not be the sole carrier of essential directions. Keep the page usable on a small screen without requiring the reader to zoom into a dense floor plan to discover the entrance name.
Separate stable venue facts from programme-specific facts
Use one maintained record for relatively stable information such as the official address, room names and public contact routes. Keep programme-specific details close to the relevant event: entry format, activity expectations and temporary arrangements. Link the two layers clearly. Repeating the same building description across many event pages creates more places for an outdated sentence to survive.
Assign an owner to each category of information. Programme colleagues confirm what happens; building or visitor-services staff confirm how arrival and facilities operate. The editor makes the language understandable without inventing missing details. A page can be concise while preserving this division of responsibility in the internal record.
Use meaningful review triggers. A changed entrance, room move, new access arrangement or programme format should prompt an update. A routine date change without checking the facts gives readers little assurance. Record what was verified and by whom internally, so later maintenance can distinguish a current confirmation from text carried forward from an older launch.
A hypothetical venue with conflicting evening instructions
Imagine a hypothetical arts centre whose main visitor page describes daytime access through a courtyard. An evening drawing class uses a street entrance after the courtyard closes, but its booking confirmation links only to the general page. New participants arrive at the closed route and assume the class has been cancelled. The website's words are individually plausible but collectively describe the wrong visit.
The centre creates a clear programme-specific arrival note, using a current photograph and the same entrance wording supplied to hosts. The general page explains that some evening activities have different arrangements and links to their event guidance. Staff verify the practical description rather than asking the editor to infer the route from the building plan.
The correction is then checked through a realistic task: an unfamiliar reader uses the actual confirmation to identify where to arrive. This hypothetical example does not claim a measured improvement for a real centre. It illustrates why a pre-visit page must connect with the documents people already receive, rather than existing as a polished but isolated website section.
Make unresolved questions easy to ask precisely
A contact route should help someone ask the question that changes their plan. Suggest including the programme name, intended date and practical information they need, while making clear that a diagnosis or identity document is not required in an initial enquiry. Avoid turning a straightforward access question into a long registration exercise that the venue does not need.
Tell the team handling enquiries where to obtain authoritative answers. A receptionist may need to consult a programme lead or building colleague rather than infer suitability. Record an answer internally only to the extent necessary for the task, and avoid republishing personal correspondence as a general example without an appropriate basis. If the same factual question returns repeatedly, add the useful general answer to the public information rather than preserving dependence on individual email replies.
Test the page before calling it complete
Ask unfamiliar readers to answer practical questions using the page and its linked event. Which entrance will they use? What requires booking? Where will they ask a specific access question? Give them a realistic scenario without explaining the answers first. Record missing information, unclear terms and contradictions between channels rather than asking only whether the page feels welcoming.
Check keyboard navigation, headings, link descriptions and mobile layout through the website's appropriate accessibility process. Avoid relying on a PDF as the only practical information route if the same essential facts can be provided in accessible HTML. A downloadable guide can be useful as an additional format, but its version and maintenance need attention too.
Publish a correction route that readers can actually use. A concise enquiry form or contact address should make it possible to identify the relevant programme and question without demanding unnecessary personal detail. When a report reveals a recurring gap, update the page and the source record. The best pre-visit information grows more reliable through use rather than simply longer through accumulated disclaimers.
Questions specific to this guide
How long should a pre-visit page be?
Long enough to answer the practical questions that affect the intended visit, with clear headings and links to programme-specific details. Length is less important than findability and accuracy. Move background history elsewhere if it obscures arrival, entry or facilities information.
Can staff write it from memory?
Staff knowledge is an excellent starting point, but practical claims should be verified against the actual operating arrangement. Different colleagues may remember different entrances or programme formats. Use their knowledge to identify questions, then establish one maintained current answer.
Does every event need a separate access guide?
Not necessarily. A maintained venue page can hold stable facts while event pages explain meaningful differences. The reader needs a clear route between them. Where an activity changes the practical experience substantially, give those details explicitly rather than hiding them behind a general statement.
Further reading
Authoritative background on related planning and access questions. These resources provide context; they do not endorse this guide or replace the current requirements for your specific setting.



