
Bellevue's Version 1.0 open data management policy, issued in August 2016, pairs three short principles with rules on licensing, APIs, prioritization, privacy and an annual program report.
What the policy does
Bellevue's document opens with three principles: grow an accessible portal, focus on high-quality and high-value data, and run the program with a bias for open. It then sets out a management policy covering purpose, scope, goals, governance and reporting.
The scope reaches all city departments and also the records of third-party contractors that create data on the city's behalf, a detail many municipal open data policies leave out.
Adoption context
The policy credits both the Sunlight Foundation's guidelines and the G8 Open Data Charter of 2013 as inspiration. It is grounded in Washington's Public Records Act, which continues to define what the public can access. The exact day of adoption within August 2016 was not recorded in the source material; this index files it under August 1.
Key provisions
- Release publishable, high-quality data tied to strategic priorities and public demand.
- Anonymize data before publication so personally identifiable information is protected.
- A method for deciding when data cannot be released, weighing risk against public benefit.
- Datasets released under an open license, with no mandatory registration.
- Datasets available through an API.
- An annual open data report to the city's Operations Policy Team, made public online.
Guidelines this policy reflects
Read against the guidelines, the policy covers proactive release, prioritization, outside services, sensitive information, public APIs, data quality and future review.
What happened next
Bellevue went on to operate a public open data portal. Readers should consult the city's website for the program's current scope, since this index does not track later revisions to the Version 1.0 policy.
What Bellevue's approach teaches about operational data
Bellevue requires anonymization before publication and a written risk-versus-benefit test. That is the right template for a business too: de-identify first, then decide what is worth sharing. Our guide to de-identified data covers the techniques, and sell my data explains what buyers look for.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Does Bellevue's policy apply to contractors?
Yes. The scope covers all city departments and the records of third-party contractors that create data on behalf of a department, so data produced under contract is not automatically outside the program.
Do users need to register to download Bellevue's data?
No. The policy says datasets on the portal carry an open, unrestricted license and require no mandatory registration, so users can download without identifying themselves.
Guidelines this policy reflects
- 1. Proactive Release
- 5. Prioritization
- 6. Outside Services
- 7. Sensitive Information
- 8. Open Formats
- 10. Open Access
- 11. License-Free
- 18. Data Portals and Websites
- 20. Public APIs
- 24. Oversight Authority
- 28. Data Quality
- 31. Future Review
Other policies in WA
Sources
Updated December 31, 2024.