
Guideline 31 asks every open data policy to schedule its own review: regular reports, assessment of who uses the data and how, and a process for revising the policy and its guidance as practice and technology change.
The final guideline closes the loop. Data needs upkeep, and so does the policy that governs it.
What the guideline means
Open data policies operate in a fast-changing environment of new tools, new privacy questions and new user expectations. Guideline 31 asks policies to mandate periodic review of the policy itself and of any guidance issued under it, so that it stays aligned with best practice and with what oversight bodies have learned.
A central focus of review should be the audience: who is using the data, which datasets they use, and for what. That evidence connects back to prioritization (Guideline 5), quality (Guideline 28) and public feedback (Guideline 26).
Model policy language patterns
Paraphrased review provisions:
- The oversight body shall submit an annual open data report to the mayor or council by a fixed date each year.
- The report shall assess progress toward the policy's goals, summarize datasets published and planned, and recommend changes.
- Staff shall report to a council committee at regular intervals during the first years of implementation.
- The policy shall be reviewed periodically and revised to reflect changes in technology and practice.
Where it appears in adopted policies
Review provisions are among the most widely adopted implementation guidelines. Examples in this index:
- Chattanooga, TN (2014) and Hartford, CT (2014) required annual open data reports to the mayor by fixed dates.
- Las Vegas, NV (2016) required an annual report to the city council assessing progress toward the initiative's goals.
- Asheville, NC (2015) required informational reports to a council committee every six months for the first two years.
- Minneapolis, MN (2014) acknowledged that technology changes rapidly and called for future review and revision.
- Washington, DC (2014) required agencies to prepare yearly open government reports.
- Cambridge, MA (2015) created an Open Data Review Board; Louisville, KY (2013), Chicago, IL (2012) and Tulsa, OK (2015) also include review mechanisms.
Common pitfalls
- Reports that count, not assess. Listing the number of datasets says little about whether they are used or useful.
- No user research. Without knowing who uses the data, reviews cannot prioritize well.
- Review without authority to revise. Findings need a path back into updated guidance (Guideline 25).
- Reports that stop. Annual requirements often lapse after leadership changes; tying them to a fixed date and a named recipient helps.
A practical checklist for review provisions
- Require an annual open data report to a named recipient by a fixed date.
- Assess outcomes, not just counts: usage, quality, public requests and progress against timelines.
- Gather evidence on who uses the data and for what purposes.
- Review the implementing guidance alongside the policy itself.
- Give the reviewing body a clear path to propose revisions.
- Schedule a fuller policy review every few years to reflect changes in technology, privacy expectations and practice.
Why this matters for your business data
Review is where an organization learns what its data is really worth. Cities that tracked usage discovered which datasets drove reuse; businesses that revisit their data periodically often find that records they ignored, such as scheduling patterns, maintenance histories or regional demand, have become valuable as AI and machine-learning buyers look for real-world operational signals.
A yearly check of what data you hold and what the market pays for it is a simple habit. The valuation calculator makes that check quick, how to value my data explains the drivers, and the de-identified data guide covers what must be removed first.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
How often should an open data policy be reviewed?
Annual reporting is the most common pattern, often due by a fixed date each year, with a fuller review of the policy every few years. Some policies require more frequent reports, such as every six months, during the first years of implementation.
What should an annual open data report include?
Progress against goals and timelines, datasets published and planned, data quality issues, public requests and responses, usage metrics, and recommendations for changes to the policy or guidance.
Why focus on who uses open data?
Usage evidence shows which datasets create value and for whom, helping governments prioritize maintenance and new releases. It also strengthens the case for continued funding and reveals communities that are not being served.
Policies in the index that reflect guideline 31
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| 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 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Chattanooga, TN | May 31, 2014 | Executive order | 123467810 |
| 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 |
| 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 |
| 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 |
Sources
Updated December 31, 2024.