Tampa synthetic-turf work needs a reviewed site plan before installation, but the verification statement describes a personal examination of the installed work. Those documents belong at different points in the project. The current City packet makes the statement an upload before scheduling the final inspection—not a truthful certification to sign before the work exists.
The file has to show where the turf goes, how the surface handles water, what remains outside the work area, and how protected trees are kept out of construction traffic.
Separate application documents from inspection evidence
The City landing page identifies the notarized statement and site plan. The actual nine-page packet explains the order and additional documents:
| Before application/review | Before the BLD Final inspection |
|---|---|
| Record type BLD Miscellaneous; permit type Driveway, Patio Slab, Deck | Approved plan onsite and verification statement uploaded |
| Site plan with coverage, boundaries, onsite trees and neighboring trees within 20 feet | Product documents and FDOT purchase/verification evidence |
| Cross-section identifying the proposed system | Supplier aggregate testing and any filter-fabric permeability specifications required by the stormwater guidance |
| Identify historic-district review and the correct occupancy route; condos require commercial permits | Notice of commencement when required; the packet identifies jobs greater than $5,000 |
The statement instructs upload under Other documents, with Synthetic Turf Verification Statement as the document name. It includes a notary block visible in the PDF even though text extraction omits that block. Ask the City who may certify the actual inspection and what registration applies. The packet identifies one BLD Final inspection for this turf permit; it does not waive unrelated permits triggered by a larger project.
Draw one parcel worksheet before choosing a product
Use a single base drawing and give every area its own row:
| Parcel field | Existing | Proposed | Evidence still needed |
|---|---|---|---|
| Total lot area | no change | Survey or accepted parcel record | |
| Building footprint | Dimensions and permitted additions | ||
| Pool, deck, and enclosure | Pool-specific layout if present | ||
| Existing hardscape | Driveway, walk, patio, equipment pads | ||
| Proposed synthetic turf | Dimensions and system detail | ||
| Remaining planted/green area | City-accepted classification and calculation | ||
| Protected tree/root zones | Approved limits and barricade locations | ||
| Surface-water route | Direction, discharge point, and stormwater detail |
Do not fill the “proposed synthetic turf” row with the whole yard. The July permitting-packet page says the packet includes different site-plan examples for a basic site, a pool, multiple landscaping areas, and a pervious system. Those examples signal that site conditions change the drawing; they do not approve a particular parcel by analogy.
There are also errors and review marks in the examples. The pool example prints 10,533 − 4,670 − 2,703 as 1,560 square feet; LSL independently recalculated those printed inputs as 3,160 square feet. That checks only the subtraction—not whether the source areas or classifications are correct. The multiple-landscape example shows 24% green space with a note that 25% or more is needed. Neither should be copied as an approved compliant design.
Record total lot area and the remaining landscape area, but let the City decide what counts. The tree-protection document references a 25-percent lot-area green-space requirement. That is a review field, not permission to subtract turf from a parcel map and announce compliance.
Resolve system details before buying aggregate
The packet’s May 2026 stormwater guidance permits only clean silica sand and/or zeolite infill, requires qualifying layers to meet its permeability criteria, and calls for at least four inches of clean stone over uncompacted underlying soil. It excludes screenings and specifies supplier test evidence. Its aggregate labels are FDOT #89, #57 or #4, while the older illustrated detail uses different numbered labels. Have the reviewer and supplier reconcile the specified material; LSL has not assumed those numbering systems are equivalent.
The guidance prohibits turf in rights of way, public easements, drainage swales, ditches and stormwater ponds. It also distinguishes pervious-area qualification from landscape/green-space requirements. A brochure calling a turf product “permeable” does not establish either result for the installed system.
Put tree protection on the construction plan
Tampa’s tree-protection record says protected-tree controls apply before construction activity. It bars unapproved grade changes, clearing, equipment or material storage, and vehicle parking inside the approved protection area.
Add these fields to the contractor-facing plan:
- each protected tree and its identification or measurement record;
- the City-approved root-protection boundary;
- barricade location and the date it was installed;
- delivery, material-storage, cutting, and equipment routes outside the protected area; and
- any City-approved tree work or deviation, preserved separately.
Artificial turf can cover what once looked like open yard. That visual change does not erase the subsurface root zone. Photograph the marked work limits before excavation, after the base is prepared, and before the surface conceals the edges.
Keep review changes instead of overwriting the drawing
Name the first site plan “submitted,” not “approved.” If the City requests another drainage detail, changes a boundary, or requires additional tree evidence, preserve the comment, response, corrected sheet, upload receipt, and approved version.
Give the installer only the accepted plan set and keep the permit number with it. At inspection, record the requested inspection type, date, result, any correction, the reinspection result, and final status. A turf warranty answers a product question; the City inspection record answers whether the installed work passed the required public review.
Source and method
Local Service Ledger rechecked the landing and packet pages, all nine packet pages and both tree-protection pages on September 21, 2026. The packet’s first page and four image-based examples/details were also visually inspected. We preserved the parcel worksheet, corrected certification timing and independently checked the cited subtraction. The tree-protection document itself is dated April 1, 2024; its later web upload is not a new rule date. We did not inspect a site, evaluate a product, or calculate compliance for a parcel.