CA practice playbook: notices, workings, and client Q&A without WhatsApp
Chartered accountancy work is deadline-driven and document-heavy. This playbook focuses on engagement hygiene: how notices, workings, and client questions should move through a firm so partners can see status without hunting personal chat histories.
Map the engagement lifecycle before you pick tools
A typical notice or filing support engagement has intake, document collection, internal preparation, client clarification, filing or response, and closure. Email and WhatsApp collapse those stages into one noisy stream. Juniors keep “final_v7” on laptops; partners ask for status in group chats that also contain birthday messages.
Define stages on paper first. Decide which artifacts must live in the engagement file (notices, workings, client uploads, final submissions) and which messages are allowed outside (appointment reminders). Tools amplify a process; they cannot invent one.
Engagement-bound messaging vs personal chat
When a client asks a technical question on WhatsApp, the answer becomes tribal knowledge on one phone. If that staff member leaves, the firm loses context and the client expects continuity. Engagement-bound encrypted messaging keeps Q&A next to the working papers so the next assignee inherits the thread.
Partners should be able to open an engagement and see conversation, files, and participants without requesting screenshots. That visibility is an operations control, not just a security feature — it reduces rework and missed deadlines.
GST notice and filing support checklist
Create one case per notice or engagement code. Upload the notice and supporting ledger extracts into the file area. Invite only the engagement team and the client contacts who must upload or approve. Use the conversation for clarifications (“which invoice series?”) instead of parallel email chains.
Store drafts and workings with clear names and dates. When the response is filed, mark closure, remove client upload rights if appropriate, and retain logs for internal review. For recurring compliance clients, reuse case types so every engagement starts with the same fields and tabs rather than improvising folders.
Staff turnover and device reality
CA firms often rely on personal devices for WhatsApp Business. That creates offboarding gaps: clients keep chatting a number that no longer belongs to the firm. Firm-owned engagement spaces let you revoke a user without asking them to delete chat history from a personal phone.
Combine access revocation with a short handover note inside the engagement: open items, filing deadlines, and where the latest workings live. Security controls fail quietly if knowledge transfer is skipped.
What good looks like after 90 days
Fewer privileged or client financial attachments in personal email sent items. Partners can open any active engagement and find the latest notice pack without asking. New joiners ramp faster because history is in the engagement, not in someone’s WhatsApp backup.
You will still use email for invitations and some regulator portals. Success is not zero email — it is zero critical workings living only in chat.
Evaluating DASH for a CA practice
Look for configurable case types, encrypted messaging, large-file uploads with scanning, roles, and audit logs. Walk the CA product workflow screens for GST-notice style journeys. Use the CA solutions page for product positioning, then pilot one notice type with a willing partner before firm-wide rollout.
Define success before the pilot: fewer client financials in personal WhatsApp, partner can open any active engagement and find the notice pack in under two minutes, and a leaver can be revoked without begging for phone access. Those outcomes matter more than feature checklists.
Partner review cadence that actually sticks
Weekly, partners should skim open engagements for stalled client uploads and unanswered clarifications — inside the system, not via a status WhatsApp blast. Monthly, review who still has access on closed notices and remove stale clients.
Tie the cadence to existing partner meetings so it is not “another IT process.” Five minutes on engagement hygiene prevents the end-of-season scramble when filings cluster. If partners refuse the cadence, the tool will fill with stale engagements and staff will retreat to WhatsApp again — treat the meeting habit as part of the security control.
Client communication templates
Send a short onboarding note when inviting a client: why you are not using WhatsApp for workings, how to upload, and who will reply inside the engagement. Clients accept friction when the reason is confidentiality and continuity — not when it feels like busywork.
For urgent “please call” moments, phone remains fine. The rule is about documents and advice trails, not replacing every human conversation with a portal.
Include a one-line escalation path: if the portal is down or the client cannot log in, use a named partner email for emergencies only, then re-upload the substance into the engagement afterward so the file of record stays complete.
Common failure modes (and fixes)
Dual-writing — staff post the same draft in WhatsApp and the engagement “just in case.” Fix by making the engagement the only place partners will look; behavior follows incentives.
Empty cases — invitations go out but nobody uploads. Fix with a day-two checklist owned by the engagement manager: notice packed, client invited, first clarification posted. Tools do not replace ownership.
Over-permissioning — entire firm added to every notice. Fix with role defaults on the case type so new engagements start least-privilege.
Product overview for CA firms · Screen-by-screen CA workflow · Request a Demo