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

Lists of Holdings: Open Data Policy Guideline 4

Lists of Holdings: Open Data Policy Guideline 4

Guideline 4 calls for a public, comprehensive inventory of the data a government holds, published or not, so that officials and residents can see the full scope of what could be released.

What a list of holdings is

You cannot publish data you do not know you have. A data inventory, sometimes called a catalog or list of holdings, records every significant data set a government maintains: what it contains, who owns it, how it is stored and whether it can be made public. The guideline asks that the inventory itself be public, including entries for data that will never be released in full.

A public inventory creates a shared map. Residents can see what exists and ask for it; departments discover overlapping systems; oversight bodies can measure progress against the whole, not just the portion already online.

How policies typically phrase it

  • A deadline for each department to complete an inventory of its data sets.
  • A requirement to publish the inventory, often on the open data portal.
  • Annual updates, with an explanation for any data set that cannot be released and an expected release date.
  • Inclusion of information that is not yet structured but could become structured data.

Places whose policies adopted it

New York City's 2012 Local Law 11 requires agencies to describe their public data sets in a compliance plan and to report any they cannot publish, with reasons and a target date. Madison's 2012 ordinance makes each agency responsible for identifying its own data sets and sets an annual reporting cycle. Montgomery County's 2012 law ties its inventory to an implementation plan issued by the chief administrative officer.

Tagged examples also include Chicago, Oakland, San Francisco (2013) and Naperville.

Common pitfalls

  • Inventories that list only what is already published, which hides the gap the inventory was meant to reveal.
  • One-time exercises. Systems change; an inventory that is never refreshed goes stale within a year.
  • No owner. Without a named data steward per data set, nobody answers questions or fixes errors.

What a useful inventory entry contains

An inventory does not need to be elaborate to be useful, but each entry should answer a consistent set of questions:

  • What is the data set called, and what does it describe?
  • Which department owns it, and who is the steward?
  • Which system stores it, and in what format?
  • How often is it updated, and how far back does it go?
  • Is it public, partly public or protected, and under what legal basis?
  • If it is not yet published, when is release expected?

Inventories built this way double as the starting point for metadata and feed directly into prioritization. They also reveal duplication: two departments maintaining separate address lists, for instance, or several systems tracking the same assets. Many governments found that the inventory paid for itself in internal savings before a single new data set was published.

Why this matters for your business data

The single most useful step a business can take before selling or licensing data is the same one cities take: build an inventory. Knowing which systems hold transaction logs, scheduling records, sensor readings or inventory movements, and how many years of history each holds, is what turns "we have data" into a priced asset.

Start with how to value my data, then try the valuation calculator to estimate what an inventory like yours could support. 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

What is a data inventory in an open data policy?

It is a catalog of the data sets a government maintains, with basic descriptions, owners and publication status. Strong policies require the inventory to be published and updated regularly, including entries for data that is not yet public.

Why publish data that cannot be released?

Listing a data set does not mean releasing its contents. Publishing the entry tells the public the data exists, explains why it is withheld, and lets residents and oversight bodies track whether it can be released later in aggregate or redacted form.

How often should an inventory be updated?

Most policies that address this require at least annual updates, often aligned with an annual open data report or compliance plan.

Policies in the index that reflect guideline 4

PlaceAdoptedInstrumentGuidelines
San Francisco, CAOct 29, 2010Ordinance47811182526
New York, NYMar 7, 2012Local law (Local Law 11 of 2012)14578101118
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
Madison, WIAug 15, 2012Ordinance457810111318
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
Pittsburgh, PAMar 19, 2014Ordinance12345678
Hartford, CTMar 26, 2014Executive order34789182224
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Chattanooga, TNMay 31, 2014Executive order123467810
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
San Diego, CANov 24, 2014Administrative policy45818202427
Boston, MAJul 30, 2015Administrative policy478132425
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Tulsa, OKDec 21, 2015Executive order123458910
New York, NYJan 5, 2016Local law (Local Law 7 of 2016)124
Seattle, WAFeb 1, 2016Administrative policy (CTO policy)14678101112
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
Knoxville, TNMay 2, 2017Executive order14578111319
Syracuse, NYJul 26, 2017Executive order1456781113

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)
  2. Project Open Data, transportation inventory case study
  3. Sunlight Foundation, US data inventory examples (GitHub)

Updated December 31, 2024.