Software for transportation, dispatch and field operations.
Dispatch, scheduling, crews, fleets and work orders — the systems that keep vehicles and people moving, built around how the day actually changes rather than how it was planned.
What we do
- Dispatch and scheduling
- Jobs matched to crews, vehicles and availability, with shift swaps, cancellations and no-shows handled as normal events.
- Field service
- Work orders out to the field and back, with status, notes and sign-off reaching the office as they happen rather than when the paperwork arrives.
- Fleet and asset maintenance
- Work orders, parts and labour tied to each vehicle or asset, so maintenance cost per asset is a number rather than a guess.
- Demand-response and paratransit
- Booking, eligibility and trip scheduling processes designed with the operational detail they need.
- Payroll and billing hand-off
- Hours, shifts and premiums flowing from operations to payroll and billing without being rebuilt from timesheets.
- Replacing operational platforms
- Ageing operational systems replaced or upgraded with integration touchpoints mapped and cutover and rollback planned up front.
Where it usually hurts
If one of these sounds familiar, it is the kind of problem we are called in for.
- Dispatch runs on a whiteboard, a spreadsheet and a lot of phone calls.
- The office finds out a job is done when the paperwork arrives.
- Shift changes and no-shows are handled by whoever picks up the phone.
- Maintenance cost per vehicle is a guess, because parts are not tied to work orders.
- Payroll is rebuilt from timesheets that disagree with the schedule.
Where this experience comes from
Our lead analyst's career history, described by sector — not an Elarion client list. More on the About page.
- A portfolio of platform upgrades at a regional transit authority — telephony, ERP, database, identity, GIS, reporting and integration services — each with cutover and rollback defined.
- A payroll and operational reporting migration at the same transit authority, reconciled against legacy payroll runs before sign-off.
- Enterprise asset management at a provincial transit operator: work orders, parts, inventory and maintenance costing in JD Edwards.
- Requirements and process design for a paratransit transportation management system serving New York City.
Dispatch, built for a client.
CrewDispatchr schedules and dispatches crews against jobs and availability, treats swaps and no-shows as normal events, and hands clean data to payroll and billing.
Questions buyers ask
- Off-the-shelf dispatch software or custom?
- If a product fits your scheduling rules, buy it. Custom earns its place when the rules are how you compete — collective agreements, mixed fleets, eligibility, or a schedule that changes all day.
- Do you work with public transit agencies?
- Yes. Our lead analyst has worked inside transit agencies on platform upgrades, payroll and asset management, and knows how public-sector governance and procurement work.
- Can it connect to our payroll and ERP?
- Yes. Most dispatch and field systems are only as useful as their hand-off to payroll, billing and the asset record, so those integrations are specified from the start.
Further reading
- Replacing spreadsheets with software, without losing what worksThe spreadsheet running your operation is not the problem.
- Off-the-shelf or custom software? How to decideThe default should be to buy.
Related services
Dispatch held together by phone calls?
30 minutes, free. Bring the problem, or the change you already have in mind.