
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:
- Boston, MA (2014): the mayor's executive order directed the CIO to issue a city open data policy, which followed as an administrative policy in 2015. That sequence is a clear example of Boston's open data policy using this guideline.
- New York City's 2012 Local Law 11 required the city's technology department to publish an open data legal policy on the portal and, within 180 days, a technical standards manual for publishing public data sets.
- Tulsa, OK (2015) asked its advisory board to produce a more detailed implementation plan for the mayor's approval.
- Chicago, IL (2012), Philadelphia, PA (2012), South Bend, IN (2013), Houston, TX (2014) and Naperville, IL (2016) include comparable directives.
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.
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
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| San Francisco, CA | Oct 29, 2010 | Ordinance | 47811182526 |
| Cook County, IL | May 4, 2011 | Ordinance | 12378131825 |
| 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 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| South Bend, IN | Aug 22, 2013 | Executive order | 237810182528 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Honolulu, HI | Nov 27, 2013 | Ordinance | 237810111820 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Boston, MA | Apr 7, 2014 | Executive order | 3891318202425 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Minneapolis, MN | Aug 1, 2014 | Council-adopted policy | 34568131819 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| Boston, MA | Jul 30, 2015 | Administrative policy | 478132425 |
| 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 |
| 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 |
Sources
Updated December 31, 2024.