Skip to content
Grand Jury Hub
← Report overview
Response synthesis and audit

Code Compliance: Board Response

The Board agrees with routing, manual, and coordination findings, partly disputes complaint-update concerns, and promises three dated actions. Its shared-page plan uses department-specific numbers rather than the recommended single complaint phone number.

Response by El Dorado County Board of Supervisors

5

Addressed

2

Partially addressed

0

Not addressed

0

Unclear

County's stated disposition

These categories reflect the County's response to each recommendation, separate from this audit's assessment.

0

Implemented

3

Will be implemented

0

Requires further analysis

0

Will not be implemented

0

Unclear

How to read this audit

Editorial review measures engagement and finding-response document completeness, not legal compliance, truth, or verified implementation. Citations use physical PDF pages. The Board attachments retain “Initial Draft Response” introductory wording; the supplied collection notes record Board approval, not independent court receipt. The signed August 18, 2026 transmittal confirms approval and states email submission for cases 26-05 and 26-06; it does not independently establish court receipt.

Commitments

Actions stated in the response

These are commitments extracted from the County's response. They describe what the response says will happen; they do not verify that implementation occurred.

3

Extracted commitments

3

Definite or bounded timing

0

Conditional timing

0

No timeframe

Item-by-item review

Findings and recommendations

Assessments describe whether the response engages each cited item. Finding scores separately describe statutory-elements completeness under California Penal Code § 933.05(a) and public usefulness. They do not independently verify the response or constitute a legal conclusion.

Showing 7 of 7 items

finding · F1

Communicating complaint resolutions

Audit: Partially addressed

Response says

The Board partly disagrees, citing Ordinance 9.02.070 confidentiality limits and support for clearer expectations and follow-up options.

Audit analysis

An ordinance provides a specific reason for limiting disclosures, but the partial position does not clearly identify which part of the reported lack of routine resolution updates is accepted or denied. Explaining confidentiality is not evidence of current update frequency.

Finding-response score

Document completeness and usefulness—not factual verification or a legal conclusion.

8/10

3/4

Statutory elements

Stated position
2/2
Applicable disagreement elements
1/2

5/6

Public usefulness

Coverage
1/2
Reason specificity
2/2
Support traceability
2/2

An ordinance provides a specific reason for limiting disclosures, but the partial position does not clearly identify which part of the reported lack of routine resolution updates is accepted or denied. Explaining confidentiality is not evidence of current update frequency.

Scoring confidence: high

finding · F2

Central complaint webpage and phone routing

Audit: Addressed

Response says

The Board agrees, describing separate departmental portals and a possible shared landing page; it says a single phone number is infeasible.

Audit analysis

Agreement addresses the absence of central routing. Concrete portal and department distinctions explain the proposed alternative, but feasibility assertions lack an identified supporting record.

Finding-response score

Document completeness and usefulness—not factual verification or a legal conclusion.

9/10

4/4

Statutory elements

Stated position
2/2
Applicable disagreement elements
2/2

5/6

Public usefulness

Coverage
2/2
Reason specificity
2/2
Support traceability
1/2

Agreement addresses the absence of central routing. Concrete portal and department distinctions explain the proposed alternative, but feasibility assertions lack an identified supporting record.

Scoring confidence: high

finding · F3

Code Enforcement procedure manual

Audit: Addressed

Response says

The Board agrees that no manual exists and says a Policies and Procedures Manual is being developed.

Audit analysis

Agreement and a specific development action directly address the finding. No draft, project record, or dated milestone is cited in this finding response.

Finding-response score

Document completeness and usefulness—not factual verification or a legal conclusion.

8/10

4/4

Statutory elements

Stated position
2/2
Applicable disagreement elements
2/2

4/6

Public usefulness

Coverage
2/2
Reason specificity
1/2
Support traceability
1/2

Agreement and a specific development action directly address the finding. No draft, project record, or dated milestone is cited in this finding response.

Scoring confidence: high

finding · F4

Planning/Assessor information coordination

Audit: Addressed

Response says

The Board agrees and identifies the Assessor’s Megabyte system and Planning and Building’s TRAKiT system as opportunities for improved data flow and communication.

Audit analysis

Agreement covers the underused relationship and concrete system differences explain coordination opportunities. Named systems identify a checkable basis; integration benefits remain proposed, not verified.

Finding-response score

Document completeness and usefulness—not factual verification or a legal conclusion.

10/10

4/4

Statutory elements

Stated position
2/2
Applicable disagreement elements
2/2

6/6

Public usefulness

Coverage
2/2
Reason specificity
2/2
Support traceability
2/2

Agreement covers the underused relationship and concrete system differences explain coordination opportunities. Named systems identify a checkable basis; integration benefits remain proposed, not verified.

Scoring confidence: high

recommendation · R1

Central complaint directions

County: Will be implementedAudit: Partially addressed

Response says

The CIO and complaint-handling departments will create a shared landing page by December 31, 2026, with category-specific phone numbers rather than one countywide number.

Audit analysis

The response gives a deadline and owner for the webpage but declines the recommendation’s single-number component while using an overall future-implementation disposition. Both the promise and exception are retained.

Extracted commitments

Create a shared complaint landing page with categories and department-specific phone numbers.

Responsible party
Chief Information Officer and complaint-handling departments
Deliverable
County complaint-routing webpage
Timing
2026-12-31 · Exact date

recommendation · R2

Code Enforcement procedure manual

County: Will be implementedAudit: Addressed

Response says

The Code Enforcement Division will complete its Policies and Procedures Manual by February 1, 2027.

Audit analysis

The response identifies a specific deliverable, responsible division, and date. Development underway is not represented as verified completion.

Extracted commitments

Complete a comprehensive Code Enforcement Policies and Procedures Manual.

Responsible party
Code Enforcement Division
Deliverable
Policies and Procedures Manual
Timing
2027-02-01 · Exact date

recommendation · R3

Property-information working group

County: Will be implementedAudit: Addressed

Response says

Planning and Building and the Assessor’s Office will establish a working group by December 31, 2026, to improve information accuracy, communication, and potential system data flow.

Audit analysis

The disposition begins on page 3; page 4 supplies members, purpose, and deadline. Creation of the group is promised, not verified integration of the two systems.

Extracted commitments

Establish a Planning and Building/Assessor working group on property information.

Responsible party
Planning and Building Department and Assessor’s Office
Deliverable
Interdepartmental working group
Timing
2026-12-31 · Exact date