Citizen Services Navigator
Outcome
Help a resident understand which public benefit or licensing programs they qualify for, what evidence each program requires, and where their submitted application currently stands, using only published program rules and the resident's own case record.
| Portfolio attribute | Value |
|---|---|
| Primary persona | Citizen |
| Primary aggregate | ResidentServiceCase |
| Cosmos DB containers | 2 |
| Grounding data | program rules, forms, services, case status |
| Development estimate | USD 60-220 monthly dev estimate |
| Runtime options | Python FastAPI and C# ASP.NET Core |
Productivity hypothesis
These measures reflect the workflow, evidence, decision boundary, and industry risk for this use case.
| Impact type | Measure | Conservative internal assumption | Customer measurement |
|---|---|---|---|
| Productivity | Intake-to-response time | 8-14% reduction | (baseline median intake-to-response minutes - assisted median minutes) / baseline median minutes * 100 |
| Quality or risk | Case rework | 3-6% reduction | (baseline reopened or corrected case rate - assisted rate) / baseline rate * 100 |
Important: Conservative internal pilot assumptions only; not public benchmarks, commitments, or expected customer results. Validate against a comparable baseline or matched control cohort with mandatory human review.
Rationale: Program rules, documents, case status, and service information can support faster and clearer citizen navigation.
Pilot guardrail: Caseworkers retain eligibility authority; preserve accessibility, language support, and evidence tracking.
Customer validation plan
- Baseline the current workflow with representative users and tasks.
- Run the accelerator on the same task mix with human review retained.
- Measure intake-to-response time and case rework with the documented formulas.
- Replace internal assumptions with customer-observed results before a business case.
Why Azure Cosmos DB
This AI solution needs an operational data plane, not only a vector index:
- Hybrid vector and full-text retrieval combines semantic recall with exact identifiers, codes, names, and domain language.
- Hierarchical partition keys and metadata predicates keep tenant and domain boundaries in the normal query path.
- Operational JSON, source chunks, workflow and agent state, feedback, and audit records remain together for low-latency reads and governed writes.
- Change feed reacts to source and operational updates without polling.
- Autoscale throughput, configurable consistency, and multi-region distribution support variable demand and enterprise availability.
Domain workflow

| Stage | Actor | Input → output | Approval |
|---|---|---|---|
| 1. Plain-language needs intake | Resident with citizen services navigator | residentQuestion → ServiceCase | Policy controlled |
| 2. Program rule retrieval | Retrieval orchestrator | ServiceCase → EligibilityRuleChunk | Policy controlled |
| 3. Advisory eligibility screening | Citizen services navigator | EligibilityRuleChunk → EligibilityAssessment | Policy controlled |
| 4. Evidence collection and verification | Resident and intake clerk | EligibilityAssessment → EvidenceItem | Human required |
| 5. Caseworker determination and notice | Eligibility caseworker | EvidenceItem → determinationNotice | Human required |
Technical architecture

Cosmos DB data model
| Container | Hierarchical partition key | Documents | Search paths |
|---|---|---|---|
residentServiceCases | /tenantId, /caseId | ServiceCase, EvidenceItem, EligibilityAssessment, CaseNote | /rationaleVectorEmbedding, /rationaleVector |
benefitPolicyLibrary | /tenantId, /programCode | EligibilityRuleChunk | /chunkVectorEmbedding, /chunkVector |
Query contract
| Query | Container | Scope | Purpose |
|---|---|---|---|
| ResidentCaseStatus | residentServiceCases | single-partition | Return the resident's current case state and next required action for the status page. |
| OutstandingEvidenceChecklist | residentServiceCases | single-partition | List documents the resident still owes before determination can proceed. |
| EffectiveProgramRuleRetrieval | benefitPolicyLibrary | single-partition | Retrieve only the program rule text in force on the application date, in plain language where available. |
| CaseInteractionHistory | residentServiceCases | single-partition | Reconstruct the full cited interaction history for an appeal or a public records request. |
Python and C# services route each document type to its declared container and hierarchical partition key. ETag-based writes protect mutable aggregates, while append-only records and bounded cross-partition queries preserve scale.
Azure deployment

Clone the source repository, authenticate with Azure, and run:
Set-Location accelerators/government-public-sector/citizen-services-navigator
az login
./Deploy.ps1 -Runtime python -Location eastus2
Change python to csharp to deploy the .NET implementation.
Explore the implementation
- Launch signed-in demo
- Implementation article
- Domain data model
- Workflow and API contract
- Python application
- C# application
- Domain container Bicep
- Platform Bicep
- Cost and configuration
- Source repository