Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Code Enforcement topic
No spam. Unsubscribe anytime.
Murrieta council backs ad hoc code‑enforcement recommendations that prioritize public education
Summary
After a two‑year ad hoc review, the council accepted recommendations to improve public education, clean up municipal-code inconsistencies, clarify downtown storage rules and adopt RV‑screening design standards while keeping a reactive, complaint‑driven enforcement approach.
The City Council on April 21 reviewed the Code Enforcement Ad Hoc Subcommittee’s recommendations and directed staff to begin implementing clearer public education, targeted code cleanups and operational coordination while retaining a primarily complaint‑based enforcement model.
Assistant City Manager Kristen Crane and Code Enforcement Manager Nolan Barentes outlined five core recommendations: enhance public education materials (including 'know‑before‑you‑buy' guidance for RV buyers and checklists for new homeowners), correct minor municipal‑code inconsistencies, clarify storage and screening standards in the downtown specific plan area, document sidewalk‑vending enforcement within state legal limits, and adopt minimum design standards for RV screening to avoid low‑quality materials.
Barentes described the department’s caseload in 2025 — about 1,877 cases opened and a roughly 90% closure rate — and listed the most common complaints: landscaping (weeds, bare dirt), recreational vehicles and inoperative vehicles, and trash/debris. The subcommittee recommended continuing a reactive approach to enforcement rather than hiring staff for citywide proactive patrols; staff estimated adding three proactive positions would cost roughly $400,000 per year.
Council members praised the staff’s analysis and approved the recommendations to prioritize public education, to bring back municipal‑code amendments where needed, and to coordinate sidewalk‑vending responses with police and public‑safety guidance. Staff will return with specific code‑cleanup language and an implementation schedule.
