What is a design QA checklist?
A design QA checklist is the final review list used before implementation or release. It catches layout drift, missing states, asset mistakes, overflow, tracking gaps, and unresolved handoff decisions.
Check each release-readiness item as you review a page, dashboard, onboarding step, or product flow. Progress stays on this device automatically, so you can leave for a fix and continue the same review later—without an account or setup form.
Design QA is finished when each discrepancy is either fixed, assigned, or explicitly accepted as an intentional deviation. Anything else becomes release risk.
Checking saved progress on this device…
A design QA session should create a short release log that explains what changed, what remains risky, and what needs measurement after launch.
Visible layout, state, copy, accessibility, or tracking gaps that block release.
Known deviations that are acceptable for this release and owned for follow-up.
Events, funnel checks, or session evidence needed after production traffic arrives.
A design QA checklist is the final review list used before implementation or release. It catches layout drift, missing states, asset mistakes, overflow, tracking gaps, and unresolved handoff decisions.
One owner should run the checklist, but design, engineering, and growth each own part of the outcome. The checklist only works when every issue has an owner and a release decision.
UX review asks whether users understand and complete the task. Design QA asks whether the approved design was implemented accurately and safely across states, breakpoints, assets, and analytics.