Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Code Enforcement topic

No spam. Unsubscribe anytime.

Rowlett code enforcement expands hours, pitches technology to cut backlog

Rowlett City Council · October 13, 2025
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

City staff told council the code enforcement division has seven members, has extended hours to 7 a.m.–9 p.m. weekdays and 11 a.m.–9 p.m. Saturdays, and recommends mobile technology and system integrations to reduce paperwork, speed response and allow more proactive inspections.

Andrew Espinosa, assistant director (speaker 16), presented an update on the Code Enforcement Division and several recommended operational changes to the council.

Espinosa said the division includes seven team members: one code manager, four residential code officers, one single‑family rental registration officer and one commercial code officer. Staff reported they flexed schedules to expand coverage without new hires: weekday hours now run 7 a.m. to 9 p.m., and Saturday coverage runs 11 a.m. to 9 p.m. Two vehicles are equipped with mobile printers so officers can generate notices in the field.

Staff described performance goals and timelines for typical cases: an initial response goal of three days for high‑priority complaints, a seven‑day compliance window after notice, and procedures for abatement if property owners do not comply (abatement can extend resolution timelines to roughly 17 days). Espinosa said total reported violations rose from about 3,000 in 2021 to nearly 9,000 in 2025 (with two new service categories added) and noted rental inspections have increased substantially year‑over‑year.

Council discussion focused on making enforcement easier for residents (clearer guidance on who to call, streamlining web portals) and increasing proactive activity instead of only reacting to complaints. Christophe and other staff said the city currently uses several disparate work‑order systems that do not communicate; staff recommended either an enterprise replacement or better integration via APIs and suggested the city pursue a technology solution that would centralize complaints, route them and provide feedback to residents.

Action and next steps: Council asked staff to continue pursuing mobile technology, consider a vendor or integrated solution to replace or tie together existing systems, and to return with recommendations and cost estimates (potentially as a midyear budget request) to improve efficiency and reduce desk time for officers.

What this means: If adopted, new software and process changes are intended to keep officers in the field longer, reduce paperwork, and make it easier for residents to submit and track complaints.