Seamless, Multimodal Transportation
TOT-P4-C20-007Implementation mechanismExecutive Action

CitySync Flood Resilience Portfolio

TOT-P4-C20-007

Track every flood project in one public portfolio

Delivery conditions

Detailed schedule is not established in the supplied canonical timeline. Timing shown is v1 editorial sequencing, subject to the source gates.

CitySync/RX pilot domain: departmental administrative authority with procurement, budget, and data rules applying (RX, T&I, OCI, PDU); scale waits on technical feasibility and a fiscal model.

The problem

Flood projects scatter across departments, budgets, and press releases — a resident trying to find out what's happening on their street ends up with fragments. Nobody should need a public-records request to learn whether the project behind their house is funded, delayed, or done. One public portfolio ends the scavenger hunt.

The plan

Build the CitySync Flood Resilience Portfolio: every flood project in one public view with stage labels — planned, funded, in design, under construction, complete — plus budget, timeline, and owner for each.

Sequence it behind technical feasibility and a fiscal model, and publish the portfolio prototype early so residents can shape it before it hardens.

How you’ll know it’s working

  • Public portfolio prototype published with stage labels
  • Every active flood project tracked with owner, budget, and timeline
  • Stage-label accuracy audited and reported
  • Resident feedback incorporated into portfolio design
Sources and research conditions

S04

SOURCE-SUPPORTED; FISCAL MODEL; TECHNICAL FEASIBILITY

Detailed schedule is not established in the supplied canonical timeline. Timing shown is v1 editorial sequencing, subject to the source gates.

Proposal FAQ

Questions, answered from the record.

What problem does CitySync Flood Resilience Portfolio address?

Flood projects scatter across departments, budgets, and press releases — a resident trying to find out what's happening on their street ends up with fragments. Nobody should need a public-records request to learn whether the project behind their house is funded, delayed, or done. One public portfolio ends the scavenger hunt.

What would CitySync Flood Resilience Portfolio do?

Build the CitySync Flood Resilience Portfolio: every flood project in one public view with stage labels — planned, funded, in design, under construction, complete — plus budget, timeline, and owner for each. Sequence it behind technical feasibility and a fiscal model, and publish the portfolio prototype early so residents can shape it before it hardens.

Who would own CitySync Flood Resilience Portfolio, and what authority would it use?

Stormwater / CitySync (RX, T&I, OCI). Executive Action: CitySync/RX pilot domain: departmental administrative authority with procurement, budget, and data rules applying (RX, T&I, OCI, PDU); scale waits on technical feasibility and a fiscal model.

How would Tampa know whether CitySync Flood Resilience Portfolio is working?

Public portfolio prototype published with stage labels; Every active flood project tracked with owner, budget, and timeline; Stage-label accuracy audited and reported; Resident feedback incorporated into portfolio design

When would CitySync Flood Resilience Portfolio move?

Sequencing: Advances after its listed research/partner gates are satisfied.

Make this real

Fund the fight for CitySync Flood Resilience Portfolio.

Help turn a published plan into organizing, outreach, and governing capacity.

Contribute on ActBlue →