Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Code Compliance Committee Future topic
No spam. Unsubscribe anytime.
Mariposa County code compliance panel discusses timeline, public outreach and next steps
Summary
The Mariposa County Code Compliance Advisory Committee reviewed its history and the work needed to finish its recommendations, urged better public communication, and approved motions to table prior minutes and to move two agenda items to a future meeting.
Get email alerts on the Code Compliance Committee Future topic
No spam. Unsubscribe anytime.
The Mariposa County Code Compliance Advisory Committee met and discussed the committee—s history, a timeline for completing its work and steps to improve public communication, agreeing to postpone approval of the Feb. 14 minutes and to move two agenda items to a future meeting.
The committee—s clerk reviewed past recommendations and asked members how much additional time they needed to complete the CCAC—s assigned tasks. Daniel Banchu, clerk of the board, told the group he would pass their recommendations to the Board of Supervisors and said the clerk—s current workload (a county services-area history project) meant the CCAC item likely would not reach the board agenda for about two months: "I'm here to listen and here to gather your guys' thoughts," Banchu said.
The discussion focused on finishing a set of code and process changes the committee has developed with county planning staff and the Planning Commission. Planning staff and members said the Planning Commission is reviewing development-code revisions that would move enforcement provisions out of Title 17 into Title I and incorporate abatement procedures aligned with California Government Code 25845. Planning staff said the Planning Commission planned hearings in May and June with an objective of having recommendations go to the board this summer.
Committee members urged clearer public-facing materials and business-process improvements. "I would love to see us as a group get this flowchart going," CCAC member Chris Castro said, describing a plain-English flowchart showing steps, time limits and where people could obtain help. Public commenter Colleen Rhodes said outreach has not happened and urged the committee not to dissolve until communication improves: "I'm very disappointed that there's no been no discussion here today about communication with the public," Rhodes said, adding that residents report one-off contacts with code enforcement and little follow-up.
Steve (planning director) summarized the county—s direction on enforcement and abatement work: "Abatement means getting rid of the problem, not fines, not taking people's property, getting rid of the problem. If there's a pile of trash, get rid of the problem, get rid of the pile of trash, right?" He and other staff recommended that the CCAC compile a checklist of outstanding items, coordinate with the Planning Commission draft changes, and tie any public-facing flows to the final code provisions so they do not prescribe processes that would conflict with adopted code.
The committee assigned near-term homework and scheduling steps: members were asked to submit lists of topics they want addressed to staff before the deadline for the next packet (staff indicated materials should be submitted by April 28 so the packet can be prepared for publication around May 2 for a May 9 meeting). Members and staff agreed to treat the code revisions and the CCAC checklist as parallel tracks that must be reconciled before the committee makes a final recommendation to the board.
Votes and formal actions taken at the meeting included tabling the Feb. 14, 2025 minutes pending a future quorum and moving agenda items E and F to the next meeting for more detailed discussion. The clerk recorded the motions; movers and seconders were named in the meeting but detailed vote tallies were not specified in the record. The committee closed with direction to emphasize public communication and to prepare a checklist of outstanding items for review at the next meeting.
