
Guideline 1 asks an open data policy to flip the default: publish public information online before anyone files a request, and define what new data should be collected and released for the first time.
What proactive release means
Most public records systems are reactive. A resident, reporter or company has to know a record exists, ask for it, and wait. Proactive release reverses that sequence: the government publishes information on its own initiative, in the places people already look for it, so the request never has to be made.
An open data policy that adopts this guideline does two things. It commits the jurisdiction to putting existing public information online as a matter of routine, and it leaves room to require that some information be collected or structured for publication for the first time. That second step matters, because the most useful data is often data nobody was previously obliged to keep in a shareable form.
How policies typically phrase it
Model language for this guideline tends to follow a few patterns, which we paraphrase here rather than quote:
- A statement that public information is open by default, subject only to stated legal exceptions.
- A duty on each department to publish qualifying data sets on a central portal without waiting for a request.
- A definition of "public data" broad enough to cover new data sets created after the policy takes effect.
- A clause tying proactive publication to the jurisdiction's existing open records law, so the policy expands access rather than replacing it.
Places whose policies adopted it
Annotators of the original policy collection tagged proactive-release language in a large share of municipal open data policies. Examples in this index include New York City's 2012 Local Law 11, which requires agencies to place their public data sets on a single web portal; Louisville's 2013 executive order, which declares public information open by default and ties publication to Kentucky's open records act; and the 2013 MetroGIS resolution recorded for Hennepin County, which asks member governments to make public geospatial data freely available.
Other tagged examples include Asheville, Chattanooga, Pittsburgh, Tulsa and Washington, DC (2014).
Common pitfalls
- Aspiration without obligation. "Departments are encouraged to publish" produces far less than "departments shall publish."
- No definition of new data. If the policy covers only records that already exist in a shareable form, departments can comply while publishing very little.
- Swallowing exceptions. Broad carve-outs for anything "sensitive" can quietly restore the reactive model.
- No feedback loop. Without a way to see which requests keep recurring, a government cannot tell which data it should be releasing proactively.
Why this matters for your business data
The logic of proactive release applies to private organizations too. A company that waits until a buyer asks before it understands what operational data it holds tends to undervalue it. Businesses that inventory, clean and describe their data in advance are the ones that get competitive offers from AI and machine-learning teams looking for real-world training and benchmarking data.
If you want to see what your own records might be worth, start with how to value your data or run the valuation calculator. The bridge from public-sector practice to private value is explained in from open data policy to data value. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
How is proactive release different from a public records request?
A public records request is reactive: someone must ask before information is disclosed. Proactive release means the government publishes qualifying information online on its own schedule, so nobody needs to know it exists or file a request. Most open data policies keep the records law in place and add proactive publication on top of it.
Does proactive release mean every record goes online?
No. Policies that adopt this guideline still exclude information protected by privacy, security or other legal restrictions. The change is the default: unless an exception applies, public data is expected to be published rather than held until requested.
Can an open data policy require new data to be collected?
It can. The guideline encourages policies to define new data broadly, so that data sets created after adoption, or data that should be structured for publication for the first time, fall within the policy instead of only legacy records.
Policies in the index that reflect guideline 1
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Washington, DC | Jun 12, 2006 | Executive memorandum | 1131822 |
| San Francisco, CA | Oct 21, 2009 | Executive directive | 11824 |
| Washington, DC | Jan 3, 2011 | Mayor's memorandum | 122630 |
| Cook County, IL | May 4, 2011 | Ordinance | 12378131825 |
| New York, NY | Mar 7, 2012 | Local law (Local Law 11 of 2012) | 14578101118 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Louisville, KY | Oct 11, 2013 | Executive order (No. 1, Series 2013) | 1234781018 |
| Hennepin County, MN | Oct 23, 2013 | Resolution of support (MetroGIS Policy Board) | 1236 |
| Pittsburgh, PA | Mar 19, 2014 | Ordinance | 12345678 |
| Chattanooga, TN | May 31, 2014 | Executive order | 123467810 |
| Phoenix, AZ | Jun 18, 2014 | Administrative policy | 13726 |
| Washington, DC | Jul 21, 2014 | Executive directive (Mayor's Order 2014-170) | 12356789 |
| 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 |
| Seattle, WA | Feb 26, 2016 | Executive order | 17242627 |
| Baltimore, MD | Mar 7, 2016 | Ordinance | 1781113182426 |
| San Jose, CA | Apr 5, 2016 | Council policy | 1681113182230 |
| Las Vegas, NV | Apr 12, 2016 | Administrative policy (City Manager policy CM510) | 12345678 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
| Bellevue, WA | Aug 1, 2016 | Management policy | 15678101118 |
| New Orleans, LA | Sep 1, 2016 | Executive order (MJL 16-01) | 124511182124 |
| 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.