
Guideline 24 asks every open data policy to name who is in charge: an officer, department, committee or ombudsman empowered to resolve disputes, coordinate departments and ensure the policy is actually carried out.
A policy without an owner is a statement of intent. Among the municipal open data policies in this index, naming an oversight authority is one of the most consistently adopted provisions.
What the guideline means
Open data programs raise questions that no policy can fully anticipate: Is this dataset sensitive? Who pays to clean it? Which department owns a record that three departments touch? Guideline 24 asks the policy to designate a single authority with the power to answer those questions and enforce compliance.
That authority can be an existing official, such as a chief information or data officer, a dedicated department, an advisory board or an ombudsman. The guideline emphasizes that oversight does not require new hires: a network of departmental data coordinators who meet regularly can spread the work and build buy-in. Oversight should work in public and be supported by implementing guidance (Guideline 25).
Model policy language patterns
Oversight provisions usually follow a few patterns (paraphrased):
- The chief information officer, or a designee, is responsible for implementation and compliance.
- Each department head shall appoint a data coordinator, and the coordinators together form an open data team chaired by the CIO.
- An advisory group or board, sometimes including outside members, shall guide implementation and report to the mayor or council.
- The oversight body may issue standards and resolve conflicts over publication.
Where it appears in adopted policies
Nearly every policy in this index names an authority. The designs differ in instructive ways:
- Single officer: Boston, MA (2014) authorized its CIO to issue the city's open data policy; Houston, TX (2014) created an enterprise data officer role; Fort Collins, CO (2017) asked the city manager to designate an open data officer.
- Coordinator teams: Hartford, CT (2014) and Chattanooga, TN (2014) paired a CIO with departmental coordinators.
- Boards and committees: Tulsa, OK (2015) created an Open Data Advisory Board; Jackson, MS (2015) a governance committee of city staff and community leaders; Las Vegas, NV (2016) a steering committee with external stakeholders; Providence, RI (2012) a commission for transparency and accountability.
- Existing department: New York City's 2012 Local Law 11 placed responsibility with the city's technology department.
Common pitfalls
- Authority without power. A coordinator who cannot compel departments to publish becomes a messenger.
- Closed-door oversight. If decisions about what to withhold are made privately, the public cannot evaluate them.
- Single point of failure. Programs built around one champion often stall when that person leaves.
- No reporting line. Oversight works best when tied to regular public reports (Guideline 31).
A practical checklist for oversight provisions
- Name one accountable official, with authority to direct departments, in the text of the policy.
- Require each department to appoint a data coordinator.
- Give the oversight body power to issue standards and resolve disputes about publication.
- Make the body's decisions and meeting records public.
- Consider including outside members, such as residents, researchers or civic technologists, in an advisory role.
- Tie oversight to deadlines and annual reporting so performance can be measured.
Why this matters for your business data
The same question decides whether a company can turn operational data into a revenue line: who owns it? Data value is often lost not because records are poor, but because no one has the authority to approve an extract, confirm what is sensitive, and sign off on de-identification. Naming an owner, even part time, is usually the first real step.
If you are that person in your business, the open data policy to data value guide maps the government playbook to a private one, and get a bid shows what a buyer would offer before you commit internal time.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Who typically oversees a city open data policy?
Most commonly a chief information officer, chief data officer or similar technology leader, often supported by data coordinators in each department. Some cities add advisory boards or committees that include residents, academics or civic technologists.
Does oversight require hiring new staff?
Not necessarily. Many policies assign the role to an existing official and distribute work among departmental coordinators. Dedicated staff help as programs grow, but a well-defined responsibility matters more than headcount at the start.
Should oversight bodies include people outside government?
Several policies include external members, such as community leaders or stakeholders, on advisory or steering committees. Outside perspectives can improve prioritization and accountability, though final decisions usually rest with an official who can direct departments.
Policies in the index that reflect guideline 24
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| San Francisco, CA | Oct 21, 2009 | Executive directive | 11824 |
| 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 |
| Chicago, IL | Dec 10, 2012 | Executive order | 34678101113 |
| Montgomery County, MD | Dec 17, 2012 | County legislation (Bill 23-12, Open Data Act) | 457811131822 |
| San Francisco, CA | Mar 28, 2013 | Ordinance | 34578101118 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Oakland, CA | Oct 15, 2013 | Council resolution (No. 84659) | 2345781011 |
| 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 |
| Cincinnati, OH | May 29, 2014 | Administrative regulation | 8101122242629 |
| Chattanooga, TN | May 31, 2014 | Executive order | 123467810 |
| 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 |
| Houston, TX | Sep 18, 2014 | Administrative policy (AP 8-7) | 234567810 |
| San Diego, CA | Nov 24, 2014 | Administrative policy | 45818202427 |
| Charlotte, NC | Jan 1, 2015 | IT policy | 2781924 |
| Boston, MA | Jul 30, 2015 | Administrative policy | 478132425 |
| Suffolk County, NY | Jul 31, 2015 | Administrative policy | 78131820222426 |
| Jackson, MS | Sep 1, 2015 | Executive order (No. 2015-06) | 12345678 |
| Cambridge, MA | Sep 21, 2015 | Ordinance | 12345678 |
| Asheville, NC | Oct 13, 2015 | Council resolution | 13489101118 |
| Durham, NC | Nov 23, 2015 | Administrative policy | 7818192430 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| Seattle, WA | Feb 26, 2016 | Executive order | 17242627 |
| Baltimore, MD | Mar 7, 2016 | Ordinance | 1781113182426 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Bellevue, WA | Aug 1, 2016 | Management policy | 15678101118 |
| 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 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.