RFPs
District request context
NovaPath can discuss route scope, procurement timing, service windows, support categories, and documentation needs through the request path.
Procurement and partnerships
Procurement, RFP, and partner transportation conversations.
Use this path for district service scope, RFP timing, partner capacity, and controlled material requests that need responsible follow-up.
Public intake guardrail
Public requests should include adult contact and service scope only. Do not include protected student information.
Engagement
Start with scope, timeline, and document needs.
The public path collects enough information for follow-up without asking for protected student records or controlled procurement details.
Partners
Program transportation
Schools, agencies, and program partners can start with adult contacts, service area, movement pattern, and service expectations.
Documents
Gated compliance materials
Detailed insurance, operating, and readiness materials belong in the compliance packet path instead of on a public page.
Request path
What to include in the first request.
Requests can move from public intake into document review, scoping calls, and procurement follow-up after requester and context are verified.
Organization and procurement contact
Route category or partner program type
Service window and review timeline
Requested documentation categories
Adult communication and escalation requirements
Billing, closeout, or reporting workflow questions
Bring NovaPath into the procurement conversation.
Share the service scope, decision timeline, and documentation needs so NovaPath can route the conversation responsibly.