Why do Operators push back when you ask for their data?
An Operator’s objection to a broad data clause may arise because the Authority has not specified what it needs or how it will handle it.
People search for
In this article
“The Operator shall provide all data reasonably required” is a familiar line in a draft contract agreement. It is ambiguous. In negotiations we have supported, treating every objection as resistance has rarely improved a schedule. The Authority must establish whether the Operator is avoiding a necessary obligation or whether it has left the request unscoped.
A detailed cost breakdown may be commercially sensitive. A legacy ticketing system may require development work to produce the requested extract. Individual journey records may contain personal data. The Authority must test each point. Without a defined request, the Operator cannot reliably estimate the work, price the risk or establish a repeatable report.
Start with the decision
Set out the decision before listing the dataset. An Authority monitoring an Enhanced Partnership may require cancellation, punctuality and mileage reports at agreed intervals and in an agreed format. For a fare or network initiative, it may also require aggregated ticket sales or passenger-demand data. Those needs do not justify a request for every transaction, customer contact record and element of the Operator’s cost base.
State the fields, level of detail, frequency, format or standard, quality checks, recipients and permitted use in the schedule. Identify each requirement as either a standing obligation or an ad hoc request. The Operator and its Suppliers can then locate the data, and the Authority can check what is supplied.
Detailed journey, account or complaint data should be discussed separately. Journey histories described as de-identified may still be personal data if other information could identify an individual.
Before sharing such material, the Authority and Operator should agree the purpose, lawful basis, access controls and retention period. They should establish whether one party processes information for the other or whether both decide how it will be used. Aggregated or genuinely anonymous reporting may answer the operational question without sharing passenger-level records.
Match the request to the operating arrangement
There is a statutory baseline for local bus information in England outside London. For services in scope, timetable, vehicle-location and fares data must be published through the Department for Transport’s Bus Open Data Service. The Operator normally publishes this data. In a franchised area, the Local Transport Authority has that role.
Data requirements beyond that baseline depend on the agreement. An Enhanced Partnership usually leaves commercial service revenue with the Operator, although supported services may differ. In franchising, the Authority determines the services and Operators run them under contract. Revenue risk may be allocated differently. Under a net-cost contract, the Operator can retain at least part of the fare revenue and bears real operating risk.
| Operating arrangement | Data an Authority will commonly need | Where scope often needs care |
|---|---|---|
| Enhanced Partnership | Open-data compliance evidence; agreed punctuality, cancellation and mileage reports; data needed for a defined partnership commitment | Detailed costs, transaction-level ticketing and customer records need a stated purpose and should not be routine requests |
| Franchised services | Contract performance, service delivery and asset information; revenue and settlement data where required by the contract | Financial detail should follow the payment and revenue-risk provisions, including any net-cost arrangement |
Scope should follow the decision. A franchising Authority reconciling revenue or paying against operated mileage needs an auditable trail. An Authority assessing whether an agreed bus-priority measure is helping may need less data.
Test the objection, then decide
When an Operator says it cannot provide a dataset, ask which system holds it, whether it exists in another form, how often it can be extracted and what change is required. If it says the data is commercially sensitive, ask which Authority decision requires it, who will receive it and whether a summary or restricted access would suffice. A data-protection objection requires a review of necessity and safeguards.
The Authority should hold its ground where necessary. Evidence needed to check a payment, a performance requirement or a legal publishing duty must still be supplied when it is inconvenient to provide. Where the Authority seeks a reporting capability that does not exist, it should expect to fund or phase the requirement. A weekly report that relies on a manual spreadsheet and one member of staff should be identified before award.
Useful questions
Use these questions when reviewing a draft data schedule or an Operator’s response:
- What specific Authority decision, payment check or passenger outcome does each dataset support?
- Have we stated the fields, frequency, format, quality threshold, recipients and permitted use clearly enough that the Operator can price and deliver the requirement?
- Which information is required under bus open-data rules and who is responsible for publishing it in our area?
- Does the requested financial and ticketing data match the contract’s allocation of revenue, payment and operating risk?
- If the data contains personal information, have we agreed a proportionate purpose, access arrangement and retention period?
More on Data & Governance