Fill in these first
- Feature and screen: [e.g. the checkout address step on the mobile web app]
- Design specification: [paste or describe: spacing values, font sizes and weights, colours as tokens or hex codes, component names]
- What was built: [paste notes, measurements from browser tools, or a description of screenshots]
- States designed: [e.g. default, focus, error, loading, empty, disabled]
- Breakpoints to check: [e.g. 360px, 768px, 1280px]
- Copy approved: [paste the final text for labels, buttons and messages]
- Release date: [date]
Task
Find every difference between the design and the build and decide what must be fixed before release.
Output format
- Verdict in two sentences: ready, ready with fixes, or not ready.
- | Area | Expected | Actual | Breakpoint | Severity: blocker, major, minor, polish |
- Missing or broken states, each with the steps to reach it.
- Copy differences: | Location | Approved text | Built text |
- Accessibility checks noticed during review: focus order, contrast, touch target size, labels on inputs.
- Fix list for developers in priority order, grouped by component.
Severity guide
- Blocker: wrong behaviour, broken layout at a listed breakpoint, unreadable text, missing error state.
- Major: wrong component, wrong colour token, copy that changes meaning.
- Minor: spacing or size off by more than 4px, wrong font weight.
- Polish: differences under 4px that nobody will notice in use.
Rules
- Compare only against the specification given; where it is silent, say "not specified" instead of guessing.
- Report each difference once, in the component where it starts.
- Do not ask for pixel-perfect matches on polish items before a release date.






