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

Build on Precedent: Open Data Policy Guideline 2

Build on Precedent: Open Data Policy Guideline 2

Guideline 2 says an open data policy should grow out of the access and accountability laws a government already has, such as open records, open meetings and ethics rules, instead of starting from a blank page.

What building on precedent means

Every local government already operates under rules that guarantee some public access: public records acts, open meetings laws, ethics and lobbying disclosure, campaign finance reporting. An open data policy is stronger when it treats those rules as its foundation. It can borrow their definitions, inherit their exemptions, and fill gaps where older laws never anticipated machine-readable data.

Grounding the policy in precedent also helps define what "data" means. Many policies describe data as the next step in the evolution of public records: the same public information, delivered in a structured and reusable form.

How policies typically phrase it

  • A recital listing the state and local access laws the policy builds on.
  • A clause stating that nothing in the policy limits or delays responses to records requests.
  • Definitions of "public data" or "protected data" that cross-reference the existing records statute.
  • A requirement that departments follow an existing data-classification or restricted-data policy when deciding what to publish.

Places whose policies adopted it

Charlotte's 2015 IT policy ties open data publication to the city's existing restricted-data policy, so departments use one classification scheme for both. Memphis's 2009 executive order, one of the earliest in this index, makes clear that the online publishing push should not slow down ordinary open records requests. Honolulu's 2013 ordinance explicitly references the State of Hawaii's earlier open data portal work.

Other tagged examples include Cook County, Houston, Oakland, South Bend and Nashville.

Common pitfalls

  • Conflicting definitions. If the open data policy defines "public" differently from the records law, departments will default to the narrower reading.
  • Treating the portal as a substitute. A portal should supplement, not replace, the right to request records.
  • Ignoring state law. Local policies that overlook state confidentiality statutes invite legal challenges and slow adoption.

A drafting checklist

Before drafting, map the access rules already in force. A short inventory of legal precedent usually covers:

  • The state public records or right-to-know statute and its exemptions.
  • Open meetings rules, which often already require posting agendas and minutes online.
  • Ethics, lobbying and campaign finance disclosure, which tend to produce high-value accountability data.
  • Records retention schedules, which determine how long data must be kept and therefore what can be archived.
  • Any internal data-classification policy used by IT or legal staff.

With that map in hand, the open data policy can reuse definitions, point to the governing exemptions and identify gaps, for example disclosure rules that require paper filings but say nothing about structured data. The result is a policy that departments can follow without consulting two conflicting rulebooks, and that courts and auditors can read as a coherent extension of existing law.

Why this matters for your business data

Companies face the same question in a different setting. Before data can be shared or sold, it has to fit inside the commitments you already have: customer contracts, vendor terms, industry rules. Building on those existing obligations, rather than ignoring them, is what makes a data program durable.

Our guide to de-identified data explains how operational records are prepared so they respect those commitments, and sell my data shows how the process works end to end. 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 should an open data policy reference the public records law?

Referencing the records law keeps definitions and exemptions consistent, signals that the policy expands access rather than replacing existing rights, and reduces the risk that departments interpret the two regimes differently.

Does an open data portal replace public records requests?

No. Policies that follow this guideline usually say so directly. The portal makes frequently requested information available without a request, but the legal right to request records remains.

What existing policies can an open data policy build on?

Typical foundations include open records and open meetings acts, ethics codes, lobbying and campaign finance disclosure, records retention schedules and internal data-classification policies.

Policies in the index that reflect guideline 2

PlaceAdoptedInstrumentGuidelines
Memphis, TNOct 10, 2009Executive order (No. 01-2009)23212627
Washington, DCJan 3, 2011Mayor's memorandum122630
Cook County, ILMay 4, 2011Ordinance12378131825
South Bend, INAug 22, 2013Executive order237810182528
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
Hennepin County, MNOct 23, 2013Resolution of support (MetroGIS Policy Board)1236
Honolulu, HINov 27, 2013Ordinance237810111820
Pittsburgh, PAMar 19, 2014Ordinance12345678
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Chattanooga, TNMay 31, 2014Executive order123467810
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
Charlotte, NCJan 1, 2015IT policy2781924
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Tulsa, OKDec 21, 2015Executive order123458910
New York, NYJan 5, 2016Local law (Local Law 7 of 2016)124
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Saint Paul, MNApr 27, 2016Council resolution12578101113
Milwaukee, WIJul 14, 2016Council resolution12356789
New Orleans, LASep 1, 2016Executive order (MJL 16-01)124511182124
Fort Collins, COFeb 7, 2017Council resolution12345678

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)

Updated December 31, 2024.