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

Timelines: Open Data Policy Guideline 27

Timelines: Open Data Policy Guideline 27

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:

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.

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

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

PlaceAdoptedInstrumentGuidelines
Memphis, TNOct 10, 2009Executive order (No. 01-2009)23212627
Cook County, ILMay 4, 2011Ordinance12378131825
Austin, TXDec 8, 2011Council resolution351627
New York, NYMar 7, 2012Local law (Local Law 11 of 2012)14578101118
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
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Pittsburgh, PAMar 19, 2014Ordinance12345678
Kansas City, MOJun 19, 2014Ordinance (No. 140443)81018242713
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
San Diego, CANov 24, 2014Administrative policy45818202427
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Tulsa, OKDec 21, 2015Executive order123458910
Seattle, WAFeb 26, 2016Executive order17242627
Milwaukee, WIJul 14, 2016Council resolution12356789
New Orleans, LASep 1, 2016Executive order (MJL 16-01)124511182124
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. New York City: Open Data Plan (2013)
  3. New York City: Updated Open Data Plan (July 2014)
  4. Montgomery County: Dataset Publishing Plan

Updated December 31, 2024.