Nonprofit & Social Impact

Caseworker Program Copilot

Designed for Caseworker

Help the caseworker move a participant through a multi-program service plan by grounding eligibility, benefit interactions and referral options in current program rules and the participant's own consented record, so scarce caseworker time goes to the relationship rather than to rule lookup.

Contract NON-01 · primary aggregate ParticipantServiceCase · mode loading

Decision brief

Strengths and needs intake with consent: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Caseworker with participant

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

3 approval gates

Approval gates prevent the copilot from making consequential decisions.

Business problem

A caseworker supports a single parent enrolled in a workforce program who is offered a wage increase through a placement.

Decision to make

Help the caseworker move a participant through a multi-program service plan by grounding eligibility, benefit interactions and referral options in current program rules and the participant's own consented record, so scarce caseworker time goes to the relationship rather than to rule lookup.

Outcome to show

ReferralRecord gives Caseworker the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Strengths and needs intake with consent
  2. 2Program rule and eligibility grounding
  3. 3Benefit interaction analysis
  4. 4Service plan co-creation
  5. 5Referral with consent and capacity check

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Caseworker with participant verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved ParticipantServiceCase evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Help the caseworker move a participant through a multi-program service plan by grounding eligibility, benefit interactions and referral options in current program rules and the participant's own consented record, so scarce caseworker time goes to the relationship rather than to rule lookup.
Primary aggregate
ParticipantServiceCase
Primary container
participantServiceCases
Hierarchical key
/tenantId + /caseId
Schema version
1

Sample scenario

A caseworker supports a single parent enrolled in a workforce program who is offered a wage increase through a placement. The copilot cites the funder rule and the state income threshold showing the increase would reduce childcare subsidy by an amount exceeding the wage gain in the first six months, then identifies a transitional childcare provision that preserves the subsidy for 90 days if applied for before the wage change takes effect. It raises a benefit interaction finding, the caseworker discusses the timing with the participant, they agree on a goal sequencing the application ahead of the placement, and a referral is made with consent basis and current provider capacity recorded.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
participantServiceCases Primary /tenantId + /caseId ParticipantCase, ServicePlanGoal, ReferralRecord, EncounterNote, BenefitInteractionFinding
programRuleLibrary Reference /tenantId + /programCode ProgramRuleChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
ParticipantCase participantServiceCases /tenantId + /caseId case::{caseId} None
ProgramRuleChunk programRuleLibrary /tenantId + /programCode program::{programCode}::rule::{ruleDocId}::{chunkOrdinal} chunkVector
ServicePlanGoal participantServiceCases /tenantId + /caseId case::{caseId}::goal::{goalId} None
ReferralRecord participantServiceCases /tenantId + /caseId case::{caseId}::referral::{referralId} None
EncounterNote participantServiceCases /tenantId + /caseId case::{caseId}::encounter::{encounterAtUtc}::{encounterId} None
BenefitInteractionFinding participantServiceCases /tenantId + /caseId case::{caseId}::interaction::{findingId} None

Query patterns