A city with a timetable
A university campus is a small city whose population turns over every autumn and whose peak navigation demand arrives in scheduled bursts: open days, enrollment week, the first Monday of term, exam season. Generic map apps cover the outdoor quads and fail exactly where the need starts, at the building door, because room E2.14 does not exist on a city map. Campus navigation is the indoor-outdoor handoff problem at institutional scale.
What should university campus navigation cover?
Four layers: outdoor routing across the campus (which generic maps handle), building entrances matched to the visitor's destination (which they do not; the right entrance for a lecture theatre is rarely the main one), indoor routing to rooms, labs, and offices, and event overlays, where the same building means different destinations in open-day mode versus exam mode. The binding constraint is the room-level directory: navigation is only as good as the mapping between "Advanced Thermodynamics, Tue 9:00" and a door on a floor plan.
The calendar is the requirements document
Campus navigation earns its keep on specific dates. Open days: thousands of first-time visitors and their families, moving between talks on a schedule, with the university's conversion funnel (literally: enrollment) degraded by every family that gives up finding the chemistry demo. First week: the entire intake navigating simultaneously, when late-to-class is the norm the institution wants to break early. Exam weeks: unfamiliar rooms assigned across the campus, high stress, zero tolerance for error. A system pitched on the average Tuesday undersells itself; size it on these peaks, with event-mode routing overlays as the test case.
Delivery: web first, kiosks at the seams
Students live on their phones, but one-time visitors (applicants, families, conference guests) will not install anything: web-based routes linked from event pages and confirmation emails carry the peak loads. Kiosks belong at the seams (transit stops, parking structures, quad junctions), placed where measured flow actually passes, per kiosk placement by flow data, and the kiosk vs static map trade-off leans kiosk precisely because campus destinations change by semester.
Accessibility is not an edge case here
Universities carry legal and moral accessibility obligations, and campuses built across a century are full of step-and-stair shortcuts that exclude. Step-free routing as a first-class mode, with accessible route data maintained as part of the map, is the difference between compliance on paper and a student who gets to class.
Where Ariadne fits
Ariadne's platform turns campus floor plans into live guidance across app, web, and kiosks, on privacy-first positioning, with the measurement layer underneath showing where journeys stall, which buildings absorb the open-day crush, and whether the new signage actually changed anything. The full platform picture is in the indoor navigation pillar, and campuses appear alongside airports and hospitals in its deployment surface.
---
