Collections workspace · Independent concept · 2026
A daily worklist for collections teams
A score can rank accounts without explaining whether to act or why. Based on my earlier banking work, I explored a worklist that brings contact restrictions, reasons, and suggested actions together. The concept assumes an existing repayment-probability model; my focus is the experience around its output.
Self-initiated concept · Not shipped or validated
This is a new concept based on earlier professional work. Names, balances, counts, and scenarios are illustrative.
Check eligibility before priority
I separated three questions: can this account be contacted, why does it need attention, and what action should be considered?
An active contact restriction keeps an account outside the actionable queue. Eligible work is then prioritized, with a separate recommendation for the next step. The bank would need to define and validate the exact rules before implementation.
Put the reason beside the action
The worklist groups accounts by when they need attention. Each row brings together urgency, relevant reasons, key figures, and a suggested action.
I kept the explanation close to the decision: a broken promise or an active arrangement can matter more here than a longer list of model inputs.
Make recommendations open to correction
The account view puts restrictions, history, and the recommendation in context. The collector can review its reasoning, report incorrect information, or choose another action.
The recommendation supports a decision; the interface must also provide a clear way to question it.
What I would test
I would use representative scenarios to check whether collectors notice restrictions, understand the reasons, and can correct an inappropriate recommendation.
I would also review the reliability of the proposed data inputs with engineering before testing the workflow against a baseline.