Temple Terrace’s email permit process has two separate deadlines: one for delivering plans when review is required, and another for paying after the City processes a complete application. Neither is a one-day approval promise. There is also a discrepancy to resolve before sending documents: the linked policy and current permit contact use different email domains.
Confirm the destination before sending plans
The linked email policy names PermitApplication@templeterrace.com and says applications sent elsewhere will not be processed. The contact link on the current Permitting Services page instead uses permitapplication@templeterrace.gov.
Call the permit coordinator at 813-506-6470 to confirm the accepted application address. LSL has not established whether either mailbox forwards to the other. Do not send duplicate applications or sensitive project documents to both addresses simply to cover the discrepancy. A sent-message receipt does not establish City acceptance.
Which projects fit the email process?
The City’s normal email lane is for over-the-counter permits that do not need zoning or plan review. Its examples include roof, plumbing, specified electrical work, air-conditioner replacement, and certain siding, openings and storm-protection work. A listed trade is not an eligibility decision for every project in that trade. Scope and examples
Two examples depend on an earlier approval:
- Residential tree removal requires City Arborist approval first.
- Electrical, mechanical, plumbing, roof and gas work connected to new construction, additions or renovations requires the building contractor’s plans to have been reviewed and the building permit issued.
For mixed work, describe the whole scope when asking staff which application route applies. The forms index identifies application families; having a form listed there does not make it eligible for email processing.
Prepare the contractor authorization, not just the PDF
The email policy requires the contractor to be registered with the City, active and current, with a Contractor Email Authorization on file. The applicant must be listed as an authorized agent. Complete, initial and sign the appropriate application before scanning it as a PDF. An owner-builder should not assume this contractor-specific authorization process establishes their own eligibility. Policy prerequisites
Retain the submitted application and any City correction request together so the revised scope remains identifiable. Before starting work, the important distinction is between an application awaiting action and a permit actually issued.
The two clocks start at different events
| Published deadline | What starts it | What the policy requires |
|---|---|---|
| One business day for a plan-review handoff | Emailing the permit application | Deliver plans and other required submittals in person when plan review is required; the policy does not accept those plans electronically through this process |
| One business day for payment | City’s notice that payment is ready after processing a complete application | Pay within the policy’s deadline; it describes loss of email privileges for late payment |
These instructions come from the linked policy. The plan-review branch is a separate physical handoff, not permission to attach reviewed plans to the ordinary over-the-counter email lane. Confirm the counter arrangements with staff before using that branch. Save the plan-delivery acknowledgment separately from the emailed application.
What must be on site before work starts
After payment, obtain the issued permit and inspection sheet, print both and post them at the site as the policy requires. A payment request, receipt or emailed application is not a substitute for the issued documents.
Use the project’s inspection sheet for the required inspections. The City’s online service supports status checks, payment, inspection scheduling and results, but issuance is not evidence that the work passed inspection. Permit services
What this comparison checked
LSL read the operative permit page, forms index and complete one-page email policy on September 21, 2026, including the policy’s original layout. We compared the scope exceptions, prerequisites, email destination and two deadlines. We did not submit an application, test either mailbox or obtain a project-specific City determination. The undated policy remains linked from the current City page; confirm the conflicting destination before relying on it.