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

Binding Regulations: Open Data Policy Guideline 25

Binding Regulations: Open Data Policy Guideline 25

Guideline 25 asks policymakers to pair the vision in an open data policy with binding guidance or regulations that spell out how agencies comply. It is often what separates a policy passed for substance from one passed for show.

Ordinances and executive orders are usually short and broad. The details that make them work, such as formats, review steps and inventory templates, tend to live in a second document. This guideline is about requiring that second document.

What the guideline means

A good open data policy is aspirational and practical at once: it explains why the government is opening its data and gives agencies concrete steps to follow. Guideline 25 recommends that the policy either contain those steps or direct an official to issue binding guidance, standards or regulations that do.

This structure lets the core policy stay stable while technical details evolve. Rather than writing every data standard into an ordinance, a council or mayor can set the framework and require an implementing handbook, technical standards or administrative rules covering formats, metadata, review of sensitive data and publishing workflows.

Model policy language patterns

Paraphrased patterns include:

  • The CIO, in consultation with departments, is directed to issue an open data policy or standards within a set number of days.
  • The responsible department shall publish technical standards governing how public datasets are formatted, documented and published.
  • The oversight body shall develop an implementation plan, including further procedures, for approval by the mayor.
  • Departments shall follow guidance issued under this policy, and that guidance shall be public.

Where it appears in adopted policies

Many policies in this index use a two-step design:

Common pitfalls

  • Guidance that never arrives. A directive without a deadline can sit unfulfilled for years. Pair it with Guideline 27.
  • Guidance that is not public. Internal standards that the public cannot see make compliance impossible to judge.
  • Over-specification in the ordinance. Hard-coding file formats into law makes the policy outdated as technology changes.
  • No authority to enforce. Guidance must come from someone with the power to require compliance (Guideline 24).

A practical checklist for implementing guidance

  • Direct a named official to issue guidance or standards, with a deadline.
  • Require that the guidance be published, not kept internal.
  • Cover the inventory process, sensitive-data review, formats, metadata, update schedules and coordinator duties.
  • Allow the guidance to be revised without amending the underlying policy.
  • Require review of the guidance along with the policy itself.
  • Where an executive order is the vehicle, consider later codifying core commitments so they survive changes in administration.

Why this matters for your business data

Businesses face the same gap between intent and execution. Saying "we could monetize our data" is the vision; a short internal playbook covering which systems, which fields, what gets removed and who signs off is the binding guidance that makes it happen. Without it, the effort stalls at the first question about sensitive fields.

A simple written procedure for producing de-identified extracts also makes a dataset more credible to buyers. The de-identified data guide is a starting template, and sell my data shows what a buyer expects to receive.

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

Why not put all the details in the open data ordinance itself?

Technical details like formats and metadata schemas change faster than laws. Keeping the ordinance focused on principles and directing an official to issue updatable guidance lets the program evolve without new legislation each time.

What does implementing guidance usually cover?

Commonly: how to build the data inventory, how to review datasets for sensitive information, required formats and metadata, publishing workflows, update schedules, and roles of departmental coordinators. Many cities published this as an open data handbook or technical standards.

Is guidance under an executive order binding?

Within the executive branch, guidance issued under a mayor's order generally binds departments under the mayor's authority. It may not bind independent bodies or survive a change of administration, which is one reason some cities later codified policies in legislation.

Policies in the index that reflect guideline 25

PlaceAdoptedInstrumentGuidelines
San Francisco, CAOct 29, 2010Ordinance47811182526
Cook County, ILMay 4, 2011Ordinance12378131825
New York, NYMar 7, 2012Local law (Local Law 11 of 2012)14578101118
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
Chicago, ILDec 10, 2012Executive order34678101113
San Francisco, CAMar 28, 2013Ordinance34578101118
South Bend, INAug 22, 2013Executive order237810182528
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Honolulu, HINov 27, 2013Ordinance237810111820
Pittsburgh, PAMar 19, 2014Ordinance12345678
Hartford, CTMar 26, 2014Executive order34789182224
Boston, MAApr 7, 2014Executive order3891318202425
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
Boston, MAJul 30, 2015Administrative policy478132425
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Tulsa, OKDec 21, 2015Executive order123458910
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
New Orleans, LASep 1, 2016Executive order (MJL 16-01)124511182124
Naperville, ILNov 15, 2016Council resolution45789101112
Fort Collins, COFeb 7, 2017Council resolution12345678

Sources

  1. Sunlight Foundation Open Data Policy Guidelines (historical reference)
  2. NYC open data law overview (NYC DoITT)

Updated December 31, 2024.