
Guideline 27 asks open data policies to set firm, appropriately ambitious deadlines with measurable checkpoints, giving agencies time to prepare while making delays visible to the public and to oversight bodies.
Deadlines are where commitments become measurable. Among open data policies, those with specific dates tend to produce visible results, and when they slip, the public can see it.
What the guideline means
A policy that says data "will be published" without saying when is easy to ignore. Guideline 27 asks for timelines that are firm, motivating and paired with benchmarks that can be measured, whether counts of datasets, inventory completion or portal milestones.
The balance matters. Agencies need enough time to inventory holdings, review sensitive information and build pipelines, but a timeline stretched too far lets the policy drift into irrelevance. Clear deadlines also make failures easy to spot, which opens the door to public oversight.
Model policy language patterns
Paraphrased timeline constructions:
- A portal shall be available within a set number of days of enactment.
- Within a stated period, the oversight body shall publish implementing standards.
- Departments shall complete an inventory of datasets by a specific date.
- The open data team shall publish a timeline naming an initial group of pilot datasets and a schedule for further releases.
- Each department shall develop and follow a schedule for publishing and updating data.
Where it appears in adopted policies
Examples from this index:
- Minneapolis, MN (2014) required a city open data portal within 120 days.
- Asheville, NC (2015) set a 180-day deadline for its first implementation steps.
- Pittsburgh, PA (2014) asked its open data team to publish a timeline with a date for an initial pilot release and a schedule for further disclosures.
- Madison, WI (2012) set a date by which public datasets would be accessible through a single site.
- New York City's 2012 Local Law 11 set staged deadlines, starting with a technical standards manual due within 180 days and ending with a December 31, 2018 target for agencies to bring their public data sets onto the single portal.
- Cook County, IL (2011) and Philadelphia, PA (2012) required publication schedules; Milwaukee, WI (2016) asked for a routinely updated public timeline.
Common pitfalls
- Deadlines without owners. A date with no responsible official (Guideline 24) rarely holds.
- All-at-once targets. Requiring everything by one date encourages low-quality bulk uploads. Phased milestones work better.
- Unpublished timelines. Internal schedules give the public nothing to measure against.
- No consequence or report. Deadlines matter most when progress is reported publicly (Guideline 31).
A practical checklist for timeline provisions
- Set near-term deadlines for naming an oversight official, issuing standards and launching or updating a portal.
- Require a published inventory by a specific date.
- Start with a defined pilot group of datasets, then a schedule for further releases.
- Use phased milestones rather than a single all-or-nothing date.
- Make every timeline public and assign each milestone to a responsible office.
- Report progress and missed deadlines in annual reports.
Why this matters for your business data
Turning operational data into value also benefits from a timeline. Projects to package company data often stall in an open-ended "cleanup" phase. A simple phased plan, such as inventorying systems in week one, producing a de-identified sample in week three and receiving a buyer's assessment after that, keeps momentum and surfaces problems early.
The valuation calculator gives a same-day estimate to anchor that plan, and get a bid is the natural first milestone. For the broader framework, see from open data policy to data value.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What is a typical deadline in a city open data policy?
Deadlines vary widely. Short-term targets of 90 to 180 days for launching a portal, issuing standards or naming coordinators are common, followed by annual milestones for inventories and publication. Larger programs set multi-year horizons for full publication.
Why do pilot datasets help?
Publishing a small initial group of datasets tests workflows, formats and review processes before scaling. It produces early results and reveals problems while they are still cheap to fix.
What happens when a city misses an open data deadline?
Usually nothing automatic, which is why public reporting matters. A published timeline and annual report let councils, journalists and residents see the gap and ask why, creating pressure that an internal plan cannot.
Policies in the index that reflect guideline 27
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Memphis, TN | Oct 10, 2009 | Executive order (No. 01-2009) | 23212627 |
| Cook County, IL | May 4, 2011 | Ordinance | 12378131825 |
| Austin, TX | Dec 8, 2011 | Council resolution | 351627 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| 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 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Kansas City, MO | Jun 19, 2014 | Ordinance (No. 140443) | 81018242713 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| Minneapolis, MN | Aug 1, 2014 | Council-adopted policy | 34568131819 |
| San Diego, CA | Nov 24, 2014 | Administrative policy | 45818202427 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 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 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| 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.