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

Public Participation: Open Data Policy Guideline 26

Public Participation: Open Data Policy Guideline 26

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:

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.

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

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

PlaceAdoptedInstrumentGuidelines
Memphis, TNOct 10, 2009Executive order (No. 01-2009)23212627
San Francisco, CAOct 29, 2010Ordinance47811182526
Washington, DCJan 3, 2011Mayor's memorandum122630
Providence, RIMar 19, 2012Resolution31824262729
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
Madison, WIAug 15, 2012Ordinance457810111318
Chicago, ILDec 10, 2012Executive order34678101113
Montgomery County, MDDec 17, 2012County legislation (Bill 23-12, Open Data Act)457811131822
San Francisco, CAMar 28, 2013Ordinance34578101118
Austin, TXAug 26, 2013Administrative memo123457810
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
Honolulu, HINov 27, 2013Ordinance237810111820
Los Angeles, CADec 18, 2013Executive directive (No. 3)37818222630
Boston, MAApr 7, 2014Executive order3891318202425
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Cincinnati, OHMay 29, 2014Administrative regulation8101122242629
Phoenix, AZJun 18, 2014Administrative policy13726
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
Denton, TXFeb 9, 2015Administrative directive357811121618
Suffolk County, NYJul 31, 2015Administrative policy78131820222426
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Tulsa, OKDec 21, 2015Executive order123458910
Seattle, WAFeb 26, 2016Executive order17242627
Baltimore, MDMar 7, 2016Ordinance1781113182426
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Saint Paul, MNApr 27, 2016Council resolution12578101113
Milwaukee, WIJul 14, 2016Council resolution12356789
Naperville, ILNov 15, 2016Council resolution45789101112
Fort Collins, COFeb 7, 2017Council resolution12345678
Knoxville, TNMay 2, 2017Executive order14578111319

Sources

  1. Sunlight Foundation Open Data Policy Guidelines (historical reference)
  2. Montgomery County: Open Data Town Hall (press release)
  3. OpenDataPhilly: Open Data Race

Updated December 31, 2024.