Live demo screen
Case Pipeline
A drag-and-drop Kanban of the consumer case pipeline, one lane per stage, running the real status state machine.
Who sees what: Manager tier. A move is authorized twice — the REST route requires manager tier, and the state machine re-checks the per-consumer edit capability.
CASE PIPELINE
Drag a case forward to advance it. 6 cases in view.
Referral Received
1Assigned
0Welcome Call Completed
1Introduction Completed
0Orientation Scheduled
0Orientation Completed
0ROI Uploaded
1Consumer Commitment Uploaded
0Pathway Plan Complete
0Job Dev Plan Complete
0Ongoing Services
1Retention Tracking
0Ready for Billing
1Compliance Approved
0Submitted to Funder
1Paid
0Case Closed
0This is the real screen, rendered live against fictional demo data — not a screenshot.Sign in to interact
What you’re looking at
The caseload as a drag-and-drop board, one lane per stage. The important part is what sits underneath: dragging a card runs the same state machine the admin screens and the API use, so the board cannot be used as a back door around the rules.
On this screen you can
- See every consumer as a card in their current stage
- Drag a card to advance a case to the next stage
- Watch an out-of-order or backward move get rejected — the card snaps back carrying the state machine’s own reason
Enforced server-side
- Every move is authorized twice — the endpoint requires manager tier, and the state machine independently re-checks the mover’s permission on that specific consumer
- A supervisor sees their team’s consumers; an org admin or owner sees the organization’s
- So the endpoint cannot be used to move a case outside the caller’s own reach
In this demo you’re watching the screen as Marcus Ellison — Program Supervisor, against a fictional organization of 6 staff and 15 consumers. Signing in with a different role changes what renders — that scoping is the product, not a demo trick.