BODS Is About to Become Much More Powerful — So Who Checks the Data?


Why bus open data can transform enforcement — but only if the evidence is transparent, auditable and capable of being challenged

A note before I begin: I write this in a personal capacity as a bus driver and trade union representative with a longstanding interest in bus safety, public transport governance and transparency.

This article is based on publicly available information, material disclosed to me by the Department for Transport under the Freedom of Information Act and my analysis of publicly available BODS compliance information.

It does not disclose confidential information belonging to my employer or any other operator, and it should not be read as making an allegation of non-compliance against any individual bus company.

My concern is with the national regulatory framework and the evidential safeguards that should accompany greater use of digital enforcement.


For several years I have argued that Britain's bus industry needs better data, greater transparency and stronger accountability.

I have campaigned for Local Transport Authorities and Combined Authorities to collect and publish meaningful bus-safety information.

I have argued for independently audited safety data, confidential reporting for workers and stronger scrutiny of the systems governing bus services.

So I am certainly not opposed to data-led regulation.

Quite the opposite.

Good data can expose poor performance, identify recurring problems, improve passenger information and help regulators intervene where operators genuinely fail to meet their responsibilities.

But there is another side to that argument which becomes increasingly important when information systems begin to be used not merely to help passengers or analyse networks, but potentially as evidence in regulatory enforcement.

If data are powerful enough to contribute to enforcement action, they must also be reliable enough to withstand scrutiny.

That is why two Freedom of Information responses I received from the Department for Transport on 16 November 2026, together with a major consultation now being undertaken by the Senior Traffic Commissioner, deserve wider attention across the bus industry.

BODS is moving beyond passenger information

The Bus Open Data Service — BODS — requires operators to publish information including timetables, fares and vehicle-location data.

That information supports journey planners, passenger information systems and real-time applications.

But BODS is increasingly developing another role.

It is becoming part of the regulatory evidence system.

The Senior Traffic Commissioner is currently reviewing the national guidance governing local bus service performance.

The consultation specifically asks whether BODS data could be used to assess operator reliability without the traditional corroborating monitoring exercise.

That is a significant change.

Traditional punctuality investigations can involve physical monitoring of a sample of journeys.

That is resource intensive and inevitably limits the number of cases regulators can examine.

BODS potentially gives DVSA and the Office of the Traffic Commissioner access to information covering much larger proportions of an operator's network.

There are obvious benefits.

It could expose persistent poor performance much more quickly and allow regulatory resources to be targeted where they are genuinely required.

But replacing roadside monitoring with digital evidence does not remove the need for safeguards.

It changes what those safeguards need to look like.

What DfT has now disclosed

In March 2026 I submitted Freedom of Information requests to the Department for Transport concerning BODS.

One asked how DfT monitors operator compliance.

DfT eventually confirmed that it uses a combination of:

  • automated technical checks;
  • analytical monitoring;
  • reporting;
  • engagement with operators; and
  • escalation for regulatory enforcement where appropriate.

The historic material disclosed with the response is particularly interesting.

An enforcement working group involving DVSA and representatives connected with the Traffic Commissioner system considered when failures should trigger investigation, assessment or warnings.

One document states:

“Bus Open Data will currently be an indicator of non-compliance.”

The word indicator is important.

An indicator tells a regulator that something may require investigation.

It should not automatically be equated with a final determination that a statutory breach has occurred.

The same historic reporting acknowledged that registration issues could affect the compliance picture.

That is not an argument that BODS is unreliable.

It is recognition of the reality of complex operational datasets.

Bus registrations change.

Timetables change.

Services can be seasonal.

Operators use different suppliers and systems.

Identifiers must be reconciled between registration systems and published feeds.

A mature regulatory system needs to understand those relationships.

DfT is developing a much more data-led enforcement model

My second FOI concerned how BODS is used by Local Transport Authorities, regulators and Combined Authorities.

DfT disclosed an internal July 2026 paper entitled:

“DVSA: Enhancing Bus Punctuality Monitoring and Enforcement.”

The paper describes a move towards a considerably more proactive and data-led system.

DVSA is expected increasingly to use BODS and ABODS analysis to:

  • identify underperformance earlier;
  • reduce reliance on complaints;
  • enable more targeted intervention;
  • develop remote enforcement capability;
  • make greater use of data-led evidence;
  • introduce intervention and escalation protocols; and
  • improve referrals to Traffic Commissioners.

