Council approves broader "responsible person" definition for code enforcement; critics warn of burden on managers

The Yucaipa City Council on Sept. 8 approved an amendment to the city's code (Ordinance No. 463) that expands the legal definition of the “responsible person” for property code violations, allowing code enforcement to cite bystanders beyond property owners, including renters, contractors, caregivers and property management firms.

Council discussion and staff presentations focused on real-world enforcement limits under the current code and on examples where enforcement could not reach the party actually causing a nuisance. Trevor Benson, the city’s Public Safety Manager, told the council: "In our current law, our current law restricts our code enforcement and citing officials ability to actually enforce the law against the correct person." Staff and the city attorney said the change aims to close those gaps to allow more targeted enforcement actions.

The council heard public comment from residents and property managers. Robert Coleman, a Yucaipa resident, argued the proposed code change would shift the burden of proof onto managers, saying the change would make "the person that you're labeling as a responsible party...gonna be guilty until they're proven innocent." He urged council to hold property owners primarily accountable.

Supporters and staff pointed to specific enforcement problems the amendment is intended to solve, including cases where properties are held through undercapitalized single-purpose LLCs with managers that effectively control operations. City staff described the typical enforcement process: investigation, warnings, fines and, if unpaid, debt collection contracted through a vendor (DataTicket) that can collect against tax returns or place liens on property.

Councilmembers debated safeguards and implementation. Several said staff must do due diligence and that owners will generally be approached first; others flagged mobile home parks and long-running problem properties as reasons to retain the broader authority. The council voted to adopt the ordinance; the formal vote was announced as carrying with two “no” votes reported by mayoral staff at the meeting, though individual “no” votes were not named on the audio record.

The ordinance adds a range of potential responsible parties to the municipal enforcement toolbox, but staff said enforcement will continue to require investigation into each case and review by the Public Safety Manager before any citation is issued. Staff and the city attorney also noted additional remedies remain available, including liens and special assessments against property owners.

The council did not change the city's established process of warnings and follow-up inspections prior to fines; staff reiterated that emergency hazards (gas leaks, major water breaks, public-health threats) are handled on a faster time scale and that routine cases often receive repeated follow-ups every 14 days until corrected.

The city will publish implementing guidance and clarified procedures to make plain how code enforcement will determine who is cited, and staff said they will return with any needed administrative protocols.

The ordinance was adopted as part of the consent/second-reading calendar. The council’s action does not alter civil or criminal due-process safeguards; staff said enforcement will continue to require documentation and supervisory review before citations are issued.

The council included no additional amendments to the ordinance at adoption; separate, related code cleanups were handled under a different ordinance later in the meeting.

Votes at a glance: Ordinance No. 463 — approved (voice vote reported as carrying; meeting record indicates two opposed votes were registered on the audio record).