Employee transport sits between three parties: the employee who needs a safe ride, the vendor who runs the vehicles and the company that pays for the service. When something goes wrong, each side has a different story and nobody has the data. TransitGuide gives all three one shared, timestamped record.
The problem: waiting, worry and "he said, she said"
Employees do not know when the shuttle will arrive, so they wait, phone the driver or give up and take their own transport, leaving an empty seat the operator still pays for. For late and night shifts the stakes are higher: HR needs to demonstrate that safety is taken seriously, and needs proof of what happened if an incident occurs.
Vendors promise on-time performance and incident response, but clients have no independent data to hold them to it.
Live tracking and stop alerts for riders
Riders see their vehicle live and can be alerted when it approaches their stop. Tracking links give guests and visitors a live view without needing an account. Dispatchers see all vehicles in a single fleet cockpit with counts of moving, idle and offline vehicles, and can work from the web dashboard or the admin mobile companion.
Incident escalation that does not depend on one person
Drivers can raise an incident from the app with location attached. On higher plans, incidents move through configurable escalation chains with severity filters and after-hours routing, so a night-shift issue reaches whoever is actually on call. Each acknowledgement is written to the audit log, and incident history is immutable on plans that include it.
- Severity-aware alerts: the default filter is a floor, so a critical alert is never hidden
- Cooldowns and de-duplication so staff are not flooded
- Roles for owner, admin, dispatcher and viewer
SLA evidence for both sides
Trip history, replay, SLA-breach alerts and response-time reports on the higher plans turn "we were on time" into a verifiable statement. Distance is computed from validated GPS fixes, with low-accuracy and spoofed locations excluded, which keeps billing reconciliation honest.
For corporate clients who want the data in their own systems, API keys and webhooks (Slack included) are available on higher plans, and trips can be exported.
Spot inefficient routes
Analytics, a fleet heatmap and route mining over real trips show where time and distance are lost: long detours, stops in an illogical order and routes that drifted from the plan. That is the evidence for renegotiating a route, not an opinion about it.
Frequently asked questions
Can the client company see data without managing the vendor's fleet?
Yes. Role-based access allows viewer-level accounts, and tenant scoping means each business only ever sees its own data.
Does it help with night-shift safety?
Incident reporting from the driver app, escalation chains with after-hours routing on higher plans, and full trip replay all support it.
Can we integrate with our HR or BI systems?
API access, outbound webhooks and trip export are available on higher plans.