Public Notice Radius: 300 vs 500 ft — Which Does Your City Require?

By Leo Yong · Last updated May 14, 2026 · 11 min read

If you are prepping a public notice mailing and your jurisdiction's code says something like "owners of property within X feet," you are trying to answer two questions at once: what is the right distance for your project type, and where exactly do you look it up? The short answer: there is no national standard. Notification distances run from 200 to 1,000 feet depending on the state, the city, the zoning district, and the permit category. The number lives in your local zoning code, often cross-referenced with a state enabling statute. This guide shows you how to find it, what common mistakes look like, and how to build the mailing list once you have the number confirmed.

The Common Ranges, and Why They Exist

Most public notice mailing radius requirements in the U.S. cluster around four distances: 200, 300, 500, and 1,000 feet. A few states set a statutory floor; most leave the number to the city or county.

The variance between 300 and 500 feet is not arbitrary. Cities that adopted their codes in the 1960s and 70s often landed on 300 feet because that was the California minimum at the time and it spread as a template. Cities that revisited their codes later, or that updated them after contested approvals, frequently bumped to 500 feet for the heavier permit categories. The practical difference at 300 feet versus 500 feet on a typical urban lot can mean 40 extra parcels or 200, depending on the neighborhood density.

Why the Radius Varies Even Within One City

The same planning department may apply three different distances depending on what you are applying for. A conditional use permit for a restaurant often triggers one radius; a zone change triggers another; a variance for a setback may trigger a third. The permit type determines which code section applies, and each section may carry its own distance.

Zoning overlays add another layer. A coastal zone overlay, hillside overlay, or historic preservation overlay can require supplemental notice to additional parties outside the standard radius. Specific plans sometimes override the base zoning code and specify their own distances. When a project falls under multiple overlapping requirements, use the largest radius that applies.

A few permit types that commonly carry elevated distances:

• General plan amendments (often 500-1,000 ft)
• Environmental impact report scoping notices (often 300-500 ft plus posted notice)
• Cannabis dispensary siting (highly variable; some California cities require 600-1,000 ft)
• Wireless telecommunications facilities (FCC shot-clock applies, but notice radius is locally set)
• Subdivision tentative maps (some states require adjacent landowner notice regardless of distance)

How to Find Your Jurisdiction's Requirement

The most reliable path is to read the actual code section. The most common mistake is relying on what a colleague said last year, or what a similar project used in a neighboring city. Those answers may be right, or they may reflect an ordinance that was amended two years ago.

Search the municipal code directly

Most cities post their full municipal code online. The fastest search pattern:

site:municode.com "[Your City]" "public notice" radius

Or search for your city on Municode Library, then look in the chapter titled "Zoning Procedures," "Development Review," or "Public Hearings." The notice radius is usually one sentence inside the section on notice requirements for the permit type you are working on.

Check the planning department's application packet

Planning departments publish application checklists that typically list the required radius and note how to document it. Search for your city name plus terms like "public hearing notice affidavit" or "mailing list requirements." These PDFs are often more current than a third-party code website.

Examples across jurisdiction sizes

Measuring the Radius: Three Common Mistakes

1. Measuring from the wrong reference point

The code almost always says "from the exterior boundaries of the subject property," not from the parcel centroid and not from the building. On a large lot, this matters. A 500-foot radius drawn from the center of a 2-acre parcel will miss properties that a 500-foot radius from the property line would catch. Draw the buffer from the parcel boundary, not the middle of it.

2. Excluding right-of-way parcels

Streets and alleys are often recorded as separate parcels in the assessor's data. They have no owner to notify, but they count as parcel geometry when your GIS calculates the buffer. If your tool does not dissolve the right-of-way parcels before clipping the radius, your circle may appear to stop short on one side. This rarely causes a legal problem, but it can exclude corner parcels across the street that the code intends to cover.

3. Using situs address instead of mailing address

Assessor data carries two addresses for most parcels: the property address (situs) and the owner's mailing address. For owner-occupied residential property they are often the same. For rental properties, commercial buildings, LLCs, and trusts, they are frequently different. The notice must go to where the owner receives mail. See our guide on assessor parcel numbers and the data they carry for more on how these fields work.

4. Missing condo units and air-rights parcels

A condominium complex may record each unit as a separate parcel, each with its own owner. A radius buffer that clips a condo building might yield 40 parcels where a single-family block would yield 4. Assessor data handles this inconsistently across counties. Some record a master parcel and a separate "unit roll"; others record each unit individually. Spot-check your output list against the building footprint for any large multi-unit structures inside the buffer.

