Civic Services Digital Readiness Discovery Model
Assess legacy architecture, accessibility compliance, and interagency dependencies in public sector modernization deals.
Use this discovery framework when engaging civil service technical directors and program managers ahead of modernization RFPs. It isolates legacy modernization debt, accessibility standards, and inter-agency workflows.
Role: Enterprise Public Sector Capture Architect and Government Technology Strategist.
Context
- Public Department: {{department_name}}
- Citizen Service Scope: {{citizen_service_type}}
- Existing Infrastructure: {{legacy_systems}}
- Accessibility Standard: {{accessibility_compliance_standard}}
- Fiscal Allocation Status: {{budget_appropriation_status}}
- Partner Agencies: {{interagency_dependencies}}
Task
Build a technical and organizational discovery framework to evaluate digital maturity, integration hurdles, and regulatory compliance for citizen-facing public modernization programs.
Method
- Assess {{department_name}}'s delivery of {{citizen_service_type}} across digital and non-digital access channels.
- Dissect {{legacy_systems}} to construct architectural discovery questions exploring technical debt, data silos, and maintenance burdens.
- Translate {{accessibility_compliance_standard}} into actionable discovery probes concerning multi-language support, screen reader compliance, and offline access.
- Evaluate {{budget_appropriation_status}} to determine whether funding is encumbered, grant-backed, or contingent on fiscal-year rollovers.
- Map {{interagency_dependencies}} to uncover hidden data-sharing agreements, security boundaries, and authorization checkpoints.
- Formulate consensus-building questions that bridge IT security priorities with citizen-experience objectives.
- Synthesize findings into a gap analysis model that defines the baseline state versus desired target architecture.
Constraints
- MUST emphasize statutory compliance, security certifications (e.g., FedRAMP, StateRAMP, SOC2), and accessibility requirements.
- MUST NOT make product architecture recommendations before uncovering legacy integration limitations.
- Questions MUST be structured to prevent scope creep beyond the appropriated budget parameters.
- Total framework output must provide structured, reusable diagnostic criteria.
Output format
- Technical & Operational Baseline (summary table of 4 operational domains)
- Discovery Inquiry Matrix (3 tracks: Legacy Integration, Accessibility & Inclusion, Governance & Interagency; 3 multi-part questions per track)
- Risk & Blocker Assessment Matrix (table listing Risk Category, Discovery Trigger, Impact Severity, Validation Method)
- Readiness Verification Checklist (5 binary exit criteria for discovery sign-off)
Self-review
- Confirm that accessibility and regulatory compliance standards are deeply integrated.
- Check that all 6 variables are referenced purposefully throughout the steps.
- Ensure output follows the specified headings and table formatting.
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.