How to choose community transport booking software: a trustee-safe checklist

Knowing how to choose community transport software is rarely urgent until it suddenly is. A coordinator is off sick, two volunteers turn up for the same minibus, or a funder asks for journey figures nobody can pull together quickly. Then the search starts, often squeezed into a budget meeting or a grant deadline.

This guide is for coordinators and trustees who need to shortlist a community transport booking system and explain the choice to a board. It gives you a practical checklist, the questions to ask every supplier, and a simple way to run a fair trial. It is not a sales pitch. Whichever platform you choose, the same checks apply.

If you are still deciding whether you need software at all, start with spreadsheets vs dedicated community transport software. For a wider overview of what these platforms do, see our practical guide to community transport software.

Start with your own journeys, not the feature list

Before you look at any supplier, write down what your scheme actually does in a normal month. Keep it short:

• How many vehicles, and which are minibuses, cars or accessible vehicles
• How many people take bookings, and how many volunteer drivers you have
• Which journey types you run: shared routes, door-to-door lifts, group hire, training, internal use
• How you charge: memberships, per-trip contributions, mileage, hourly or daily hire
• What trustees and funders ask you to report

This one page becomes your test script. Every demo and trial should be judged against it. A long feature list is no help if the software cannot handle the three journey types you run every week.

The checklist at a glance

Area	What good looks like	Question to ask
Booking types	Each journey type has its own rules on one shared calendar	"Show me our dial-a-ride, a recurring lift and a group hire, side by side"
Double-booking	The system blocks clashes at the point of booking	"What happens if I try to put a driver on two overlapping trips?"
Compliance	MOT, tax and insurance dates with alerts before they lapse	"Where will I see that a vehicle's MOT is due next month?"
Invoicing and mileage	Invoices created from completed bookings, mileage recorded per trip	"Take one finished journey through to an invoice"
Hosting and data	UK hosting, backups, data separated from other organisations	"Where is our data stored, and how is it backed up?"
Roles and 2FA	Role-based access and two-factor sign-in for every user	"Can a volunteer take bookings without seeing billing?"
Trial and support	A real trial, published prices, a clear support route	"How long is the trial, and how do we get help during it?"

Use this community transport booking software checklist against every demo. The sections below explain each line in more detail.

1. Booking types: one-off, recurring, dial-a-ride and car schemes

Community transport is not one kind of journey. A good community transport booking system treats each type on its own terms rather than forcing everything into a single "job" screen.

Check that the software handles:

• One-off trips. A single hospital appointment or shopping run, booked quickly, with the cost shown before you save.
• Recurring journeys. Weekly dialysis or a regular day-centre run should repeat without copying the same booking fifty times. Ideally you can preview the dates and skip any that clash.
• Dial-a-ride and shared routes. Several passengers on one planned route need a clear passenger list, not a separate tab. If this is your main service, a dedicated dial-a-ride booking system should show who is on board and where.
• Community car schemes. One member, a pickup, a drop-off and a volunteer driver, often with a return trip. See what to look for in community car scheme software.
• Group hire, training and blocked time. If you hire vehicles to other groups, assess drivers, or need to take a vehicle out of service, those should sit on the same calendar too.

Decision tip: ask the supplier to book your three most common journeys live in the demo. If they need workarounds or "we'd set that up for you later", note it.

2. Double-booking prevention

This is the most common reason schemes leave spreadsheets. Two people with two copies of the diary will, eventually, book the same vehicle.

Look for software that:

• Blocks a vehicle or driver being saved onto overlapping trips
• Adds buffers between jobs so a minibus has time to get back and be cleaned
• Respects volunteer availability, so a trip cannot be assigned outside a driver's saved hours
• Helps you find a free vehicle and time when a last-minute request comes in

Ask what happens at the moment of the clash. A warning someone can click past is not the same as a hard block. For volunteer-heavy schemes, also ask how drivers are asked to take a trip and whether their reply is recorded. Our page on volunteer driver software covers this in more detail.

3. Compliance and MOT alerts

A minibus that misses its MOT does not just create admin. It stops the service and can put your insurance at risk.

Your booking software should:

• Hold MOT, tax, insurance and maintenance dates against each vehicle
• Alert you before those dates lapse, not on the day
• Show at a glance which vehicles are road-legal and ready to book
• Ideally, hold driver records too: licence checks, DBS status and training such as MiDAS, with expiry warnings

Trustees care about this line more than most. It is the part of the system that protects passengers and the organisation. For a deeper look, read our guide to community transport MOT tracking.

