A realistic 90-day rollout for audit automation at a mid-size firm runs in three deliberate 30-day phases rather than a single switch: days 1-30 for setup — configuring templates, migrating prior-year data for the pilot clients, and training the pilot team; days 31-60 for a live pilot on one or two representative engagements, run alongside the firm's existing process where needed as a safety net; and days 61-90 for expansion to additional teams, incorporating the specific lessons from the pilot rather than repeating the same setup blind — with the explicit understanding that a mid-size firm's full rollout across every engagement may reasonably extend beyond day 90, and treating day 90 as a milestone to re-evaluate rather than a hard deadline to finish by.
Days 1-30: setup
- 01Week 1: assign a rollout owner and select the pilot client(s)One person needs to own this, even at a firm where the decision was made collectively — see the companion article on the pilot-client selection criteria.
- 02Weeks 1-2: run the vendor's security and onboarding process in parallel with internal setupDon't wait for IT sign-off to start configuring templates if the two can run concurrently.
- 03Weeks 2-3: migrate prior-year working papers for the pilot client(s) specifically, not the whole portfolio yetUse the companion data-migration checklist, scoped to just the pilot engagements to keep this phase manageable.
- 04Weeks 3-4: train the pilot team on the actual workflow they'll run, not a generic product overviewTraining that walks through the firm's own checklist inside the new system is more useful than a vendor's standard demo.
Days 31-60: live pilot
- 01Run the pilot engagement(s) through the new system as the primary workflow, not a side experimentA pilot run half-heartedly alongside the old process in full produces weak signal about whether the new one actually works.
- 02Check in with the pilot team weekly, specifically asking what friction came up, not just whether things are 'going fine'A general status check gets a general answer; ask about specific steps that took longer than expected or produced confusion.
- 03Keep a running list of configuration or template changes needed, rather than fixing issues ad hoc and forgetting themThis list becomes the input to the expansion phase, so it needs to be written down as issues arise.
- 04Hold a specific go/no-go review at day 60 against criteria set before the pilot startedSee the companion pilot-decision article — deciding the criteria after seeing the result invites bias toward whatever outcome is already preferred.
Days 61-90: expansion
| Aspect | Pilot phase (days 31-60) | Expansion phase (days 61-90) |
|---|---|---|
| Templates | Vendor defaults, adjusted as issues surface | Firm's refined templates, informed by the pilot's specific findings |
| Team | One team, closely supported | Additional teams, trained using lessons already captured, not starting from zero |
| Support need | High — expect frequent questions | Lower per team, since common issues were already resolved in the pilot |
| Data migration | Pilot clients only | Remaining clients, following the now-tested migration checklist |
A firm that tries to compress all three phases into 30 days, or runs the pilot and the full rollout simultaneously, tends to repeat the pilot's own mistakes across every team at once instead of catching and fixing them once. The 30-day spacing exists specifically to let each phase inform the next.
Common practice, not a requirement
90 days is a realistic plan for a mid-size firm's first meaningful rollout wave, not a promise that every engagement will be on the new system by day 91. Treat the day-90 review as a checkpoint to plan the next wave, not a deadline the whole firm has to clear.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Audit workflow & automationPilot on one client or roll out firm-wide: a decision frameworkThe right rollout speed depends on how similar the firm's engagements actually are to each other, not on how confident the partner feels after the demo.
- Audit workflow & automationData migration checklist: moving prior-year working papers to new softwareThe question isn't just what to move over — it's what to deliberately re-create instead of migrating, and how to document the switch itself.
- Audit workflow & automationMulti-partner firm technology decisions: who needs to be in the roomA managing partner, an audit partner, and a quality-control partner are evaluating three different things when they look at the same software. Here's what each one actually cares about.
- Audit workflow & automationAudit software for firms with 50+ audit staff: what changesPast roughly 50 audit staff the decision stops being about one partner's workflow and starts being about standardising dozens of them at once.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.