A paper pass is not merely a piece of card. It sits inside a workflow for issuing entitlement, checking it at the door, handling exceptions, replacing lost passes, and proving what happened later. A digital system is only an improvement if it performs that whole workflow more reliably for your operation.
UK transport policy continues to favour simpler, joined-up ticketing and better digital passenger information. The Department for Transport’s 2026 delivery plan describes contactless, integrated ticketing as a national direction, but that does not make every digital product suitable for every service. Operators still need to test the specific pass, device, data, and support model they intend to use. See the government’s current vision for buses.
Define the migration you are actually considering
“Digital ticketing” can describe several different systems:
- an operator issues a period pass to a named passenger;
- a passenger buys a ticket online;
- a bank card acts as the travel token;
- a driver validates a QR code or barcode;
- several operators accept the same ticket;
- a back office reconciles fares and payments; or
- a local bus operator publishes fares data to the Bus Open Data Service.
These capabilities are related, but they are not interchangeable. MoveCore currently supports operator-issued term and period passes, QR validation, passenger and service management, and scan records. It does not currently provide passenger ticket sales, card payments, contactless fare capping, offline validation, or Bus Open Data Service feeds.
Write down the exact paper workflow you want to replace before comparing products.
Map the current paper process
Follow one representative pass from creation to expiry:
- Who decides that the passenger is entitled to travel?
- Which service, stop, dates, or journey conditions apply?
- Who prints, distributes, and replaces the pass?
- What does a driver check at boarding?
- What happens when a pass is forgotten, damaged, copied, expired, or used on the wrong service?
- Which boarding evidence is recorded, and who can inspect it?
- How are changes and revocations communicated?
- What work is required at the end of a term or contract?
Record the time, materials, handoffs, recurring mistakes, and unresolved exceptions. This creates a baseline without assuming that digital is automatically cheaper or easier.
Compare the whole operating workflow
Pass rules
Confirm that the digital product represents the rules you use today. Test the relationship between passenger, service, stop, and validity dates. If you sell single, return, flexi, multi-operator, or zonal tickets, an operator-issued period-pass product is not a substitute.
Door validation
Use the device and connection a driver will have in service. Test a valid pass, a wrong-service pass, an expired or not-yet-valid pass, and a revoked or unknown pass. The result must be clear enough for the driver to act without interpreting an administrator’s screen.
Ask whether the validator works without a connection. If offline operation is essential, disconnect the device during the pilot. Do not accept a roadmap statement as evidence.
Exceptions and fallback
Agree what the driver should do when:
- the passenger has no usable device;
- a printed QR code is damaged;
- the scanner camera fails;
- the network is unavailable;
- the operator entered incorrect passenger data; or
- a person disputes the validation result.
A fallback should protect the service without creating an undocumented second system. Decide which exceptions need a record and who reviews them.
Records and access
A scan log can show that a validation happened, but it is not automatically a compliance report, proof of payment, or complete passenger count. Check the fields, timestamps, service relationship, result meanings, access controls, correction process, retention period, and export options.
For local bus services with stopping places in England, the Bus Open Data Service requirements cover timetable, fares, vehicle-location, and historic performance data. A private boarding log does not by itself satisfy those duties.
Accessibility and passenger access
Do not assume that every passenger owns a suitable smartphone or can reliably load a pass at the point of boarding. Test printed alternatives, screen magnification, contrast, language, delegated access for a parent or carer, and the replacement process.
Keep the pass itself separate from legally required onboard information. The Public Service Vehicles (Accessible Information) Regulations guidance addresses audible and visible route and stop information for in-scope services. A digital pass does not satisfy that separate obligation.
Privacy and security
List the personal information the system needs and remove fields that do not serve the operating purpose. Establish the controller and processor roles, lawful basis, privacy information, access rules, retention, deletion, incident process, and data-return terms.
The ICO’s UK GDPR guidance and resources is the primary starting point. A supplier’s security features do not make the operator’s processing automatically compliant.
Build a fair cost comparison
Compare the cost of the complete workflow over the same period.
For paper, include:
- design, stock, printing, and postage;
- staff time for preparation, distribution, reconciliation, and replacement;
- equipment, storage, and secure disposal; and
- the cost of exceptions that cannot be traced.
For digital, include:
- subscription, setup, transaction, message, and support charges;
- validator devices, mounts, connectivity, and replacement;
- migration, configuration, training, and support time;
- integrations and data export; and
- the paper or manual fallback you still need.
Use your own volumes and staff costs. Generic savings percentages are not evidence for a particular operation.
Pilot before removing paper
Choose one service that includes ordinary boardings and realistic exceptions. Define success before the pilot:
- the correct passengers receive the correct passes;
- drivers complete every agreed validation scenario;
- the operator can understand the resulting records;
- the fallback works when a device or connection fails;
- passenger support needs are recorded; and
- staff can repeat the workflow without supplier intervention.
Run paper and digital in parallel only for a defined transition period. At the end, record which system is authoritative, how duplicate records are resolved, and the conditions for expanding or stopping the pilot.
Where MoveCore fits
MoveCore is a candidate when the immediate problem is operator-issued term or period passes, QR validation at the door, and scan records for scheduled services. The free tier lets an operator test one service with up to 30 active passengers.
MoveCore is not the right current choice when passenger ticket sales, card payments, offline validation, live vehicle tracking, passenger notifications, public integrations, or Bus Open Data Service feeds are required on day one. Those capabilities are not shipped.
Use the transport software buyer’s guide to score the wider decision, or start with one service if the current MoveCore workflow matches your must-have requirements.