Start Here: Your Transportation Snapshot

• Tell me briefly how your bus fleet and route program are structured today, including number of buses, number of routes, and who owns route-building
• How many students are enrolled in your district this year and how many different bell schedules do you operate? Options: Under 2,000 students, 2,000 to 10,000 students, 10,001 to 30,000 students, Over 30,000 students
• Walk me through your typical annual route rebuild, who runs it, and roughly how many staff-days it consumes Options: Less than 5 staff-days, 5 to 20 staff-days, 21 to 60 staff-days, More than 60 staff-days
• When a bell time, boundary, or enrollment change happens, what is the fastest window your team can turn a new routing plan into active routes? Options: Under 2 weeks, 2 to 4 weeks, 4 to 8 weeks, Longer than 8 weeks
• Describe the top three metrics your leadership looks at for transportation performance Options: On-time arrivals, Number of buses used, Hours per route, Fuel cost, Ridership by stop, Safety incidents, Other
• Which roles will we need to involve from your side during discovery and implementation? Options: Transportation director, Dispatchers/route builders, IT/SIS admin, Finance, Human resources/driver manager, School leadership

Where the Daily Schedule Breaks Down

• If a single recurring scheduling failure could be fixed tomorrow, which one would free the most time or money for your team?
• Which of these fail most often in your day to day: late buses, missed stops, cancelled runs, or unsafe pick up/drop patterns? Options: Late buses, Missed stops, Cancelled runs, Unsafe stop placement, Other
• Who is the first person to hear about a late bus or parent complaint, and how is that issue logged and tracked? Options: Dispatcher, Transportation director, School admin, Parent portal, Other
• When a route is understaffed because of driver shortage, what is your immediate contingency and how often does that contingency cause route cancellations? Options: Use subs from pool, Combine routes, Cancel runs, Run late with fewer stops, Other
• Describe the last time you had to cancel or significantly alter routes for a week or more, what triggered it and what broke next in operations
• Which operational change would convince you to stop using your current routing process immediately? Options: Sustained safety incidents, Unacceptable fuel or overtime costs, Chronic missed stops, Inability to integrate with SIS, Other

Safety, Compliance, and Parent Trust

• How do you currently detect and investigate a safety incident from a parent or staff report to final resolution, and what part of that workflow takes the longest
• Which compliance items do you track per driver today, and which of those are most likely to fall out of date? Options: CDL status, Drug and alcohol testing, Medical certifications, Background checks, Training hours, Other
• When parents ask where their child's bus is, what channels do they use and how satisfied are they with the response time? Options: Phone, Email, Parent app, School website, Social media, Other
• Tell me about a safety incident that changed your process or reporting, what you changed, and whether it fully addressed the issue
• If real-time vehicle tracking were 90 percent reliable tomorrow, what immediate outcomes would you expect to see in parent complaints, route efficiency, or driver accountability
• Which single unresolved safety or compliance gap would cause you to delay any new system rollout until it is resolved

The Operational Constraints That Hide Costs

• Where does the current system force you to accept higher cost or lower service because of a constraint you cannot change today
• How clean and current is your student address data in the SIS, and who owns ongoing updates Options: Very clean and owned by SIS admin, Mixed quality and shared ownership, Poor quality and no clear owner, Unknown
• Which vehicle or asset inventories are accurately tracked today: vehicle VIN, GPS device assignment, maintenance history, or fuel logs Options: VIN and basic inventory, VIN plus maintenance, Full GPS and maintenance tracking, None are accurate
• Who on your team would be the named owner for daily data feeds and who could approve access to SIS exports and GPS vendor portals
• Which physical or policy constraints would make a proposed optimization impossible, for example restricted stop locations, union rules, or vehicle hour limits Options: Restricted stops, Union rules, Vehicle hour limits, Contracted drivers, School safety policies, Other
• What single operational constraint, if unchanged, would force you to stick with your current way of working rather than moving to a new platform

Competitive Landscape and Alternatives You Are Weighing

• Which kinds of alternatives are you actively considering: incumbent vendors, building internally, or a hybrid approach Options: Incumbent vendor, New external vendor, Internal build, Hybrid/integrated approach, Unsure
• Name the categories of current systems in your stack that any new solution must replace or integrate with, such as your SIS, GPS provider, or payroll/HR system Options: Student information system, Existing GPS vendor, Routing software, HR/payroll, Parent communication tool, Other
• What would have to be demonstrably true about your current system for you to keep it instead of switching to a new vendor Options: Lower total cost, No additional integration work, Meets safety reporting needs, Better parent communications, Other
• Has anyone internally proposed building the routing or tracking capability in house, and if so, who would lead that effort and what timeline did they propose Options: Yes, IT proposed it, Yes, transportation staff proposed it, No one has proposed it, Unsure
• If a pilot proves a measurable reduction in buses or a clear improvement in on-time performance, what internal approval would you need to move to a procurement decision that week

