Every trip with time, place and signature Accountability per client No more retyping trip sheets

Custom trip accountability app for specialised passenger transport

Appfront builds apps that let drivers in contract passenger transport account for every trip on the spot: boarding and alighting with time and location, a signature or code from the passenger, a reason for a no-show or a deviation, and at the end of the day an accountability report per client that matches the trip assignment. So the municipality or care provider pays for what was actually driven, with no trip sheets and no disputes.

What is a trip accountability app in contract passenger transport?

Trip accountability in contract passenger transport is the evidence that goes with every trip: which passenger, from where to where, what time they were picked up and dropped off, who was with them, and whether it matched what the client had ordered. The app records it on the spot, on the driver's phone, using the device's location and time and a signature or code from the passenger or escort. By the end of the day the accountability report is ready, per client, in the format that client requires.

Without an app like this, the driver fills in a trip sheet at the end of the shift, from memory, and then someone types the schedule into the client's system. A trip that didn't go ahead is recorded as completed; a trip that ran twenty minutes late is recorded as on time. The municipality carries out spot checks, rejects the report, and the operator cannot prove what actually happened. With tenders that impose penalties per late trip, that is money lost straight away.

We build custom software because every client asks for a different format and every type of transport has its own rules: pupils on a fixed route with a parent who signs, Wmo transport with a dispatch centre that assigns the trip, patient transport with an eligibility assessment per trip. The app knows those rules per contract and delivers to each client what the contract requires. A standard driver app knows one format and one type of trip.

Trips accounted for on the spot

Boarding and alighting with the device's time and location, the passenger present or not, and a signature or code. Nothing reconstructed from memory afterwards.

Deviations with a reason

No-show, passenger not ready, detour, extra escort: the driver picks a reason from a list and the deviation appears in the accountability report with time and place.

Accountability per client

At the end of the day, per municipality, institution or dispatch centre, the trips in the format the contract requires, ready as a basis for invoicing and as evidence in an audit.

How we build your trip accountability app for contract passenger transport

We start with the contracts: what each client wants to see per trip, what rejections over recent months were about, and how the schedule currently reaches the driver.

1
Mapping contracts and trips

For each client, the accountability format, the rules for late arrivals and no-shows, and how trip orders come in. We look at the rejections and penalties from the past period.

2
Building the driver app

The day's trips on the phone, boarding and alighting per passenger with time and location, signature or code, and deviations with a reason. Works without a signal.

3
Accountability and deviations

Per client, the accountability report in its own format, the comparison with the trip order and a list of deviations for dispatch to review.

4
Integrations and handover to maintenance

The integration with your scheduling system and the dispatch centres, the export to invoicing, and then ongoing maintenance and new contracts.

What a trip accountability app for contract passenger transport actually does

The components below appear at almost every contract passenger transport operator. Which ones you need depends on your contracts and your scheduling system.

Trips of the day

The schedule on the driver's phone, with the passengers, addresses, time windows and special requirements for each trip, such as a wheelchair or an escort.

Boarding and alighting

One tap per passenger at boarding and alighting, with the device's time and location. A passenger who doesn't show up is logged as a no-show with a reason.

Signature or code

The passenger, parent or escort signs on the screen or gives a code. For regular passengers, a pass or QR code can be enough.

Deviations

Detour, waiting time, extra passenger, incident: a reason from a list, a note and optionally a photo, with time and place attached.

Accountability per contract

Per client, the trips in its own format, with the comparison against the trip order and an export to its portal or as a file.

Checks for dispatch

A list of trips with deviations before the accountability report goes out, with the option to correct them with a reason.

Who we build a trip accountability app for in special-needs transport

The app is for transport operators who account for each trip to a client, where a rejected trip means lost revenue or a fine straight away.

WMO and regional taxi operators

Trips from a dispatch centre with time windows and penalties for lateness. The integration with the centre and the time registration are the core.

School transport

Fixed routes with the same children, parents who sign and schools who confirm. Attendance per child and the signature matter most.

Seated patient transport

Trips with an authorisation per trip and the health insurer as the client. What you need is reporting in the insurer's format.

Transport to day care

Care institutions as clients, with escorts and group trips. Attendance per passenger and the escort being present are the core.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

This page is about accounting for trips to the client. For school transport planning, see our page on school transport software, and for a taxi app with booking and payment, see our page on a taxi app. You can read about our approach on custom software development.

For the office, with accountability per client and an invoice generated from the same trips, there is our trip accountability software for special-needs transport.

Driver app with the day's trips Time and location for every boarding and drop-off Signature, code or pass per passenger Deviations with reason and photo Works without coverage Accountability per client in their own format Integration with planning systems and dispatch centres Export to invoicing Checklist for planning Log per trip

Why Appfront for your trip accountability app in special-needs transport?

An accountability report is evidence. It has to be created on the spot, not afterwards, and it has to match what was ordered, per client. That is what we build on.

Recorded at the moment

Time and location come from the device, the signature from the passenger. That is what an inspector trusts, and what a trip sheet filled in afterwards never is.

Per contract, not per app

Every client gets their own format from the same registration. A new contract means a new template, not a new way of working for the driver.

Deviations are not mistakes

A no-show with a reason and a time is a trip you can invoice. A no-show without evidence is a trip you lose.

Security and privacy in a trip accountability app for special-needs transport

The app processes personal data of vulnerable passengers: names, addresses, sometimes an authorisation or a medical note. Access is set up per role: the driver only sees today's trips, and after the shift the data disappears from their device. Signatures and locations are stored encrypted and kept no longer than the contract and the retention obligation require.

The app runs in a European data centre, with encrypted storage and daily backups. We provide the data processing agreement and the description of the processing that you need for your clients.

Frequently asked questions about a trip accountability app for special-needs transport

Questions that special-needs transport operators ask before getting started.

The driver accounts for each trip on the spot: boarding and drop-off with time and location, attendance, signature or code, and deviations with a reason. At the end of the day, the app prepares the accountability report for each client in their format, compared with the trip order, ready to serve as the basis for invoicing and as evidence.

Yes. The day's trips are stored on the device, and every registration is saved with the time and location of that moment and sent as soon as there is a connection. A driver in a rural area or a car park simply carries on registering.

A parent, escort or staff member from the institution signs, or gives a code that belongs to the passenger. For regular passengers, a pass or QR code can be enough. What is permitted per contract is configured per client; the app does not enforce anything the contract does not require.

Yes. Trip assignments come from your planning system or directly from the dispatch centre, and the trip records go back in the format the centre or the client requires. Which integrations are possible depends on the systems involved; most dispatch centres offer an interface or file exchange.

It goes onto the planning team's review list before the records leave the building, with the driver's reason, the time and the location. The planner reviews it and corrects it with a reason. That way no records go out that would fail an audit, and every correction can be traced.

For WMO and regional taxi transport, school transport, seated patient transport and transport to day care. Each has its own rules and its own client, and the app knows these per contract. A transport operator with several types uses a single app, with the rules that apply to each trip.

Check that first. Planning software for special-needs passenger transport often has a driver module, and that may be enough with a single client. Custom software makes sense if you have several contracts with their own formats, if your records are currently being rejected, or if your package's module does not work without coverage or does not capture a signature.

Every trip accounted for on the spot, in the client's format?

Tell us which contracts you run, which planning system you use and how many trips have been rejected in recent months. We will show you what the driver app, the review list and the per-client records look like.

Edit content