What a public hearing actually is

A public hearing is a formal, recorded proceeding before a city’s Planning & Zoning Commission or City Council where your project is presented, public comment is taken, and a vote is held. It is the public-facing moment in the entitlement process — the part that ends up in the newspaper, the social media post, and the meeting minutes.

By the time the hearing starts, three things should already have happened:

  1. Staff has issued a recommendation (approve, approve with conditions, or deny)
  2. You’ve held a neighborhood meeting if your city or application requires one
  3. Your design team has prepared and rehearsed the presentation

If any of those three are missing, the hearing is more likely to be the place where you discover problems instead of the place where you confirm that the problems have already been solved.

Most public hearings are not a good environment for explaining a plan. They’re an environment for confirming what’s already been agreed.

Bailey methodology

The hearing format varies slightly by city, but the structure is consistent: staff presents the application and recommendation, the applicant presents the project, the public testifies (in favor and against), the applicant gets a brief rebuttal, the body deliberates, and a vote is taken.

Who decides what

In most Treasure Valley cities, two bodies make entitlement decisions:

Planning & Zoning Commission

P&Z is typically a five- to nine-member appointed body of city residents. Its authority varies by city:

  • In Boise, Meridian, and Nampa, P&Z recommends to City Council on annexations, rezones, comp plan amendments, preliminary plats, and most major land use applications. It decides standalone CUPs and variances (with appeal rights to Council).
  • In Garden City, P&Z is the final decision maker on conditional use permits and variances. This is unusual and means commissioner relationships matter more, not less.
  • In Eagle, P&Z recommends on all major applications, with City Council making the final call. The Design Review Board adds a third layer for commercial and subdivision applications.

P&Z hearings tend to be more deliberative and technical than Council hearings — commissioners are typically appointed for their land use expertise and ask detailed questions about code compliance, site design, and conditions.

City Council

City Council is the elected body that makes final decisions on most major land use applications. Council hearings tend to be more political — councilmembers respond to public testimony, organized neighborhood opposition, and the political hot buttons of the moment.

The PZ-to-Council disagreement rate varies significantly by city:

  • Boise: 19.1% — the highest in the valley. Nearly 1 in 5 applications that clear PZ get a different outcome at Council.
  • Meridian: 9.2% — moderate.
  • Nampa: 6.1% — the lowest. Once you clear PZ in Nampa, you almost always clear Council too.

Plan both hearings independently. PZ approval is necessary but, in some cities, not sufficient.

How to prepare for the hearing

The week before the hearing matters more than the day of. Three preparation moves separate winning hearings from contested ones:

Role-playing the presentation

Schedule a meeting with your design team two weeks before the hearing. Present the project specifics to a select internal audience. Each presenter — engineer, planner, traffic consultant, attorney — should be specific, on-point, and easy to understand.

The developer should act as the mayor and run the role-playing scenario seriously. Question every issue. Challenge the experts to think on their feet and concisely answer every question asked. Have other staff attend and ask the most adversarial questions you can imagine.

This format energizes the design team into a state of readiness and surfaces every weak point in the presentation before the public can. Nonbiased internal discussion of any lingering political issue is invaluable. Use visual aids during the role-play. Judge approach, style, and content against the goals you established for the project. Encourage the team to answer questions completely without offering more information than the question requires.

Know what your design team will say, when they will say it, and why they will say it.

Pre-meeting dinner with the design team

Schedule a dinner meeting two to three hours before the hearing. This focuses everyone on the task at hand. Discuss any last-minute strategies or issues that might surface. All handouts and exhibits should be available at the dinner. A relaxed environment for last-minute debate of issues, openly expressed. Once the team agrees on how to handle each specific issue, everyone adheres to the consensus. A united professional team that believes in the project provides positive emotion that translates into momentum.

Knowing your numbers

If the planning board asks for a road widening, a sidewalk extension, an infrastructure contribution, or a development agreement condition, you need to know your costs cold. A project pro forma with well-defined costs, contingencies, soft costs budgeted, and profit margin objectives lets you make an instant decision at the dais. There are no winners in legal confrontation at the planning board table. If the project can support the planning board’s request, a compromise is the best solution — but only if you know what you can afford to give up.

What a winning presentation looks like

