Daily manifest
Each driver sees the runs, pickup windows and passenger assistance notes for their shift, in the order they will drive them.
A driver app for a medical transport company gives drivers and attendants their daily manifest, vehicle checks and passenger notes on one phone, and gives the operations lead a live view of every run. SIZ Group develops the iOS and Android versions with wheelchair lift and stretcher checklists built in, so each crew starts the day from the same list.
An operations lead will approve a driver app only if drivers can run the day without phoning dispatch for every change. The first proof point is a manifest that matches what the driver actually drives. The second is that pickup and drop-off times are captured during the run, not typed up at the end of a long shift. The third is that the lead can see which vehicles have passed their checks, which runs are at risk and where a second driver is needed.
Ask for a replay of a real Tuesday, including a no-show, a late dialysis session and a van that fails its lift check. If the app handles all three without a phone call, the lead has the evidence to approve a rollout. A short list of what drivers still find awkward is worth more than a long list of features.
Most transport companies already run dispatch software, a billing system that files claims with payers and a maintenance log for the vans. The driver app should take its manifest from dispatch and write trip times back, so billing receives clean records. For navigation, the app can hand each route to the phone's own maps app instead of building one from scratch.
If dispatch software has no open interface, the first release can use a daily manifest file that the dispatcher exports and drivers open on their phones, with trip records sent back at the end of the day. Vehicle checks can start as a dated checklist per van, which is often enough to answer an inspector's question about when a lift was last tested.
The company needs a driver roster with license classes, training completion dates and the vehicles each driver is cleared to operate. It also needs the checks each van requires before a run, such as lift tests and tie-down points, and the pickup documentation each payer expects. These lists decide what the app asks drivers to do, so they should be written down before the design starts.
Access needs clear rules. Drivers should see their own manifest and the passenger notes for their own runs, and nothing more. Dispatchers and the operations lead need wider views, while mileage and fuel approvals should follow the company's authority limits. Passenger details should stay limited to what a driver needs for pickup, and the compliance advisor should review the final field list.
Each driver sees the runs, pickup windows and passenger assistance notes for their shift, in the order they will drive them.
Lift, tie-down and safety checks are completed before departure, with a time stamp and a note for any item that fails.
Times for each stop are recorded during the run, ready to match against the payer's documentation.
Open issues, late runs and vehicle faults pass to the next driver or dispatcher, so nothing waits on a phone call.
The most damaging error is asking drivers to type too much. A driver who has just unloaded a passenger in the rain cannot complete a long form on a small screen. Each step should take a tap or two, with optional notes kept for the moments that need them and everything else pre-filled from the manifest.
Another mistake is ignoring the paper trail the business already needs. If the app records a pickup time that differs from the time written on a payer form, billing will spend days reconciling the two. Compare the app's fields with the documentation each payer requires, and settle the differences before the pilot starts.
Start with one vehicle group, such as the wheelchair vans that run dialysis trips, and the drivers who already know those routes well. Keep the paper manifest in the vehicle for the first two weeks, then remove it once the app's records have matched the billing file for several days in a row.
Train drivers on the three screens they use on every run, and ask dispatch to walk through exceptions with them rather than handing over a manual. Hold a short debrief at the end of each shift during the first month. The fixes that come out of those debriefs matter more than any launch announcement.
Measure what the operations lead can already count. Runs with a complete pre-run check before departure, manifests matched to recorded pickups, late pickups explained inside the app and billing records that reconcile on the first pass are strong signals. Compare each one with the month before launch, using records the company already keeps.
Look at the cost side as well. Mileage per completed trip, overtime caused by re-keyed paperwork and the number of calls drivers make to dispatch about routine questions show whether the app is saving effort. Review these monthly with the owner, and treat any rise as a process question before it becomes a driver question.
Yes. The manifest downloads at the start of the shift, and pickups, checks and notes are saved on the phone and sync when coverage returns. We would test the rural routes your vans run most, because dead spots matter more than a map suggests.
It can, once the operations lead and the compliance advisor agree that the digital form meets your requirements. Each check is timed and tagged to the driver's login, and failed items alert dispatch. Some companies keep a paper copy in the vehicle as a backup, and we would plan for that choice.
The app flags the open run to dispatch once the scheduled drop-off time has passed. Dispatch can close it with a reason, and the record shows who did it and when. The driver's earlier entries are kept as they were.
Each company keeps its own manifests, vehicles and records, and a driver sees only the company they are signed in to. Drivers who work across companies sign into each one separately, so hours and checks are attributed correctly. We would confirm the setup during scoping.
Most drivers learn the core screens in one short session, because a run uses the same few functions every time. Dispatchers need a second session on exceptions. We would build the guide with your operations lead, using your real vehicles and routes.
Book a free scoping call to walk through the checks and get the price in writing.