Temple Terrace accepts some applications by email, but email is only an intake channel. It is not permission to begin work. The work-ready record is the issued permit after fees are paid, with both the permit and inspection sheet posted at the site.
Route the scope before sending a file
The City’s current Permitting Services page limits email processing to permits typically issued over the counter and not requiring zoning or plan review.
| Scope condition | First record to preserve | Likely handoff to confirm |
|---|---|---|
| Named over-the-counter example with no zoning or plan review | Scope-specific application | Email intake |
| Work requires reviewed plans | Application plus complete submittal | In-person plan handoff |
| Residential tree removal | City Arborist approval | Email only after that approval |
| Trade work tied to new construction, addition, or renovation | Issued building permit and reviewed-plan reference | Related trade-permit application |
| Scope does not fit a named example | Written City route response | Channel the City assigns |
The City’s examples include roof, plumbing, certain electrical work, air-conditioner replacement, siding or stucco, soffit or fascia, specified openings and storm-protection work, and conditional tree or related-trade applications. An example is not a blanket determination. Mixed scopes can create another review branch.
Keep a ten-event custody ledger
| Event | Evidence to save | Stop condition |
|---|---|---|
| 1. Jurisdiction | Address and City confirmation | A Temple Terrace mailing address alone is not enough |
| 2. Scope | Itemized work description | Mixed or uncertain work needs a route decision |
| 3. Prerequisite | Arborist, zoning, building-permit, or other approval | Do not skip a required earlier authority |
| 4. Applicant authority | Contractor status, email authorization, and authorized-agent record | Missing authority blocks the policy route |
| 5. Application | Signed scope-specific form from the current index | A form alone is not submission |
| 6. Submission | Sent PDF and delivery record | Submission is not approval |
| 7. Correction | City notice and amended resubmission | Incomplete applications are not processed as complete |
| 8. Payment/issuance | Fee notice, receipt, issued permit, inspection sheet | Do not start with only a payment request |
| 9. Site/inspection | Posted records, inspection requests, and results | Work is not final after issuance |
| 10. Closeout | Final inspection or City-issued completion record | Confirm the exact final record for the permit |
This ledger prevents the emailed PDF, payment notice, and issued permit from being saved under one ambiguous filename.
Satisfy the policy prerequisites before emailing
The City’s email policy says the contractor must be registered with the City, active and current, and have a Contractor Email Authorization on file. The applicant must also be listed as an authorized agent.
The process calls for the appropriate application to be completed, initialed and signed, scanned as a PDF, and sent to the specific address named in the live policy. Save the final PDF and the sent-message record. Do not reproduce the policy address in a reusable template without checking the live document again.
If the City identifies missing information, keep its notice with the amended application. Do not overwrite the original: the difference between versions explains what changed.
Plan-review work leaves the email lane
The policy says plans requiring review are not accepted electronically through this email process. It directs applicants to provide them in person with the other required submittals within one business day after emailing the permit application.
Record the emailed application time and the separate counter receipt. The one-business-day instruction is a handoff clock, not a promise that review or issuance will finish in one day.
Use the current forms page to identify the application family—building, electric, gas, mechanical, plumbing, roof, tree, or another listed scope. The form name helps route the file; City staff still decides the complete submittal.
Payment is not the same event as issuance
After a complete application is processed, the policy says the City emails a notice that payment is ready. It sets a one-business-day payment requirement and describes consequences for late payment.
Keep four separate items:
- the City’s payment notice;
- the payment receipt;
- the issued permit; and
- the inspection sheet.
The policy requires the permit and inspection sheet to be printed and posted before work starts. A receipt without the issued documents does not satisfy that sequence.
Check exceptions against the current page
The City page also publishes exemptions and a July 2026 HB 803 request route. Those rules are scope-specific. Mechanical, electrical, gas, and plumbing work are treated differently from listed nonstructural work, and the Building Official must approve an HB 803 exemption request before work begins.
Do not infer an exemption because a project is small, describe a repair as maintenance without City confirmation, or divide a larger operation into smaller pieces. Preserve the approved exemption record if that route applies.
Finish with the inspection record
Temple Terrace’s online permit service can display application status, fees, inspection results, and inspection scheduling. Save the permit number, each requested inspection, result, correction, reinspection, and final record. The inspection sheet identifies project-specific steps more reliably than a generic checklist.
Source and method
Local Service Ledger reviewed the City’s current permit page, linked email policy, and form index on August 24, 2026. We converted them into a route matrix and ten-event custody ledger. We did not file a permit, interpret code, inspect work, or receive a City decision for a specific property.