The most effective hearing presentations share a few characteristics:

  • They start with the bottom line. What is the project, where, what’s being built, and why is it good for the community.
  • They acknowledge the political context. If the city’s hot button is school capacity, the presentation addresses school capacity in the first three minutes — not buried in slide 18.
  • They use plain language. Engineers and planners who default to technical jargon lose rooms full of laypeople. The best technical professionals translate fluently between code language and neighbor language.
  • They anticipate every question. Answering questions before they’re asked makes a positive impression on every commissioner. The applicant who can stand at the podium and say “I know you’re going to ask about traffic — here’s the ACHD coordination letter, here’s the trip generation analysis, here’s how we addressed the queue length on Ustick” controls the room.
  • They resolve controversy outside the public forum. Try to handle the hard issues with staff and commissioners before the hearing. Minor issues can be resolved during the presentation and entered into the record. Major unresolved issues at the public hearing benefit only the opposition.

Whenever an issue is discussed in the public forum and cannot be satisfactorily resolved by the design team, three things happen: the individuals voicing objections benefit, the planning board members face a political dilemma, and the design professionals end up in a compromising position. Most likely, the approval will be delayed until the issue is resolved. A one-month delay can change the project schedule by more than one month if circumstances — site conditions, weather, financing — affect the start of the project after the issue is finally resolved.

Public testimony — written and oral

Public testimony falls into two categories:

Written testimony

Most Treasure Valley cities accept written testimony submitted to the City Clerk before the hearing. The submission deadline varies — Eagle requires written testimony to be submitted no less than five working days before any public hearing to be included in the packet and made part of the record. Boise’s deadline is typically shorter (~3 days), Meridian varies. Late testimony may not be included in the record in stricter cities.

For applicants, written testimony is an opportunity to put supporters on the record. For opponents, it’s a way to organize neighborhood objection. Both sides use it.

Oral testimony at the hearing

Most cities allow members of the public to testify orally at the hearing, typically with a 3-minute speaking limit. Testimony is taken in favor first, then opposition, then the applicant gets a brief rebuttal opportunity.

The applicant who has done neighborhood outreach knows what the oral testimony will say. The applicant who hasn’t is hearing it for the first time at the worst possible moment.

Common questions

How long does a public hearing actually take? Variable. A simple uncontested item might take 15 minutes. A contested rezone with public testimony from 20 neighbors can stretch to 3 hours or more. Plan the design team’s time accordingly — if your hearing is the third item on the agenda and the agenda is contested, you may not present until 9 PM.

What happens if the hearing gets continued? Continuance happens when the body needs more information, more time to deliberate, or when the applicant needs to revise the application based on questions raised. Most continuances add 2–6 weeks to the project schedule. Plan for the possibility — never assume the first hearing date is the last.

Can I meet with planning commissioners before the hearing? Sometimes — and this varies sharply by city culture. In some cities, pre-hearing meetings with individual commissioners are routine. In others, they’re considered ethically questionable. The safest approach is to use the city’s site plan review committee or development review committee process, which is designed specifically for informal pre-hearing discussion with staff and selected board members.

What happens if the hearing goes badly? First option: ask for continuance to address specific issues. Second option: withdraw the application and refile after addressing the concerns. Third option: appeal a denial to the next level (Council if PZ denied, court if Council denied). All three add time. The fastest recovery is usually withdrawal and refile with a revised application that addresses the concerns directly.

Do I have to attend every hearing personally? For most projects, yes. The applicant — or a senior representative — should be present at every hearing for the project. Sending only consultants signals that the developer isn’t engaged. Sending a senior member of the development team signals commitment and gives the body someone to ask hard questions of in person.

Is there a way to avoid public hearings? For some application types, yes. Administrative approvals (some certain platting, some boundary adjustments, minor site plan modifications) don’t require a public hearing. But the major entitlement application types — annexation, rezone, comp plan amendment, CUP, preliminary plat — almost always require at least one public hearing, and often two.

What’s the most common mistake at a public hearing? Showing up cold. Applicants who arrive without knowing the political context, without having held a neighborhood meeting, without having addressed staff comments thoroughly, and without having role-played the presentation are the ones who get continued, conditioned, or denied. The hearing is the wrong place to be doing the work for the first time.