The audit report: structure and tone

A director receives a 40-page audit report. The opening pages cover history and methodology, and the main point is buried on page 31. The result is predictable: the director flips through the headings, phones the auditor to ask "So what is the short version?", and the report goes on a shelf. Weeks of the auditor's work never become a management decision. For an audit report to work, it must be written in a different order: conclusion first, evidence after.

A report's job is not to show how hard the auditor worked, but to help management make the right decision.

Report structure: conclusion first

The report opens with a one-page conclusion (the executive summary). It holds five things: what was examined, the 3–4 main findings with figures, an overall assessment, the single most important recommendation and the question management has to decide.

For a wholesale warehouse of furniture fittings it might read: "Of 4,120 items, 494 (12%) did not match between records and reality. The total difference is 38.6 million so'm of shortage and 9.2 million so'm of surplus. Most of it comes from three processes: two different article numbers stored under one barcode, late booking of returns and manual correction of balances. The first step is to separate the article codes."

The remaining sections

When the order is always the same, a manager finds the right place at once:

1. Title page: site, period, date, distribution list.
2. A one-page conclusion.
3. Objective, scope and method: half a page is enough.
4. Findings by significance, most serious first.
5. Management's response and agreed deadlines.
6. Appendices.

Order findings by importance, not by when they were discovered: the first page should carry what matters most.

Every finding in the same pattern

To keep findings easy to read, they are written to one template:

1. Condition: what was found, and how widespread.
2. Criteria: what should be the case (procedure, contract, ordinary practice).
3. Cause: why it happened.
4. Effect: the loss in so'm or time.
5. Recommendation: what to do, who does it, by when.

For example: "In the hinges and handles zone, stock differences were found on 62 items, and on 48 of them different sizes are held under a single code. Criteria: a separate code for each article. Cause: articles are merged in the item master. Effect: a shortage of 11.4 million so'm and a surplus of 3.1 million so'm, a net 8.3 million so'm. Recommendation: separate the codes; owner: the goods accountant; deadline: 30 days."

Tone: facts, not blame

A report describes a process, not a person. "The storekeeper is careless" cannot be proved and triggers defensiveness. "17 delivery notes were signed without counting the goods" is a fact that can be checked. A few rules help:

• put the basis next to every figure: "494 items (12%)", not simply "many";
• avoid absolute words such as "always", "never" and "completely": one exception destroys credibility;
• if a cause is a guess, say it is a guess, and state plainly what has been proved;
• record what works well too: showing what is right raises trust in the report.

Examples of replacing a judgement with a fact: instead of "record-keeping is sloppy", write "23 stock adjustment documents have an empty comment field"; instead of "there are problems with suppliers", write "9 deliveries last quarter were received short, and in 3 of them no claim was raised".

Appendices and checks before handing over

The main text stays short and detail goes into appendices: the reconciliation statement, the list of documents tested by sampling, photographs, calculation tables. Each figure refers to a working paper in the appendix, so management or an outside reviewer can find where it came from. One or two charts are enough, such as the share of differences across a few processes. Personal data about staff and detailed notes on disputed cases go into a separate appendix with restricted distribution.

Checks before handing over

1. Agree the facts with the warehouse manager: they need not accept the assessment, only confirm the figures are right.
2. Put the audited party's response in a separate section.
3. Check that totals equal the sum of their parts.
4. Add a date, version number and distribution list.

Conclusion

A good report starts with a short message, proves every finding with a figure and shows management a concrete step. OmborAudit builds its reports this way: a one-page conclusion, findings in a single pattern and full evidence in the appendices.