The client should see the next request — not a mystery.
This illustrative flow follows a missing-item request through a controlled portal and status view, internal review, and an owned exception.
Client-service lead · accounting and tax · a file waits on documents and the client keeps asking what is missing
What happens today
Today staff send repeated emails, clients upload to the wrong place, and nobody can tell whether a request was received, accepted, or still missing.
Why it matters
The risk is client uncertainty, repeated requests, and a file aging without an owner.
Where this starts
A scoped record has a required-item rule, an approved client message and status model, and a person responsible for review.
The workflow
- 1The coordinator opens the record and sees the specific item still needed, and the person responsible for follow-up.
- 2An approved request is created; the client sees only the permitted status and action through a portal, where that is scoped.
- 3The client uploads or responds; the system records receipt and alerts the internal reviewer.
- 4The reviewer accepts, returns, or requests clarification, keeping the source and the decision visible.
- 5If the record still waits, the exception view shows its age, dependency, and owner for the next review.
Where a person decides
A client-service owner approves the request language, and a reviewer decides whether an item meets the readiness rule.
If it does not go to plan
An unsupported file, an access problem, or no response enters a human-owned exception and an assisted path. No automated message or portal access is assumed.
Where this ends
The client and the team see the appropriate next action, without exposing internal notes or another client's record.
What you can see
A request and status diagram, and an approved owned demo capture only where one exists. No generated portal interface is shown.
Why that is useful
A client request becomes visible work with a known owner and a status.
What this does not claim. Portal, identity, document storage, accessibility, e-signature, and notification rules are all scoped work — none is assumed. No response-time or adoption guarantee is made. Workflows are scoped in the Envisioning Workshop, and named integrations require discovery.
Workflow reviewed 2026-08-13