One total fence length will not explain a project with different materials, heights or gate movements. St. Cloud’s application needs a drawing that identifies those differences. Its current instructions also leave an upload question unresolved: some documents have conditional explanations but required-field markers.
Prepare the drawing, not just the total
The City checklist allows either an annotated property survey or a site plan containing the additional listed property information. Show each proposed run, its material, height above grade and length; identify gate locations and opening directions. If the fence is set inside the boundary, show that offset. Separate runs when material or height changes.
For the site-plan alternative, include boundaries, structures, applicable easements, nearby drainage features and the proposed fence’s FEMA flood zone. That option is not permission to guess where a property line lies.
LSL’s optional working legend below can be keyed to your own drawing. Replace the blanks with verified project information; it is not a City form or a design recommendation.
| Drawing label | Description to complete | Cross-check before copying to the application |
|---|---|---|
| Run A | ___ feet long; ___ material; ___ height | Same start/end points and boundary offset on drawing |
| Run B | ___ feet long; ___ material; ___ height | Separate from A if its specification changes |
| Gate G1 | ___ location; ___ opening direction | Gate count and movement agree with drawing |
Add labels as needed. This helps expose a mismatch—for example, two differently specified runs collapsed into one undifferentiated total—before asking the City to review the application.
When an upload says required but the explanation says conditional
The public application says the covenant is needed for a fence on a drainage/utility easement. Its covenant upload is nevertheless marked required, and the checklist lists the covenant without that qualifier. The owner-builder explanation applies to residential owners acting as contractor, but that upload also carries a required marker.
Ask Community Development at 407-957-1567, the checklist’s contact, how to handle the particular inapplicable attachment. Name the field and describe why its stated condition does not fit. We inspected the displayed instructions, not a submitted application or its validation behavior. Do not sign an inaccurate declaration or upload invented evidence just to proceed.
The checklist separately calls for a Certificate of Appropriateness application and applicable fee for property in the Downtown Historic District. The live form also gives notice and ownership conditions; confirm your project’s requirements rather than treating every attachment as universal.
Read what the signatures actually attest to
The two-page covenant addresses access to easements, removal costs and private restrictions. It expressly separates a City permit from compliance with private deed restrictions, and describes circumstances in which the City may require an as-built survey over possible encroachment. Those provisions make it more than an upload receipt. Review the complete document and get qualified advice about private rights or obligations you do not understand.
The separate installation affidavit asks the owner or contractor to affirm that installation will follow the attached approved survey and review requirements. If preparing the checklist’s site-plan alternative, ask which approved drawing the City requires with that affidavit. A signature does not itself establish that the City approved a drawing or passed an inspection.
Checked September 12, 2026: the public form and its three linked PDFs. No private boundary, easement, historic designation, application or fence was examined. The original checklist link was broken; the current linked documents, not a search snippet’s date, support this preparation guide.