10 to the 23 AI logo

Domain Atlas

Caseworker documentation & copilots

Generative and rules-based assistants that transcribe, summarize, triage, and increasingly draft the records and decisions institutions run on — meeting scribes, mail-triage filters, evidence summarizers, ruling drafters, and automation that removes the caseworker from the routine path entirely. The human review step is the load-bearing control, and the throughput that justifies the tool is the same pressure that erodes it — with a verifier that checks human work at one edge of the range and deployments halted after the harm was measured at the other.

Use cases

What AI is doing here

Generative case documentation

Generative

Transcription and drafting of assessments and case notes, reviewed by workers before entering the record.

General staff copilots

Generative

Office assistants (drafting, summarizing, search) used informally across casework and administration.

Evidence summarization for decision-makers

Generative

Generative compression of case evidence — interview transcripts, policy or country-guidance notes, medical and administrative records — into the summary a caseworker reads before deciding, standing in for the underlying reading it replaces.

Correspondence & document triage

Predictive

Language-model classification of inbound letters, forms, and evidence to flag vulnerability or route work, reordering the queue ahead of a human without itself touching the entitlement decision.

Generative decision drafting

Generative

AI drafting of the decision itself — proposed orders, determinations, or notification letters — for a human to review and adopt, where the machine draft becomes the record once accepted.

Rules-based decision automation & verification

Predictive

Rules and NLP systems operating directly on the eligibility or benefit decision — automating recurring determinations end-to-end with a human exception path, or flagging a human-drafted decision against enumerated quality rules before it issues.

Case files

What has gone wrong, and right

Documented deployments, presented as model organizations calibrated to the evidence, with full citations.

System map

Who is in the system, and what pushes on it

Who is in the system

  • Frontline workers. Caseworkers, screeners, eligibility staff — the operator network whose judgment the system augments or erodes.
  • Supervisors & QA. The institutional correction layer: overrides, second reads, quality review.
  • Agency leadership. Owns procurement, policy, and the authority map; answers for the system publicly.
  • Served people & families. Those the decisions land on. Deliberately outside the PAN dynamics — their outcomes are measured, never simulated.
  • Vendors. Build and update the systems; hold the information asymmetry procurement must govern.
  • Regulators & oversight bodies. Boards, auditors, data-protection officers, inspectorates — external correction capacity.
  • Advocates & community organizations. Surface harms institutions do not see; historically the earliest accurate signal.

Dominant pressures

  • Caseload surge. Demand outruns staffing; per-case attention shrinks and review becomes triage.
  • Reviewer bottleneck. One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
  • Vendor opacity. The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
  • Deadline pressure. Statutory or managerial timeliness rules reward fast approval of machine output over slow disagreement.
  • Staff turnover. Experienced skepticism leaves; new staff calibrate their trust on the tool itself.
  • Compliance over substance. Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.

Governance

Questions leaders should be asking

  1. 1. What fraction of AI-drafted or AI-triaged records is substantively changed before a human accepts it — and does anyone measure that edit rate, or is 'a human reviews everything' asserted without evidence it survives the workload?
  2. 2. How much of the work now reaches a record or a decision without a human reading it at all — and who set the rule that decides which cases take the no-human path?
  3. 3. When the affected person is never told a system touched their case, the operator's own vigilance is the only thing between an error and its consequence — is anyone auditing what that vigilance misses, and would a live bias or error surface before an outside body forced it to?
  4. 4. Are AI-written entries labeled where they land, so a later reader, an auditor, or a downstream risk tool knows the record was machine-drafted and not independently established — and if one shared tool writes everyone's records, who notices when a single error mode is repeating across all of them?

For the actions behind these questions, see the Practice Library.

Seeing your organization in this domain? Mapping its actual pathways, pressures, and correction capacity is engagement work.

Work With 1023AI