Live demo screen
Case Pipeline
Every consumer case on one board, one lane per stage, running the real status state machine. Lanes wrap instead of scrolling sideways, and a case can move to any stage as long as the detour carries a reason.
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 to any stage, or use its Move button. A move that is not the next step asks for a reason and is recorded on the case timeline. 6 cases in view.
Press the right arrow key to advance this case one stage, or use its Move button to choose any stage. Moving out of order asks for a reason first.
This is the real screen, rendered live against fictional demo data — not a screenshot.
No install, no card, no sales call first.
Take CaseSteward for a spin
You get 20 minutes signed in as a real staff member, on a fictional organization. Click around, change things, break things — everything resets when you are done.
What you’re looking at
The caseload as a board, one lane per stage. The important part is what sits underneath: every move 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. Real work does not always run in order, so the board can send a case anywhere — it just insists the detour be explained and written down.
On this screen you can
- See every consumer as a card in their current stage
- Advance a case three ways: drag the card, press the right arrow key on it, or tap its Next button, which names the stage it will move to
- Send a case to any stage, forward or back, from the card’s Move menu, which lists every stage and marks the ones that will ask for a reason
- Give that reason when a move is not the next step: it goes on the case timeline as an override, next to the name of whoever moved it
- Get asked to confirm before a case reaches Submitted to Funder or Case Closed, with the required stages the case has not reached yet listed by name
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
- Moving out of order is its own permission, held by supervisors, org admins and owners. Without it the board offers forward moves only, and a reason alone will not buy the move
- A reason is required, not merely invited: the state machine refuses an override that arrives without one
- The board works on a phone: the lanes wrap instead of scrolling sideways, and stages holding no cases stay out of the way until you ask for them
In this demo you’re watching the screen as Marcus Ellison — Program Supervisor, against a fictional organization of 10 staff and 15 consumers. Signing in with a different role changes what renders — that scoping is the product, not a demo trick.