Detailed schedule is not established in the supplied canonical timeline. Timing shown is v1 editorial sequencing, subject to the source gates.
Departmental engineering plus Council/funding/regulatory dependencies: the operating system is engineering-led, with Council appropriations, grants, and permits required for capital delivery.
The problem
Flooding doesn't respect election cycles, and a flood plan that lives in one mayor's head dies with the administration. Residents need something durable: a standing system that keeps measuring, maintaining, and building no matter who holds the office. The Flood Resilience Operating System is the machinery that makes Flood-Ready Tampa permanent.
The plan
Codify the operating system as the durable model tying it all together: watershed master planning, basin scorecards, the asset register, green-gray alternatives, real-time control, and the public portfolio — one engineering-led, technology-neutral loop of measure, maintain, build, and report.
Publish baselines before claiming progress, refresh the capital sequence annually, and issue an annual performance report — the system is accountable by design, not by press release.
How you’ll know it’s working
- Operating system documented and published as a standing model
- Annual capital-sequence refresh and performance report
- Baselines published before progress claims
- Independent verification of reported flood-risk outcomes
Sources and research conditions
S04 Flood-Ready Tampa; S01 resilience chapters
SOURCE-SUPPORTED; FISCAL MODEL; BASELINE DATA
Detailed schedule is not established in the supplied canonical timeline. Timing shown is v1 editorial sequencing, subject to the source gates.