An account based ticketing pilot programme is the safest way to find out whether account-based fares and passenger accounts suit your routes before you change anything for every rider. This guide is written for bus company owners and operations leads who are weighing a trial.
It does not explain what account-based ticketing is. For that, read our overview of how account-based ticketing works for bus operators. Here the question is narrower: how do you run a small, honest test and know when it has passed?

Why Run an Account Based Ticketing Pilot Programme First
Switching how every passenger is identified and charged is a big change, and an account based ticketing pilot programme keeps it manageable. Staff habits, customer support scripts and reporting all shift at the same time.
An account based ticketing pilot programme lets you see those shifts on a small slice of your network while the rest keeps running as it does today.
A well-run account based ticketing pilot programme also protects your reputation. If something is awkward at the boarding door, a handful of riders notice instead of your whole customer base. You learn quickly, fix the process, and only then decide whether to widen it.
Finally, a pilot gives you evidence. Instead of choosing based on a demo or a sales call, you decide based on what your own drivers, agents and passengers did during a real period of service.
7 Essential Steps in an Account Based Ticketing Pilot Programme
Use this list as a working outline. Each step is short on purpose, so you can assign an owner and a date to it without a long planning meeting.
- Pick one route or one group of riders
- Write down what success means before you start
- Decide which sales channels take part
- Set up passenger accounts and a simple sign-up path
- Brief drivers and station staff
- Run for a fixed period and log every issue
- Hold a review and make a go or no-go call
The sections below take these steps in order, with the questions an operator should ask at each one.
Step 1 and 2: Choose a Narrow Scope and Define Success
The best scope for an account based ticketing pilot programme is small enough to watch closely and real enough to matter. A single route with regular riders, a commuter group, or one terminal is usually better than a mix of everything.
Avoid choosing a route that is already in trouble, because you will not know what caused the problems.
Before launch, write down the pass mark for your account based ticketing pilot programme. Keep it in plain language that your whole team can read. For example: riders can board without asking for help, staff can find a booking quickly, and the daily numbers match the money.
If a target needs a number, set it from your own history, such as how long boarding takes today on that route. Do not borrow a figure from another company. Your pilot should be judged against your baseline, not against a headline.

Step 3: Decide Which Channels Take Part in the Pilot
In any account based ticketing pilot programme, an account only helps if every place you sell sees the same passenger and the same seat count. Decide early whether the pilot covers your website, your counter, phone sales and any third-party sellers, or only some of them.
If the pilot runs on one channel while others sell as before, make sure seats are still shared. Overselling during a trial would teach you nothing useful and would cost you riders. Our article on how to stop overselling bus seats explains why one shared inventory matters.
UBT describes its shared APIs as syncing instantly across all sales channels, including third-party websites. Whatever system you test, ask the same thing: when a seat sells in one place, how fast does every other place know?
Step 4 and 5: Set Up Accounts and Brief Your Team
An account based ticketing pilot programme depends on riders having an account, so the sign-up path needs attention. Keep the first screen short. Ask only for what you need to run the trip, and tell riders what the account will be used for.
Then train the people who meet passengers during the account based ticketing pilot programme. Drivers and station agents need to know what a rider will show at the door, what to do if someone forgot their login, and who to call when a booking cannot be found.
A one-page cheat sheet beats a long manual.
Flexible validation helps here. UBT lists flexible ticketing validation options among its features, so staff are not forced into a single method at the door. When you test any system, check which validation options it offers and what happens when a phone has no signal.
For more, see our guide to bus ticket validation options for operators.
Step 6: Run the Pilot and Log Every Issue
Pick a fixed period for the account based ticketing pilot programme and stick to it. A pilot that drifts on without an end date turns into a half-launch, and nobody is sure who is responsible for what. A clear start and end also help riders understand that this is a trial.
Keep a simple shared log. Every time something goes wrong, note the date, the route, what happened and who handled it. Include small annoyances, because those often point to a training gap rather than a software problem.
Look at the reports every day during the first week. Real-time reporting is one of the core capabilities UBT lists next to POS, ticket validation and inventory control, and it is exactly what makes a short pilot readable.
If a system cannot show you yesterday’s activity quickly, judging a pilot becomes guesswork.
Step 7: Review and Decide Whether to Expand
At the end of the account based ticketing pilot programme, sit down with the log and the reports. Compare them with the pass mark you wrote before you started. Be honest about what was caused by the system and what was caused by your own process.
There are only three sensible outcomes for an account based ticketing pilot programme. You can expand to more routes, you can extend the pilot with specific fixes, or you can stop.
Stopping is a valid result. A pilot that tells you early that the approach does not fit your business has done its job.
If you want a wider checklist for judging vendors alongside the pilot, our bus ticketing scorecard turns the same questions into a simple score sheet.
Questions to Ask Any Vendor About a Pilot
An account based ticketing pilot programme only works when the terms are clear. Before you agree to anything, ask these questions in writing and keep the answers.
- Is there a cost to run the pilot, and what happens to my data if I stop?
- Who sets up my routes, and how long does that take?
- Which validation methods can drivers use, and do they work offline?
- Can I move or cancel a departure during the pilot?
- What reports can I see, and how often are they updated?
- Can I leave at the end without further obligations?
Notice the last point. Many operators hesitate to try new software because of the fear of being locked in. UBT states plainly that the service is free with no obligations, and that if you do not like it, there will be no cost and no obligations to you.
That is the kind of clarity you should expect from any partner.
Start Your Account Based Ticketing Pilot Programme
A well-run account based ticketing pilot programme takes a few weeks of attention and gives you something a sales deck never can: proof from your own routes. Keep the scope small, write down the pass mark, and review honestly.
Ready to test it? Request a free trial of UBT’s bus ticketing platform and see how shared inventory, flexible validation and real-time reporting perform on one of your own routes.
