
Austin's 2013 Open Government Directive, delivered by administrative memo to the Mayor and Council, set a presumption of openness and gave departments short deadlines to catalog public information and publish high-value datasets.
What the directive does
On August 26, 2013, an Assistant City Manager transmitted the City of Austin Open Government Directive to the Mayor and Council, answering the 2011 council resolution. The directive commits the city to transparency, participation and collaboration, and then turns those words into departmental tasks with deadlines.
Its core idea is a presumption of openness: information should be published unless law, privacy, confidentiality or security says otherwise, and publication should happen online in open formats that can be searched and reused.
Adoption context
The covering memo notes that the city's data portal was already live with dozens of datasets, charts and maps. The directive's structure closely follows the 2009 federal Open Government Directive, adapted to city departments, a model several local governments borrowed at the time.
Key provisions
- Departments publish budget figures, crime and health statistics, contracts, policies and frequently requested records online.
- Each department sets a publication schedule and notes when information is updated.
- A citywide open government web page is created on a short deadline.
- Each department builds a catalog of its public information, including any license or privacy limits.
- Each department identifies and publishes at least three high-value datasets not previously available.
- Open source, partnerships and funding are addressed as part of implementation.
Guidelines this policy reflects
This is one of the more complete policies in the index. It lines up with proactive release, lists of holdings, prioritization, sensitive information, open code, oversight authority and funding.
What happened next
Austin continued to operate a public open data portal and an open government program after the directive. Exact dataset counts and governance arrangements changed over the years, so the city's own pages are the best current reference.
What the directive teaches about the value of operational data
The requirement to name three high-value datasets is a useful exercise for any business. Most companies hold a few operational tables (transactions, service logs, inventory movements) that are far more useful to outside analysts than everything else combined. Identifying them is the first step in selling your data, and our guide to de-identified data explains how to prepare them safely.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
What counts as a high-value dataset in Austin's directive?
The directive asks each department to pick datasets that were not already publicly accessible and that improve accountability, respond to public demand or create economic opportunity. Each department had to publish at least three.
How is this directive related to the 2011 resolution?
The 2011 council resolution asked the City Manager to develop an Open Government Framework. The 2013 directive is the administrative follow-through, translating those goals into catalogs, schedules and publication deadlines for departments.
Guidelines this policy reflects
- 1. Proactive Release
- 2. Build on Precedent
- 3. Goals and Values
- 4. Lists of Holdings
- 5. Prioritization
- 7. Sensitive Information
- 8. Open Formats
- 10. Open Access
- 11. License-Free
- 16. Open Code
- 18. Data Portals and Websites
- 22. Real-Time Updates
- 24. Oversight Authority
- 25. Binding Regulations
- 26. Public Participation
- 29. Funding
- 30. Partnerships
- 31. Future Review
Other policies in TX
Sources
Updated December 31, 2024.