Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Guidelines / Open data policy guideline 06
Open data policy guideline 06

Outside Services: Open Data Policy Guideline 6

Outside Services: Open Data Policy Guideline 6

Guideline 6 asks that an open data policy reach data held by contractors, vendors and quasi-governmental bodies, so outsourcing a service never means the public loses access to its own information.

What the guideline covers

Governments rely on vendors to run software, process payments, operate transit systems and conduct research. If an open data policy only reaches data stored on government servers, every outsourced function becomes a blind spot. Guideline 6 says the public should keep access to information gathered with public money or public authority, regardless of who manages it.

The same reasoning extends to quasi-governmental bodies such as regional authorities, government-sponsored entities and publicly funded institutions.

How policies typically phrase it

  • A requirement to add open data clauses to new technology contracts and renewals.
  • Language giving the government rights to raw data a vendor creates or stores on its behalf, in a usable format.
  • A definition of "agency" or "department" broad enough to include boards, authorities and commissions.
  • Procurement guidance favoring systems that can export data in open formats.

Places whose policies adopted it

Chicago's 2012 executive order directed the city to develop contract provisions promoting open data in technology procurements. Houston's 2014 administrative policy asks legal staff to ensure new contracts and renewals make vendor-held raw data available in an agreed format. Minneapolis's 2014 ordinance applies contract provisions to appropriate IT procurements awarded after January 1, 2015.

Other tagged examples include Cambridge, Pittsburgh, Milwaukee and Washington, DC (2014).

Common pitfalls

  • Applying only to new contracts, leaving long-running vendor relationships untouched for years.
  • Rights without formats. A contract that grants ownership but not export in a usable structure leaves data locked in a proprietary system.
  • Forgetting affiliated bodies, such as transit or housing authorities, where much high-value data lives.

Contract clauses worth including

When an open data policy reaches into procurement, the contract language usually addresses a few recurring points:

  • Ownership: data created, collected or maintained for the government belongs to the government.
  • Export: the vendor must provide complete, documented exports in an open, machine-readable format on request and at contract end.
  • Publication support: where appropriate, the system should be able to publish directly to the open data portal or through an API.
  • Privacy and security: the vendor follows the government's rules on protected information.
  • Transition: data must be handed over in usable form if the contract is not renewed.

These clauses are far easier to negotiate before a contract is signed than afterward. They also protect the government from lock-in, since a system whose data can be exported cleanly is a system that can be replaced.

Why this matters for your business data

The private-sector version of this lesson is about your software vendors. Much of a company's operational data sits inside SaaS tools: accounting, scheduling, point of sale, field service. Whether you can export it cleanly, and whether your contracts let you use it, determines whether it can become an asset.

See sell my data for the systems we commonly work with and de-identified data for how exports are prepared. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

Do open data policies apply to government contractors?

Policies that follow this guideline extend to data a vendor creates or stores for the government, usually through contract clauses in new procurements and renewals. Without such clauses, outsourced data often stays out of reach.

What is a quasi-governmental agency in this context?

Bodies such as regional authorities, transit agencies, government-sponsored entities and publicly funded institutions that perform public functions but sit outside the core city or county structure.

Why do procurement rules matter for open data?

The systems a government buys determine whether data can be exported in open formats. Procurement language is the cheapest point at which to secure data rights and export capability.

Policies in the index that reflect guideline 6

PlaceAdoptedInstrumentGuidelines
Chicago, ILDec 10, 2012Executive order34678101113
Hennepin County, MNOct 23, 2013Resolution of support (MetroGIS Policy Board)1236
Pittsburgh, PAMar 19, 2014Ordinance12345678
Chattanooga, TNMay 31, 2014Executive order123467810
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Seattle, WAFeb 1, 2016Administrative policy (CTO policy)14678101112
San Jose, CAApr 5, 2016Council policy1681113182230
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Milwaukee, WIJul 14, 2016Council resolution12356789
Bellevue, WAAug 1, 2016Management policy15678101118
Fort Collins, COFeb 7, 2017Council resolution12345678
Syracuse, NYJul 26, 2017Executive order1456781113

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)
  2. US Digital Services Playbook, Play 13

Updated December 31, 2024.