Author once. Publish everywhere.
Trip patterns and service calendars in one editor. Publish to your website, the driver portal, passenger journey planners and a print-ready PDF - without re-keying.
One source of truth, every channel.
Blueprints: design the whole network, not route-by-route
Lay out a day's service across every route on one canvas. Pick the routes on a map, set how often each runs and how many buses and drivers you need by time of day, then publish once - RouteStra turns the design into trips, driver duties and vehicle blocks together. Republish safely as you tweak: unchanged trips stay put, so driver assignments don't break. The timetable and the rota are built from the same plan.
Trip patterns with a calendar that knows half-terms
Build a service once with its trip pattern (the sequence of stops and times). Calendars handle weekday / Saturday / Sunday plus UK school-term exceptions. The system compiles the right trips for the right day, automatically - no two timetables for term-time vs holidays.
Disruption messages, one push
When the road's closed, write the disruption once: it appears on the public timetable, the embeddable widget and the driver portal. Stops get their own affected-message; passengers don't see the whole route flagged.
Journey planner publishing + audit log
Export to the standard formats journey planners read in one click. Every change is logged: who edited which trip, when, with what before / after - the trail you'll need when the regulator asks who changed the 0732.
Timetable to passenger, end to end.
Build the trip pattern
Sequence of stops with times - the editor handles the maths.
Set the calendar
Weekday / weekend / school-term exceptions in one place.
Publish
One click sends the timetable to your website, the driver portal and journey planners.
Disruption?
Write it once; it appears on every channel a passenger sees.
Audit when asked
Audit log shows every edit, every approver, every export.
Three timetable workflows.
One service, multiple variations (peak / off-peak / Sunday). Build the trip pattern once; let the calendar handle when each trip runs.
Embed the timetable on your website with a one-line iframe; passengers see the live version every time, no PDF re-uploads.
Every Timetables module.
Author
- Blueprints (network design)
- Timetabling
- Trip Pattern Editor
- Service calendars
Publish
- Embeddable widget
- Print-ready PDF
- Journey planner export
- Driver portal sync
Operate
- Disruptions
- Audit log
- Shifts integration
- Route Mapping
Common questions
We export to the standard formats - Google Maps, Citymapper, third-party apps, and the central UK feed (BODS) all read what we generate. The export is one click; direct API publishing is on the roadmap.
Other parts of the platform
Ready to simplify your scheduling?
Tell us about your fleet and we'll come back with a tailored quote. We'll help you migrate your data and walk your team through every module you turn on.
We're with you before, during, and after setup - our team is here to help every step of the way.