On time, or a full refund.How the guarantee works

Figma handoff checklist

The 78 checks we run on a design file before we build it. Run them first and you’ll get fewer questions and fewer QA rounds, and the build will match your design.

Jump to the checklist
  • Free · no login
  • 78 checks in 14 groups
  • Works with any developer
  • Prints to a clean PDF

Why handoffs go wrong.

In our experience, most build problems start before anyone writes a line of code. This is the list we use to catch them there.

  • A missing mobile frame becomes a developer’s guess.
  • An undefined hover or error state means extra QA rounds.
  • Lorem ipsum hides a layout that breaks when the real headline arrives.
  • A font with no web licence holds up the launch.

Written for Figma, our default. Almost all of it applies to Adobe XD and layered PSD files too, which we also build from.

File and page set-up

So the developer opens the file and knows what is final.

Frames and breakpoints

What the design does at every width, including the ones you didn’t draw.

Styles and variables

Your design tokens become the site’s CSS variables, so name them.

Components and variants

Anything used twice is built once, so it has to be one thing in the file.

Auto layout and spacing

Auto layout shows the developer how you meant things to space and resize.

Typography and font licences

The most common reason a launch waits is a font nobody has a web licence for.

Interactive states

The states nobody designed are the ones that come back in QA.

Content

Layouts are approved with placeholder text and break with the real thing.

Images, icons and export

What the developer can export from the file, and what has to be sent.

Motion and interactions

Motion can’t be read off a static frame, so write it down. Skip this group if the site has no animation, sliders or carousels.

CMS and dynamic content

What your client will edit after launch, and what stays fixed. Skip this group for a one-page site with no editable content.

Forms and integrations

A form is a design, a set of rules and a destination. The file usually has only the first.

Accessibility

Cheap to get right in the design, slow to fix in the build.

SEO and page structure

The basics to settle before the build starts, while they’re still cheap to change.

Sign-off

The last two things before the file goes to the developer.

Want this handled for you?

When you send us a design file, we check it for missing states, breakpoints and edge cases, and send you a short list of questions before the build starts. We’d rather ask then than guess later.

What’s in the file, we build as designed. Anything that differs from your approved design is a defect, and defects are fixed free.

Checklist questions.

What designers ask before they hand a file over.

All resources

It’s written for Figma, because that’s what most agencies send us. Almost everything applies to Adobe XD and layered PSD files too. Where an item names a Figma feature, such as variables or auto layout, do the nearest thing your tool offers and write a note on the cover page.

Groups A to I apply to every project, and so do forms, accessibility and SEO. Motion and CMS only come in when the site has animation or content your client will edit. Each of those groups says when you can skip it.

No. We check every design file ourselves before we build, and send you a short list of questions. Running the checklist first means a shorter list.

Yes. Nothing in it is specific to us. It’s the handoff any developer needs, whoever builds the site.

Yes. Share the page, or print it: the print button gives you a clean black and white copy you can save as a PDF.

Yes, but only in this browser. The ticks are saved on your device and never sent to us; the reset button clears them. There’s no login and no email form.

Send us the file. We’ll check it, then build it as designed, under your agency’s name.

Next, you send a short brief and we reply with a fixed price and a delivery date in writing. You pay nothing until you sign the order.