
Guideline 22 asks open data policies to require ongoing publication and regular updates, as close to collection time as practical, because a dataset released once begins going stale the next day.
A one-time data dump makes a good press release. It does not make a useful public resource. This guideline is about turning publication into a routine.
What the guideline means
The ideal is publication close to the moment data is collected. Guideline 22 recognizes that releasing a dataset once is not enough: the moment new records are created and not published, the public copy becomes incomplete. Policies should therefore require ongoing publication and specify how frequently datasets are refreshed.
Real-time publication is demanding, but the guideline notes that it becomes much easier when combined with structured collection (Guideline 21), a central portal (Guideline 18) and APIs (Guideline 20). Automation, rather than staff effort, is what makes frequent updates sustainable.
Model policy language patterns
Update provisions commonly take these forms (paraphrased):
- Published datasets shall be updated on a regular schedule appropriate to how often the underlying data changes.
- Each department shall set and publish an update frequency for every dataset it releases.
- Datasets shall be kept current and, where feasible, refreshed automatically from source systems.
- The public shall be notified when datasets are updated.
Where it appears in adopted policies
Ongoing-update language is common among municipal open data policies. Examples in this index include:
- Chicago, IL (2012), whose executive order asked agencies to make reasonable efforts to update public data regularly.
- Philadelphia, PA (2012), which directed each department to develop a schedule for publishing and updating information.
- New York City's 2012 Local Law 11, which required datasets to be updated as often as needed to stay useful and called for technology that notifies the public of updates.
- Madison, WI (2012), Montgomery County, MD (2012), Los Angeles, CA (2013), Houston, TX (2014) and Washington, DC (2014).
Portland, OR (2009) addressed ongoing publication through agreements with regional partners to publish and maintain datasets.
Common pitfalls
- Launch-day spike, then silence. Many portals show a burst of uploads around adoption and few refreshes afterward.
- No stated frequency. Without a published schedule, users cannot tell a current dataset from an abandoned one.
- Manual pipelines. Updates that depend on one employee exporting a spreadsheet stop when that person changes jobs.
- Silent schema changes. Frequent updates are only useful if columns and definitions stay stable or changes are documented.
A practical checklist for update provisions
- Require a stated update frequency for every published dataset, recorded in its metadata.
- Show the date of last update prominently.
- Automate refreshes from source systems wherever possible.
- Notify users of updates through feeds, change logs or portal alerts.
- Document schema changes before they take effect.
- Track and report datasets that miss their stated schedule, so stale data is visible to oversight bodies and the public.
Why this matters for your business data
Freshness is one of the clearest drivers of data value. For AI and machine-learning buyers, a historical extract is useful, but a historical extract plus a reliable recurring refresh is worth considerably more, because models trained on current conditions outperform those trained on stale ones.
Businesses already produce data continuously through their operating systems. The question is whether a consistent, de-identified extract can be produced on a schedule without heroic effort. Get a bid to see how buyers price one-time versus recurring delivery, or use the valuation calculator for a first estimate.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Does real-time mean every dataset must update continuously?
No. The goal is publication as close as practical to collection, matched to how often the data changes. Transit positions may update by the minute, permits daily, budgets annually. The key is a stated, reliable frequency rather than one-time release.
How can a small government keep datasets current?
Automation is the main answer. Connecting the portal directly to source systems, collecting data electronically, and scheduling exports remove the need for manual uploads. Starting with a handful of automated, high-demand datasets is more sustainable than many manual ones.
Should policies require update schedules to be published?
It is good practice. A published frequency tells users whether a dataset is current and gives oversight bodies a simple metric for compliance. Many policies place the update frequency in each dataset's metadata.
Policies in the index that reflect guideline 22
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Washington, DC | Jun 12, 2006 | Executive memorandum | 1131822 |
| Portland, OR | Sep 30, 2009 | Council resolution | 37810162230 |
| 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 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Los Angeles, CA | Dec 18, 2013 | Executive directive (No. 3) | 37818222630 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Cincinnati, OH | May 29, 2014 | Administrative regulation | 8101122242629 |
| 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 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Asheville, NC | Oct 13, 2015 | Council resolution | 13489101118 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| San Jose, CA | Apr 5, 2016 | Council policy | 1681113182230 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Naperville, IL | Nov 15, 2016 | Council resolution | 45789101112 |
| Fort Collins, CO | Feb 7, 2017 | Council resolution | 12345678 |
Sources
Updated December 31, 2024.