Meridian staff recommends data‑first approach to construction dust and noise; council favors adding mitigation language to development findings

City staff recommended a measured, data‑driven approach to address recent construction dust and noise complaints and proposed clarifications to design review and building‑height rules.

Public works staff presented four options after meeting with internal departments, the Building Contractors Association (BCA), and the Idaho Department of Environmental Quality (DEQ). Staff’s recommended Option 1 would: create a single online reporting page for construction complaints, distribute a best management practices packet at preconstruction meetings, require submission (but not immediate enforcement) of SWIPs for most projects, and improve interagency enforcement coordination. Staff emphasized that Meridian currently handles about 10–15 dust complaints per year citywide and that roughly 250 active construction projects each year mean many workdays without complaints; staff argued better data will reveal whether problems are widespread or project specific.

Council members supported Option 1 but several asked that the city make dust‑mitigation plans part of development findings where projects are approved (to create an expectation for developers) even if the city does not immediately add enforcement tools or criminal penalties. Council member Schaer suggested linking a required dust control mitigation plan or adopting BCA standard BMPs into findings; other council members argued development findings can carry weight in the permitting process even if code enforcement typically uses compliance‑and‑cure procedures rather than stop‑work orders.

Staff described potential next steps if data showed persistent problems: amend nuisance or noise ordinances to address construction hours or explicitly add dust to the nuisance code; or require SWIP submission to the city and build inspection/enforcement capacity. Staff warned that criminal enforcement requires physical on‑site observation and can result in misdemeanor charges against individuals using equipment — an outcome council members said they did not want as the initial approach.

On design review and building height, planning staff reviewed the history of the city’s standards (design manual, architectural standards) and noted the Unified Development Code defers many height definitions to building code. Staff proposed three possible changes: define building height precisely (measure to roof peak), limit or clarify appurtenance exceptions (parapets, stair towers, elevator shafts, rooftop amenities) and require disclosure of any requested height exceptions at the public hearing level. Several council members said they favored clarifying height language and making any exceptions visible during public hearings, and some asked staff to focus first on residential districts before expanding changes to nonresidential zones.

Council directed staff to proceed with Option 1 for construction practices (create reporting website, distribute BMPs, track complaints) and to return with proposed UDC language that clarifies building‑height definitions, tightens appurtenance language, and ensures height exceptions are disclosed at hearing level. Several council members requested that the staff draft results be incorporated into development findings where practical and that staff report back after one year with complaint data.