What This Template Is For
A UX audit is a systematic evaluation of a product's usability against established heuristics. It identifies friction points, inconsistencies, and usability failures before users encounter them. Unlike usability testing, which observes real users, a heuristic audit is an expert review. One evaluator with this checklist can surface 40-60% of usability issues in a few hours.
This template uses Nielsen's 10 usability heuristics as the evaluation framework, adds severity ratings (cosmetic through catastrophic), and structures findings so engineering and design can act on them immediately. Each finding links evidence (screenshots, recordings) to a specific heuristic violation, a severity level, and a recommended fix.
Most teams skip audits because they feel time-consuming. They are not. A focused audit of a single flow takes 2-4 hours and typically surfaces 15-30 issues. The alternative is discovering those issues through user complaints, support tickets, and churn. Teams doing structured product discovery use heuristic audits as a fast, low-cost way to identify problems before investing in more expensive research methods. For AI-assisted evaluation, the AI UX Audit tool can accelerate parts of this process.
How to Use This Template
- Define the scope. Pick a specific flow, feature, or page set to audit. Trying to audit an entire product at once produces shallow findings. One flow at a time.
- Walk through the flow as each major user type. Note every point where a heuristic is violated. Take screenshots and annotate them.
- Rate each finding by severity (0-4 scale). Severity determines priority, not your personal opinion about design taste.
- Write a concrete recommendation for each finding. "Fix the error message" is not actionable. "Replace 'Error 403' with 'You don't have permission to view this page. Ask your admin to grant access.'" is.
- Sort findings by severity. Present catastrophic and major issues first. Cosmetic issues go at the bottom.
- Share with design and engineering in a review session. Walk through the top 5 findings together. Let the team discuss solutions rather than dictating them.
The Template
Audit Metadata
| Field | Details |
|---|---|
| Product / Feature | [Name of product or feature being audited] |
| Auditor | [Your name] |
| Date | [Date] |
| Scope | [Specific flow, pages, or feature area] |
| User types evaluated | [e.g., New user, Admin, Free tier, Power user] |
| Device / Browser | [e.g., Chrome 122 / macOS, Safari / iOS 17] |
Severity Scale
| Rating | Label | Definition |
|---|---|---|
| 0 | Not a problem | No usability issue identified |
| 1 | Cosmetic | Minor visual inconsistency. Fix only if time permits |
| 2 | Minor | Users can work around it, but it causes friction |
| 3 | Major | Significant usability issue. Users struggle or fail on first attempt |
| 4 | Catastrophic | Users cannot complete the task. Must fix before release |
Heuristic Evaluation Checklist
H1. Visibility of System Status
- ☐ System provides feedback within 1 second for user actions
- ☐ Loading states are visible for operations over 1 second
- ☐ Progress indicators show for multi-step processes
- ☐ Current location is clear (breadcrumbs, active nav state, page title)
- ☐ Success and failure states are explicitly communicated
H2. Match Between System and Real World
- ☐ Language uses user terminology, not internal jargon
- ☐ Icons are recognizable without labels
- ☐ Information is ordered logically (not by database schema)
- ☐ Metaphors match user mental models
- ☐ Date, currency, and number formats match user locale
H3. User Control and Freedom
- ☐ Undo is available for destructive actions
- ☐ Users can cancel in-progress operations
- ☐ Back/escape returns to a predictable state
- ☐ Modal dialogs can be dismissed
- ☐ Users can edit or delete their own content
H4. Consistency and Standards
- ☐ Same action uses same label across the product
- ☐ Button styles match their importance (primary, secondary, destructive)
- ☐ Navigation is consistent across all pages
- ☐ Form patterns are consistent (validation, labels, placeholders)
- ☐ Error message format is consistent
H5. Error Prevention
- ☐ Destructive actions require confirmation
- ☐ Form inputs validate before submission
- ☐ Constraints are communicated before the user hits them
- ☐ Default values reduce the chance of incorrect input
- ☐ Inline validation catches errors as the user types
H6. Recognition Rather Than Recall
- ☐ Recently used items are accessible
- ☐ Labels and instructions are visible (not hidden behind tooltips)
- ☐ Search suggestions and autocomplete are available
- ☐ Users do not need to remember information between screens
- ☐ Help is contextual and in-place
H7. Flexibility and Efficiency of Use
- ☐ Keyboard shortcuts exist for frequent actions
- ☐ Power users can customize or accelerate workflows
- ☐ Bulk actions are available for repetitive tasks
- ☐ Filters and sorting are available on data-heavy screens
- ☐ Frequently used features are accessible within 2 clicks
H8. Aesthetic and Minimalist Design
- ☐ Each screen shows only relevant information
- ☐ Visual hierarchy guides the eye to primary actions
- ☐ Color and contrast are used purposefully
- ☐ No decorative elements that compete with functional content
- ☐ White space is used to group related elements
H9. Help Users Recognize, Diagnose, and Recover from Errors
- ☐ Error messages state the problem in plain language
- ☐ Error messages suggest a specific corrective action
- ☐ Errors are shown near the field that caused them
- ☐ System errors do not expose technical details to users
- ☐ Empty states include guidance on what to do next
H10. Help and Documentation
- ☐ Onboarding or first-run guidance exists for new users
- ☐ Contextual help is available for complex features
- ☐ Documentation is searchable
- ☐ FAQ or help center is accessible from within the product
- ☐ Tooltip text is concise and actionable
Findings Log
| # | Heuristic | Severity | Finding | Screenshot | Recommendation |
|---|---|---|---|---|---|
| 1 | [H1-H10] | [0-4] | [What is wrong] | [Link] | [How to fix] |
| 2 | [H1-H10] | [0-4] | [What is wrong] | [Link] | [How to fix] |
| 3 | [H1-H10] | [0-4] | [What is wrong] | [Link] | [How to fix] |
Summary and Prioritization
Total findings: [Count]
By severity: Catastrophic: [n] | Major: [n] | Minor: [n] | Cosmetic: [n]
Top 5 priority fixes:
- [Finding # and one-line summary]
- [Finding # and one-line summary]
- [Finding # and one-line summary]
- [Finding # and one-line summary]
- [Finding # and one-line summary]
Recommended next steps:
- ☐ Fix all severity 4 issues before next release
- ☐ Schedule severity 3 issues for the next sprint
- ☐ Group severity 2 issues into a UX debt backlog
- ☐ Log severity 1 issues for future polish passes
Filled Example: SaaS Dashboard Settings Flow
Audit Metadata
| Field | Details |
|---|---|
| Product / Feature | Acme Analytics: Dashboard Settings |
| Auditor | Sarah Kim |
| Date | March 2026 |
| Scope | Settings page, notification preferences, team management |
| User types evaluated | Admin user, Member user |
| Device / Browser | Chrome 122 / macOS Sonoma |
Findings Log
| # | Heuristic | Severity | Finding | Recommendation |
|---|---|---|---|---|
| 1 | H9 | 4 | Deleting a team member shows "Error: null" if the member has active dashboards. No recovery path. | Show "This member owns 3 dashboards. Reassign or delete them first." with a link to the dashboards. |
| 2 | H3 | 3 | No undo after removing a notification rule. Users must recreate rules from scratch. | Add a 10-second undo toast after deletion. |
| 3 | H4 | 3 | "Save" button is blue on the profile page but green on the notification page. Inconsistent primary action styling. | Standardize primary button color across all settings pages. |
| 4 | H1 | 2 | Saving notification preferences shows no confirmation. Users click "Save" repeatedly, unsure if it worked. | Add a success toast: "Notification preferences saved." |
| 5 | H6 | 2 | Timezone selector shows 400+ entries with no search. Users scroll for 30+ seconds to find their timezone. | Add search/autocomplete to the timezone dropdown. Detect browser timezone as default. |
| 6 | H8 | 1 | The "Danger Zone" section for account deletion has a red background that draws attention away from routine settings above it. | Reduce visual weight. Use a red border instead of a red background. |
Summary
Total findings: 6
By severity: Catastrophic: 1 | Major: 2 | Minor: 2 | Cosmetic: 1
Top 3 priority fixes:
- Finding #1: Error on team member deletion (blocks admin workflow)
- Finding #2: No undo for notification rule deletion (causes user frustration and support tickets)
- Finding #3: Inconsistent button styling (erodes trust in UI predictability)
Key Takeaways
- Focus on one flow at a time. Depth beats breadth in UX audits
- Severity ratings, not personal taste, determine fix priority
- Include evidence (screenshots, recordings) for every finding
- Write actionable recommendations, not vague observations
- Fix catastrophic issues immediately. Batch minor issues into a UX debt backlog
About This Template
Created by: Tim Adair
Last Updated: 3/4/2026
Version: 1.0.0
License: Free for personal and commercial use