Public Assistance Knowledge Portal Modernization Plan
Guide the transition of public assistance help articles into an accessible, Plain Language standard knowledge repository.
Use this template when planning the overhaul of complex civic support documentation for public aid applicants. It structures accessibility audits, content hierarchy redesign, and agency review workflows.
Role: Principal Civic Technology Knowledge Architect specializing in public sector accessibility and service design.
Context
- Agency: {{agency_name}}
- Program Portfolio: {{public_program_scope}}
- Literacy Standard: {{target_readability_grade}}
- Language Needs: {{supported_languages}}
- Existing Infrastructure: {{current_kb_platform}}
- Legal & Regulatory Baseline: {{compliance_mandate}}
Task
Generate a phased modernization and restructuring plan for the public assistance knowledge base to reduce applicant confusion, support case workers, and meet statutory accessibility standards.
Method
- Analyze legacy article inventory across {{public_program_scope}} to identify high-traffic failure points and outdated policy language.
- Formulate a citizen-centric taxonomy grouping articles by real-world life events rather than agency departmental silos.
- Design a Plain Language rewrite protocol ensuring all public-facing guides conform strictly to {{target_readability_grade}}.
- Establish a translation and localization workflow for {{supported_languages}}, balancing automated drafting with human-in-the-loop validation.
- Audit technical architecture in {{current_kb_platform}} against {{compliance_mandate}}, identifying screen reader and mobile accessibility remediation requirements.
- Structure a role-based content governance schedule assigning specific review intervals to policy leads and legal reviewers.
- Define quantitative operational KPIs measuring deflection, resolution rates, and user satisfaction score improvements.
Constraints
- MUST adhere to {{compliance_mandate}} and enforce {{target_readability_grade}} readability thresholds throughout.
- MUST NOT require proprietary third-party software beyond {{current_kb_platform}} features unless strictly necessary.
- Phasing must account for continuous public availability without system downtime.
- Recommendations must distinctly separate citizen-facing self-service content from internal case-worker playbooks.
Output format
Provide the plan across four structured sections:
- Executive Summary & Accessibility Objectives (max 200 words)
- Taxonomy & Information Architecture Blueprint (hierarchical category table)
- 4-Phase Implementation Roadmap (Phase, Workstream, Key Deliverables, Timeline)
- Quality Assurance & Ongoing Governance Protocol (bulleted policy checklist)
Self-review
- Confirm all 6 method steps are addressed across the implementation phases.
- Verify that both public-facing and internal case-worker pathways are clearly delineated.
- Ensure all variables are appropriately contextualized without placeholders.
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.