Reach Student Life Management Demo

Keystone Academy

Transit Tracking

A purpose-built dashboard for tracking students moving between a base location and campus destinations, with transit timing, late detection and SISO actions. Built in the Reach Design System. Start with the live board.

The product

Live Board The main screen. Home base with floor tiles, in-transit panels split by location, and destination cards with capacity and late-to-return counts. Search or scan a student, run bulk sign-outs and arrivals, review recent activity. Open the board → System Configuration: In Transit Four settings that define the board — 5900 Home Base (location plus a Reach Lookup sub-element), 5910 To Transit, 5911 From Transit, 5912 Destination Locations. Open config →

Governance pages

Design Spec & Logic Read-only record of every rule and why it exists, in numbered sections with a jump-to contents list. Ends with the open questions still unresolved. Read the spec → Lifecycle Board What is built and what is not, as an org chart across four stages — or as a chronological timeline. Filter by status, open any item for a copyable build prompt. Open the board → Ideas Board A status-free holding pen for unformed thoughts, before anything becomes tracked work. Promote an idea to the Lifecycle Board when it is ready. Open the board →

Documents

User Guide Seven sections for boarding staff, with annotated diagrams of the board and its panels. A4, prints cleanly, with right-click page breaks. Read the guide → Board Status Report A printable point-in-time record — summary counters, overdue callout, floor and location tables, and the day's movements. Open the report → Presentation Deck Fourteen slides covering the arrival model, the thresholds, build status and open questions. Arrow keys to navigate. Open the deck →

Running this demo

Serve the folder over HTTP rather than opening the files directly — from the folder, run python3 -m http.server and visit localhost:8000. Board data and your duty status, board filters and page breaks are stored in the browser, so they persist between visits. Two files load from the internet — Font Awesome icons and Google Fonts — so the demo needs a connection to look right.