# Marketing audit report template

BEIZ Studio · 24 October 2026

An educational working template. This is not a client report, a completed audit or a promise of results. The example and blank fields help you describe evidence, limitations and implementation tasks.

Guide: https://beizstudio.com/en/journal/useful-audit/
Service: https://beizstudio.com/en/services/audit/

## 1. Question and scope

- Business and pages/accounts being reviewed:
- Main audit question:
- Geography, audience and languages:
- Data period:
- Review date:
- Included scope:
- Not reviewed:
- Business contact who can explain the process:

## 2. Sources and limitations

For each source, complete:

- Name and link with suitable access:
- Period covered and export date:
- Definition of enquiry / qualified enquiry / sale:
- Completeness and duplicate checks:
- Missing evidence and limitations:

Do not include personal passwords, keys, verification codes or identifiable conversations. Mark unavailable sources explicitly. Missing analytics is not evidence of missing enquiries.

## 3. Decision summary

- What was confirmed:
- What remains a hypothesis:
- What evidence is needed:
- What to do first and why:
- What can wait:

## 4. Finding card

Copy this card for each distinct issue or hypothesis.

- ID and title:
- Question answered:
- Observation:
- Source, period and reproduction steps:
- Status: confirmed / hypothesis / insufficient evidence:
- Confirmed consequence:
- Possible consequence requiring further investigation:
- Recommendation:
- Reason for priority:
- Dependencies:
- Owner:
- Effort estimate and who confirmed it:
- Acceptance check:
- Retest date and result:

### Completed educational example

- ID: DEMO-01.
- Question: does the “lead” event mean an accepted enquiry?
- Observation: in an illustrative test environment, the event fires when the empty form button is clicked, before the enquiry is saved.
- Basis: a repeatable empty-form test, event log and absence of a saved enquiry. This describes a training scenario; no real measurements are attached.
- Finding: such an event would describe a click rather than an accepted enquiry.
- Unknown: real enquiry count, reporting distortion and impact on sales.
- Recommendation: separate the click from confirmed receipt of the enquiry.
- Priority: fix the event definition before comparing cost per confirmed enquiry.
- Owner: the form and analytics implementer, assigned by the team.
- Acceptance: an empty form and a failed save create no successful-lead event; a correctly accepted request creates one event.

## 5. Action plan

For each task: finding ID → action → owner → dependency → estimate → agreed date → check → status.

Keep fixes separate from experiments. Do not set deadlines without an estimate from the person doing the work. For a 90-day plan, arrange agreed tasks into stages and identify when new evidence will trigger a review.

## 6. Result check

- What changed and when:
- How the technical fix was verified:
- Metric definition used:
- Comparable periods being assessed:
- Other changes during that time:
- What can and cannot yet be concluded:

A lower cost per click, higher reach or a button click does not by itself establish higher sales. Use accepted enquiries and their subsequent statuses where evidence is available.