
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.
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
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| San Francisco, CA | Oct 29, 2010 | Ordinance | 47811182526 |
| 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 |
| Madison, WI | Aug 15, 2012 | Ordinance | 457810111318 |
| 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 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Hartford, CT | Mar 26, 2014 | Executive order | 34789182224 |
| Nashville, TN | May 12, 2014 | Executive order (No. 043) | 2345781011 |
| Chattanooga, TN | May 31, 2014 | Executive order | 123467810 |
| 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 |
| Boston, MA | Jul 30, 2015 | Administrative policy | 478132425 |
| 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 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| New York, NY | Jan 5, 2016 | Local law (Local Law 7 of 2016) | 124 |
| Seattle, WA | Feb 1, 2016 | Administrative policy (CTO policy) | 14678101112 |
| 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 |
| Knoxville, TN | May 2, 2017 | Executive order | 14578111319 |
| Syracuse, NY | Jul 26, 2017 | Executive order | 1456781113 |
Sources
Updated December 31, 2024.