A peer reviewer's first pass through a sampled file is structural, not substantive: can they locate the scope, the population tested, the exceptions and the sign-off without hunting. A firm that uses the same named-section template across every engagement for a given procedure passes that first check instantly, file after file. A firm where every engagement team invented its own layout forces the reviewer to re-learn the format each time, which slows the review and increases the chance something gets missed simply because it was in an unexpected place.
What peer review readiness actually means at the file level
Peer review readiness is usually discussed as a documentation-completeness question — do the files contain enough evidence. That's necessary but not sufficient. The other half is navigability: a reviewer working through a sample of twenty or thirty engagements across different clients and different staff needs to find the same things in the same place every time. A firm that documents thoroughly but inconsistently still makes the reviewer's job harder than it needs to be, and a harder review is a slower review with less time left for the parts that actually require judgement.
The structural checklist a reviewer runs before reading content
- Is the scope of the procedure stated, and stated in a predictable place
- Is the population or sample tested identified before the testing detail
- Are exceptions, if any, called out as their own section rather than buried in narrative
- Is the conclusion separated from the testing detail, not mixed into it
- Is the sign-off trail (preparer, reviewer, partner) visible and in a consistent location
Regulatory requirement
SA 230 requires an auditor to prepare documentation sufficient to enable an experienced auditor, having no previous connection with the audit, to understand the nature, timing and extent of procedures performed, the results obtained, and significant judgements made. A peer reviewer is exactly that experienced auditor with no previous connection — the standard is written around the reviewer's situation, even though it doesn't mandate any particular template.
Why a firm-wide template helps here specifically
A template doesn't make a weak working paper strong — it can't add evidence that wasn't gathered. What it does is remove one entire source of reviewer friction: not knowing where to look. If every bank reconciliation working paper in the firm has a 'Reconciling items' section in the same position, the reviewer stops spending attention on navigation and spends all of it on whether the reconciling items were actually investigated properly. That reallocation of attention is the real benefit, and it compounds across a sample size large enough that peer review actually covers.
| A consistent template buys this | A consistent template cannot buy this |
|---|---|
| Faster navigation across a sample of files | Evidence that wasn't actually gathered |
| Confidence that a missing section is really missing, not just relocated | A conclusion that was never properly reasoned through |
| Easier comparison of similar procedures across engagements | Compliance with SA 230 on its own |
A firm sometimes treats 'we have a template' as the whole peer review preparation story. It isn't. A perfectly structured file with thin testing still fails on substance. Structure earns the reviewer's attention faster; it does not replace the work the attention is spent judging.
Where this breaks down in practice
The common failure isn't the absence of a template — most firms have some house format by the time they're large enough to face peer review. It's inconsistency in application: the senior who's been there eight years uses the house format faithfully, the article who joined in June uses whatever the previous firm's template looked like, and a partner reviewing both doesn't always catch the drift before the file is closed. A template that lives only as a saved Word file on a shared drive is a suggestion. A template enforced at the point the working paper is created is a standard.
How we think about this
Lekhya lets a firm admin define a named section structure once per procedure, and every working paper generated for that procedure follows it automatically, for every engagement and every client. The structure is fixed by the firm; what's written inside each section is still entirely the engagement team's own work — never generated or pre-filled.
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 documentationSA 230: what actually has to be in the fileThe experienced-auditor test explained in plain terms, what documentation has to demonstrate, when the file has to be assembled, and the gaps that most often draw comment on review.
- Audit documentationAudit working papers: what they should containThe anatomy of a paper that stands on its own: objective, population, sample basis, procedure, results, exceptions, conclusion and sign-off, and what each must establish.
- 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 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.
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.