With responsibility for 10 billion journeys and an annual budget of £9bn we are a complex organisation which publishes a huge amount of data on a range of subjects including contracts, expenditure, how reliable our services are, customer satisfaction, journey data, and our financial performance. This data helps people understand how we run London's transport network, and how we spend the money raised through fares and taxes.
Openness and transparency is helping to transform the way we operate. It strengthens our relationships with customers and stakeholders, and raises awareness of how we can work with local communities and businesses to improve our services.
Also, this information enables innovation in the way our customers travel, with our data feeds leading to the development of a number of smartphone apps to help people get around the Capital. Transparency also helps us drive efficiency across the business.
By being open and accountable we:
This information is in line with the Code of Recommended Practice issued by the Department for Communities and Local Government in September 2011.
As part of our continuing commitment to openness and transparency we are identifying additional information to publish. We will be making some new operational and performance information available in the coming weeks, as well as updating the information we publish in line with the Code of Recommended Practice. We are now publishing all expenditure of more than £250 allowing even greater scrutiny of how money is spent, the previous reporting threshold was £500.
Since July 2012, we have been publishing contracts over the value of £10million. This threshold has also been lowered so that all contracts with a value above the appropriate OJEU threshold entered into as a result of an Invitation to Tender issued after 1 September 2013 will be published within 20 days of being signed. Older contracts will be published on request and any contract announced in a press release will also be published in full. From early next year we will launch a contracts webpage with a new searchable function to enable people to locate the contract they are interested in.
Find out about us and how the organisation is run including key governance information on meetings of the Board, its Committees and Panels, TfL's Standing Orders, our Annual Reports, legislative framework and company structure.
You can how our business is structured in our organisation chart.
The pay multiple (the ratio between the highest paid salary and the median average salary) for TfL and Tube Lines in 2011/12 was 8.14. The pay multiple for TfL and Tube Lines in 2012/13 was 7.79.
See details of offers to TfL staff of tickets to London 2012 Games events and related hospitality.
We publish contracts on the contracts finder website.
Details of contract opportunities can be viewed in our eTendering site.
Capital & Counties Properties PLC and TfL have established a joint venture, Earls Court Partnership Limited, which will enable the development of Earls Court 1 and 2 in line with the Earls Court Masterplan. See the Earls Court transaction documents. A report into the feasibility of moving the activities at Lillie Bridge Depot has been completed. See the Lillie Bridge Depot Feasibility report.
We allocate money to the London boroughs to spend on projects which support the Mayor's Transport Strategy through a Local Implementation Plan.
We publish a report every quarter with updates on how well our services are operating and how we are performing financially. See reports on our finances and the performance of our services.
We also publish operational and performance data that we are regularly asked about, including:
We carry out regular audits of our activities and, where issues are found, actions are agreed to address them. See our final internal audit reports.
Please see the Property Asset Register for mapping information about TfL's land ownership.
We receive many Freedom of Information (FOI) requests which ask for the same information, so to help people access this data more easily we will be proactively publishing information that we get regular requests for. This information can be found in Finance, operations and performance.
We also publish our performance figures for FOI so you can see how we are doing in responding to the many requests we receive.
To make a request for information please write to us, detailing the information you want and giving an address for our response. You can apply by post or email to:
We deal with requests as quickly as possible and within the FOI Act's statutory timescales.
Sometimes we have to pass requests to partner organisations within the Greater London Authority for some or all of the information. We will let you know if this happens.
Find out more about the FOI requests we get and our performance in responding to them.
Many of the FOI requests we receive are made through an external website, What Do They Know, where you can view requests, and our replies, or make an FOI request to us yourself.
Information about planned lift and escalator works and the planned works calendar can be found in Status updates.
We publish working timetables which are the rail industry version of public timetables. They show all movements on the Tube network including empty trains and train movements in and out of depots. They include identification codes for each train, times at locations other than stations (eg junctions).
Short summaries of our complaints data for Q3 (2012/13) and Q4 (2012/13) can be found in our quarterly progress reports and detailed summaries of our complaints data can be found in our Operational and Financial Performance report from Q1 (2013/14) onwards.
You are encouraged to use and re-use the information made available through this page, freely and flexibly, with only a few conditions. These are set out in the Open Government Licence for public sector information.
Please note that the Open Government Licence conditions do not apply to the information also made available to open data users. This information is subject to the Transport data service terms & conditions and Syndication Developer Guidelines.