How to Create a
UX Audit Report.
The technical and strategic steps we use at the studio to score heuristics, annotate findings, and turn a review into a PDF deliverable stakeholders actually act on.
Scope the Audit
A clear scope prevents scope-creep and gives the report a shape. Before opening a single screen, agree on what's in and what's out.
- Define the flows under review (e.g. sign-up, checkout, onboarding)
- Set the devices and viewports you'll cover — desktop, mobile, tablet
- Choose a persona or two whose intent you'll evaluate against
- Confirm business goals so severity mapping is anchored to real outcomes
- Timebox the audit — 3, 5, or 10 days changes depth, not method
Choose Your Heuristics
A report is only as credible as its framework. Pick a well-known set of heuristics so findings are defensible and easy for stakeholders to read.
- Nielsen's 10 Usability Heuristics — the default for most audits
- WCAG 2.2 AA — for the accessibility section
- Cognitive-load principles (Hick's, Miller's, Fitts's) for flow reviews
- Brand-consistency criteria — for visual audits alongside UX
- Document which heuristic each finding maps to; readers trust structure
Capture & Annotate Screens
Every finding needs a picture. Annotated screenshots are what separate a professional report from a bulleted list.
- Screenshot at real device widths — 375, 768, 1440 as a minimum
- Number each finding on the screen (F-01, F-02) — the numbers carry into the write-up
- Use arrows, boxes, and short callouts — no essays on the image
- Keep annotation style consistent — one accent color, one type size
- Include a 'before' screen so the finding is grounded in reality
Score Severity & Impact
Stakeholders want to know what to fix first. A simple, transparent scoring rubric turns opinions into a shipping plan.
- Severity 1 — Critical: blocks a task or breaks trust
- Severity 2 — Major: adds friction, likely lost users
- Severity 3 — Minor: rough edge, fix during next iteration
- Severity 4 — Cosmetic: polish, batch with a design refresh
- Add an effort score (S/M/L) so priority is severity × effort, not gut feel
Write Findings
Each finding is a mini case: what you saw, why it matters, what to do. Write them the same way every time so the report reads like one voice.
- Observation — describe what's on screen, no interpretation yet
- Heuristic — which principle it violates and how
- Impact — the user or business consequence, in plain language
- Recommendation — a concrete change, not 'improve UX'
- Reference — link to the annotated screen and any supporting data
Prioritize Recommendations
A great audit ends with a plan, not a pile. Group recommendations into waves the team can actually schedule.
- Quick wins — high impact, low effort, ship this sprint
- Structural — needs a design pass or new component
- Strategic — belongs in a broader redesign or research cycle
- Add owners where obvious (design, engineering, content, product)
- End with a one-page action plan so leadership can act without reading the appendix
Design the PDF Document
The PDF is the artefact stakeholders will forward, print, and reference for months. Treat it like a product surface, not a slide deck.
- Cover — client, scope, dates, auditor, version
- Executive summary — top three findings and the headline recommendation
- Methodology — heuristics, viewports, scoring rubric
- Findings by section — grouped by flow or by heuristic, consistent template
- Appendix — full screen inventory, glossary, references
- Set the type at a print-safe size — 10–12pt body, generous line-height
Deliver & Present
A written report answers half of the question. A live walkthrough is where decisions actually get made.
- Send the PDF ahead of the meeting so stakeholders arrive prepared
- Walk through only the top findings — don't read the report aloud
- End with the action plan and named owners for the first wave
- Offer a follow-up review after the first fixes ship
- Version the report — v1.0 on delivery, v1.1 after review notes
Commission a UX audit
We'll follow this exact method on your product — annotated screens, scored findings, and a prioritized PDF you can hand straight to your team. Reply within two business days.