Free checklist template

Design handoff checklist

A good handoff answers developers’ questions before they ask them. Run through this checklist before you mark a design ready to build, then walk through it together in a short handoff meeting.

Preview of the design handoff checklist

Design handoff checklist

DESIGN HANDOFF CHECKLIST: [Project or feature name]

1. Screens and flows
☐ Final designs approved and marked ready to build
☐ Every screen in the flow included, with the order or a prototype link
☐ Old and exploratory versions removed or clearly archived

2. States
☐ Hover, focus, pressed and disabled states for interactive elements
☐ Empty, loading, error and success states
☐ Long text, missing images and other edge cases

3. Responsive layouts
☐ A layout for each breakpoint: [mobile / tablet / desktop widths]
☐ Notes on what changes between breakpoints

4. Styles and components
☐ Colours, type, spacing and corner radius use named styles or tokens
☐ Components match the design system, or new ones are documented

5. Assets
☐ Icons and illustrations exported, as SVG where possible
☐ Images exported at the sizes needed (for example 1× and 2×)
☐ Fonts named, with licences that cover web or app use

6. Content
☐ Final copy in place, not placeholder text
☐ Button labels, error messages, links and alt text written

7. Behaviour and accessibility
☐ Animations and transitions described (what moves, duration, easing)
☐ Text and background colours meet WCAG contrast
☐ Focus order and keyboard behaviour noted for custom components

8. Open questions
☐ Known gaps listed, each with an owner and a date

Replace everything in [square brackets]. Free to use and adapt; no attribution needed.

Tips for using it

Hand off in person

A short walkthrough with the developers catches more questions than any document. Record it for anyone who can’t attend.

Design the unhappy paths

Empty, loading and error states are easy to forget. Designing them upfront saves guesswork during the build.

Review the build against the design

Once it’s built, compare screenshots of the build with the design and pin each difference as a comment, so fixes are specific.

Frequently asked questions

What should a design handoff include?+

Final approved screens, every state, responsive layouts, named styles or tokens, exported assets, fonts, final copy, interaction notes and accessibility notes.

How do I make handoff smoother?+

Use named styles and components, design every state, walk the developers through it, and keep questions in one place.

How do I check the build matches the design?+

Take screenshots of the built pages, compare them with the designs side by side, and pin each difference as a comment for the developer.

Collect the feedback in one place

Capture any public web page in full and collect pinned comments on it. Clients comment with a link, no account needed.

See website feedback

All templates →