Civic Public Records Automation Evaluation Checklist
Validate public records request triage and redaction agents for statutory compliance and privacy protection.
Use this checklist when evaluating public records (FOIA/sunshine laws) processing agents for local or regional government. It enables civic transparency officers to audit automated redaction accuracy, exemption citations, and timeline adherence prior to releasing records.
Role: Chief Civic Privacy and Transparency Officer specializing in automated records governance and municipal administrative compliance.
Context
- Municipal Entity: {{municipality_name}}
- Public Records Legislation: {{public_records_statute}}
- Protected Information Classes: {{exempt_information_classes}}
- Automated Processing Pipeline: {{agent_redaction_pipeline}}
- Acceptable Error Tolerance: {{acceptable_error_tolerance}}
- Administrative Appeals Mechanism: {{appeals_review_process}}
Task
Construct a comprehensive evaluation checklist to audit the accuracy, legal defensibility, and privacy safeguards of the automated public records triage and redaction agent before certifying it for production use in {{municipality_name}}.
Method
- Map the statutory exemption clauses in {{public_records_statute}} directly to the agent's identification patterns and classification taxonomies.
- Formulate verification criteria for automated recognition and redacting of {{exempt_information_classes}} across heterogeneous formats (PDFs, scans, body-worn camera audio, emails).
- Structure precision-recall test requirements across {{agent_redaction_pipeline}} to ensure performance complies with {{acceptable_error_tolerance}}.
- Define inspection items for mandatory legal explanation generation, verifying that statutory citations accompanying redactions are accurate and legally sound.
- Establish verification checks for request routing, timeline monitoring, and automated deadline calculation under {{public_records_statute}}.
- Detail procedural audit checks verifying integration with {{appeals_review_process}} when requesters challenge withholdings or redactions.
- Develop security and audit trail verification criteria to prevent irreversible destruction of original civic records during automated processing.
Constraints
- Every checklist item MUST state the validation procedure, mandatory evidence, and legal liability risk level (Severe, Moderate, Low).
- MUST NOT permit automated disclosure of unredacted records within {{exempt_information_classes}} under any circumstance.
- Checklist items must be actionable by both municipal IT administrators and city attorneys.
- Prohibit open-ended assertions; all checks must yield a binary Pass or Fail outcome.
Output format
- Audit Governance Header (Scope, Statutory Authority, Evaluation Version in 3 lines)
- Checklist 1: Exemption Identification & Privacy Protection (5 numbered items)
- Checklist 2: OCR, Multi-Modal & Text Parsing Integrity (4 numbered items)
- Checklist 3: Legal Citation & Administrative Notice Defensibility (4 numbered items)
- Checklist 4: Workflow Timelines & Appeals Integration (4 numbered items)
- Production Certification Gate (A markdown summary table with 5 mandatory release criteria)
Self-review
- Ensure every item in {{exempt_information_classes}} has explicit redaction verification tests.
- Confirm {{acceptable_error_tolerance}} is utilized as a quantitative threshold in the accuracy checks.
- Verify all references to {{public_records_statute}} and {{appeals_review_process}} match standard municipal legal workflows.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.