UI Module Map
On this page
This page maps the CRAIG user interfaces to user roles and Comprehensive Child Welfare Information System (CCWIS) functional modules.
User Roles
The staff roles below are the nine realm roles the built system enforces (six operational roles plus the ADR-054 office-authority axis).
| Role | Description |
|---|---|
Caseworker |
Front-line staff responsible for investigations, case management, and direct client service |
Supervisor |
Reviews and approves caseworker actions; monitors caseloads and timeliness |
Administrator |
Manages users, jurisdiction configuration, reporting submissions, and compliance workflows |
Eligibility Worker |
Determines Title IV-E eligibility; the financial navigation (payments, subsidies) admits this role alongside supervisors and administrators |
ICPC Coordinator |
Manages Interstate Compact on the Placement of Children (ICPC) requests; the data-exchange navigation admits this role alongside supervisors and administrators |
Read-only |
Audit-oriented read access; sees subsidy agreements realm-flat without any write surface |
County Director / Regional Director / State Office |
The office-authority axis (ADR-054): these roles supply the verified-office proofs behind subsidy approvals, sweep execution, and import history rather than gating separate screens |
Three further personas belong to the Phase 11 self-service portals (epic &50), which are designed but not yet built:
| Persona | Description |
|---|---|
Family / Client |
Constituents with an active case; will access their own information and tasks via the family portal |
Foster Parent / Kinship Caregiver |
Caregivers with children in placement; will access placement information and payments via the foster parent portal |
Provider / CWCA |
Contracted child welfare contributing agencies (CWCAs); will submit service records and access assigned cases via the provider portal |
Module Summary
| Module | Primary Users | Key Functions |
|---|---|---|
Caseworker, Supervisor |
Hotline intake, investigation tracking, safety assessment |
|
Caseworker, Supervisor |
Case lifecycle, case plans, contacts, court orders, Indian Child Welfare Act (ICWA) tracking |
|
Caseworker, Supervisor |
Placement matching, foster home licensing, placement history |
|
Caseworker, Supervisor, Administrator |
Rules-driven IV-E determination, eligibility history, documentation (an API surface today; the determination wizard UI is a design target) |
|
Eligibility Worker, Supervisor, Administrator (subsidy agreements readable by every worker tier, including Caseworker and Read-only) |
Maintenance payments, IV-E claiming, federal financial participation (FFP) tracking, and the subsidy operator surface (agreements, reviews, sweep queue) |
|
Supervisor, Administrator |
Data quality monitoring; Adoption and Foster Care Analysis and Reporting System (AFCARS) and National Child Abuse and Neglect Data System (NCANDS) submissions |
|
Rules Management |
Administrator |
Rule-set CRUD in the JSON Decision Model (JDM) format, import/export, evaluation audit trail. Admin-only nav item surfaces the craig-rules admin UI. |
Data Exchange & ICPC |
Administrator, ICPC Coordinator, Supervisor |
Exchange partner registry, data-sharing agreements, transaction log, ICPC interstate compact requests with home studies and attachments. |
Security & Compliance |
Administrator, Supervisor |
Audit log browser, biennial security reviews, NIST SP 800-53 control tracking, archive management, detection rule configuration and security alerts. Partner API-key and signer-key management stays administrator-only. |
Public Intake Review |
Caseworker (intake queue), Administrator, Supervisor |
Reviewing and screening public-reporter submissions, converting screened-in reports to referrals. (Partner API-key and signer-key management lives in Security & Compliance, administrator-only.) |
Personalize |
All staff roles |
Per-user dashboard layout personalization (own-user scoped; every authenticated worker) |
Jurisdiction Studio |
Administrator |
Composition shell-layout override and read-only panel view for the composed surfaces (ADR-035) |
Unauthenticated public reporters |
6-step wizard for submitting suspected abuse/neglect reports, status lookup by confirmation code, partner JWK registration for integrity-signed submissions. |
|
Family Portal (Phase 11, not yet built) |
Family / Client |
Case status, upcoming events, tasks, document upload |
Foster Parent Portal (Phase 11, not yet built) |
Foster Parent / Kinship Caregiver |
Child information, visits, payments, training requirements |
Provider Portal (Phase 11, not yet built) |
Provider / CWCA |
Assigned cases, service record submission, data exchange |
Navigation Model
All caseworker UI screens share a common top navigation bar.
As built, the active module is marked with the highlighted-link style plus aria-current="page", and the top-right shows the signed-in user’s name, avatar initials, and a sign-out link.
The mockup below shows the designed navigation model, whose remaining elements are not yet built:
-
⚠ N: a count of overdue tasks or critical data quality errors requiring action
-
User name ▾: a dropdown with profile, jurisdiction settings, and sign out
-
Each top-level item expands to the primary screens for that module (the built bar is a flat row of one link per module)
The self-service portals (Family, Foster Parent, Provider) use a simplified header appropriate to each audience and do not share the caseworker navigation bar.
Design Engagement
An external design-partner engagement is underway to evolve CRAIG’s visual system and design the unbuilt self-service portals; CRAIG was previously engineered without an in-house design team.
The durable design substance lives in Antora:
-
UI Philosophy: the ordered design principles that supersede one-off engineering preferences; read this first before new UI work.
-
Current State: what CRAIG looks like today, with screenshot references and the pain-point inventory.
Engagement-specific material — RFPs, decision logs, and handoff bundles — lives outside Antora under docs/handoffs/, since it is scoped to the engagement rather than being durable project reference.
Locked engagement decisions
Five decisions were settled with the design partner at kickoff and now frame all design-adjacent work:
-
Start with the caseworker dashboard: the most-visited surface for the most-numerous role, and the anchor for the composability (panel-grid + persistence) model other surfaces inherit.
-
Design CRAIG’s own identity, not Georgia-state branding: the brand is a per-jurisdiction overlay; the system should read as "CRAIG (currently in Georgia colors)," not "Georgia DHS product."
-
A shared design language, with audience-appropriate presentation per portal: the same tokens, primitives, accessibility patterns, and motion semantics across surfaces, with density and aesthetic register tuned to each audience (caseworker dense; portals spacious; constituent calm).
-
Explore 2–3 visual-style variations first, then density, then interaction: visual style is most foundational and sets the tone; layout/density is most adjustable within a chosen direction; the interaction model belongs to design-system foundation work and is explored last.
-
Produce design sketches in parallel: the design partner sketches the system foundation from the philosophy doc while engineering delivers files, so the two streams converge rather than block each other.
|
These five are locked with the design partner. Do not unilaterally change the starting screen, brand direction, portal coupling, variation strategy, or sequencing — re-open the conversation with the design team first. |