Integration, Data, and Technical Readiness

• How many days of dedicated IT or SIS admin time can you commit to initial integrations and troubleshooting during implementation Options: Under 5 days, 5 to 15 days, 16 to 30 days, More than 30 days
• Which integration endpoints must be supported by any solution: SIS student records, third-party GPS provider API, HR/driver records, or rostering feeds Options: SIS student records, GPS provider API, HR/driver records, Rostering feeds, Clever/other SSO
• Describe the current state of your SIS export process, is it automated, manual, nightly, or ad hoc, and who can enable API access if needed Options: Automated nightly export, Manual scheduled export, Ad hoc manual export, API access available
• Which of these data quality issues exist today in your student records: duplicate addresses, outdated guardians, missing grade/route assignments, or inconsistent stop fields Options: Duplicate addresses, Outdated guardians, Missing grade or route fields, Inconsistent stop data, None of the above
• Who must sign off on data sharing and security agreements, and how long does your legal or procurement process usually take Options: Transportation director, IT security, Legal, Procurement, School board
• Which technical blocker would stop integration work before it starts, for example no API access, vendor contract restrictions, or lacking SFTP credentials Options: No API access, Vendor contract limits, No SFTP credentials, Internal policy restrictions, Other

Decision Criteria, Pilot Success, and Acceptance

• If a pilot delivers the expected savings or service improvements, what three things must be true for you to recommend a full rollout
• Which acceptance metrics will you insist on during a pilot: percent reduction in buses, on-time pickup percent, parent satisfaction score, or driver overtime hours Options: Reduction in buses, On-time pickup percent, Parent satisfaction score, Driver overtime hours, Safety incidents
• How quickly could your district sign a contract once a pilot meets acceptance criteria Options: Immediately, Within 2 weeks, Within a month, Longer than a month
• Who is the final decision maker for transportation vendor selection and what concerns would they raise that could block approval
• What single unanswered question, if left unresolved, would kill the deal even if the pilot metrics look strong

Next Steps, Owners, and Timing

• Who on your team will act as the day-to-day owner for the engagement and who will be the executive sponsor
• Which launch window does your district prefer for a pilot or initial rollout: summer routing rebuild, fall semester start, mid-year, or other Options: Summer routing rebuild, Fall semester start, Mid-year, Other
• What constraints or blackout dates would prevent field work such as GPS installs or driver training during the next six months Options: School start dates, State testing windows, Holidays, Union-negotiated dates, None
• How would you like us to demonstrate value first, through a route optimization pilot, GPS reliability test, or a parent communication trial Options: Route optimization pilot, GPS reliability test, Parent communication pilot, Combined pilot
• Finally, when would you be available to review a proposed pilot scope and timeline with named owners present Options: This week, Next week, In two to four weeks, Later than four weeks

• Solution Experience Session

• Confirm the current state and its cost to your team
• You confirm the routing workflow shown eliminates the manual rework and meaningfully reduces route-building time and route count.
• Provide a representative SIS export (enrollment and addresses) and last year's route file for a proof optimization run.
• You confirm that real-time tracking plus parent notifications address the complaint scenarios and shorten incident response time.
• Proof: Route optimization on your scenario
• Seller to run the route optimization on the provided dataset and deliver a before/after route count, estimated staff-hours saved, and projected fleet impact before the follow-up session.
• Identify three high-priority routes or incidents to use as live scenarios in the pilot or next session.
• You agree that the driver management and substitute workflow prevents cancellations and meets your compliance needs.
• Proof: Real-time tracking and parent notifications
• Proof: Driver management and substitute workflows
• You accept the proposed integration approach and list the remaining data items needed to validate nightly SIS syncs.
• Define the acceptance criteria for on-time performance and incident response that will be used to evaluate pilot success.
• Proof: SIS and data integration validation
• Validate that this maps to what you said you needed

• Solution Experience Session
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Optimize annual route network and stop assignments
• Migrate route and stop data from prior provider
• Integrate student enrollment and address data (SIS)
• Install and configure GPS tracking units
• Activate real-time GPS tracking and geofencing
• Implement driver assignment and substitute dispatch
• Digitize and manage driver compliance records
• Provision turn-by-turn navigation for drivers
• Deploy parent mobile app and arrival notifications
• Simulate routes for bell time and boundary changes
• Implement fleet maintenance scheduling workflows
• Deliver route efficiency, on-time, and ridership reporting
• Train drivers and dispatchers on platform use

