Shared Signals: A Data Compact for Smaller Bus Operators and Their Regions

Regional transport debates often proceed on partial evidence. A local authority can see patronage trends and highway schemes; a smaller bus operator can see missed trips, ticket-machine counts and depot incident logs. Neither view is complete. In 2026, the practical task is not to build a grand data platform but to create a repeatable data compact between operators and the authorities that plan and fund local services. The aim is a modest exchange that answers shared questions, respects privacy and survives changes of staff.

Start with three shared questions

Before any fields are specified, agree the questions. A quarterly set of three is enough for most districts: where are scheduled journeys losing most time; which corridors are gaining or losing passengers; and what incident patterns affect reliability or passenger confidence. These questions should be jointly owned by the operator and the local transport authority. They also set a test for every data request: if a field does not help answer one of the questions, it should not be collected.

Build the agreement around purpose and limits

A compact need not be a lengthy legal document, but it should record purpose, lawful basis, fields, frequency, format, retention and access. A workable sequence is:

1. Define the purpose in one paragraph and state what the data will not be used for.
2. List the minimum fields, their source systems and the named owner at each organisation.
3. Use common identifiers such as NaPTAN stop codes, route numbers and time bands.
4. Apply data minimisation: aggregate counts, avoid personal details and strip commercial information that is not needed.
5. Set privacy safeguards, retention periods and secure transfer arrangements.
6. Name a data lead at the operator and an analyst at the authority, with an escalation route.
7. Review the agreement annually and remove fields that have not been used.

This is not legal advice. Operators and authorities should take their own advice on UK data protection law and follow Information Commissioner's Office guidance. The important point is that the agreement is written for the people who will use it, not for a filing cabinet.

Keep the technical layer modest

Most smaller operators cannot justify a bespoke portal. CSV templates, a shared folder with named users, and a quarterly extract are sufficient to begin. Use stop identifiers, route numbers, vehicle types and time bands. A one-page data dictionary prevents mismatched definitions, such as whether a journey is counted as late at three minutes or five. The local authority can provide analyst time; the operator provides the operational record. Where a combined authority or sub-national transport body already employs analysts, that capacity can be shared across districts. The point is to avoid buying technology before the governance is stable.

Put privacy safeguards where people can see them

Privacy should be visible in the protocol, not buried in an appendix. For incident reports, separate the factual account from personal details. Redact names, addresses and staff identifiers, or replace them with pseudonyms. Aggregate passenger counts below a minimum threshold, such as five boardings, so that small rural stops cannot be linked to individuals. Keep raw extracts for a defined period and delete them when the review is complete. Use access-controlled folders rather than email attachments. A short data protection impact assessment may be needed if personal data is involved. Publish a plain-English note for staff and, where relevant, passengers.

Agree that data supplied for service planning will not be repurposed for enforcement without a separate agreement. That distinction matters for trust. Operators must see the compact as a route to better services, not a compliance trap.

Run a quarterly rhythm that ends in actions

The compact lives through a calendar. Ten working days after quarter end, operators submit the agreed extract. The authority's analyst produces a four-page brief: punctuality by corridor, passenger counts by time band, incident categories, and two proposed actions. A meeting of operators and officers reviews the brief, agrees no more than two actions, and records who will do what. The next quarter begins with those actions. An annual session refreshes the fields and removes anything unused. This rhythm is more valuable than a one-off data dump because it builds memory and accountability.

Return insight to the region

Data sharing should be reciprocal. The authority can share highway works, patronage estimates, funding timetables and planned service changes. Operators can benchmark their own punctuality against corridor averages without exposing commercially sensitive detail. Regional summaries should be published where possible, so that parish councils, user groups and members can see the evidence behind decisions. The value stays in the region when the analysis informs local timetables, stop improvements and funding bids rather than being extracted for a distant report.

Judge the compact by its use

After two quarters, ask four questions: Did the data answer the agreed questions? Did it lead to actions? Is the burden proportionate? Are privacy safeguards working? If a field is unused, drop it. If a meeting produces no action, change the format. The compact should be lightweight enough to continue through staff changes and robust enough to protect personal information.

Smaller operators do not need perfect systems to contribute useful evidence. They need a clear purpose, a modest technical route, visible privacy rules and a quarterly habit. In 2026, that combination can turn routine operational records into regional insight without imposing a heavy IT bill. The handshake is not a single signature; it is a repeated practice.