Maitland’s demolition checklist asks whether trees will be removed and whether a separate tree permit has been obtained. Treat that as a hold point: the demolition application cannot stand in for the tree decision.
Open two project tracks
The demolition checklist supports a file for the structure, ownership, site plan, utilities, debris, tree effects, application, permit, inspections, and closeout. Beside it, create a tree track with tree identifiers, location plan, photographs or supporting evidence requested by the City, application, decision, permit, conditions, inspection, and final result.
| Milestone | Demolition proof | Tree proof |
|---|---|---|
| Intake | Accepted demolition package | Accepted tree package if triggered |
| Review | Corrections and approvals | Tree corrections and written decision |
| Authorization | Issued demolition permit | Issued tree permit |
| Field work | Demolition inspection record | Tree inspection or condition record |
| Final | Demolition final status | Tree permit final status |
Do not mark a row complete from the neighboring column.
Treat fee evidence narrowly
The application-fee page lists tree-removal activity separately. Record the dated row and the City’s actual assessment, but do not use it to estimate the whole demolition or tree cost. Payment proves a transaction, not approval.
Connect changes explicitly
If the demolition plan changes which trees are affected, resubmit the relevant records to both tracks as the City directs. Retain the revised plan and written responses before field work.
Local Service Ledger reviewed the checklist and fee page on August 27, 2026. We did not inspect a structure or tree, advise utility disconnection or debris handling, calculate charges, or obtain permits.