DfT has allocated funding across the 2026–29 Spending Review period to support the programme.

I have no objection to that direction in principle.

Indeed, properly implemented, it could considerably improve bus regulation.

But one sentence in the paper deserves particular attention.

It says funding supports remote enforcement capability:

“but not sole use of remote data for enforcement.”

That strikes me as an important safeguard.

The question now is what that means operationally.

What does “Requires Attention” actually mean?

My interest increased when I examined a DfT BODS compliance dataset in detail.

The dataset contained 15,063 rows.

After identifying the active in-scope service rows appropriate for a present-state analysis, I identified 9,125.

Of those:

  • 7,632 showed timetable publication;
  • 7,303 showed AVL publication;
  • 6,467 showed fares publication.

At the same time, 4,720 service rows were marked “Requires Attention”.

That figure requires careful interpretation.

It would be wrong simply to say:

“More than half of bus services have failed BODS.”

That is not what the data establish.

Approximately 1,880 of the service rows marked “Requires Attention” showed timetable, AVL and fares information as published.

The attention flag can therefore reflect matters beyond complete non-publication.

Examples appearing within the dataset include:

  • timetable look-ahead;
  • timetable timeliness;
  • data-quality observations;
  • AVL-to-timetable matching;
  • fares compliance;
  • registration reconciliation; and
  • other technical conditions.

That is precisely why terminology matters.

“Requires Attention” is not automatically synonymous with “proven statutory breach”.

One underlying condition can produce many service-row flags

A further feature of the dataset illustrates why raw totals must be handled carefully.

I identified a group of dozens of service rows belonging to the same operator which were all marked “Requires Attention”.

However, the relevant timetable was published, fares were published and compliant and almost all of the services showed AVL publication.

The common issue arose from a shared timetable dataset which did not provide the complete future look-ahead period expected by the compliance report.

One underlying dataset condition therefore generated a large number of individually flagged service rows.

I am deliberately not identifying the operator because the policy point does not depend upon doing so.

The important evidential principle is:

A service-row count is not necessarily a count of independent failures.

And neither is automatically the same as a count of proven statutory breaches.

That does not mean the underlying requirement should be ignored.

It means the data should be interpreted correctly.

Matching and reconciliation matter

I also identified examples in the public data where compliance information and downstream BODS-derived passenger information appeared to require further reconciliation.

There can be several legitimate technical explanations for an apparent discrepancy.

For example:

  • publication may have changed between snapshots;
  • a new variation may need reconciliation;
  • identifiers may have changed;
  • cached information may remain downstream;
  • or different systems may be examining different aspects of the same service record.

I do not believe it would be responsible to use such examples publicly to accuse an individual operator of wrongdoing.

The lesson is the opposite.

Where data sources appear inconsistent, investigate before concluding.

That principle protects everybody:

passengers;

responsible operators;

regulators;

and ultimately public confidence in enforcement.

This is not an argument against enforcement

Operators which persistently refuse to comply with statutory obligations should face regulatory action.

The Senior Traffic Commissioner is right to distinguish the most serious cases — for example where no statutory information is published and an operator refuses to engage with the available support.

Responsible operators invest resources in compliance.

They should not be disadvantaged by businesses which simply ignore legal requirements.

My concern is therefore not whether BODS should be enforced.

It should.

The issue is ensuring that the evidence used to establish a breach actually demonstrates the breach alleged.

That becomes particularly important where financial sanctions can potentially be calculated by reference to every vehicle authorised on an operator's licence.

Strong enforcement requires strong evidence.

Digital enforcement does not need to mean roadside enforcement

None of this means recreating an old-fashioned monitoring system simply for the sake of it.

There is no reason every regulatory case should require someone physically standing beside a road with a clipboard.

Digital evidence can be better evidence.

But before an automated result becomes a regulatory allegation, a robust system should be capable of answering straightforward questions:

Which registered service is involved?

Which BODS dataset has been matched to it?

Which specific rule triggered the adverse status?

What did the system show at the relevant point in time?

Is there a known data-quality or matching issue?

Was the apparent problem temporary or persistent?

Was the operator notified?

What explanation was provided?

Did a human reviewer verify the evidence before enforcement action followed?

