Speed without a stop rule is just a faster mistake. Acholoehub treats the reviewer as part of the machinery. The pack is incomplete until their note is there.
Four eyes, above a line you choose
Small, stable returns can be reviewed lightly. A variance over the threshold you set — we often start at a percentage of last period’s liability, plus a fixed floor — needs a second person. The threshold is written down. It is not a mood.
Preparer is not the filer
Where the team has more than one person, the person who built the pack does not press submit. A sole practitioner records a timed pause instead: build, leave it, review against the checklist, then file. The log shows both moments.
Stop-file rules
Bank feed still open past the freeze.
Control account outside the tolerance.
Exception older than its allowed age.
Reviewer note missing or unsigned.
Software period that does not match the calendar period.
Any one of these holds the pack. Overriding a stop requires a named reason, not a click.
Evidence, kept together
The archive holds the return, the source list, the adjustments, the exception log and the reviewer note in one folder per entity per period. Six years is the retention we design for unless you instruct a longer hold for a specific matter. We do not scatter this across email.
An audit trail a tired partner can read.
Each change of tax code, each cleared exception, and each release records who, when, and why. The view is a page, not a database export. If an HMRC enquiry arrives, the folder is the answer to “how did you get this number”, not a reconstruction project.
This is an operational record. It is not a substitute for your professional file, and it does not create a legal privilege where none exists.