Optimize annual route network and stop assignments

• How many active route IDs do you rebuild each year (approximate)? Options: Less than 50, 50-200, 200-500, 500-1,000, More than 1,000
• Which stop assignment method do you currently use for student pick-ups (reference your stop ID and zone rules)? Options: Boundary-based (walk-to-zone stops), Stop-based (fixed stops per student), Door-to-door for special needs, Hybrid
• Provide your target maximum student ride-time threshold per student in minutes (for example 45 or 60)
• Are there Individualized Education Program (IEP) or special education cohorts that require dedicated route segments or aides? If yes, list counts and mobility constraints tied to stop IDs. Options: Yes, No
• Describe the naming and numbering convention used for your current route IDs and stop IDs (examples: Route_101_AM, STOP_5A).
• What measurable acceptance criteria will confirm the optimized network is ready for driver testing (examples: average ride time ≤ X minutes, reduction of bus count by Y%, or max route miles ≤ Z)?

Migrate route and stop data from prior provider

• Do you have a current export of routes, stops, and stop sequences from your prior provider to ingest (attach or indicate file availability)? Options: Export available for download, Export available but needs preparation, No export available
• Which file formats are available for migration of route and stop data (check all that apply)? Options: CSV (stops/routes), GeoJSON / KML, Proprietary route file, API endpoint, Other
• How many route records and how many stop records are included in the export (approximate counts)?
• Attach or describe any custom stop attributes we must preserve during migration (examples: bell-tier, pickup-window, special-instruction text tied to stop IDs).
• What migration completeness threshold will you accept for route/stop reconciliation (example: 98% of stops migrated with matching coordinates and stop IDs)? Options: 95%, 97%, 98%, 99% or higher, Custom
• Who on your team will own migration validation and provide signed acceptance of migrated route files (role/title and email contact)?

Integrate student enrollment and address data (SIS)

• Which student information system (SIS) do you use and which release/version if known (provide vendor name and export method)?
• Do you provide bulk nightly exports, API access, or manual CSV extracts for student enrollment and address data (select primary method)? Options: Nightly CSV export, SIS API, Weekly/manual CSV extract, Batch SFTP delivery
• List the SIS fields required to map to the platform (examples: student ID, grade, home address, primary guardian phone, special transport flag, school assignment, zone code).
• Are address standardization rules required (for example district uses USPS-standardized addresses or address validation against parcel data)? Options: Yes - USPS standardization, Yes - parcel/geo reference, No
• How frequently do student address changes occur during peak months (August-September) and what is the expected daily update volume? Options: Less than 50/day, 50-200/day, 200-500/day, More than 500/day
• Who is the SIS administrator who will provide API credentials or scheduled export files and approve field mappings (role/title)?

Install and configure GPS tracking units

• How many vehicles require GPS device installation and provide current vehicle ID/plate or fleet ID list?
• Which GPS device models or telematics providers are already installed, if any, and do you have device serial numbers or IMEIs for each vehicle? Options: No devices installed, Devices installed with serial list available, Mixed devices — partial inventory
• Who will coordinate physical access for installers to the vehicles and supply required vehicle contact person(s) and windows (examples: maintenance garage hours, vehicle IDs for same-day installs)?
• Provide any fleet electrical constraints or vehicle-specific mounting notes we must plan for (examples: wheelchair lift vehicles, electric buses, auxiliary batteries).
• What device provisioning SLA and acceptance evidence do you require for completed installs (examples: device online, accurate GPS fix within X meters, IMEI logged to vehicle ID)?
• Do you require installation records and a signed installation checklist per vehicle that includes device serial, vehicle ID, installer name, and test GPS ping time? Options: Yes, No

Activate real-time GPS tracking and geofencing

• Which geofence types do you need configured at go-live (stop-level arrival/departure, school yard polygons, depot boundaries)? Options: Stop-level geofences, School polygons, Depot/yard geofences, Route segment geofences
• What acceptable latency do you require for location updates in the parent app and dispatcher view (for example under 30 seconds)? Options: <15 seconds, <30 seconds, <60 seconds, Real-time not required
• Describe any stop-level behavior rules tied to geofences (examples: require dwell time ≥ 30s to mark stop served, ignore brief pass-by within X meters).
• Are there vehicle classes that must be excluded from geofence events (examples: maintenance-only vehicles, spare buses)? Options: Yes - list classes, No
• Who will approve geofence polygon edits and emergency unlocks during the pilot (role/title)?
• Do you require historical location retention for investigations and audits and what retention period is needed (examples: 90 days, 1 year)? Options: 90 days, 180 days, 1 year, Custom

