Detailed schedule is not established in the supplied canonical timeline. Timing shown is v1 editorial sequencing, subject to the source gates.
Departmental administrative authority; legal review and technical feasibility gated.
The problem
City data is a tangle of disconnected systems nobody fully owns. When data is wrong, missing, or locked in a vendor's black box, nobody can say who's responsible — and decisions get made on shaky numbers.
The plan
Every major city dataset gets a named data steward or integration owner — one accountable person for data quality, access, and integration with other systems. Stewards work with departments to open data safely and legally.
The program advances after legal review and technical feasibility checks, so integration never outruns privacy or security.
How you’ll know it’s working
- Major datasets have published named stewards
- Data-quality standards published
- Integration owners documented for shared systems
From the Blueprint
- Replaces informal ‘department liaisons’ with accountable Data Stewards / Integration Owners in every department.
- Stewards own data meaning, quality, refresh cadence, and compliance readiness for their department’s feeds.
- Each steward ensures semantic clarity: what a metric means, how it’s calculated, and how often it updates.
- Operating split: T&I builds infrastructure and security, the Civic Insights Office governs KPIs and dashboards, programs use the tools.
- Every major delivery team gets either an embedded Civic Insights analyst or a defined reporting funnel.
Integration owners, not intermediaries.
Sources and research conditions
S01 pp. 41-42, 92-96
SOURCE-SUPPORTED; LEGAL REVIEW; TECHNICAL FEASIBILITY
Detailed schedule is not established in the supplied canonical timeline. Timing shown is v1 editorial sequencing, subject to the source gates.