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 30
Open data policy guideline 30

Partnerships: Open Data Policy Guideline 30

Partnerships: Open Data Policy Guideline 30

Guideline 30 encourages governments to work with nonprofits, universities, businesses, civic technologists and neighboring jurisdictions to expand open data, set priorities, connect datasets and share the workload.

No city publishes data in a vacuum. The most effective open data programs have tended to lean on outside partners for priorities, tools, skills and reuse.

What the guideline means

Partnerships can help with nearly every stage of open data: identifying what residents need (Guideline 5), increasing what is available, and connecting government information with data held by nonprofits, research institutions and nearby governments. They can strengthen civic participation and reveal gaps in service delivery.

The guideline recognizes several partnership forms: formal contracts, informal cooperation, or exchanges of rights and privileges. It also encourages regional cooperation, where neighboring governments agree on common formats and share experience and workload.

Model policy language patterns

Paraphrased partnership provisions:

  • The city shall work with regional partners to publish and maintain shared datasets that are open and freely available.
  • The oversight body shall seek partnerships with academic institutions, nonprofits and the private sector to promote use of public data.
  • The city shall support events and programs that encourage developers and residents to build on open data.
  • The city shall coordinate with neighboring jurisdictions on common standards.

Where it appears in adopted policies

Partnership language is common. Examples in this index include:

Regional examples from the period include civic hack nights and collaboratives such as the Smart Chicago Collaborative.

Common pitfalls

  • Exclusive arrangements. Partnerships that give one company privileged access to public data undermine open access (Guideline 10).
  • Outsourcing accountability. A partner can help publish data, but responsibility should stay with government.
  • Event-only engagement. One-day hackathons without follow-through rarely produce lasting tools.
  • Incompatible formats across neighbors. Regional data sharing fails without agreed standards.

A practical checklist for partnership provisions

  • Authorize the oversight body to pursue partnerships with universities, nonprofits, businesses and neighboring governments.
  • Keep public data open to everyone, even when a partner helps publish or analyze it.
  • Document partnership terms and make them public.
  • Coordinate with neighboring jurisdictions on formats and standards for shared regional data.
  • Support ongoing user communities rather than one-off events alone.
  • Evaluate partnerships during policy review to see which ones produced lasting results.

Why this matters for your business data

Partnerships are also how private operational data reaches the people who can use it. Most businesses do not have the channels to find AI and machine-learning buyers, negotiate licenses or verify de-identification on their own. A structured intermediary process handles those steps while the business keeps control of what leaves its systems.

Like a good public partnership, the arrangement should be non-exclusive where possible, documented and transparent about how data will be used. Sell my data explains the process, get a bid starts it, and the open data policy to data value guide explains the broader parallel.

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

What kinds of partners do open data programs work with?

Common partners include universities and research centers, nonprofits, civic technology groups, local businesses, philanthropic organizations, and neighboring governments. Each brings different strengths, from analysis skills to community reach to shared infrastructure.

Can partnerships conflict with open access?

Yes, if a partner receives exclusive or early access to data that should be public. Good partnership terms keep the underlying data open to all and focus the partnership on capacity, tools or outreach rather than privileged access.

Why do regional partnerships matter?

Residents and businesses cross city lines constantly. When neighboring jurisdictions publish comparable data in common formats, analysts can study regional issues like transit or housing, and smaller governments can share tools and experience.

Policies in the index that reflect guideline 30

PlaceAdoptedInstrumentGuidelines
Portland, ORSep 30, 2009Council resolution37810162230
Washington, DCJan 3, 2011Mayor's memorandum122630
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
San Francisco, CAMar 28, 2013Ordinance34578101118
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Honolulu, HINov 27, 2013Ordinance237810111820
Los Angeles, CADec 18, 2013Executive directive (No. 3)37818222630
Pittsburgh, PAMar 19, 2014Ordinance12345678
Hartford, CTMar 26, 2014Executive order34789182224
Boston, MAApr 7, 2014Executive order3891318202425
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Durham, NCNov 23, 2015Administrative policy7818192430
San Jose, CAApr 5, 2016Council policy1681113182230
Saint Paul, MNApr 27, 2016Council resolution12578101113
Milwaukee, WIJul 14, 2016Council resolution12356789
New Orleans, LASep 1, 2016Executive order (MJL 16-01)124511182124
Naperville, ILNov 15, 2016Council resolution45789101112
Fort Collins, COFeb 7, 2017Council resolution12345678

Sources

  1. Sunlight Foundation Open Data Policy Guidelines (historical reference)
  2. Open Gov Hack Night resources
  3. Smart Chicago Collaborative
  4. Pacific Northwest data resources

Updated December 31, 2024.