Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Guides / Pillar guide · Open data to data value
Pillar guide · Open data to data value

From Open Data Policy to Data Value: What Cities Taught Us About the Worth of Operational Data

From Open Data Policy to Data Value: What Cities Taught Us About the Worth of Operational Data

Open data policy taught governments that operational records are an asset worth publishing in open, machine-readable formats. The same lesson now applies to private business data: your day-to-day operational records have value, and de-identified, they can be licensed.

OpenDataPolicies.org began as an index of city, county and state open data policies. Those policies are still here, in the guidelines and the policy library. This guide connects that history to what the site does today: helping businesses recognize, protect and license the value in their own operational data.

What an open data policy is

An open data policy is a formal commitment, usually an executive order, ordinance, resolution or administrative policy, that directs a government to publish the data it already collects in the course of its work. Crime reports, building permits, 311 service requests, budgets, transit schedules, restaurant inspections: the everyday records of running a city.

The Open Knowledge Foundation's Open Data Handbook gives the shortest definition in common use: open data is data that can be freely used, re-used and redistributed by anyone, subject at most to attribution and share-alike. It highlights three features:

  • Availability and access: the data is available as a whole, ideally downloadable online, in a convenient and modifiable form.
  • Re-use and redistribution: the terms allow re-use, including mixing with other datasets.
  • Universal participation: anyone can use it; no "non-commercial only" or field-of-use limits.

Our guidelines section breaks these ideas into the individual provisions that policies actually contained.

A short, dated history

Open data policy in the United States grew quickly once a few pieces were in place. The dates below are drawn from official sources listed at the end of this page.

  • May 21, 2009: the General Services Administration launched Data.gov as a central catalog of federal datasets.
  • May 9, 2013: an executive order made open and machine-readable data the new default for federal information, and the Office of Management and Budget released memorandum M-13-13, "Open Data Policy - Managing Information as an Asset," the same day.
  • January 14, 2019: the OPEN Government Data Act was signed into law, making Data.gov a statutory requirement.

Cities and counties ran in parallel. Many of the local policies in our browse index were adopted in the late 2000s and 2010s, often borrowing language from model guidance such as the Sunlight Foundation's Open Data Policy Guidelines. Version 3 of those guidelines lists 31 provisions grouped under what data should be public, how to make data public, and how to implement policy. The Sunlight Foundation itself notes it has been inactive since September 2020, but the guidelines remain a widely cited reference.

The core ideas: proactive, open format, open license, machine-readable

Strip the legal language away and most open data policies say four things.

  1. Publish proactively. Do not wait for a records request. Sunlight's first guideline is to proactively release government information online.
  2. Use open formats. Choose formats anyone can read without proprietary software, such as CSV or JSON, and provide more than one where needed.
  3. License openly. Sunlight recommends mandating that data be explicitly license-free, so there is no doubt about re-use.
  4. Make it machine-readable. Data built for software, not just for human eyes, so it can be analyzed at scale.

M-13-13 put the "asset" idea into the title. Its supplemental guidance asked federal agencies to build an enterprise data inventory using a common metadata schema and to post a public data listing at a standard location (agency.gov/data.json). In other words: know what you have, describe it consistently, and publish the description.

The lesson hiding in the policies: data is an asset

The open data movement argued, and largely proved, that the routine records of operations have value well beyond the office that created them. A permit log was just a byproduct of approving permits. Published openly, it became the basis for analysis, apps, journalism and research.

That insight does not stop at government. Every business produces the same kind of byproduct: email threads that show how requests get negotiated, tickets that show how problems get solved, project boards that show how work slips or ships, invoices that show the real rhythm of cash. Most of it sits in software, unused after the moment it was created.

The difference is what you do with that value. Governments publish because the data belongs to the public. A private business keeps ownership of its records, protects the people in them, and can choose to license a de-identified version to those who need it. Read more about the term operational data.

Where public and private data diverge

Open data principles map onto private data licensing, but not one-to-one. The contrasts matter.

  • Openness versus licensing. Public open data is meant for anyone, with no field-of-use limits. Private operational data is licensed to specific buyers, for specific purposes, under contract. See data licensing.
  • Free versus paid. Open data is typically free or at reproduction cost. A business's operational data can command a price, because it is not available anywhere else.
  • Sensitive information. Sunlight's guidelines included appropriately safeguarding sensitive information. Private licensing goes further: personal details are removed before anything moves. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
  • Timing. Public datasets are meant to be permanent. The private value of operational data may be time-limited, because once models have learned a type of workflow, the next seller of that workflow has less to offer.

What carries over intact is the discipline: inventory what you have, describe it in a standard way, use machine-readable formats, and be explicit about rights.

Applying open data discipline to your business

The practices that made government data usable also make private data sellable. Here is the translation.

1. Build an inventory

