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

Goals and Values: Open Data Policy Guideline 3

Goals and Values: Open Data Policy Guideline 3

Guideline 3 asks an open data policy to state plainly why the government is publishing data: transparency, efficiency, civic engagement, economic development, or a mix tied to the community's own mission.

What the guideline means

Open data can serve many public purposes. Some governments emphasize accountability and honesty; others stress efficiency, service delivery, economic growth or civic participation. A clear statement of goals tells departments why the work matters and gives the public a yardstick for judging results.

The guideline also suggests that writing the statement can itself be participatory. Bringing residents, businesses, researchers and staff together to define the purpose of an open data program surfaces uses that a small drafting team might miss.

How policies typically phrase it

  • Preamble clauses ("whereas") describing the values the government is pursuing.
  • A purpose section linking open data to specific outcomes such as better services or economic opportunity.
  • References to the jurisdiction's broader mission statement or strategic plan.
  • Language inviting local developers and community groups to build tools with the data.

Places whose policies adopted it

This is the most commonly tagged guideline in the collection. Boston's open data policy of 2014 frames open data as part of a commitment to participation, transparency and collaboration. Portland's 2009 resolution is notable for its economic angle, explicitly encouraging the local software community to build applications with public data. Chicago's 2012 executive order grounds its program in transparency, honesty and accountability.

Many other cities that have passed an open data policy include similar statements, among them Raleigh, Philadelphia, Los Angeles and Minneapolis.

Common pitfalls

  • Boilerplate purpose statements copied from another city that do not reflect local priorities.
  • Goals with no measures. If the policy names economic development as a goal but never tracks reuse, nobody can tell whether it worked.
  • Too many goals. A list of a dozen aims gives departments no guidance on what to publish first (see prioritization).

Turning goals into measures

A purpose statement is most useful when each goal can be observed. Policies that do this well pair their values with indicators, often reported in an annual open data report:

  • Transparency: number of data sets published, share of the inventory online, reduction in repeat records requests.
  • Efficiency: staff time saved by self-service data, internal reuse across departments.
  • Civic engagement: portal visits, community events, data requests submitted and fulfilled.
  • Economic development: applications and businesses built on public data, partnerships with universities and companies.

Linking goals to the oversight and future review provisions closes the loop. When the policy is revisited, the government can show which aims were met and adjust priorities, rather than relying on anecdote.

Why this matters for your business data

Several of these policies say outright that public data has economic value. The same is true of the operational data inside private companies, and the clearest way to unlock it is the same: decide what you want the data to accomplish. For many businesses the answer is a new revenue line from AI and analytics buyers who need real-world signals.

Our pillar on open data policy to data value traces that idea from city hall to the private sector, and you can get a bid when you are ready to test the market. 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 does an open data policy need a goals statement?

A goals statement explains to staff and the public why data is being published and what success looks like. It also helps resolve trade-offs, such as which data sets to release first, by pointing back to the stated purpose.

What goals do municipal open data policies usually name?

Transparency and accountability are the most common, followed by operational efficiency, civic engagement, better service delivery and economic development through reuse of public data by businesses and developers.

Should the public help write the goals?

The guideline recommends it. Involving residents, businesses and researchers in drafting the purpose statement builds support for the policy and surfaces practical uses for data that staff may not anticipate.

Policies in the index that reflect guideline 3

PlaceAdoptedInstrumentGuidelines
Portland, ORSep 30, 2009Council resolution37810162230
Memphis, TNOct 10, 2009Executive order (No. 01-2009)23212627
Cook County, ILMay 4, 2011Ordinance12378131825
Austin, TXDec 8, 2011Council resolution351627
Raleigh, NCFeb 7, 2012Council resolution381618
Providence, RIMar 19, 2012Resolution31824262729
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
Chicago, ILDec 10, 2012Executive order34678101113
San Francisco, CAMar 28, 2013Ordinance34578101118
South Bend, INAug 22, 2013Executive order237810182528
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
Hennepin County, MNOct 23, 2013Resolution of support (MetroGIS Policy Board)1236
Honolulu, HINov 27, 2013Ordinance237810111820
Los Angeles, CADec 18, 2013Executive directive (No. 3)37818222630
Pittsburgh, PAMar 19, 2014Ordinance12345678
Hartford, CTMar 26, 2014Executive order34789182224
Boston, MAApr 7, 2014Executive order3891318202425
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Chattanooga, TNMay 31, 2014Executive order123467810
Phoenix, AZJun 18, 2014Administrative policy13726
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
Denton, TXFeb 9, 2015Administrative directive357811121618
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Tulsa, OKDec 21, 2015Executive order123458910
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Milwaukee, WIJul 14, 2016Council resolution12356789
Fort Collins, COFeb 7, 2017Council resolution12345678

Sources

  1. Sunlight Foundation, Open Data Policy Guidelines (historical reference)
  2. Sunlight Foundation blog, "Greetings from OpenData-land" (2013)

Updated December 31, 2024.