Do I have to hold a neighborhood meeting?

For most major land use applications in the Treasure Valley, yes. Even when it's not formally required by the city's code, planning staff and elected officials expect to see one in the application packet. Skipping the meeting is a signal that the applicant isn't serious — and it tends to predict denial or extensive conditions.

What's the right radius for notification?

Most cities require notification of property owners within 300 feet of the project boundary. Some cities use 500 feet. Always verify with city planning staff. When in doubt, expand the radius — the cost of mailing extra invitations is trivial compared to the cost of a contested hearing.

What if no one shows up to the meeting?

That's still a successful meeting. Document the attempt — sign-in sheet (even if blank), photos of the room and exhibits, the mailing list, the proof of mailing. Cities typically accept a documented no-attendance outcome as evidence of good-faith effort.

What if the meeting gets ugly?

It happens. Neighbors arrive angry. Voices get raised. The applicant team should stay calm, listen, document, and follow up in writing. A meeting that exposed real opposition is more useful than a meeting where nobody spoke up. You now know what's coming at the public hearing and can prepare for it.

Should I bring an attorney?

For contested projects, yes. For most projects, the project planner and engineer are sufficient. If your project is in a politically charged environment (Caldwell post-2026 pushback, Meridian post-restrictiveness shift, Eagle post-Avimor), having legal counsel present is appropriate.

Can I hold the meeting virtually?

Most Treasure Valley cities now allow virtual or hybrid neighborhood meetings, particularly for projects with non-local property owners. Verify with planning staff before assuming. Hybrid format (in-person and virtual) is the most inclusive but requires more setup.

How do I document the meeting for the application?

Most cities require: a sign-in sheet, the mailing list with proof of mailing, photos of the meeting room with exhibits visible, a written summary of concerns raised, and the applicant's response to each concern. Bailey assembles all of this as a standard part of every entitlement engagement.

What's the difference between a neighborhood meeting and a public hearing?

A neighborhood meeting is informal, organized by the applicant, held before the hearing, and serves as a private conversation with neighbors. A public hearing is formal, organized by the city, held in front of the planning board or city council, recorded, and ends with a vote. The neighborhood meeting is your chance to influence what happens at the public hearing.

Are neighborhood meetings required before a public hearing in Idaho?

What a neighborhood meeting actually is

A neighborhood meeting is a structured, pre-hearing conversation between the project applicant and the people who live near the proposed development. It is required by most Treasure Valley cities for any major land use application — annexation, rezone, comp plan amendment, preliminary plat, conditional use permit. The meeting happens before the public hearing, typically with notice mailed to property owners within a defined radius (commonly 300 feet) at least 10 days in advance.

The format is loose by design. Most meetings are held on a weekday evening, between 5:30 and 8:00 PM, in a neutral location — a community room, a church hall, sometimes a virtual session for remote participants. The applicant presents the project, takes questions, and listens.

Documentation matters as much as attendance. The meeting summary, sign-in sheet, mailing list, and photo of the project exhibits go into the application packet. Cities verify that the meeting actually happened before they accept the application.

Neighborhood meetings are not where you sell the project. They’re where you find out what the project will face.

Bailey methodology

Why they work

Two reasons.

1. They surface opposition before the hearing

Public hearings are not a good environment for explaining a plan or negotiating with neighbors. The clock is running, the room is full, the cameras are on, and the planning board is watching. By the time someone stands up at the microphone and says “this project will ruin my view,” it’s too late to redesign — the only options are to argue, to defer, or to take the loss.

A neighborhood meeting puts that same conversation in a low-stakes environment. The neighbor can explain their concern. The applicant can explain the design choice. Sometimes the design changes. Sometimes it doesn’t, but the neighbor leaves understanding why. Either way, the conversation happens before the city council is deciding whether to approve, condition, or deny.

Most neighborhood views and most builder/developer views are not going to be consistent. That’s expected. But it’s far better to stand before the planning board and say “we held meetings with the neighbors and incorporated their feedback where we could” than to be hearing the objection for the first time at the dais.

2. They satisfy the city’s expectation that you’ve done the work

Planning staff and elected officials look at neighborhood meetings as a signal of whether the applicant is serious. An applicant who skipped the meeting, ran it badly, or gave it lip service is treated differently than one who clearly invested in the conversation. The follow-up matters: cities want to see that concerns raised at the meeting were actually addressed in the application.

In Boise, applicants who can demonstrate substantive neighbor engagement get the benefit of the doubt on close calls. In Meridian, where the council has grown more cautious, demonstrated community engagement is one of the few things that still moves the needle on contested applications. In Caldwell, where the political temperature is elevated and the P&Z chair has reported death threats, neighborhood meetings are a precondition for any contested project — applicants who don’t engage early lose.

How to run a meeting that earns trust

The mechanics are simple. The execution is where projects win or lose.

Get the notification right

Order the property owner list from the city or county. Most Treasure Valley cities will provide a 300-foot radius mailing list for a small fee. Garden City requires you to request the list from [email protected] for the SAP process.
Mail invitations at least 10 days before the meeting. Some cities require longer notice — verify before scheduling.
Include date, time, location, project address, a brief description of what’s being proposed, and a phone number/email to contact the applicant.
If you can, hand-deliver to immediate neighbors as well. The neighbor who got an envelope under the door is more receptive than the one who got a form letter.

Pick the right location and time

Weekday evening between 5:30 and 8:00 PM. Most working neighbors can’t attend daytime meetings.
Neutral location within reasonable distance of the project. Community rooms, church halls, library meeting rooms, or virtual sessions all work.
Comfortable enough for a conversation. A sit-down format with chairs facing exhibits invites discussion. A formal podium-and-rows-of-chairs setup invites confrontation.

Bring the right materials

A site plan exhibit large enough to walk people through.
Architectural elevations or renderings if your project includes vertical construction.
A simple project summary handout — one page, plain language.
A sign-in sheet with name, address, and email.
A note-taker who captures every concern raised.

Run the meeting like a host, not a defender

Start by introducing the design team. Engineers, planners, the developer themselves if possible.
Walk through the project at a high level — what’s being built, where, and when.
Then shut up and listen. The neighbors are not there to hear you talk for 40 minutes. They’re there to ask questions and raise concerns.
Take every concern seriously, even the ones that don’t seem relevant. The neighbor who feels heard is the neighbor who doesn’t show up to the public hearing with a sign.
Don’t promise what you can’t deliver. If a concern can’t be addressed, say so honestly and explain why.
Document every concern in writing.

Follow up

The most overlooked part of the process. After the meeting:

Send a written summary to every attendee within a week.
Update the application packet to address concerns where the design changed.
For concerns that didn’t change the design, document the reason.
For attendees who became allies, ask if they’re willing to provide written or oral testimony in support at the public hearing.

City-by-city requirements

Neighborhood meeting requirements vary across the Treasure Valley. A few that matter:

Boise: Required for most major applications. Notice typically 10+ days before the meeting.
Meridian: Required for annexation, rezone, comp plan amendment, conditional use, and preliminary plat. Documentation in the application packet.
Nampa: Required for major land use applications. The city’s three-criteria test for approval includes evidence of community engagement.
Eagle: Required, with a stricter five-working-day rule for written testimony at the hearing itself. Plan accordingly.
Garden City: Mandatory for the Specific Area Plan (SAP) process. Includes a 300-foot property owner list requirement (request from [email protected]), 10-day mailing notice, and held between 5:30 and 8:00 PM on a weekday. Verification required at submittal.
Caldwell, Kuna, Middleton, Star: Verify current requirements with planning staff. All four have neighborhood meeting expectations for contested applications even when not formally required for every application type.