The Story
An operational governance and process-control assessment for a Chartered Accountancy firm, focused on reducing operational dependency, improving ITR processing, strengthening staff accountability, and giving management a clearer view of day-to-day operations.
The Challenge
The Firm had a familiar problem for a growing professional-services firm: the work was getting done, but too much of the operation depended on people remembering what needed to happen next.
Client requirements were being exchanged across WhatsApp messages, phone calls, and informal conversations. Staff could be working on the same client without a single place showing what had been requested, what had been received, who owned the next step, or what was still outstanding.
The ITR process had also grown around individual experience rather than a defined workflow. Experienced team members knew the process almost instinctively, but that knowledge was difficult to transfer, measure, or replace when someone was unavailable.
Management faced another visibility problem. It was difficult to distinguish a genuinely complex workload from a delayed task, a client-side dependency, or an inefficient internal process because there was no consistent data around task ageing, completion time, overdue work, or rework.
The assessment therefore focused on a practical question: how could the firm create enough structure and visibility to scale without introducing unnecessary bureaucracy?
The Solution
The engagement began by mapping the operational problems using an Observation → Risk → Root Cause → Recommendation → Owner framework. This helped separate symptoms from the underlying process issues and gave each finding a clear path toward remediation.
The first priority was visibility. We recommended centralising client requirements and introducing a single case owner for each engagement, supported by standard request templates for common engagement types such as salaried individuals, business and professional clients, capital gains, and rental income.
The ITR process was then redesigned as a defined sequence: Onboarding → Requirement Identification → Document Request → Collection → Verification → Preparation → Internal Review → Client Confirmation → Filing → Acknowledgement → Closure. Each stage would have clear completion criteria rather than relying on individual memory.
A major part of the work addressed key-person dependency. Critical activities concentrated around Sandeep were identified for documentation, knowledge transfer, and backup ownership. The objective was not simply to remove one person from the process, but to turn their operational knowledge into repeatable processes that the wider team could follow.
We also introduced a stronger accountability model: every task should have an owner, due date, status, and completion evidence. Standard statuses such as Not Started, In Progress, Waiting for Client, Under Review, Blocked, and Completed would make operational bottlenecks visible instead of leaving them buried in conversations.
Finally, the recommended operating model introduced a lightweight management dashboard covering active cases, overdue tasks, client dependencies, blocked activities, staff workload, and ITR status. A 10-minute daily operational review and weekly management review would provide the cadence needed to identify problems before they became deadlines or escalations.