Civic Plain-Language Content Accessibility Report
Evaluate public agency collateral and produce a plain-language compliance and distribution report for civic programs.
Use this template when preparing public policy announcements, social benefit rollouts, or public health notices. It evaluates accessibility barriers and establishes an equitable communications plan.
Role: Senior Civic Content Strategist and Digital Inclusion Specialist with expertise in public sector plain-language mandates.
Context
- Public Agency: {{agency_name}}
- Priority Community: {{target_community}}
- Public Initiative: {{civic_program_topic}}
- Baseline Outreach Collateral: {{current_outreach_materials}}
- Target Readability Benchmark: {{reading_grade_level_target}}
- Language Access Requirements: {{multilingual_requirements}}
Task
Author a comprehensive plain-language accessibility report for {{agency_name}} that diagnoses reading barriers in {{current_outreach_materials}} and delivers an equitable public communication strategy for {{civic_program_topic}}.
Method
- Analyze the sample text in {{current_outreach_materials}} for bureaucratic jargon, passive voice, and procedural ambiguity.
- Evaluate readability against {{reading_grade_level_target}} using recognized civic plain-language scoring criteria.
- Identify cultural and systemic communication barriers experienced by {{target_community}}.
- Design simplified information architectures that highlight eligibility criteria, deadlines, and direct action steps.
- Align content adaptation protocols with {{multilingual_requirements}} to ensure semantic accuracy across translations.
- Formulate plain-language rewrite examples demonstrating the transformation of complex public policy text.
- Establish verification protocols for community-level feedback and accessibility compliance.
Constraints
- MUST ensure all recommendations strictly meet {{reading_grade_level_target}} standards.
- MUST NOT alter or omit statutory legal disclaimers while simplifying procedural text.
- Content structures MUST prioritize mobile-first readability for low-bandwidth users in {{target_community}}.
- Recommendations MUST directly address all items listed under {{multilingual_requirements}}.
Output format
Provide a structured evaluation report in markdown with these exact headings:
Civic Plain-Language Strategy Report: {{civic_program_topic}}
1. Program Accessibility Overview (Agency: {{agency_name}})
2. Readability Diagnostics & Barrier Analysis (3 core findings)
3. Plain-Language Rewrite Models (Before vs. After side-by-side comparison)
4. Multilingual & Inclusion Distribution Strategy (addressing {{target_community}})
5. Compliance & Review Checklist
Self-review
- Verify that the 'Before vs. After' models demonstrably achieve {{reading_grade_level_target}}.
- Ensure legal integrity is preserved while eliminating municipal jargon.
- Confirm clear, actionable guidance is provided for each language specified in {{multilingual_requirements}}.
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.