There are three elements to gathering the necessary data. The first is creating the data in the first place. Then comes the need to access the data which might be stored across other governmental departments and private sector suppliers. Finally there is the need to collect the data, which is the act of gathering, storing and using the data.

Governments like the private sector, are increasingly becoming aware of the value of data and the accumulation, linking and usage of datasets from across the public and private sector. Unlike the private sector, however, public procurement is in an advantageous position to influence their datasets through the levers of law and mandate.

Ways to create the data include mandates for companies to submit their CO2 emissions as part of the procurement process and to release this information. Governments can be more ambitious still and mandate yearly publication by companies as part of those companies’ other returns such as tax returns and financial account submissions.

This of course raises concerns about the burdens on business for instance around sole traders. These can be alleviated through introducing thresholds for reporting and limiting mandatory reporting to the largest firms or larger contracts. By way of example, mandatory carbon measurement and reporting might only apply to the largest 1000 firms in a country. Mandatory carbon reporting in procurement might only apply to firms bidding on a contract with a value of more than $10m.

Where the same financial data is required by multiple agencies, but no central repository for this data exists, it may be desirable to collect data on suppliers in a central bidders database, so that suppliers can record and post required information once and multiple agencies can use this data when assessing bids.

Data should flow between governmental departments to allow all parties the information they need to better serve their public. The way this is typically achieved is through data sharing agreements between departments, where both departments agree to share defined data.

One example of this is a registry of public bodies held by a Ministry of Finance or Ministry of Public Administration that is shared between other governmental departments or even openly published. Such a list would make inter-departmental spending and communications easier because there is a canonical reference to a body certified by that Ministry. Such a registry would also make data sharing agreements between departments easier to achieve. This is because there are two defined bodies making a commitment to share data with each other.

A data sharing agreement in place would reduce the need for administration and negotiation around sharing data between parties for each and every instance of data transfer. At the most optimal form, a cross department data sharing agreement organised by a Ministry of Public Administration reduces the need for multiple data sharing agreements and the administration around this.

Of course, the easiest way, especially for datasets around Sustainable Public Procurement, is to release this information openly so that departments and even regions or states can access this data

It is not uncommon for a Government to hold their data on private sector hosted systems, for instance e-procurement portals. In order for data to be usable and analysable, it is important that the governments that rely on these solutions have unfettered access to the data and that the license rights belong to the government in question. This is because a tender notice from a buying authority that is legally owned by a third party creates liability issues with real cost implications for that body later on. If a government analyses data around procurement it needs to be without limitations to access of the data, and the threat of cost claims from suppliers. Open licensing and open identifiers get around this issue as these can be shared and reused without limitation.

Public sector organisations around the world all create rich datasets whether its data on cities, taxation, companies or procurement. This can take many forms, whether from excel spreadsheets to servers hosted on site to cloud storage.

Access cases can depend from department to department and even country to country, ranging from a SQL analyst make queries from across datasets to APIs feeding into a central data repository to a mixture of these. Regardless, the important point is for the data cleaned and standardised in one place to allow meaningful analysis of the data and create evidence based policy and action.