
Guideline 26 asks governments to keep the public involved after an open data policy passes, gathering feedback on data quality, selection, formats and usability, and formally considering it when the policy is reviewed.
Public input shapes many open data policies before adoption. This guideline is about what happens afterward, when the people using the data are best placed to say what is working.
What the guideline means
Residents, journalists, researchers and developers are the main users of open data, and they quickly discover missing fields, stale datasets and confusing formats. Guideline 26 asks open data policies to create meaningful, ongoing channels for that feedback, covering data quality, quantity, selection and format, as well as the usability of the portal itself.
Feedback should not disappear into an inbox. The guideline recommends that it be formally considered when the policy is reviewed (Guideline 31) and that it inform prioritization (Guideline 5).
Model policy language patterns
Common paraphrased forms:
- The portal shall include a mechanism for the public to request datasets and comment on published data.
- The oversight body shall solicit public input on priorities and report how that input was used.
- The city shall hold public meetings, workshops or events to engage data users.
- Annual reports shall summarize public requests and the city's responses.
Where it appears in adopted policies
Participation language is widespread in this index. Examples include:
- Memphis, TN (2009), an early order that connected online services with citizen engagement.
- Montgomery County, MD (2012), which provided for public input; the county also held an open data town hall.
- Philadelphia, PA (2012), Chicago, IL (2012) and Madison, WI (2012).
- Oakland, CA (2013), Los Angeles, CA (2013), Boston, MA (2014) and Washington, DC (2014).
- Jackson, MS (2015), Tulsa, OK (2015), Saint Paul, MN (2016) and Milwaukee, WI (2016).
Common pitfalls
- Feedback forms with no response. Requests that are never answered teach users not to bother.
- Hearing only the usual voices. Online comment favors people already comfortable engaging government; outreach to neighborhoods and community groups broadens it.
- One-off hackathons. Events build enthusiasm but do not substitute for a standing channel.
- No link to decisions. If public input never visibly changes priorities, participation is decorative.
- Ignoring internal users. City staff in other departments are heavy users of open data too, and their feedback on gaps and errors is often the most specific.
A practical checklist for participation provisions
- Provide a dataset request form and a comment channel on every dataset page.
- Commit to responding to requests within a stated period, including explanations when requests are declined.
- Reach beyond online channels through community meetings and partnerships with local organizations.
- Include public members on advisory bodies where appropriate.
- Summarize public input and the government's response in the annual report.
- Feed participation results into prioritization and policy review.
What participation teaches about the value of operational data
Open data programs learn what is valuable by listening to users. The private-data market works the same way: what a dataset is worth depends on what buyers actually need, which is not always what the data owner expects. A plumbing contractor's job logs may matter more to a model builder for their timing and parts patterns than for their revenue figures.
Before investing effort in cleaning or packaging data, it pays to hear from the demand side. Get a bid is a low-effort way to learn which parts of your operational data buyers care about, and how to value my data explains the factors behind those preferences.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
How can residents give feedback on a city's open data?
Most portals provide dataset request forms, comment features or contact links for each dataset. Some cities also hold public meetings, advisory boards with community members, or events where residents and developers work with city data and report gaps.
Why isn't public demand the only way to prioritize data?
Relying solely on public requests can amplify the preferences of people already engaged with government. Guidelines recommend balancing demand with accountability value, cost and policy relevance, and proactively reaching communities less likely to submit requests.
Should feedback be published?
Publishing a summary of requests and responses, often in an annual report, shows that input is taken seriously and lets the public see why some requests were declined, for example because of privacy or cost.
Policies in the index that reflect guideline 26
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Memphis, TN | Oct 10, 2009 | Executive order (No. 01-2009) | 23212627 |
| San Francisco, CA | Oct 29, 2010 | Ordinance | 47811182526 |
| Washington, DC | Jan 3, 2011 | Mayor's memorandum | 122630 |
| Providence, RI | Mar 19, 2012 | Resolution | 31824262729 |
| Philadelphia, PA | Apr 26, 2012 | Executive order (No. 1-12) | 34578182224 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Oakland, CA | Oct 15, 2013 | Council resolution (No. 84659) | 2345781011 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Los Angeles, CA | Dec 18, 2013 | Executive directive (No. 3) | 37818222630 |
| Boston, MA | Apr 7, 2014 | Executive order | 3891318202425 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Cincinnati, OH | May 29, 2014 | Administrative regulation | 8101122242629 |
| Phoenix, AZ | Jun 18, 2014 | Administrative policy | 13726 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Minneapolis, MN | Aug 1, 2014 | Council-adopted policy | 34568131819 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| Denton, TX | Feb 9, 2015 | Administrative directive | 357811121618 |
| Suffolk County, NY | Jul 31, 2015 | Administrative policy | 78131820222426 |
| 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 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| Seattle, WA | Feb 26, 2016 | Executive order | 17242627 |
| Baltimore, MD | Mar 7, 2016 | Ordinance | 1781113182426 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
| Fort Collins, CO | Feb 7, 2017 | Council resolution | 12345678 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
Sources
Updated December 31, 2024.