5. Stale assessor data

County parcel data updates on different schedules. Some GIS layers are refreshed weekly; others lag by months after a sale closes. For contested projects or hearing-critical mailings, request a certified owner list from the county assessor's office directly, or note the data date in your affidavit. The UrbanKit Parcel Atlas lists which counties publish live REST feeds versus static annual snapshots.

Legal Notice vs. Courtesy Notice

Not every mailing you send has the same legal weight. Most permit processes require a legal notice sent by first-class mail (some by certified mail) to all property owners within the required radius. That mailing, its date, and the complete list typically need to be documented in an affidavit of mailing that gets attached to the hearing record.

A courtesy notice is anything beyond the legal minimum: additional owners you notify voluntarily, email notices to registered neighborhood associations, door-hanger drops. There is no penalty for courtesy notice, and it often reduces hearing opposition from neighbors who feel blindsided. Some planners add a courtesy buffer of 50 to 100 extra feet on top of the legal minimum for exactly this reason.

The practical difference matters if the project is challenged. An applicant who sent legal notice to every required owner, documented in an affidavit, is in a stronger position than one who informally emailed people and assumed the mailing list was handled. Keep the paper trail.

When to Intentionally Over-Notify

There is no legal downside to notifying more property owners than required. There are several reasons to do it.

Projects near district boundaries often have radius buffers that stop a few feet short of a neighborhood association boundary or school district boundary. Including those extra parcels costs a few more stamps and reduces the chance a stakeholder group appears at the hearing claiming they had no idea the project was happening.

For politically sensitive projects, a larger mailing list also demonstrates good-faith outreach. Planning commissions and city councils take note when an applicant shows up with a 600-foot mailing list for a project that only required 300 feet. It is a visible signal that the applicant is not trying to minimize notice.

The calculus flips only when cost is prohibitive on large parcels. A 500-foot radius around a 20-acre industrial site can yield 2,000 or more property owners. In those cases, confirm the exact legal minimum and document it carefully.

State-Statute Floors Worth Knowing

A few states set a minimum by statute that local codes cannot go below. These are floors, not ceilings. Local codes commonly exceed them.

• California: Government Code § 65091 requires mailed notice to owners within 300 feet for most discretionary approvals. The provision also requires notice to "occupants" in some cases, which is often missed. Local cities frequently set 500 feet for zone changes.
• Texas: Local Government Code § 211.006 requires written notice to owners within 200 feet of proposed zoning changes. Texas cities vary widely on other permit types.
• Florida: The state does not set a general radius floor for local zoning notices. Each municipality sets its own requirement under its land development regulations.
• Washington: RCW 36.70B.110 governs project permit notice and requires notice to "owners of property within 300 feet" for certain project types, but city codes frequently go higher.
• Oregon: ORS 227.175 requires notice to property owners within 100 feet for Type II procedures at the state minimum, though most cities use 300 feet or more in local code.

If you are working in a state not listed here, search the state legislature's site for the phrase "within [X] feet" "property owners" "notice" in the planning or zoning statutes section. That search pattern usually surfaces the relevant provision within two or three results.

Finding the Right Layer for Your Mailing List

Once you know your radius, the next task is identifying which parcels fall inside it and pulling the owner mailing addresses. County GIS departments publish parcel layers through ArcGIS REST endpoints. Our guide on finding any county's ArcGIS parcel layer URL covers the search patterns. The short version: search for [county name] arcgis rest services parcel and look for a URL containing /arcgis/rest/services/.

Some counties separate the spatial parcel layer from the owner data. The GIS layer holds geometry and the parcel number; the assessor's database holds the mailing address. If your parcel layer returns geometries but no mailing addresses, you may need to query the assessor's database separately using the parcel number (APN or PIN) as the join key. The Parcel Atlas notes which county layers expose mailing address fields directly on the GIS endpoint.

Related Resources

• Public Notice Radius Requirements: What Varies by Jurisdiction — a broader overview of notification types, supplemental requirements, and documentation best practices
• What is an APN? — how assessor parcel numbers work and why they matter for building a clean mailing list
• How to Find an ArcGIS Parcel Layer URL — locate the REST endpoint for your county's parcel data
• Deduplicating Mailing Lists: LLCs, Trusts, and Same-Owner Parcels — how to handle entity-owned and co-owned properties in your list
• Radius Notice Generator — generate the mailing list once you have your radius confirmed
• Parcel Lookup Tool — look up individual parcel details by APN or address
• Parcel Atlas — county-by-county index of parcel layer endpoints and field coverage