Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Policy index / Open data policy index
Open data policy index

Seattle Executive Order 2016-01: Open Data by Preference (2016)

Seattle Executive Order 2016-01: Open Data by Preference (2016)

Seattle Executive Order 2016-01, signed by Mayor Edward Murray in February 2016, ordered every city department to carry out the new Open Data Policy, treat city data as open by preference after privacy and security screening, and fully comply by December 2016.

What the order does

Executive Order 2016-01 is the enforcement step for Seattle's Open Data Policy OD-1. It does not restate the technical rules; it orders departments to follow the policy maintained by the Department of Information Technology and gives them a deadline.

The preamble places the order in context. Seattle's Open Data Program dated to 2010 and the launch of data.seattle.gov, the city had related tools for performance and budget data, and it had created a privacy program to build public trust in how data is collected and opened.

Key provisions

Departments must:

  • Make the city's data holdings open by preference.
  • Establish department accountability, including naming an Open Data Champion.
  • Build open data publishing into routine work.
  • Take part in running the Open Data Program.
  • Engage stakeholders, including the public, civic technologists and parties acting for the city.

All departments were to fully implement the policy, with help from the program, by December 2016.

Which guidelines it reflects

On its own, the order reflects proactive release, sensitive information screening, oversight authority, public participation and timelines. Most of the detailed guideline coverage sits in the companion policy.

Why this matters for your business data

Seattle paired openness with a formal privacy program, and that pairing is what makes data release workable at scale. The same is true for businesses: operational data can be shared or sold only when personal details are removed first and governance is clear. Read what de-identified data means and 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.

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

Why did Seattle need both a policy and an executive order?

The policy, OD-1, holds the detailed rules and can be revised by the technology department. The executive order carries the mayor's authority, requiring departments to follow the policy and setting a compliance deadline. Splitting them keeps the technical rules flexible while making participation mandatory.

When did Seattle's open data program start?

According to the order's preamble, the program launched in 2010 with the data.seattle.gov portal. The 2016 order and policy formalized and expanded a program that already existed.

Guidelines this policy reflects

Other policies in WA

Sources

  1. Original executive order (historical; may no longer resolve)
  2. Original press release (historical; may no longer resolve)
  3. Policy text (Sunlight Foundation open data policy collection, GitHub)

Updated December 31, 2024.