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)
- The current datum is settled and verified: Sec. 27-43 reads "Height: The vertical distance between the required finished floor to the highest point of the structure," and Ord. No. 2026-49 amends Sec. 27-43 by addition only and touches Table 4-1 (uses) rather than Table 4-2 (height), so nothing in the adopted 2026 cycle moved it ([[2026-10-24-tampa-ord-2026-49-height-definition-check]]).
- The datum's elevation is also now pinned: Tampa codifies no freeboard of its own and deliberately declined to amend FBC-R R322.2.1, so the operative requirement is the statewide BFE + 1 ft, which puts the required finished floor at 12.0 ft NAVD88 on this lot ([[2026-10-25-tampa-freeboard-ae-zone-codified-requirement]]).
- The arithmetic the answer feeds: ridge ~33 ft above ~8.5 ft average grade, so ~41.5 ft NAVD88. From a 12.0 ft required floor that measures 29.5 ft against 35 - 5.5 ft of slack. From existing grade it measures 33.0 ft - 2.0 ft of slack ([[2026-10-21-tampa-rs75-height-limit-datum]]).
- The rewrite's shape was already mapped: Installment 1 folds RS-75 and RS-100 into RSS: Residential Single-Family Suburban (Sec. 3.2.4), carrying forward the 75 ft lot width and the 35 ft height with no FAR, lot-coverage or impervious row. That brief read Article 3 and Sec. 9.2.6 but never reached the Article 9 height definition ([[2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage]]).
- Retrieval note inherited and confirmed: Municode 403s WebFetch and curl and yields only to Playwright, but static tampa.gov PDFs fetch fine with a browser user agent. That is the route that worked here - no Playwright needed.
What the web says
- The draft text was retrieved and read directly. City of Tampa, Updated Land Development Code, Installment 1 Public Draft, dated February 17 2026, 411 pages, still the exact file linked from
tampa.gov/TampaForwardas of 2026-10-27. Article 9 is "Definitions and Rules for Construction and Interpretation." - The answer, verbatim. Draft Sec. 9.2.4 Buildings, subsection A, "Building Height" (page 9-9): "The vertical distance between the required finished floor to the highest point of the structure. The required finished floor shall be established in accordance with all applicable City, county, state, and federal laws and regulations, including but not limited to the standards in Section 5-121, Flood-Resistant Development, of the City Code." The required-finished-floor datum is kept word for word; "grade" does not appear.
- The drafters say so themselves. Footnote 603, attached to the heading: "Carries forward definition in Section 27-43 of the current LDC but updates the reference to 'required finished floor' to specifically reference the flood-resistant development regulations." The only change the drafters claim is a tightening of the cross-reference, in the direction of the flood datum rather than away from it.
- There is no competing definition anywhere in the draft. Section 9.3, Definitions, runs A to Z over pages 9-12 to 9-55 with 875 footnoted entries, and it has no "Height" entry at all - the H run is Helistop, Hedge, Highway, Home Based Business, Home Garden, Hospital, Hotel. Height moves out of the alphabetical definitions and into Section 9.2, Rules of Measurement, renamed "Building Height." A full-text scan of the 19,196 extracted lines finds "existing grade" exactly once (an unrelated build-to-line provision requiring the first 10 ft of setback to hold the adjacent right-of-way grade in a mixed-use district) and zero occurrences of "average grade," "natural grade" or "crown of the road." The grade-based machinery a grade datum would need is simply not in the document.
- RSS keeps the number too. Table 3.2.4-A: RSS Intensity and Dimensional Standards reads Height, max (ft) = 35, with no footnote on the height row. Footnote 15 explains the consolidation "maintains minimum lot width and maximum height standards to maintain the desired district character."
- Collateral evidence that the draft thinks in flood-elevated terms throughout. The porch exception at Sec. 3.1.5.A(4) caps the eave at "Twelve (12) feet above finished grade; or ... If the first floor of the dwelling is elevated to address flooding, 12 feet above the finished floor." The drafters reach for the finished floor whenever flooding is in play.
- Status: not adopted, and adoption has not started. From the City's own LDC Advisory Team presentation of October 2 2026, Next Steps slide: "Installment 3 being drafted, portions already being reviewed"; "City and Clarion collaborating on revisions to Installment 1 (Zoning Districts and Uses) and, following engagement, Installment 2"; "Updated drafts, testing, and start of adoption process expected in 2027." Installment 1 (Feb 17 2026) = Zoning Districts and Uses; Installment 2 (Oct 1 2026) = Administration; Installment 3 = Development Standards plus Articles 1, 7 and 8. The original "complete in the second half of 2026" target has slipped; 2027 is the start of adoption, not the end.
- Two status qualifiers that cut against over-reading the find. First, every Article 4 and Article 9 page carries the footer "Installment 1 Public Draft (Preview)" while Article 3 pages carry "Installment 1 Public Draft" without it - the height definition sits in the preview-labelled portion. Second, the same presentation states "Footnotes will not be included in final LDC," so footnote 603's carry-forward statement is drafting commentary that will not survive into enacted text; only the body of 9.2.4.A will.
- A live comment window, two days out. Public meeting Thursday October 29 2026, 6:30-8:00 PM, 2555 E Hanna Avenue (virtual option offered); written comments to TampaForward@tampagov.net. The page also notes more than 1,000 emails and questionnaire responses received so far, and names Articles 3 and 4 - not Article 9 - as what staff is currently reworking.
Convergences and contradictions
- Four independent surfaces inside the draft converge on "datum kept": the operative text of 9.2.4.A, the drafters' own footnote claiming carry-forward, the total absence of a competing Height entry in the A-to-Z definitions, and the near-total absence of grade vocabulary in 19,196 lines. The current code and the draft rewrite now agree, which closes the datum question on both branches rather than one.
- One genuine drafting wrinkle, and it is the opposite of what we feared. The draft's new explicit pointer is to Section 5-121, Flood-Resistant Development - and [[2026-10-25-tampa-freeboard-ae-zone-codified-requirement]] established that Section 5-121 contains no lowest-floor elevation requirement for a principal dwelling, because Tampa amended R322.2.2 through R322.3.7 and pointedly skipped R322.2.1. The operative BFE + 1 ft comes from the statewide Florida Building Code, Residential, not from Section 5-121. The phrase "including but not limited to" preserves the state source, so 12.0 ft NAVD88 still holds. But the one section the rewrite names is the one section that does not set the number, which makes the cross-reference read tighter than it actually is.
- No contradiction with the 10-11 brief, and a scope correction to it (U). That brief reported Installment 1 as "Articles 3, 4 and 9" and read Sec. 9.2.6; it did not record that Articles 4 and 9 are footer-labelled "(Preview)" while Article 3 is not, nor that the City's own installment taxonomy describes Installment 1 as "Zoning Districts and Use Regulations" with Definitions riding along. Immaterial to its conclusions, worth carrying forward correctly.
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
- When the revised Installment 1 is published, does Sec. 9.2.4.A survive unchanged, and does the enacted-text version keep the "including but not limited to" phrasing that preserves the statewide FBC-R source once footnote 603 is stripped?
- Does Installment 3 (Development Standards, Articles 1/5/6/7/8, still being drafted) introduce any height exception, encroachment or measurement provision for single-family detached development in RSS - the current code's Sec. 27-158(a) exclusions for parapets, chimneys and cupolas have no visible counterpart in the published installments?
- Does the rewrite carry forward Sec. 27-158(a) at all, and if not, does the ridge remain the governing point for a hip roof under the new code?
- On a zoning-map basis rather than a text basis, is 1212 S Suffolk Dr actually proposed for RSS, and is a conversion map published anywhere - Installment 1 describes a text-level district consolidation with no parcel mapping cited?
- Does Tampa's plan-review practice measure height from the required finished floor or from the as-built finished floor, since the draft keeps the word "required" and the gap between a 12.0 ft code floor and a 13.0-14.0 ft design floor is worth a foot or two of ridge budget either way? This is a Zoning Verification Letter question, not a desk-research one.
Related
- [[2026-10-24-tampa-ord-2026-49-height-definition-check]] - the parent brief; this discharges its first open follow-up
- [[2026-10-21-tampa-rs75-height-limit-datum]] - the original datum verdict and the slack arithmetic this brief reuses unchanged
- [[2026-10-25-tampa-freeboard-ae-zone-codified-requirement]] - pins the required finished floor at 12.0 ft NAVD88 and establishes that Sec. 5-121 sets no lowest-floor elevation, which is what makes the draft's new cross-reference worth a comment
- [[2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage]] - mapped the rewrite installments, RSS consolidation and Sec. 9.2.6; dedupe-checked, it never reached the Article 9 height definition
- [[2026-10-17-sterling-plan-fit-and-cost]] - the ~33 ft ridge estimate the surviving verdict applies to
- [[zoning-flood-zone-findings]] - parcel zoning and flood facts, and the Zoning Verification Letter question queue this feeds
- [[2026-07-22-ae-zone-elevation-cost-premium-tampa]] - BFE, grade and elevation-certificate numbers behind the slack math
Sources
- City of Tampa, Updated Land Development Code, Installment 1 Public Draft, February 17 2026, 411 pages (Sec. 9.2.4.A Building Height and footnote 603 at page 9-9; Section 9.3 Definitions pages 9-12 to 9-55; Table 3.2.4-A RSS at page 3-13 and footnotes 15-16 at page 3-12; Sec. 3.1.5.A(4) porch eave exception at page 3-6) - https://www.tampa.gov/sites/default/files/document/2026/tampa-updated-ldc-inst-1-public-draft-feb-17-2026-1.pdf (read 2026-10-27; downloaded with a browser user agent, text extracted with
pdftotext -layout, 19,196 lines, full-text scanned for grade vocabulary) - City of Tampa, LDC Advisory Team Installment 2 presentation, October 2 2026 (Work Program and Schedule slide 4-5; Updated LDC Installments slide 7; "Reviewing the Draft - footnotes will not be included in final LDC"; Update on Installment 1 slides 42-44; Next Steps slide 46 "Updated drafts, testing, and start of adoption process expected in 2027") - https://www.tampa.gov/sites/default/files/document/2026/tam_adv-team-installment-2-presentation-initial_final-rem.pdf (read 2026-10-27)
- City of Tampa, "Tampa Updates its Land Development Code" (tampa.gov/TampaForward) - announcement timeline through October 2026, Installment 2 release, October 29 2026 public meeting details, and the TampaForward@tampagov.net comment address - https://www.tampa.gov/development-coordination/tampa-updates-its-land-development-code (read 2026-10-27;
tampa.gov/TampaForwardredirects here) - City of Tampa, Updated LDC Installment 2 Public Draft, October 1 2026 (Administration; cited for installment sequencing only, not read for this question) - https://www.tampa.gov/sites/default/files/document/2026/tampa_updated_ldc-inst_2_public_draft_oct_1_2026_remediated-v6.pdf
- City of Tampa, Tampa Forward project timeline graphic (Task 2 Assessment to March 2025, Task 3 drafting April 2025 to May 2026, Task 4 testing June-July 2026; superseded by the October 2026 presentation) - https://www.tampa.gov/sites/default/files/document/2026/tampa-forward-timeline_ada.pdf
- WebSearch, "Tampa Forward Land Development Code update Installment 3 adoption schedule 2026 2027" (2026-10-27) - returned no published Installment 3 adoption schedule; the city presentation above is the authoritative timing source. One result, cp.soar.com, self-identifies as AI-generated and was not relied on.
- Vault: ~/rdco-vault/06-reference/research/2026-10-24-tampa-ord-2026-49-height-definition-check.md
- Vault: ~/rdco-vault/06-reference/research/2026-10-21-tampa-rs75-height-limit-datum.md
- Vault: ~/rdco-vault/06-reference/research/2026-10-25-tampa-freeboard-ae-zone-codified-requirement.md
- Vault: ~/rdco-vault/06-reference/research/2026-10-11-tampa-sunset-park-zoning-overlay-far-lot-coverage.md
- Vault: ~/rdco-vault/01-projects/life/home-build/2026-10-17-sterling-plan-fit-and-cost.md
- Vault: ~/rdco-vault/06-reference/research/2026-07-22-ae-zone-elevation-cost-premium-tampa.md
- Vault: ~/rdco-vault/01-projects/home-rebuild-2027/zoning-flood-zone-findings.md