/client/cases list and 5 case detail states · all on one page. This page is not part of the cabinet — it exists as a quick reference for any pill combination without opening 6 different prototypes.
Every case displays 1–4 pills, grouped by layer with vertical dashed separators between groups:
Lifecycle stage. Always present. Single most important state indicator. Always visible first.
Who acts next. Hidden in terminal states (Decision received / Closed / Cancelled).
Only shown when Core = Decision received. Always includes the provider name (red lines compliance).
Computed from underlying data. Multiple can appear. Always secondary to Core / Decision.
Both badges signal that the client has work to do. They are different states with different visual identity, different copy, and different next steps. The reference page makes this split explicit so they are not used interchangeably.
When it shows: case is still in Draft or In preparation. Nothing has been sent to the provider yet. Submit button is disabled until all blocking requirements are completed.
What blocks it: blocking readiness items inside the case itself — missing documents, missing required profile fields, jurisdiction excluded by provider config.
Next step copy: "Complete N blocking requirements before submission" or a specific item like "Upload Certificate of Incorporation".
Visual identity: amber (warning, not urgent) — work is needed but no deadline is running, no provider is waiting.
When it shows: case is already submitted and under provider review, but the provider has opened a clarification request and the client has open required action items inside it. Submit is not relevant here — the client should respond to the request.
What blocks it: open required items inside the active provider request. Response bundle cannot be sent partial.
Next step copy: "Complete N provider-requested tasks" or a specific action item.
Visual identity: red (urgent) — provider is waiting, deadline is running. Different stakes than pre-submission readiness.
If no active provider request exists and there are blocking readiness items → Not ready. If an active provider request exists and there are open required items inside it → Action required. The two states are mutually exclusive — a case cannot be both Not ready and Action required at the same time.
On the list view, every card uses minimum Core + Waiting pills. Derived badges and Decision are only shown when they need to attract attention (deadline approaching, decision received). Full 4-layer breakdown lives on case detail.