4. Invoicing and mileage

Many schemes stay solvent through membership fees, per-trip contributions and group hire charges. If invoices are rebuilt by hand from the diary each month, mistakes creep in and treasurers lose confidence.

Your community transport booking software should create invoices from completed bookings. Check that it can:

• Create a journey invoice from a completed booking, using your pricing (hourly, daily or mileage)
• Handle membership invoices separately from journey invoices
• Record end mileage on each trip and report miles by vehicle, driver and booking type
• Take payments in the ways your members use, and let you record cash or cheque by hand
• Produce reports your treasurer and funders can actually read

Be clear about what the software does not do. Some platforms record mileage but do not process volunteer expense claims or pay drivers. That may be fine, but you need to know. If you reimburse volunteers, our article on volunteer driver mileage rates explains the current HMRC position.

5. UK hosting and data protection

You hold sensitive information: names, addresses, medical appointments, mobility needs. Your board needs to be comfortable with where it lives.

Ask every supplier:

• Where is the data hosted? UK hosting keeps things simpler for UK GDPR and for anxious trustees.
• How is it backed up, and how often?
• Is our data separated from other organisations?
• Is there an audit trail showing who changed a booking or a price?
• Can we export our data if we leave?

You do not need to be a security expert. You do need written answers you can file with your data protection records.

6. Roles and two-factor sign-in

Most schemes have a mix of paid staff, part-time coordinators and volunteers taking bookings. They should not all see the same things.

Look for:

• Role-based access, so a volunteer can take bookings without seeing billing or changing prices
• Two-factor authentication for every user, admins included
• A simple way to invite new users and remove leavers
• Billing and settings restricted to the people who need them

Decision tip: ask how quickly you can remove someone's access on the day they leave. The answer should be "straight away, from one screen".

7. Trial, pricing and support

A demo shows you the best version of the product. A trial shows you your version.

Before you commit, check:

• Is there a free trial, and does it need a card?
• Are prices published, so trustees can compare like with like? Watch for limits on users, members, vehicles and storage.
• How is support provided — ticket, email, phone — and what response times are realistic?
• Is setup help available for importing members, vehicles and regular bookings?
• Can billing fit your funding cycle, for example paying upfront for a fixed period when a grant lands?

Comparing community transport software: who to shortlist

A fair community transport software comparison usually includes a handful of established names alongside newer platforms. UK schemes commonly look at tools such as OPTiMiSe, CATSS, CTX and Road XS, as well as OpenCommute. Each has its own history, approach and type of customer, and many schemes run them successfully.

Rather than relying on anyone's summary, including ours, put each one through the same checklist above. Ask for a demo using your journeys, request current pricing in writing, and talk to a scheme of a similar size that already uses it. Features and prices change, so check the details directly with each supplier at the time you are deciding.

Where OpenCommute fits

OpenCommute is a browser-based community transport booking system for UK schemes. Coordinators take dial-a-ride, one-to-one, group hire, training, internal and blocked bookings on one shared calendar, with vehicle compliance alerts, role-based access with email two-factor sign-in, and invoices created from bookings. Data is hosted in a London data centre.

To be clear about what it does not do yet: there is no passenger or member app today. Staff and volunteers make bookings on members' behalf in the admin panel. A member app is planned but not available. If self-service booking for passengers is essential for you right now, factor that into your shortlist.

You can see the full list on the features page.

How to run a fair trial

Whichever tools make your shortlist, a structured trial will tell you more than any brochure.

1. Pick two weeks of real bookings. Include a recurring trip, a shared route and at least one awkward last-minute change.
2. Involve more than one person. Ask a second coordinator or a volunteer to take bookings without your help.
3. Try to break it. Attempt a double-booking. Add a vehicle with an MOT due soon. Assign a driver outside their hours.
4. Close the loop. Take a finished journey through to an invoice and a report.
5. Score against your checklist. Use the table above and agree the scores as a team.

Then ask the question that matters most: could someone else run tomorrow's list from this system without a handover call? If yes, you have found a fit.

Taking it to trustees

Trustees want to know three things: does it reduce risk, what does it cost, and what happens if it goes wrong. Your checklist scores answer the first. Published pricing and an estimate of staff time saved answer the second. Written answers on hosting, backups, data export and support answer the third.

If you would like to include OpenCommute in your comparison, you can view pricing or start a 28-day free trial with no payment needed, and test it against your own journeys alongside the other tools on your list.