Fence requirements vary with location and site conditions. A permit exemption is not a blanket exemption from other rules. Start with the authority serving the property address and describe the proposed location, material, height and relationship to streets, corners and retaining walls.
Prepare a useful inquiry
Bring a simple plan and elevation rather than asking only whether fences need permits. Identify front, side and rear boundaries, existing grade, nearby intersections and any wall beneath the fence. Describe gates and any special use of the enclosure. Ask which department addresses zoning, building permits and right-of-way questions. Save the response with the date and the project description so later design changes can be compared against the same facts.
Use examples as prompts
Seattle publishes a fence guidance page that discusses permit conditions and other location-related rules. Its value here is to show the kinds of questions a city may address, not to establish a national fence height. Your jurisdiction may measure height differently or apply different conditions near streets or retaining walls. Check the current local source and ask about the actual site. Community association requirements, where applicable, should be tracked separately from public approvals.
Keep an approval record
Maintain a short checklist of required submissions, responsible parties and unresolved items. Record the final reviewed layout alongside relevant correspondence or permits. If the location, height, material or gate arrangement changes, check whether the earlier answer still applies. Include the current drawing revision in the contractor brief and avoid describing a preliminary concept as approved. The purpose of this record is simple: the person ordering infill and the person installing the fence should be working from the same current scope.
Evidence & scope
Illustrative local permitting source only. Rules and permit exemptions are jurisdiction- and site-specific.
Original planning guidance. References support their stated technical scope; examples and workflows do not establish product approval.