M-13-13's enterprise data inventory has a direct private equivalent: a list of every system that holds operational history, with years, seats and volume. The data readiness checklist walks you through it.

2. Publish a description, not the data

Agencies published a listing of datasets with standard metadata. Businesses do the same thing privately with a header sample: column names only, no records. It tells buyers exactly what exists without exposing anyone.

3. Prefer machine-readable exports

The CSV and JSON exports most SaaS tools offer are exactly the open, machine-readable formats open data advocates pushed for. Buyers expect them.

4. Be explicit about rights

Open data required a clear license. Private data needs one too, just a different kind: a written agreement that sets scope, permitted use and a ban on re-identification. See data licensing agreements.

Metadata: the open data habit that pays off privately

Among the provisions in Sunlight's guidelines are requirements to publish metadata, to publish how data was created, and to use unique identifiers. Those three habits turned piles of files into datasets people could trust. They do the same for a business preparing to license its records.

  • Metadata tells a buyer what each field means, which system it came from and what period it covers. Even a one-line note per column helps.
  • Creation process explains how records came to exist: was a ticket opened by email, phone or web form? Did invoices come from a job system or get keyed in by hand? Context like this changes how a model learns from the data.
  • Stable identifiers let records link across systems, so a support ticket can be tied to a project task or an invoice. After de-identification, those links are preserved with neutral IDs instead of names.

Agencies that documented their data well saw it reused. Businesses that describe their data well receive clearer, faster bids. The work is mostly writing down what your team already knows.

Why the window matters now

When cities first opened their data, the earliest datasets got the most attention. Something similar is happening with private operational data, but with a deadline. AI and machine learning builders have consumed much of the public web; what they lack is the private, everyday record of how businesses operate. That gap is the opportunity.

Unique data is the asset. Whoever holds unique operational records has leverage while those records are still rare. The founder puts it bluntly: "Every industry is a geek away from being uberized." - Jeff Cline.

According to Jeff Cline, small companies have been paid more than $100,000 for their data, and offers from multiple buyers mean sellers see the highest bid. Results vary; not a guarantee.

From the policy archive to a bid

If you came to this site looking for a city's open data policy, the archive is still here: browse adopted policies in the index and the provisions they share in the guidelines.

If you run a business and the open data story made you wonder what your own records are worth, the process is short:

  1. Tell us which tools you use, how many years of history, how many seats and roughly how much volume, on the bid request form.
  2. Send a header sample with column names only.
  3. Compare the offers buyers submit.
  4. De-identify, sign the license, deliver, and get paid.

According to Jeff Cline, bids typically come back within 72 hours when the data is described correctly with a header sample, and deals typically close in about 90 days. Results vary; not a guarantee. For the full picture, start with how to sell my business data.

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 an open data policy?

An open data policy is a formal government commitment, such as an executive order, ordinance or administrative policy, to proactively publish the data it collects in open, machine-readable formats under terms that allow free re-use. Our archive of these policies is in the browse index.

What was M-13-13?

M-13-13 was the U.S. Office of Management and Budget memorandum "Open Data Policy - Managing Information as an Asset," released May 9, 2013. It directed federal agencies to treat data as an asset, keep an enterprise data inventory and publish data in open, machine-readable formats.

What are the Sunlight Foundation's Open Data Policy Guidelines?

They are a model set of provisions for writing open data policies. Version 3 lists 31 guidelines covering what data should be public, how to make it public and how to implement policy, and many local governments drew on them.

Is private business data the same as open data?

No. Open data is published for anyone to use for free. Private operational data stays owned by the business, has personal details removed, and is licensed to specific buyers under contract, often for a fee.

Why would a business's operational data have value?

Because it records how work really happens, which is hard to find anywhere else. AI and machine learning builders want real examples of requests, hand-offs, delays and outcomes to train models that automate business workflows.

Does licensing business data mean sharing customer information?

No. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control, so buyers receive operational patterns rather than people.

Is the open data policy archive still available?

Yes. The policy index remains available in the browse section, and the shared provisions are explained in the guidelines section of this site.

Sources

  1. Sunlight Foundation: Open Data Policy Guidelines (version 3)
  2. OMB Memorandum M-13-13: Open Data Policy - Managing Information as an Asset (May 9, 2013)
  3. Resources.data.gov: Supplemental guidance on the implementation of M-13-13
  4. Data.gov: Timeline
  5. Data.gov
  6. Open Knowledge Foundation: Open Data Handbook, What is open data?

Updated November 19, 2026.

OpenDataPolicies.org connects businesses with buyers of de-identified operational data. We are not a law firm, broker-dealer or investment adviser, and nothing on this site is legal, tax or financial advice. Statements about amounts, timing and outcomes are Jeff Cline's statements based on past transactions. Results vary; nothing here is a guarantee of any bid, price, buyer or closing. Every deal depends on the data, its quality, its rights and buyer demand at the time.