
Guideline 5 asks an open data policy to explain how a government will decide which data sets to release first when staff and budget limit how fast everything can be published.
Why prioritization matters
In principle, every public data set should be online. In practice, release happens in stages because staff time and budgets are finite. Guideline 5 asks governments to be transparent about how they will order that work, so the sequence reflects public value rather than convenience alone.
The guideline describes several legitimate inputs: data that supports ethics oversight and accountability; data tied to new laws, rules or policy initiatives; evidence of public demand, measured both by past records requests and by fresh public comment; and cost. It cautions that public comment should not be the only input, since it tends to amplify people who are already comfortable engaging with government.
How policies typically phrase it
- A requirement that an implementation or compliance plan rank data sets for release.
- Named criteria, such as accountability value, public demand, request volume or cost.
- A public mechanism for suggesting data sets, with stated review rules.
- A final deadline by which all public data sets must be online.
Places whose policies adopted it
New York City's 2012 Local Law 11 required agencies to prioritize their public data sets so that all would be on the portal by the end of 2018. Montgomery County required an implementation plan within 18 months that included prioritization; its implementation plan later published a data set scoring method. Denton's 2015 directive gives the public a way to suggest data sets and ranks requests partly by the effort required to produce them.
Other tagged examples include Philadelphia, Houston, Minneapolis and Saint Paul.
Common pitfalls
- Cost as the only criterion, which pushes cheap but low-value data to the front of the line.
- Demand-only ranking, which over-weights the loudest requesters.
- No end date, so prioritization becomes permanent postponement.
A simple scoring approach
Governments that publish a prioritization method often use a weighted score. A typical version rates each candidate data set on a few factors:
- Accountability value: does it shed light on spending, contracts, enforcement or performance?
- Demand: how often is it requested through records requests, the portal or public meetings?
- Policy relevance: does it support a current initiative, rule or legislative debate?
- Readiness: is it already structured, documented and free of sensitive fields?
- Cost: how much staff time will preparation and ongoing updates take?
Weighting the first three above the last two keeps the process from favoring whatever is easiest. Publishing the scores, and revisiting them each year, lets residents see why a requested data set is or is not near the top of the list.
Why this matters for your business data
Buyers of operational data prioritize too. AI and analytics teams look first for data that is large, longitudinal, consistently structured and hard to obtain elsewhere. Knowing which of your data sets score well on those criteria tells you where to start.
Our guide on how to value my data walks through the factors buyers weigh, and you can get a bid on the data sets that rank highest. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
How do cities decide which open data to publish first?
Common criteria include accountability value, public demand measured through records requests and public comment, relevance to current policy initiatives, and cost of preparation. Strong policies publish the criteria and set a final deadline.
Should residents be able to request data sets?
Yes, and many policies create a request form on the portal. The guideline warns that requests should be one input among several so that prioritization does not simply reflect who participates most.
Is cost a valid reason to delay publishing?
Cost is a practical factor, but the guideline says it should be balanced against value. A data set that is expensive to publish but important for accountability may still deserve early release.
Policies in the index that reflect guideline 5
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Austin, TX | Dec 8, 2011 | Council resolution | 351627 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| Philadelphia, PA | Apr 26, 2012 | Executive order (No. 1-12) | 34578182224 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| 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 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| 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 |
| San Diego, CA | Nov 24, 2014 | Administrative policy | 45818202427 |
| Denton, TX | Feb 9, 2015 | Administrative directive | 357811121618 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 12345678 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| 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 |
| Bellevue, WA | Aug 1, 2016 | Management policy | 15678101118 |
| 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 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.