Those safeguards do not frustrate enforcement.

They strengthen it.

Why historical records matter

DfT also told me that it does not retain historic copies of its downloadable overall compliance report.

That raises another legitimate policy question.

If persistence is relevant to enforcement, how is persistence evidenced?

A service may be flagged for a brief technical reason and return to compliance.

Another operator may remain non-compliant for months despite repeated intervention.

Those situations are obviously different.

There may be other systems — databases, supplier records, audit logs or case-management histories — which preserve the necessary information.

I am currently seeking greater clarity about that.

The principle is simple:

if historical compliance affects regulatory decisions, the evidence demonstrating that history should be capable of being reproduced.

This connects with a much wider bus-safety argument

For years I have argued for better bus-safety information nationally.

My concern has never been simply to collect more figures.

It is to:

collect the right data, define it consistently, preserve it, audit it, publish it appropriately and use it to improve the system.

That principle sits behind my work on Local Transport Authority safety reporting.

It sits behind proposals for independent auditing of safety information.

It sits behind campaigns for confidential safety reporting.

And it sits behind my wider examination of how safety is governed as increasing responsibility moves towards Local and Combined Authorities.

BODS should be treated according to the same principle.

More data do not automatically create better accountability. Well-governed data do.

The Senior Traffic Commissioner wants to hear from the industry

This is not simply an academic discussion.

The Senior Traffic Commissioner is currently consulting on major changes to the guidance governing local bus service punctuality, BODS compliance, Local Transport Authority responsibilities and franchising.

The consultation was published on 17 September 2026 and closes on 11 December 2026.

It is open to operators, local authorities, industry stakeholders and individuals who have relevant evidence or experience.

Among other matters it asks about:

  • the existing 95% punctuality standard;
  • reasonable excuses for poor performance;
  • realistic timetables;
  • Local Transport Authority network management;
  • BODS non-compliance and penalties;
  • whether some BODS cases can be decided without a public inquiry; and
  • whether BODS can be used to assess performance without the traditional corroborating monitoring exercise.

I have submitted my own detailed personal response.

I would encourage others with genuine operational, passenger, regulatory, workforce or technical experience to read the consultation and submit their own views.

Official consultation information and all questions:

https://www.gov.uk/government/consultations/local-bus-service-performance-standards-consultation/local-bus-service-performance-standards-consultation

Responses can be emailed to:

tccoconsultations@otc.gov.uk

The closing date is:

11 December 2026

The Senior Traffic Commissioner expressly says contributors do not have to answer every question if some are outside their experience.

That makes this a genuine opportunity for drivers, operators, unions, local authorities, technology specialists, accessibility groups and passengers to contribute evidence from their own perspective.

A major opportunity — if we get it right

I believe BODS can become one of the most important tools available to modern bus regulation.

It could identify poor performance earlier.

It could allow regulators to look across entire networks rather than tiny samples.

It could improve passenger information.

It could help responsible operators identify problems before they become regulatory cases.

And it could make enforcement more consistent.

But increased regulatory power must be accompanied by increased evidential discipline.

Operators should know how they are being assessed.

Regulators should be able to reproduce the evidence upon which decisions are based.

Relevant historical information should be preserved.

Known limitations should be documented.

Technical indicators should be distinguished from final regulatory findings.

And anybody facing regulatory action should have a meaningful opportunity to understand and challenge the evidence.

DfT's own internal paper appears to recognise that principle by stating that its emerging approach is not based upon the sole use of remote data for enforcement.

That safeguard now needs to survive the transition from policy document to everyday regulatory practice.

This is not about protecting poor operators from enforcement.

It is about ensuring that when enforcement occurs, the evidence is strong enough that operators, regulators and the public can trust the outcome.

BODS is about to become much more powerful.

That makes the question of who checks the data more important than ever.


This article represents my personal views. It is based upon publicly available information and information released under the Freedom of Information Act. It does not represent the views of my employer, and no confidential employer information has been used.


Comments

Popular posts from this blog

Who Is Taking Responsibility for the Tomatopia/Senapt Collapse — And Who Will Stop This Happening Again?

RMT AGM Backs Emergency Motion on Bus Driver Heat Safety — Now the Reality Is Already Hitting Home

50 Years of Data Shows Bus Workers Face Higher Death Risks — This Is a Bus Safety Issue