Priorities and assignees: making sure no client request goes cold
Every client request needs an owner and a priority. Practical rules to keep follow-ups visible and stop work from going cold mid-quarter.
A client emails asking whether they can claim a vehicle expense. It lands in a shared inbox, three people glance at it, everyone assumes someone else will reply, and a fortnight later the client rings to ask why they have heard nothing. Nobody dropped the ball deliberately. The request simply never had a name attached to it.
This is how work goes cold in an accounting practice. Not through neglect, but through ambiguity. The fix is unglamorous and reliable: every incoming request gets one owner and one priority, the moment it arrives. This guide sets out practical rules for doing that consistently, and how to keep the trickiest cases, the ones waiting on the client, from quietly disappearing.
Why an owner matters more than a queue
Shared mailboxes feel efficient because everyone can see everything. In practice, shared responsibility is no responsibility. When a request belongs to the team, it belongs to no one, and the diffusion of accountability is exactly what lets a BAS query sit unanswered for a week.
The first rule is simple: a request is not triaged until it has an assignee. In Finye, every inbound client request becomes a work item on a board, and that work item carries an explicit assignee field. Email-to-ticket turns client emails into work items automatically, so the message that used to languish in a mailbox now appears on a board where it can be picked up and owned.
Assigning an owner does not mean that person does all the work. It means one person is accountable for the request moving forward, for chasing internally if it stalls, and for being the point of contact the client can be told to expect a reply from. If the work needs to pass to a senior reviewer or a bookkeeper, the assignee changes, and accountability moves with it. There is always exactly one name on the item.
A priority scale your team will actually use
Priority only helps if it changes behaviour. A four-level scale that everyone applies inconsistently is worse than none, because it creates false confidence. Keep the definitions concrete and tied to consequences rather than feelings.
- Urgent — a hard external deadline within days, or a client unable to operate: a BAS due this week, an ATO deadline, a payment that has failed. These jump the queue.
- High — time-sensitive work with a deadline this fortnight, or a request from a client who is waiting on you to proceed.
- Normal — standard turnaround work with no immediate deadline. The bulk of requests sit here.
- Low — useful but not time-bound: a query you can batch, a tidy-up, a nice-to-have.
Anchor the scale to dates and lodgment obligations rather than to how loudly the client asked. The client who emails three times is not necessarily urgent, and the quiet client with a Div 7A loan that needs documenting before year end may be the one who genuinely is. In Finye, each work item carries both a priority and a due date, and your compliance engine already tracks the real ATO and ASIC deadlines, so the two reinforce each other instead of relying on memory.
Triage at the front door, not in a weekly meeting
The cost of a request going cold is highest in its first hour. If something is assigned and prioritised the moment it arrives, it is visible and owned. If it waits for the Monday huddle to be triaged, it has already spent days invisible.
Make triage a fast, front-door habit. Whoever is on intake reads each new work item, sets the priority, picks an assignee, and adds a due date. That is the whole ritual, and it should take under a minute per item. For practices handling a steady stream of requests, Finye's AI triage can suggest a priority, an assignee and a category for each incoming request, so the person on intake is confirming a sensible default rather than starting from a blank field. The judgement stays with your team; the typing does not.
The discipline that matters here is the no-orphan rule: no work item leaves the intake stage without an owner and a priority. If you only adopt one habit from this article, make it that one. Read more about structuring intake in our guides.
The waiting-on-client trap
Here is where most cold requests are actually born. You reply to the client asking for a missing invoice, a signature, or confirmation of a figure. The ball is now in their court, so you mentally tick it off. The client gets busy, forgets, and the item sits in limbo. It is not your turn, so it never resurfaces, and three weeks later it is genuinely overdue.
The mistake is treating waiting-on-client as done. It is not done; it is parked, and parked work needs a tripwire. A few rules keep these visible:
- Give it a status, not silence. Move the work item to a distinct waiting-on-client column on the board rather than letting it look closed. A glance at the board should show you everything that is stalled on someone else.
- Keep the owner. The assignee does not change just because you are waiting. It is still their job to chase. Waiting on the client is not a transfer of responsibility.
- Set a follow-up date. Use the due date as a chase date. If the client has not responded by then, the item surfaces and the owner follows up. Two or three nudges, then a decision about whether to escalate or close.
- Make the request itself trackable. For documents and signatures, use Finye's document and PBC requests and engagement e-signing so the outstanding item is a tracked object with its own reminders, rather than a line in an email you have to remember.
The principle is that nothing should depend on someone remembering to check. Parked work needs a date that brings it back. If it has no date, it has no future.
Make the board tell the truth
Rules only hold if the board reflects reality. The point of assigning owners and priorities is that a manager can open the list view, filter by assignee, and see at a glance who is carrying urgent work, what is overdue, and what has been waiting on a client for too long. That visibility is what turns individual diligence into a practice-wide safety net.
Spend five minutes a day, or run a short weekly review, looking specifically for two things: work items with no assignee, and items sitting in waiting-on-client past their follow-up date. Those two lists are where requests go to die, and catching them early is the entire game. Comments, checklists and subtasks on each work item keep the context attached, so whoever picks up a reassigned item is not starting cold.
None of this requires a new methodology. It requires one owner, one priority, and a follow-up date on every request, enforced at the front door and reviewed regularly. Do that, and cold requests stop being a recurring apology and become a thing that simply does not happen.
Finye gives every client request an owner, a priority, a due date and a visible board, with AI triage and tracked document requests built in. Start a free trial and see how your intake runs when nothing goes cold, or review the pricing to find the plan that fits your practice.