Implement driver assignment and substitute dispatch

• How many active drivers and substitute drivers are in your roster and how are they identified (employee ID or badge number)?
• Which shift patterns or bell-time tiers must the driver assignment engine respect (examples: AM only, PM only, split shifts)? Options: AM only, PM only, Split shifts, Flexible
• Describe your substitute dispatch workflow (how are absences reported, lead time for replacement, use of pool drivers).
• Do you require driver qualifications or endorsements to be enforced in assignments (examples: passenger endorsement, school bus endorsement, required vehicle training)? Options: Yes - enforce by endorsement, No - manual check
• Which notifications should be triggered to drivers when assigned or re-assigned (examples: SMS, in-app push, email) and backup contact method? Options: In-app push, SMS, Email, Phone call
• Who will act as dispatcher owner for day-of substitute decisions and provide 24/7 escalation contact during first two weeks of operations (role/title)?

Digitize and manage driver compliance records

• Which compliance document types must be tracked per driver (examples: CDL, medical certificate, annual background check, drug test records)? Options: CDL, Medical Certificate (DOT physical), Background check, Drug/alcohol test, Training certificates
• What are the expiration rules you require for compliance reminders (examples: 30 days before CDL expiration, 7 days before annual training)?
• Do you require electronic signature capture and storage for driver attestations and annual license verification? Options: Yes, No
• Provide current source and format for driver records (examples: HR CSV, paper files, state DOT portal export).
• Are there district policies or regulatory regimes we must reflect in compliance workflows (examples: state DOT audit checklist items, county hiring rules)? Options: Yes - list policies, No
• Who is the compliance owner who will validate digitized records and receive automated expiry alerts (role/title)?

Provision turn-by-turn navigation for drivers

• Which navigation preferences must be enforced for student safety (examples: avoid highways, prefer right turns, school yard ingress rules)?
• Do you require offline navigation capability on driver devices and if so, which routes or regions need offline tiles? Options: Yes - entire fleet, Yes - specific regions, No
• List vehicle-specific constraints to include in navigation (examples: bus length, height restrictions, weight limits tied to vehicle class).
• Which driver device types will receive turn-by-turn instructions (examples: district tablets, driver smartphones, integrated in-vehicle displays)? Options: District tablets, Driver smartphones, In-vehicle displays, Mixed
• How will drivers confirm route receipt and acceptance (examples: in-app acknowledgement, dispatcher sign-off)? Options: In-app acknowledgement, Dispatcher confirmation, Paper manifest signed
• Who will own the driver navigation rollout and training schedule (role/title)?

Deploy parent mobile app and arrival notifications

• What parent communication channels do you require at go-live (examples: mobile app push, SMS, email) and which should be primary? Options: Mobile app push, SMS, Email, Web notifications
• Do you require user provisioning integration with SIS for parent contact matching or will parent accounts be created via invitation links? Options: SIS-synced parent contacts, Invitation links, Hybrid
• List the notification types to enable at launch (examples: bus on route, arrival imminent, stop missed, route change) and required default thresholds (minutes before arrival).
• Are there district privacy or opt-in rules for parent notifications (examples: FERPA considerations, required consent forms)? Options: Yes - consent required, No
• How will you measure parent adoption during pilot (examples: X% of households with app installed, daily active users)?
• Who will manage parent communications and respond to parent escalations during the first 30 days (role/title)?

Simulate routes for bell time and boundary changes

• Which scenario types must be simulated before finalizing routes (examples: single-day bell time shift, district-wide boundary change, new school opening)? Options: Bell time shifts, Boundary changes, New school/school closure, Emergency re-routing
• Provide typical bell time windows and acceptable pickup/drop offset tolerances used when validating simulations (examples: 15-minute pickup window).
• What KPIs must each simulation report include to approve a scenario (examples: buses required, average ride time, capacity utilization, number of students over threshold)?
• Do you require parent notification templates tied to scenario outcomes (examples: new stop assigned, pickup time changed)? Options: Yes, No
• Who will approve scenario outputs and confirm bell time or boundary changes for publication (role/title)?
• How many what-if scenarios do you want produced as part of the configuration phase (examples: baseline plus 2 alternate bell-time plans)? Options: Baseline only, Baseline + 1 alternate, Baseline + 2 alternates, Custom

