
Las Vegas's Policy and Procedure on Open Data (CM510), approved by the City Manager's office on April 12, 2016, commits the city to proactive release of publishable data and sets up an Open Data Steering Committee to oversee it.
What the policy does
CM510 is a citywide administrative policy issued by the Office of the City Manager. It commits Las Vegas to proactive release of all publishable data in open formats with no limits on reuse. It also covers documentation and permanence, a central web portal, and protection of sensitive data. Like several policies in this index, it extends to third-party contractors who create or acquire data for the city.
Adoption context
Las Vegas adopted CM510 in April 2016. The original collection lists it as "Legislation," but the document is an administrative policy and procedure approved through the City Manager's office. The Sunlight Foundation's published records say the city had that organization's formal help through the What Works Cities program.
Key provisions
- An Open Data Steering Committee of internal staff and outside stakeholders, appointed by the City Manager.
- A lead open data coordinator in each department, working with the city's IT data architect.
- A published, regularly updated inventory of datasets for each department.
- A risk-and-benefit review for potentially sensitive data, and prioritization based on public demand such as records request frequency.
- Review steps covering format, quality and timeliness before publication, plus a public release timeline.
- Download availability for published datasets.
Guidelines it reflects
The policy covers a wide range of guidelines, including proactive release, outside services, thoughtful formats, data quality, real-time updates through its release timeline, and binding regulations.
What happened next
Because CM510 is an administrative policy, the City Manager's office can update it without a council vote. That flexibility is common among cities that have passed an open data policy through the executive branch. For a council-adopted alternative from the same year, see Milwaukee's 2016 policy.
Why this matters for your business data
CM510's review step, which checks every dataset for format, quality, timeliness and exposure of protected information before release, is also a good quality-control checklist for any company that wants to turn operational data into revenue. The de-identified data guide explains the privacy part, and the valuation calculator estimates what your data could be worth. We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Was the Las Vegas open data policy passed by City Council?
The document is numbered CM510 and issued by the Office of the City Manager with an approval date of April 12, 2016. It reads as an administrative policy and procedure, not a council ordinance. Check the city's official records if the legal form matters for your work.
Does CM510 cover contractors?
Yes. It applies to all city departments, boards and commissions, including the records of third-party contractors that create or acquire data for the city.
Guidelines this policy reflects
- 1. Proactive Release
- 2. Build on Precedent
- 3. Goals and Values
- 4. Lists of Holdings
- 5. Prioritization
- 6. Outside Services
- 7. Sensitive Information
- 8. Open Formats
- 9. Thoughtful Formats
- 10. Open Access
- 11. License-Free
- 14. Open Data Creation
- 18. Data Portals and Websites
- 19. Bulk Data
- 21. Data Collection
- 22. Real-Time Updates
- 24. Oversight Authority
- 25. Binding Regulations
- 26. Public Participation
- 28. Data Quality
- 31. Future Review
Sources
Updated December 31, 2024.