
Guideline 29 asks open data policies to plan for money: staff, software, training and hosting needed to launch and sustain the program. Funding is often the difference between a durable program and one that fades after launch.
Funding is the least-adopted implementation guideline in many collections of open data policies, and arguably the one whose absence explains the most stalled programs.
What the guideline means
Open data is not free to produce. Inventorying holdings, reviewing sensitive information, building pipelines, maintaining a portal and answering user questions all take time and tools. Guideline 29 asks policymakers to identify funding for both implementation and long-term maintenance.
The guideline lists the usual cost categories: new administrative, technical and legal staff; software to store, extract and publish data; training; and server or hosting costs. Each jurisdiction's capacity differs, but the policy should at least show that resources were considered.
Model policy language patterns
Paraphrased funding provisions:
- The chief information officer shall make appropriate budget requests to carry out the policy.
- The oversight commission shall identify sources of funding to support the changes the policy requires.
- The program shall be funded through the regular budget process, with costs reported annually.
- Recitals noting that resources were allocated in the current budget to establish the program.
Where it appears in adopted policies
Explicit funding language is relatively rare. In this index it appears in:
- Milwaukee, WI (2016), which directed its CIO to make appropriate funding requests to implement the program.
- Providence, RI (2012), which tasked its transparency commission with identifying funding sources.
- Saint Paul, MN (2016), whose resolution noted that the mayor's proposed budget allocated resources to establish an open data program.
- Austin, TX (2013) and Tulsa, OK (2015), which addressed resources as part of implementation planning.
Many cities in this period also relied on outside support, such as philanthropic programs, to get started; that is one reason partnerships (Guideline 30) often travel with funding.
Common pitfalls
- Unfunded mandates. Requiring every department to publish without new resources pushes open data to the bottom of every to-do list.
- Launch funding only. Grants that cover a portal launch but not maintenance produce stale catalogs.
- Hidden costs. Legal review of sensitive data and staff training are often left out of estimates.
- No measurement of return. Programs that never document savings, such as fewer records requests, struggle to defend budgets.
A practical checklist for funding provisions
- Direct the responsible official to request implementation funds through the normal budget process.
- Estimate costs for staff, software, hosting, training and legal review, including ongoing maintenance.
- Distinguish one-time launch costs from recurring costs.
- Identify outside resources, such as grants or partnerships, without making the program dependent on them.
- Track and report program costs and documented savings, such as reduced time spent answering records requests.
- Revisit funding during each policy review.
Why this matters for your business data
Funding is the point where the private and public stories diverge most sharply. Governments must budget for open data as a cost. A business holding de-identified operational data can treat the same work as an asset: the extract that would cost a city money to publish can earn a company revenue when licensed to AI and machine-learning builders.
That revenue can fund the very cleanup and documentation that make the data better. To see the numbers for your situation, try the valuation calculator, read how to value my data, or get a bid.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What does it cost to run a city open data program?
Costs vary with city size and ambition. Main categories are staff time (coordination, technical and legal review), portal software or hosting, data pipeline tools and training. Many programs start with existing staff and modest software costs, then expand as demand grows.
Can open data save governments money?
Proponents often point to reduced time spent answering repetitive records requests and better internal data sharing. Documenting these savings helps sustain budgets, which is why funding and review provisions work well together.
Why do so few policies mention funding?
Many policies are executive orders or resolutions that cannot appropriate money themselves. They may direct officials to request funds through the normal budget process instead. Even so, naming the need in the policy helps ensure it is addressed.
Policies in the index that reflect guideline 29
| Place | Adopted | Instrument | Guidelines |
|---|---|---|---|
| Providence, RI | Mar 19, 2012 | Resolution | 31824262729 |
| Austin, TX | Aug 26, 2013 | Administrative memo | 123457810 |
| Cincinnati, OH | May 29, 2014 | Administrative regulation | 8101122242629 |
| Tulsa, OK | Dec 21, 2015 | Executive order | 123458910 |
| Saint Paul, MN | Apr 27, 2016 | Council resolution | 12578101113 |
| Milwaukee, WI | Jul 14, 2016 | Council resolution | 12356789 |
Sources
Updated December 31, 2024.