Running a multi-partner firm on one shared workflow
How to align partners on shared statuses, templates and visibility without forcing everyone into the same style, so cross-team work stops stalling.
In a single-partner practice, the workflow lives in one person's head and that is usually fine. Add a second or third partner and the cracks start to show. One partner runs a tight kanban, another keeps everything in a spreadsheet, a third just remembers. Work that crosses teams stalls at the handover, a BAS sits in someone's inbox, and the client chases because nobody owns the next step. A workable multi partner firm workflow does not mean forcing every partner into an identical routine. It means agreeing on a few shared anchors so work moves cleanly between teams while each partner keeps the style that suits their clients.
Where multi-partner firms actually lose time
The friction in a multi-partner practice rarely comes from the accounting. It comes from the seams between people. A return needs a partner review, but the reviewer cannot see it is ready. A bookkeeping client asks a tax question and the request bounces between two teams with no record of who has it. A job marked done by one partner is still open in another partner's mind because they use different definitions of finished.
These are coordination failures, not capability failures. They get worse as the firm grows because every new partner adds another private system that the others cannot see into. The fix is not a mandate that everyone work the same way. It is a small set of shared conventions that travel with the work itself, so a job carries its own state no matter whose desk it lands on.
Agree on shared statuses, not shared styles
The single highest-leverage agreement partners can make is a common set of statuses. When every job across the firm moves through the same named stages, anyone can glance at a board and know exactly where work sits without asking. A practical baseline is something like To Do, In Progress, Waiting on Client, In Review and Done, with priorities and assignees layered on top.
In Finye, client requests and jobs are work items that live on boards, viewable as kanban or as a list, with status workflows, priorities, assignees, comments, attachments, checklists and subtasks. That last point matters for partners who think differently: the underlying status is shared, but how each partner looks at it is not. One partner can work the kanban and drag cards across columns; another can stay in the list view and triage by priority. Same data, same definitions of done, two completely different working styles. You get alignment on what a stage means without dictating how anyone spends their day. See how boards are structured on our guides.
The discipline is in the language. If "In Review" means a partner sign-off in the tax team but a quick peer-check in bookkeeping, the status stops being trustworthy. Write a one-line definition for each stage, agree it once, and the board becomes a source of truth the whole firm can lean on.
Templated recurring work so handovers do not depend on memory
Compliance work is the same shape every quarter, which makes it the easiest place to remove friction. Quarterly BAS, IAS, annual returns and ASIC reviews follow predictable steps, so the steps should not be reinvented by whichever partner happens to pick the job up. Finye supports templated recurring jobs that auto-generate, so a quarterly BAS appears as a fresh work item on schedule, already carrying its checklist and structure.
For a multi-partner firm the value is consistency across teams. When the template defines the steps, a job started by one partner can be finished by another without a verbal handover, because the checklist already says what is left. New staff inherit the firm's way of working rather than one partner's habits. The compliance engine reinforces this by tracking Australian lodgment obligations and due dates, including BAS, IAS, income tax returns and ASIC reviews, with a dashboard and a per-client view, so deadlines belong to the firm rather than to whoever remembered them. That shared visibility is what stops a return from quietly slipping past its ATO due date during a busy patch.
Visibility across teams without surveillance
Partners are wary, rightly, of tools that feel like they are watching staff. Useful visibility is about the work, not the worker. The question a partner needs answered is simple: where is this client's job and what is it waiting on? With shared boards and a per-client view, any partner can open a client and see the requests in flight, who holds each one, and what is blocking it, without interrupting anyone to ask.
This is also where cross-team requests stop falling through. When a bookkeeping client raises a tax question, email-to-ticket turns the inbound email into a work item rather than leaving it buried in one partner's inbox. From there it can be assigned to the right person and tracked to done. AI triage can suggest a priority, assignee and category on incoming requests, which takes the routing guesswork out of work that lands at the boundary between teams. The point is not to automate judgement away, but to make sure nothing sits unowned at a handover.
Make the shared workflow real with a few habits
Tools only hold a firm together if the habits are agreed. A handful of partner agreements do most of the work:
- One definition of done. Write a short definition for each status and stick to it across teams.
- Every job on a board. If it is not a work item, it does not exist. No private side-lists that only one partner can see.
- Templates own the routine. Recurring compliance jobs run from shared templates so handovers do not rely on memory.
- Waiting on Client is a real status. It tells the firm a job is parked on the client, not on a partner, which protects everyone from chasing the wrong thing.
- Review by exception. A shared In Review stage lets a partner sign off when a job is genuinely ready, instead of being copied on everything.
None of this asks a partner to abandon how they like to work. It asks them to agree on the seams: the statuses, the templates and the visibility that let work cross between teams cleanly. Inside those seams, run the practice however suits your clients.
If your firm is stitched together across spreadsheets, inboxes and a few people's memories, a single shared workflow is the quiet upgrade that makes the partnership feel like one practice. You can start with Finye and put your teams on shared boards, or look at what is included on our pricing page first.