• Master Services Agreement (MSA)
• Order Form / Subscription Agreement
• Statement of Work (SOW)
• Service Level Agreement (SLA)
• Data Processing Agreement (DPA)
• FERPA & Student Records Addendum (applies if you are a K-12 or public education entity)
• Public Sector Procurement & Security Addendum (applies if you are a public-sector buyer)
• Hardware Purchase & Installation Agreement
• Integration & API Access Addendum
• Mutual Go/No-Go Criteria and Acceptance Plan
• Change Order Agreement
• Data Return & Decommissioning Addendum

• Go-live Health Check (Weeks 1-4)
• First Measurement Review (Weeks 4-10)
• Acceptance Gate Review (Around Day 90)
• Monthly Operations Review (Ongoing, first 6 months)
• Quarterly Performance Review (Ongoing, quarterly)

• Publish a prioritized enhancement list with expected delivery windows and criteria for operational vs product items.
• Produce a documented acceptance decision against the numeric targets recorded in Solution Scope with outcomes captured for each criterion.
• Confirm the incumbent system is either decommissioned or formally retained-read-only with data archived or migrated-complete.
• Document any remediation actions, their verification steps, and the final resolution timeline.
• Publish the formal acceptance record that lists pass/fail per Solution Scope criterion and attaches the supporting data extracts.
• Execute the incumbent wind-down checklist including contract status, data archival confirmation, and user transition verification.
• Create a remediation tracker for any failed criteria with target completion dates and verification steps.
• Operational metrics dashboard review
• Maintain or improve on-time arrival rate and reduce route cancellations due to driver shortages month-over-month.
• Resolve high-severity safety incidents with documented corrective actions and interim mitigations.
• Keep the open issue backlog to a manageable size with clear resolution timelines for all priority tickets.
• Update the incident response log with corrective actions and verify closures against evidence.
• Re-confirm success criteria and owners
• Deliver a one-page monthly summary of on-time rate and route cancellation trends for distribution to district leadership.
• Quarterly KPI summary
• Confirm whether on-time arrival rate, safety incidents per 100,000 student-trips, and buses required versus baseline meet or are improving toward targets.
• Agree on 2-3 systemic improvements to address recurring issues and set timelines for implementation.
• Ensure the enhancement backlog and operational roadmap are aligned with the district's seasonal planning for route changes and bell-time adjustments.
• Deliver a quarter-end performance packet including raw metric extracts, trend charts, and incident detail for audit.
• Create a cross-functional remediation plan for any systemic risk areas with milestones and verification methods.
• Schedule required SIS sync and boundary-change simulation runs ahead of the next route-building season.
• Confirm the deployment is functionally complete and all critical integrations are producing expected data.
• Capture and prioritize any deployment blockers with target resolution dates.
• Validate that user onboarding shows no major adoption drop-offs requiring escalation.
• Publish a stabilization checklist showing live integrations, data health checks, and open incidents for async tracking.
• Run a data reconciliation between SIS exports and imported enrollment records and report discrepancies.
• Schedule targeted driver training sessions for any groups showing low route-tracking usage.
• Present first-window metrics
• Determine whether on-time arrival rate and average daily ridership are trending toward the numeric targets recorded in Solution Scope.
• Identify the root causes for any gaps and document concrete remediation tasks with target completion dates.
• Validate readiness status for the acceptance gate or list the remaining outstanding items that must be closed before day 90.
• Produce a root-cause report for the top three underperforming routes including telemetry snapshots and recommended fixes.
• Implement GPS signal checks and map any coverage blackspots with a plan for remediation or workarounds.
• Publish an updated timeline to the acceptance gate showing which Solution Scope criteria will be met and which have remediation plans.
• Restate acceptance criteria and numeric targets
• Safety incident review
• Present outcome data against each criterion
• Drill into outliers and root causes
• Deployment and migration validation
• Trend analysis and cost/efficiency impact
• Open issues and hypercare ticket burn-down
• Early adoption and usage signals
• Document pass/fail and formal acceptance decision
• Operational blockers and data-quality issues
• Persistent issues and systemic risks
• Enhancement and backlog prioritization
• Enhancement request prioritization and next-quarter plan
• Agree corrective actions and timeline to acceptance
• Incumbent system wind-down confirmation
• Open blockers and defect triage
• Agree remediation items and close-out timeline
• Confirm acceptance gate readiness checklist
• Short action review and next steps
• Quarterly action register and verification plan
• Agree immediate remediation actions