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

Oversight Authority: Open Data Policy Guideline 24

Oversight Authority: Open Data Policy Guideline 24

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:

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.

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

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

PlaceAdoptedInstrumentGuidelines
San Francisco, CAOct 21, 2009Executive directive11824
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
Chicago, ILDec 10, 2012Executive order34678101113
Montgomery County, MDDec 17, 2012County legislation (Bill 23-12, Open Data Act)457811131822
San Francisco, CAMar 28, 2013Ordinance34578101118
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
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
Cincinnati, OHMay 29, 2014Administrative regulation8101122242629
Chattanooga, TNMay 31, 2014Executive order123467810
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
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
San Diego, CANov 24, 2014Administrative policy45818202427
Charlotte, NCJan 1, 2015IT policy2781924
Boston, MAJul 30, 2015Administrative policy478132425
Suffolk County, NYJul 31, 2015Administrative policy78131820222426
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Durham, NCNov 23, 2015Administrative policy7818192430
Tulsa, OKDec 21, 2015Executive order123458910
Seattle, WAFeb 1, 2016Administrative policy (CTO policy)14678101112
Seattle, WAFeb 26, 2016Executive order17242627
Baltimore, MDMar 7, 2016Ordinance1781113182426
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Milwaukee, WIJul 14, 2016Council resolution12356789
Bellevue, WAAug 1, 2016Management policy15678101118
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
Syracuse, NYJul 26, 2017Executive order1456781113

Sources

  1. Sunlight Foundation Open Data Policy Guidelines (historical reference)
  2. Sunlight Foundation: An open data ombudsman and rethinking oversight authorities (2014)

Updated December 31, 2024.