UX audit report and prioritized-backlog template

What is in the template? A ten-page PDF report frame for a bounded UX audit, plus a CSV backlog that imports into Jira or Linear. Pages 2 to 7 are blank to fill in. Pages 8 to 10 show a complete worked example. Cover with product, dates, client, reviewer and report version. Scope and method: goal, tasks, roles, devices and widths, the build reviewed and what is out of scope. It also records methods, a baseline and limits. Ratings: written definitions for four severity levels, effort sizes, confidence levels and the priority rule. Findings ledger: ID, flow or step, finding, evidence, severity, effort, confidence and owner. Finding detail cards for critical and major issues: steps to reproduce, the heuristic or WCAG criterion, why this severity, the recommendation and acceptance criteria. Prioritized backlog in Now, Next, Later and Validate-first tables. Close-out: what passed, what was not tested, a re-test plan and sign-off lines. Worked example on three pages: scope, ledger and backlog from our own sample audit. Who is it for? Product managers, designers and founders who run their own review, or who want to hold an outside auditor to a clear format. It also suits agencies that need a consistent report across clients. It assumes you can walk the product yourself and take screenshots. Analytics and usability sessions make the findings stronger, and the template has fields for both, but you can start without them. How do you use it? Fill in the scope page first, and confirm it with the product owner before you review anything. Walk each task at a phone width and a desktop width. Try the error paths, not only the happy path. Log one ledger row per problem, with evidence someone else could reproduce: what you did, the browser, the width and the date. Rate severity from the user’s side, then ask the team that will do the work for effort. Apply the priority rule on page 3. Merge shared causes, send critical issues and WCAG 2.2 AA failures to Now, then score the rest. Write one acceptance criterion per backlog item that a tester can check, then export the backlog as CSV. The full method behind these steps is in our guides on how a UX audit works and how to prioritize UX audit findings. What does the worked example show? The last three pages hold a sample audit of our own project brief and UX audit page, run on November 11, 2026. It is labeled as a sample of our own site, not client work. It lists 14 findings, from a mobile button that erases every answer to a privacy link with a contrast ratio of 1.53 to 1. Each finding carries its evidence, severity, effort, confidence and owner. The backlog page shows two findings merged into one item because they share a cause. It also shows how the accessibility gate lifts an item that scored low on its own. How does the CSV backlog work? The CSV has one row per finding and 19 columns. Beyond the ledger columns, it holds the evidence type, WCAG criterion, score and bucket. It also has the recommendation, acceptance criteria, status and date found. A backlog_item column groups findings that merge into one ticket. Download the backlog CSV (UTF-8, 14 sample rows) Delete the sample rows, keep the header, and add your own findings. Most trackers map the columns on import. Map the finding to the title, the acceptance criteria to the description, and the owner to a label or team. What does the template not do? It does not make a review into a usability study. Findings without participants are observed or predicted, and the template asks you to say so. It is not a WCAG conformance report. The accessibility fields cover the flows in scope only. The priority rule is a convention for ordering work. Change the weights if your team prefers others, and write the change on page 3. Auditing a SaaS product? Pair this template with the SaaS UX audit checklist, which gives you 64 testable checks to produce the findings. If you would rather have the audit done for you, see our UX audit service. For a fix list that needs design work, UI/UX design and SaaS product design pick up from the backlog.