A firm-wide working paper template is not a fixed document — reviews turn up gaps, procedures get added, and a firm admin revises it. The operational question that revision creates is what happens to engagements already underway on the old version: do they finish on the template they started with, switch mid-stream to the new one, or end up with some files on each version sitting in the same engagement file. Left unaddressed by default, different staff on the same engagement will answer that question differently, which produces exactly the structural inconsistency the template existed to prevent in the first place.
Why this is a real problem, not a theoretical one
Template revisions don't happen at convenient moments. A quality-control review in November finds that two unrelated engagements are both missing documentation of how a sample was selected, which is a sign the related-party or revenue testing template needs an added section. By November, a mid-size firm typically has a dozen or more statutory audits already substantially underway, each with working papers already drafted on the old template. Revising the template immediately is correct — waiting until next season to fix a known gap means repeating the same gap on every file closing between now and then. But immediate revision collides with files that are already most of the way done.
The three realistic options, and their actual costs
| Option | What it costs |
|---|---|
| Finish all in-progress engagements on the old template | The known gap persists on every file closing this season, including the two that triggered the revision |
| Switch every in-progress engagement to the new template immediately | Rework on files that are 80% done, for a change that may only matter going forward |
| New engagements get the new template; in-progress ones finish on the old one, flagged as such | A firm has two valid versions in circulation simultaneously, and has to track which is which |
Common practice, not a requirement
The third option is the one most firms converge on in practice: finish what's in flight on the version it started with, apply the new version to everything that hasn't started drafting yet, and explicitly record which version each engagement used. It accepts that the fix isn't retroactive rather than pretending it is.
What has to be recorded when a template changes
- The date the revision took effect
- What specifically changed — a section added, renamed, split, or removed
- Which engagements, if any, were switched mid-stream rather than finishing on the old version
- Who approved the revision, since a template change is a quality-control decision, not a drafting preference
The riskiest version of this problem is silent drift rather than a deliberate revision — a partner tells one senior to add a section 'for this client', that senior reuses the modified template on the next engagement because it's already open on their screen, and within a season the firm has several working, undocumented variants of what was supposed to be one firm-wide template. That isn't a template change; it's the loss of the thing a template was for, without anyone deciding it should happen.
Why the answer can't be 'whoever is editing the file decides'
A template exists so a reviewer doesn't have to learn a new structure per file. If individual preparers can revise it on the fly whenever they think of an improvement, the firm is back to engagement-by-engagement formats, just with extra steps. A genuine improvement to a template is valuable and should be made — but it should be made once, deliberately, by whoever owns the firm's documentation standards, and then applied consistently going forward, not patched into one file by whoever happened to notice the gap first.
How we think about this
Lekhya's templates are owned at the firm-admin level, not by individual engagement teams. A revision changes the template going forward for new working papers; it does not silently rewrite the structure of working papers already generated under the version that existed when they were created.
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 documentationVersion control for audit working papersThe file name is a confession. If a working paper needs 'actualfinal' in its name, the firm has no real way of knowing which version was reviewed.
- Audit documentationCustom working paper templates: standardising a firm's own format, not inventing a new oneA reviewer should be able to open any engagement's working papers and know where to look. That only happens if the format was decided once, not reinvented per file.
- Audit documentationReviewing and signing off audit working papersWhat a reviewer is responsible for, a defensible review order, writing points that get cleared properly, and why approval must lapse when the paper changes.
- 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.
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.