Skip to content
Audits

What does a website or app audit report contain? An annotated example

What a good audit report looks like: an executive summary, findings ranked by severity, evidence, a costed action plan. An annotated template, a sample finding and the questions to ask before ordering an audit.

By Damien Ladurelle · Updated · 6 min read

Contents
  1. The template structure
  2. Severity levels
  3. A sample finding, as it appears in the report
  4. The action plan
  5. Questions to ask before ordering an audit
In short

A good audit report opens with a summary management can read, then details each finding with its severity, evidence, impact and recommended fix, and ends with a prioritized, costed action plan. It also says what works well. A report that is just a list of alerts produced by an automated tool does not help you decide.

Before ordering an audit, the right question is not only “what will it check?” but “what will I receive and what can I do with it?”. A useful report lets you decide and act. Here is the structure I use, section by section, with a sample finding.

The template structure

Section Content For
1. Summary The overall state in one page, the 3 to 5 priority points, the recommendation Management
2. Scope What was audited, how, with what access, what was not Everyone
3. What works well The strong points, not to be touched Management and team
4. Detailed findings One finding per sheet, ranked by severity Technical team
5. Action plan Ordered fixes, estimated effort, cost Management and team
6. Appendices Measurements, inventories (plugins, dependencies, access), screenshots Technical team

The “Scope” section is often overlooked. Yet it is essential: an audit only vouches for what it examined.

Severity levels

Level Meaning Suggested timeline
Critical Exploitable now, with a strong impact Immediately
High Real risk, under narrower conditions Within a few weeks
Medium A weakness that worsens other risks or slows development To schedule
Low A best practice not followed When convenient

A sample finding, as it appears in the report

Finding 4 — Severity: high Title: a form plugin is no longer maintained. Evidence: the installed version has had no update for more than two years; a public vulnerability affects this version. Impact: an attacker could upload files to the server through the contact form. Fix: replace the plugin with a maintained alternative and rebuild the existing forms. Estimated effort: half a day, including backup and testing.

Every finding follows the same model: you understand the problem, you can verify it, you know what to do and what it costs.

The action plan

The plan turns findings into ordered work. It groups fixes that go together, shows the effort and the suggested order, and separates what can be fixed in-house from what needs a specialist. In my full audit, it is costed and presented in a 2-hour debrief, followed by 30 days of support to answer questions while the fixes are made.

Questions to ask before ordering an audit

  1. What is included and excluded? Code, server, database, performance, accessibility?
  2. Is the code read, or is only the outside of the site tested?
  3. Does the report rank the findings and cost the fixes?
  4. Is there a debrief and follow-up after the report?
  5. What happens if the audit uncovers an emergency while it is running? (I tell you immediately, without waiting for the report.)

My two options are detailed on the technical audit page: express at $650 (€589)excl. VAT with a report and optimization plan, full at $2,200 (€1,990)excl. VAT with a detailed report, costed plan, debrief and support. To choose the right type of audit for your situation, the Audits section lists them all.

Frequently asked questions

Can I understand the report without being a developer?

The summary and the action plan should be understandable: they are there to help you decide. The detailed findings are for the team that will fix them, with the technical details they need. The two levels are kept separate in the report.

Can I share the report with my provider?

Yes, that is its normal use. The report is yours: you can hand it to your team, your current provider or a new one to carry out the fixes.

What is a free audit from an online tool worth?

It gives hints, useful for a first look. But an automated tool does not read the code, does not test permissions role by role and does not know what matters for your business. It often produces many alerts without ranking them.

Is the report confidential?

Yes. It describes the weaknesses of your site or application: it should only go to the people who need it. I never publish the content of an audit; the examples on this page are generic.

Not sure about your project?

Let’s talk for 30 minutes: I’ll tell you honestly which option I would choose in your place.

Appearance
Book a 30-minute call Version française