Status clarity
A person should not have to guess whether a filing packet was uploaded, staged, submitted, rejected, corrected, or accepted for further review. Status should be plain, current, and tied to evidence of what happened.
Recoverable workflows
Clear states
Status names should reflect the actual workflow state instead of vague labels.
Outcome evidence
Important events should leave a record that can be reviewed later.
Correction loops
Deficiencies should explain what is missing and what the next step is.
No silent failure
Filing and payment-adjacent workflows should be designed so uncertainty is surfaced quickly.
Integration posture
For official filing workflows, integrations should use authorized or certified channels where required. Public pages should not imply scraping, bypassing, or unofficial court submission.