Campus applications
Campus Outdoor LCD Wayfinding: Plan the Visitor Journey Before the Screen
A visitor arrives at a campus entrance and needs to find reception. Before choosing a display format, decide what they need to know at that point and how the next part of the journey will be confirmed. Use the screen as one information point in the wider route.
This planning guide applies to campus and business-park wayfinding discussions. It is not a completed project example or a promise of navigation, mapping or interactive features in a JIAMIAI LCD product. Confirm the actual display and content configuration with your supplier.
Choose a few journeys to test
List the visitors the information point should serve: first-time guests, delivery personnel or people attending a scheduled event, for example. For each group, identify the arrival point, likely destination and decision they need to make.
Start with specific journeys instead of placing every building name on the first screen. Ask the site team which destinations generate questions and which names visitors already recognize. Record the intended task, such as finding the reception entrance, rather than assuming a map alone answers it.
Locate information at the decision point
Mark candidate screen positions and visitor approaches on a site plan. Check what people can see before they must choose a path and whether they have a suitable place to pause and read.
- Can a visitor identify the display from the normal arrival route?
- Does the message appear before the relevant junction or entrance?
- Could nearby signs, planting or parked vehicles obscure it?
- What confirms the route after the visitor leaves the screen?
Use the site survey checklist to document the location. Compare freestanding and wall-mounted formats against the same visitor journey, including service access and site responsibilities.
Keep destination names consistent
Create an approved list of destination names and check it against building signs, visitor instructions and reception terminology. Record any building code, public name or translated name that must appear together.
Assign a site owner to approve changes. A renamed department or temporary reception move should trigger a review of the related messages and signs. Keep abbreviations only where the site team has confirmed visitors will understand them.
If several languages are required, have the responsible team review the translations and test the actual characters on the proposed system. Include the longest expected names in the content sample.
Verify maps and directions on site
Ask the responsible site team to approve any map, location marker, arrow and route instruction. Review the content from the installed screen's viewing position. Do not copy an arrow from another screen without checking what it means at this location.
Walk the intended route with an approved draft and record unclear junctions, missing confirmations or changes to entrances. Include relevant step-free routes in the site's review, and have the appropriate specialists confirm any accessibility requirements. This checklist is not an accessibility compliance assessment.
Keep everyday directions distinct from regulated or emergency information. Any such requirements should be defined by the responsible site professionals rather than inferred from a general wayfinding layout.
Plan temporary notices and fallback content
Events, access restrictions and building works need a content owner and a removal date. For each temporary notice, record the affected locations, approving person, start and end time, time zone and replacement message.
Specify what should remain visible if an update cannot be delivered. Confirm the supported behavior for the actual player and software rather than assuming live maps or remote updates are included. Use the content workflow and offline planning guide to organize those questions.
Test the whole journey before sign-off
Ask a reviewer who has not prepared the layout to complete each agreed visitor task. Note where they look, which destination they select and which instruction needs clarification. Review the display under the relevant site conditions using the readability test checklist.
Record the content version, observation point, conditions, outcome and required revision. Retest the affected journey after a change. Keep untested routes and unresolved approvals visible in the handover record.