Transport for London – A Guide to Using TfL as a Source for Transit, Street and Service‑Quality Reporting

Transport for London (TfL) is the integrated transport authority for Greater London, responsible for the Tube, buses, trams, Docklands Light Railway, London Overground, Elizabeth line, London River Services, roads, cycling infrastructure and the congestion charge zone. For anyone reporting on London’s urbanism, housing, public realm or transport policy, TfL’s official website and its open‑data platform are the primary sources of authoritative, regularly updated information.

This reference page explains how to navigate TfL’s public resources, what data you can find and how to use it for street‑level, network‑wide and service‑quality reporting. It is not a replacement for the official site but a guide to getting the most out of it.

What the TfL website offers

The main TfL website at tfl.gov.uk is the public face of the authority. It provides journey‑planning tools, live departure boards, service status alerts, maps, fares, travel advice, and corporate information including board papers, Annual Reports, Business Plans and the Mayor’s Transport Strategy.

For reporters and researchers, the most useful sections are the Status & disruptions page (which shows current issues on every mode), the Maps section (including the Tube map, bus spider maps, cycling maps and walking maps) and the Corporate area where long‑term plans, consultation documents and performance data are published. The site is updated in real time for travel alerts and at least quarterly for performance statistics.

TfL Open Data – a deeper layer

The TfL Open Data portal (tfl.gov.uk/info-for/open-data-users/) is the engine behind most third‑party transport apps and many internal analyses. The portal provides:

• Unified API – live feeds for Tube, bus, DLR, Overground, Elizabeth line, tram, river and cable car. Data includes vehicle positions, arrival predictions, service disruptions and line status.
• Route and timetable data – GTFS (General Transit Feed Specification) feeds for all modes, updated every time a timetable changes.
• Road network data – Traffic flow, congestion, road works, cycle counters and street‑level datasets such as footfall counts and road surface conditions.
• Bike‑share (Santander Cycles) data – Real‑time station occupancy, trip history and availability.
• Station and stop data – Coordinates, accessibility information, step‑free access status, entrance locations and interchange details.
• Historical performance – Archived datasets on service reliability, punctuality and customer satisfaction.

The data is free to use under an Open Government Licence, but you must create an account and accept the terms of use.

How to use TfL resources for street and service‑quality reporting

Journalists and urbanism researchers can draw on TfL data in several ways:

1. Live service monitoring – The Status & disruptions page and the Unified API give minute‑by‑minute updates on delays, closures and planned works. This is essential for real‑time reporting on incidents, but also for building a picture of chronic reliability issues over time.

2. Street‑level analysis – TfL’s road‑network API provides average speeds, traffic counts and congestion data. Combined with the Cycling and Walking data, you can assess how road space is used, where cycle lanes are most effective, and where pedestrian safety or air quality is a concern.

3. Accessibility and inclusion – The station data includes step‑free access, lift availability and audio‑visual information. Reporting on the gap between policy commitments and actual conditions can be supported by cross‑referencing the open‑data feeds with TfL’s published accessibility plans.

4. Performance benchmarks – TfL publishes quarterly and annual reports on customer satisfaction, asset reliability (e.g. escalator downtime, signal failures) and financial performance. These are available in the Corporate section. For a quick overview, the “Performance” pages on the main site show key metrics.

5. Mapping and visualisation – The open‑data feeds are designed to be consumed by developers, but anyone with basic GIS skills (or using tools like QGIS, Mapbox or Google Looker Studio) can import the GTFS or GeoJSON data to produce custom maps showing, for example, bus route frequency, Tube station coverage or traffic‑speed hotspots.

Table of key data types and their uses

Practical tips for getting started

• Bookmark the data pages. The Open Data user page explains how to request an API key and which feeds are available. Keep a link to the TfL Open Data community forum for troubleshooting.
• Use the Status dashboard for history. The site does not offer a public historical archive of disruptions, but you can scrape the live feed or use the “Status updates” section (which shows recent events) to build a short‑term record.
• Combine TfL data with other sources. For a fuller picture, cross‑reference TfL data with the Department for Transport’s road traffic statistics, Transport for London’s own Travel in London reports, and local authority (borough) transport plans.
• Check the licence. Most TfL open data is under the Open Government Licence v3.0, which allows reuse with attribution. Always credit TfL as the source.
• Verify with the official site. If a data point looks unusual or a service status is critical, confirm it on tfl.gov.uk before publishing. The API is robust but can occasionally lag.

Sources and limits

This reference page is based entirely on information published by Transport for London. The official website and open‑data portal are the authoritative sources for all data mentioned. Because TfL updates its services, performance targets and datasets frequently, readers should always verify the latest information on the following pages:

• Transport for London: https://tfl.gov.uk/
• TfL Open Data: https://tfl.gov.uk/info-for/open-data-users/

No specific dates, project statuses, funding amounts or legal requirements have been stated here because they may change. This guide is a starting point, not a substitute for consulting the primary sources.