What we still need from the client
An example of the client mirror of staff chase: a clear list of missing and rejected items, due dates, and an upload path that matches the pack.
Example flow from custom practice builds. Not a packaged product feature.
See it in motion
How this feels in the working day
A short simulated run of the practice UI. No live AI on this page. Open the portal demo when you want to click through the real queues.
What we still need from you
The client mirror of staff chase. Specific asks, not a vague email.
From Harper & Associates
What we still need from you
3 items · 7 days left
- 1
Fixed asset additions
Please re-upload with the fixes above.
- 2
Payroll summary
PAYE, FPS, pension contributions
- 3
Directors loan account
Movement schedule for the SA pack
Clients see a clear list from the firm: what is missing, what to re-upload, and how many days until the deadline.
The problem
Clients guess what is outstanding
The firm knows what is missing. The client gets a vague chase and either over-sends or goes quiet until the deadline.
Vague chases get vague replies
“Please send everything for year end” produces the wrong PDFs and another chase.
Rejections disappear into email
A rejected fixed-asset schedule never becomes a clear re-upload task on the client side.
No shared countdown
Clients do not see days left against the same list staff are chasing.
Staff and client flow
How this example runs
Staff chase updates the same still-needed list the client sees. Uploads clear lines. Rejections come back with notes.
Chase from Missing from client
Reminders point at specific missing or rejected documents on the pack.
Open what we still need
They see numbered items, due date, and firm notes such as what to fix on a re-upload.
Upload against the list
Each file lands on the matching checklist line, not in a personal WhatsApp.
Clear the line for both sides
Staff queues and client progress update together when something is accepted or sent back.
In the week
What changes in the week
Fewer “what do you still need?” replies. Clearer ownership of the gaps.
Clients act on a specific still-needed list instead of guessing
Rejected items come back with fix notes on the same list
Staff chase and client uploads stay on one shared pack state
Custom each time
An example, not a product SKU
This is an example from builds like the Harper Associates portal demo. Every system is scoped to your process, branding, and channels after a discovery call.
FAQ
Common questions
Straight answers on fit, scope, and what custom means here.
Explore
More example workflows
Want this shaped for your firm?
Book a free discovery call. We will map your process and put a clear project price in writing if there is a fit. Try the portal demo if you want to click through an example first.