
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:
- Portland, OR (2009), whose resolution called for agreements with regional partners to publish open datasets and for promoting Portland as a host for open source events.
- Philadelphia, PA (2012), Louisville, KY (2013), Los Angeles, CA (2013) and San Francisco, CA (2013).
- Boston, MA (2014), Hartford, CT (2014), Nashville, TN (2014), Pittsburgh, PA (2014) and Washington, DC (2014).
- Cambridge, MA (2015), Jackson, MS (2015), Milwaukee, WI (2016), New Orleans, LA (2016) and Fort Collins, CO (2017).
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.
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
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Portland, OR | Sep 30, 2009 | Council resolution | 37810162230 |
| Washington, DC | Jan 3, 2011 | Mayor's memorandum | 122630 |
| Philadelphia, PA | Apr 26, 2012 | Executive order (No. 1-12) | 34578182224 |
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Los Angeles, CA | Dec 18, 2013 | Executive directive (No. 3) | 37818222630 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Boston, MA | Apr 7, 2014 | Executive order | 3891318202425 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 12345678 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Asheville, NC | Oct 13, 2015 | Council resolution | 13489101118 |
| Durham, NC | Nov 23, 2015 | Administrative policy | 7818192430 |
| San Jose, CA | Apr 5, 2016 | Council policy | 1681113182230 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| New Orleans, LA | Sep 1, 2016 | Executive order (MJL 16-01) | 124511182124 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
| Fort Collins, CO | Feb 7, 2017 | Council resolution | 12345678 |
Sources
Updated December 31, 2024.