Every pack.
A visible next step.
Submit a complete sample pack, switch to the reviewer and record a decision.
Fictional demonstration · original sample rules and dataEmail attachments → chase reviewer → uncertain version
Complete pack → review decision → status + notification
Prepare and review
Use the role switch to try both sides of the handoff.
Completeness is checked before submission. The author cannot approve their own pack.
Decision trail
Sample notification outbox
Notifications are shown here only; nothing is sent.
Watch the 18-second walkthrough
Transcript: Try to submit an incomplete pack: the completeness check blocks it. Add both sample documents and submit. The author cannot approve. Switch to reviewer and request changes. Switch to author, resubmit, then approve as reviewer. Version 2 is approved and the decision trail and sample notifications stay visible. No documents are uploaded and no messages are sent.
Silent clip assembled from actual demonstration interaction states.
What this shows, checks and limits
This original example checks required documents and role-dependent actions, preserves decisions and increments the version when a returned pack is resubmitted. A real system needs server-enforced access, private file storage, actual identity and audit controls, retention decisions and a tested notification service. The role switch is a demonstration control, not security. No uploaded documents or real delivery records are used.
Have a similar workaround?
Bring one repeated task. We can discuss a useful, bounded first step.