Transportation & safety
Driver fitness check-in, pre-trip and post-trip inspections, defects, routes, stops, trips, ridership and live safety alerts.
ConfigurableEnterprise district infrastructure
Transportation, maintenance, custodial, grounds and student safety in one district system.
Bell & Key runs the daily work behind the school day: driver check-in and bus inspections, defects and work requests, routes and trips, custodial rounds and supplies, grounds schedules, conduct records and the reporting district leaders need to see all of it.
District Overview
Demonstration environment · Sample data
The operating gap
Inspections on paper. Defects by text message. Work requests by email. Custodial rounds on a clipboard. Conduct notices in a folder. Leadership finds out later.
Before Bell & Key
Bell & Key
One operational layer across the district.
The district support ecosystem
Every morning a district moves buses, drivers, crews, buildings, grounds and students. Bell & Key is the layer that records, routes and reports that work.
District support infrastructure
What is in the system today
These are working areas of Bell & Key, configured per district. Districts define schools, departments, roles, checklists and who approves what.
Your departments. Your workflows. Your district. One system.
Pre-Trip & Post-Trip Inspections
Driver Fitness Check-In
Bus Fleet Files
Defect & Repair Queue
Work Requests
Routes & Stops
Field Trips
Ridership Records
Meal Delivery Stops
Student Conduct Notices
Custodial Room Rounds
Supply Inventory & Par Levels
Grounds Schedules & Assets
Safety Alerts
Family Notifications
Executive command center
Move from district to school to department to the individual inspection, repair or round without rebuilding the report at every level.
District Overview
Demonstration environment · Sample data
Platform capabilities
Each department works in its own console with the checks, queues and records it actually uses. Leadership sees all of it in one place.
Driver fitness check-in, pre-trip and post-trip inspections, defects, routes, stops, trips, ridership and live safety alerts.
ConfigurableBus files, repair queue, work requests by department, compliance records and controlled return-to-service approval.
ConfigurableRoom checklists, QR room scans, daily rounds, inspection scoring, assigned work and supply ledger with par levels.
ConfigurableAsset registry, recurring schedules, crew assignments, request intake and completion records by campus.
ConfigurableBus conduct notices, driver and administrator signatures, review queue and printable dual-signed records.
ConfigurableGuardian access to notices, trip visibility and a moderated channel for questions where the district enables it.
ConfigurableSchools, departments, staff accounts with Employee ID sign-in, roles, permissions, credentials and district-scoped reporting.
ConfigurableOne system, distinct views
Each role receives the level of access, context and accountability appropriate to its work.
Role view
District-wide operational status across every support department.
Operating model
Without Bell & Key
With Bell & Key
Enterprise implementation
Bell & Key is configured with the district—not handed over as a fixed template.
Programs, workflows and objectives.
The district operating model.
Roles, forms and reporting.
Data, training and launch.
By program, school or district.
Train and monitor use.
Refine as needs evolve.
Board-ready reporting
Turn daily inspections, repairs, rounds and alerts into concise views of fleet readiness, service coverage and response time.
Board of Education briefing
Demonstration report · Sample data only
Campus reporting rate
Report includes
Fleet readiness
Work request throughput
Campus service coverage
From operational activity to board-ready reporting.
Records and accountability
Bell & Key timestamps the work as it happens: who inspected the bus, what was found, who was notified, what was repaired, who approved the return to service. Districts keep that history for operational review; Bell & Key does not certify regulatory compliance.
Activity record / demonstration
Architecture
Integration requirements are assessed during implementation. No vendor connection is represented as available unless verified for the district.
Security & data governance
Role-based access, permissions, data segmentation, auditability and governance are treated as operating requirements. Verified security documentation is provided during district evaluation.
Enterprise scoping
Solutions are scoped around district size, programs, implementation requirements and configuration.
District consultation
One place to coordinate programs, people, workflows, resources and reporting—without adding another disconnected solution.