06-reference/research

tampa forward article 9 height definition datum

2026-10-27·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
home-buildtampa-zoningtampa-forwardbuilding-heightrs-75

It Keeps It, and Strengthens It - Draft Sec. 9.2.4.A Measures Building Height From the Required Finished Floor and Now Names the Flood Chapter Explicitly, So the Sterling Ridge's Slack Survives the Rewrite

The question

"Does Tampa Forward's Article 9 draft definition of 'Height' keep the required-finished-floor datum or revert to existing grade?"

Context: this was the one remaining route by which the 35-ft RS-75 datum could still move before a 2027 permit at 1212 S Suffolk Dr. If the rewrite measured from existing grade, the ~4.5-5.5 ft of slack under the planned Sterling ridge would collapse to ~2.0 ft and the roof design would change.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

Direct answer: it keeps the required-finished-floor datum. Draft Sec. 9.2.4.A reproduces the current Sec. 27-43 formula verbatim in its first sentence and then replaces the current code's generic "all applicable regulations of the city, county, state and federal government" with the same generic phrase plus an express pointer to the flood chapter. The drafters' own footnote describes the change as a carry-forward with a tightened cross-reference. There is no grade-based height definition in the 411-page draft, and Section 9.3's complete A-to-Z definition list contains no Height entry that could compete. On the live dependency, the answer is unambiguous: the roof does not change. Under RSS's 35 ft measured from a 12.0 ft NAVD88 required floor, the ~33-ft-above-grade Sterling ridge measures 29.5 ft and clears with 5.5 ft of slack - the identical number it clears by under current Chapter 27.

The practical risk picture is now closed on both branches, which is a stronger result than the question asked for. The 2027 permit is very likely processed under current Chapter 27 regardless, because the City's own October 2026 schedule puts 2027 as the start of the adoption process - public hearings, Planning Commission, two Council readings and an effective date all still ahead, with Installment 3 not yet drafted and Installments 1 and 2 under revision. A code rewrite of this size that begins adoption in 2027 is not binding a permit pulled in 2027. And in the branch where it somehow is, the replacement text preserves the datum. That retires the height-datum watch item from the home-build risk register rather than merely deferring it. The residual exposure is narrow and nameable: Installment 1 is being revised and the revised Article 9 has not been published, Article 9's pages are footer-labelled "(Preview)," and the footnote that documents the carry-forward intent will be stripped from the enacted code. None of those is a reason to design differently today; all three are a reason to re-read 9.2.4.A once when the revised Installment 1 drops.

The one thing worth acting on is a public comment, and the window is Thursday. The new cross-reference to Section 5-121 is well-intentioned and slightly broken: Section 5-121 does not set a lowest-floor elevation for a principal dwelling, because Tampa deliberately left FBC-R R322.2.1 unamended. "Including but not limited to" saves the provision, but a plans examiner reading 9.2.4.A as a closed reference would find no number at the end of the pointer, and ambiguity in a measurement datum is exactly the kind of thing that gets resolved against the applicant at the counter. A one-paragraph comment to TampaForward@tampagov.net asking that 9.2.4.A cite FBC-R R322.2.1 (or "the design flood elevation as determined under the Florida Building Code, Residential") alongside Section 5-121 is cheap, is squarely inside the feedback process the City is soliciting, and protects the single provision that gives this build 3.5 ft of roof budget it would not otherwise have. That is a founder-side action - he is the property owner and the comment carries more weight from him - and it is the only decision this brief surfaces.

Method note worth banking. Three briefs have now hit Tampa primary sources, and the retrieval map has stabilized: Municode requires Playwright, tampa.gov static PDFs take a plain curl with a browser user agent, tampamonitor.com mirrors the Council attachment set, and the tampa.gov /search path is Cloudflare-blocked to everything including headed Chrome. The Tampa Forward document pages follow a stable pattern - tampa.gov/document/<slug> returns HTML carrying one sites/default/files/document/<year>/*.pdf link - so the installments and advisory-team decks are reachable without ever touching the blocked search endpoint. Equally useful: in a 411-page draft, the footnotes are the fastest read, because the City instructs reviewers to use them to identify what is new versus carried forward, and footnote 603 answered this question in one sentence before the body text confirmed it.

Why this is in the vault

This discharges the first open follow-up in [[2026-10-24-tampa-ord-2026-49-height-definition-check]] and closes the last live route by which the 35-ft measurement datum could have moved before the 2027 permit, which means the Sterling-plan roof and ceiling heights in [[2026-10-17-sterling-plan-fit-and-cost]] can be taken to an architect without a height contingency. It also surfaces one time-boxed founder action: a public comment on draft Sec. 9.2.4.A's cross-reference ahead of the October 29 2026 Tampa Forward public meeting.

Open follow-ups

Related

Sources