Handoffs
Adult-to-adult coordination
Requests should identify adult contacts, service windows, pickup and dropoff expectations, and non-protected support notes.
Special education transportation
Specialized student transportation with consistent handoffs and support.
NovaPath supports transportation that needs aide coordination, accessibility planning, clear communication, and route records without exposing protected student information on public channels.
Public intake guardrail
Public requests should include adult contact and service scope only. Do not include protected student information.
Operating posture
Built for routes where details matter.
The public request path collects service scope and adult contacts. Sensitive student-specific material belongs in authorized district workflows after intake.
Routes
Documentation around the route
Route records, assignment checks, exceptions, and closeout notes keep support needs tied to the service record.
Privacy
Sensitive details stay gated
Public pages and public forms do not collect student names, IEP documents, diagnoses, medical details, or protected student information.
Coordination
What NovaPath can discuss publicly.
Districts and schools can share non-protected service context first. That lets NovaPath understand route shape before any controlled documentation exchange.
Service window and frequency
Pickup and dropoff area, not student identity
Adult contact and escalation path
Vehicle or support category requested
Procurement timeline and required documentation types
Communication expectations for route start, changes, and closeout
Begin with service scope only.
Use the request form for adult contact details, route scope, timeline, and support category. Keep protected student information out of public intake.