← Back to Concept Study

The Unrecorded Audit Sequence

Why audit governance fails in low-capacity administrations, and what should replace it

An audit follows a sequence every manual states in the same terms. A sequence is a fact rather than an opinion — it either was followed or it was not. It should be the most governable thing an authority does. It is the first thing to fail.

The work, and the record of it

Officers follow the sequence. What the institution can later verify is another matter entirely.

recorded institutionally no trace outside the officer
01

Overview

An audit is not an unstructured enquiry. It follows a lifecycle every revenue authority recognises in substantially the same terms: a case is assigned; the officer investigates and requests information; an unanswered request escalates; findings are documented; the findings support an assessment; the liability is pursued; and the case closes when a supervisor approves it.

Of everything a revenue authority does, this should be the most governable, because a sequence is a matter of fact. Whether an assessment rests on documented findings is not a question of professional opinion. It either does or it does not, and the answer is knowable.

And yet the sequence is precisely what disappears first. The failure is not one of training, culture, or diligence. Officers know the lifecycle and generally follow it; what the institution lacks is any means of confirming that they did without asking them. Nothing here is miscalculated — the work is done correctly and the record of it simply does not exist outside the person who did it.

The central claim

The revenue lost to weak audit governance is, in the main, not revenue that was wrongly assessed. It is revenue that stalled — a request no one was tracking, findings waiting in an inbox, a liability assessed and never reconciled against what was recovered.

02

Diagnostic framework

Process reconstruction of the as-is cycle, failure-mode decomposition against a problem tree, and design prescription derived by inverting the root condition.

Key diagnostic insights

  1. 01 Deadlines live in private calendars, so a lapse is reported by the person it reflects upon, or not at all — an arrangement that would be recognised as unsound anywhere else in the institution.
  2. 02 Nothing establishes that documented findings were complete when the assessment was drawn from them. The gap is immaterial until the assessment is contested — which is rare, late, and precisely when it is most costly.
  3. 03 Case history departs with the officer who held it. The successor rebuilds what can be rebuilt and proceeds without the rest, and the loss is never quantified because nothing recorded what was there.

The root condition

The audit lifecycle is treated as a collection of independent administrative tasks, performed by individual officers upon artefacts the institution does not hold, rather than as a single governed sequence for which the institution maintains a continuous, shared and verifiable record.

03

The reference design

The prescription is organised around a single invariant, from which the architecture follows.

The invariant

No stage of the lifecycle may be skipped or silently reordered. An assessment must reference the findings it rests upon; closure must follow an approval recorded by someone other than the officer who conducted the work; and every transition between stages is permanently recorded, never quietly corrected. Governance is the act of enforcing this sequence — not of second-guessing the officer’s judgement within it.

The three-record model

Claimed · D

What the audit determined

The liability determined by the audit, recorded against the findings it rests upon, with a unique reference and issue date. Never overwritten by what is subsequently recovered.

Recovered · C

What was realised

Amounts received against this specific assessment, including partial payments, each matched to the claim it settles.

Outstanding · V

The residual case

V = D − C, held as a record rather than derived on request, with its age and the recovery action taken. The figure the manual process does not produce.

04

What should be measured

An implementation should be evaluated against outcomes rather than delivery milestones. Each indicator below is observable, and each degrades visibly when the design is failing.

Indicator What it measures Healthy trend
Recording latency Elapsed time between an event and its entry in the record. Falls toward same-day and stays there. This is the leading indicator for every other measure; rising latency invalidates them all.
Overdue obligations Requests and escalations past their date. Rises sharply at implementation as concealed backlog becomes visible, then falls. An authority that has not anticipated the rise will misread the first success as the first failure.
Stage ageing How long cases remain at each stage. Distribution tightens. Attention belongs on the tail, not the mean.
Approval latency Time between closure request and decision. Low and stable. A rising figure converts a control into a delay.
Reconstruction Whether a closed case can be reproduced end to end on demand. Complete, and tested by reconstructing a case at random without contacting anyone.
05

Study reference & lineage

Domain: Domestic revenue mobilisation · tax audit administration · case governance · administrative reform.
Unit of analysis: The audit lifecycle of a national revenue authority, from assignment to closure.
Method: Process reconstruction, failure-mode decomposition, design prescription.
Applicability: Revenue administrations with growing taxpayer populations and limited audit capacity.

This study advances a general argument about administrative design. It does not describe, endorse, or evaluate any commercially available system.
© 2026 The Unrecorded Audit Sequence — concept study prepared by Sujoy Maitra.