Operational fit
Can your team model its vehicles, staff, routes, stops, students, morning runs, and afternoon returns without workarounds?
← BusMap overview Product & user guide
From first route setup to a dependable daily trip.
Use this guide to evaluate BusMap, prepare a controlled pilot, or understand the everyday workflow for fleet administrators, school teams, drivers, conductors, and families.
For schools and fleet operators
Evaluate the operating loop, not just a moving dot.
A useful trial should prove that setup, authorization, live movement, student journey records, family access, exceptions, and review all stay connected on your real routes.
Field reliability
Do the selected phones, permissions, connectivity, and battery policies keep location current during a complete real journey?
Access boundaries
Do administrators see the fleet while drivers and families see only the routes and actions assigned to them?
Operational response
Can the team identify stale movement, route deviation, boarding state, and other exceptions early enough to act?
Suggested first pilot
One school, a small route set, named owners, and real devices.
- Choose representative short and long routes.
- Name a school owner, fleet owner, and driver-device owner.
- Agree what “location current” and “on time” mean operationally.
- Run dry journeys before exposing live information to families.
- Record defects, support questions, and go/no-go criteria.
Administrator setup
Build the transport model in dependency order.
Later choices depend on earlier records. Following this sequence prevents empty dropdowns, invalid assignments, and trips with missing context.
- 1
Confirm the organization
Review the organization name, address, phone, and email. The form checks sensible length and format limits before saving.
- 2
Add vehicles and driver records
Use the dashboard quick actions or management pages. Enter real operational identifiers, realistic seating capacity, a valid contact number, and license details where applicable.
- 3
Create routes and stops
Name the route, choose pickup, drop, or both, assign its vehicle and staff, then add stops in travel order. Road-aware geometry follows streets where routing data is available.
- 4
Add students against valid route stops
Select a route first; the Stop field then offers only stops belonging to that route. This keeps the student’s pickup or drop point internally consistent.
- 5
Verify account assignments
Sign in as the intended driver and family test users. Confirm the driver sees assigned routes and a family sees only the child’s route before any live trip.
- 6
Run a controlled dry trip
Exercise location permissions, trip start, route filtering, boarding and alighting, alerts, trip completion, and report output with synthetic students before operational use.
Everyday use by role
Each person gets the view needed for their responsibility.
Set up, monitor, and review
- Use Dashboard for active trip, vehicle, driver, and route context.
- Use Quick Actions to create vehicles and drivers.
- Create or edit routes, stops, assignments, and students.
- Filter Live Map to investigate one route without unrelated layers.
- Review alerts, tracking links, and saved reports; export CSV when needed.
Operate assigned journeys
- Open Routes or Start New Trip and select an assigned route.
- Confirm the assigned vehicle and route before starting.
- Grant the requested location permission and keep device location enabled.
- Record manual boarding or alighting only for students on the active route.
- Pause when operations require it and complete the trip at the real endpoint.
Follow the relevant journey
- Use the authenticated family view for a child’s assigned route.
- Check whether a trip is scheduled, active, paused, or complete.
- Treat stale or unavailable location as unavailable—not as a simulated bus.
- Use a school-issued public link only until its expiry; do not repost it.
- Contact the school’s transport desk for operational decisions or emergencies.
Daily trip flow
Prepare, authorize, track, account, complete.
The live map is the visible part of a larger controlled sequence. A trip should not begin until assignment and device readiness are confirmed.
Confirm route, vehicle, driver, device power, data connection, and location permission.
Select the assigned route and vehicle. BusMap checks the assignment before authorizing the trip.
Publish current location, record boarding state, and watch for stale GPS, speed, or deviation exceptions.
Resolve student state, end the trip, confirm location stops updating, and review alerts or notes.
Use reports and history to review what happened; do not fill unavailable telemetry with assumed values.
Common questions
Check assignment and freshness before recreating data.
A driver sees no routes or cannot start a trip.
Confirm the driver record is active, the route is assigned to that driver, the driver account uses the verified matching phone, and the assigned vehicle is correct. Sign out and back in after an administrator changes access.
The map still shows every route after a filter is selected.
Confirm the selected filter is not “All routes,” then hard-refresh the browser. If an older installed web app or service worker is present, clear site data once so the current application bundle loads.
A route card has no stop count or route details fail to open.
Verify the route has active stops and the account can access that route. On Chromium, clear an older cached web bundle if Firefox or another fresh browser shows newer behavior.
A bus is missing from the Live Map.
Check that the trip is active, the driver device is uploading location, the correct route filter is selected, and the location timestamp is current. BusMap should show an unavailable or stale state rather than inventing a position.
A form refuses a value.
Use realistic lengths and formats. Route and stop selections must reference existing records; seating capacity and phone values must be sensible; related records must belong to the selected organization or route.
When should an issue be escalated immediately?
Escalate wrong-organization data, a family seeing an unrelated route, an unauthorized driver action, exposed child information, or a location attached to the wrong trip. Preserve privacy-safe timestamps and identifiers—never share tokens or raw student data.
A truthful product boundary
The core platform works; production confidence must be earned in context.
BusMap is not presented as a self-serve public launch. A paid rollout should follow evidence from the target school, its devices, hosting, integration, and operating team.
- Role-aware fleet, route, trip, student, and family workflows
- Management and live tracking services with tenant boundaries
- Manual attendance, alerts, reports, exports, and expiring links
- Road routing and route-filtered maps
- EduCore connection and synchronization framework
- Real Android and iOS background-location behavior
- Production TLS, hosting, monitoring, backup, and restore
- Peak load and sustained journey testing
- The school’s actual EduCore tenant contract and reconciliation
- Push-provider credentials and approved mobile release/signing
Current supported attendance path
Manual boarding and alighting are supported. QR/NFC scanning and provider-delivered push notifications should not be assumed complete unless explicitly included and demonstrated in an agreed pilot scope.
Bring your real operating questions
Contact IKS Cloud