How we work / Sample audit report
What an audit report looks like
Every audit engagement ends with a written report in this format — findings with evidence, causes rather than guesses, and a prioritized plan with honest effort estimates. You keep it whether or not we do the follow-on work.
Sample format — this is the document format you receive on a real engagement. Everything below is illustrative: the business, numbers, and findings are examples, not client data.
Prepared for: Example Store Co. (illustrative)
Scope: Theme, apps, performance
Format: 8–15 pages, written
1. Executive summary
Three sentences your non-technical stakeholders can read: what state the site is in, the one or two things causing most of the pain, and what fixing them costs. No jargon — the detail lives in the findings.
2. Findings, by severity
Each finding names the evidence (where we saw it, how we measured it), the business impact, and the effort to fix. Illustrative rows:
| Severity | Finding | Impact | Est. fix |
|---|---|---|---|
| Critical | Checkout JavaScript error on iOS Safari when a discount code is applied | A share of mobile checkouts silently fails | 2–3 hrs |
| High | Six installed apps inject scripts on every page; two are no longer used | ~1.9s of the mobile load time, paid monthly | half day |
| High | Product images served at full resolution and resized in the browser | Largest single cause of slow product pages | 1 day |
| Medium | Theme duplicated for edits 14 times; no single source of truth | Every future change is slower and riskier | process change |
3. Measurements
Performance claims come with their receipts: device profile, network setting, and the before numbers a fix will be judged against — so “faster” is a measurement, not an adjective.
4. Prioritized plan
- Phase 1 — stop the bleeding: the critical and quick-win fixes, priced as one fixed quote
- Phase 2 — structural: the changes that make future work cheaper, priced separately
- Not worth doing — the findings we'd consciously leave alone, and why
5. Repair or rebuild, answered
Where the question exists, the report answers it with numbers: what repair costs over 12 months versus a rebuild, and our recommendation with reasons. The audit fee is credited in full against either path — and the report is yours to hand to any developer.
Want documents like this about your systems?
Describe the problem in plain language — broken, slow, manual, or missing. We'll tell you honestly whether and how we can help.
- 01We reply within one business day
- 02A short call to understand the problem
- 03A written scope and fixed quote — no obligation