When Figma asked developers about working with designers for its 2025 trends report, 52% named "differences in assumptions" as their most common challenge. In a white-label Webflow project that gap is wider than usual, because the people who designed the site and the people who build it work for different companies.
This guide is for agencies that design in-house and outsource the Webflow build. It turns those assumptions into 31 written checks, with the published rules (Webflow's plans, WCAG 2.2, Core Web Vitals) that settle several of them.
Why the second round of QA happens
A second QA round is rarely about poor building. It happens when the partner had to guess, guessed reasonably, and the designer would have chosen differently. The guess stays invisible until staging review, by which time it has spread to every template that shares the component.
The UX Tools design delivery survey puts numbers on the designer's side: 90% said the design does not match the final product, 80% said developers miss design changes, and 55% said developers use the wrong design system element. The page shows no year or sample size, so read these as designers' frustration rather than a measured defect rate. Figma's report is kinder: 67% of developers and 63% of designers rate their collaboration as effective. Teams can get on well and still lose a week to rework.
| Comment on staging | What the partner was missing | Checks |
|---|---|---|
| "The hover state is wrong" | No designed states | 5, 17 |
| "This breaks on tablet" | Desktop and mobile frames only | 2, 15 |
| "The headline wraps badly" | Designed with ideal copy | 21, 24 |
| "That grey is not our grey" | Hex values instead of variables | 8, 12 |
| "Spacing feels off" | No spacing scale | 11, 13 |
| "We changed that last week" | Edits after handover, no record | 7, 29 |
| "Can the client add more?" | Static section, CMS expected | 22, 23 |
| "Is this done?" | No definition of done | 30, 31 |
Source: Octo Agency mapping of common QA comment types to the checklist below
How to use the checklist
The designer fills it in before the file is shared. Each item gets a yes, a no with a reason, or "not in scope". A "no" is fine; an unanswered item is what produces the guess.
Figma's own tools carry it. Dev Mode, on Professional, Organization and Enterprise plans, includes a Ready for dev status for frames, sections and components, annotations for notes and measurements, and Compare changes to show what moved since an earlier version. The partner needs a Full or Dev seat to use it. For white-label work, share from the agency's Figma account and keep end-client comments off shared pages. Our guide to white label Webflow development covers the commercial split; this list covers only the design handover.
Group one: file, naming and version (checks 1 to 7)
| # | Check | Why it matters |
|---|---|---|
| 1 | Build-ready frames are marked Ready for dev | Nobody builds an exploration frame |
| 2 | Each unique template has desktop, tablet and mobile frames | Tablet is where guesses break |
| 3 | Frames use auto layout, with Hug, Fill and Fixed set deliberately | Maps closely to flexbox |
| 4 | Layers are named for building, not "Frame 427" | Names become classes |
| 5 | Repeated elements are components with state variants | One component, not six copies |
| 6 | A page map marks templates versus static pages | CMS scope is right from day one |
| 7 | A named version is saved at handover | Later edits are visible |
Source: Figma Help Center, Guide to auto layout and Guide to Dev Mode; Finsweet Client-First
Check 3 is the most useful single habit. Figma's auto layout already holds what a build needs: direction, gap, padding, wrap, and minimum and maximum widths. A frame built that way says how it should flex; loose layers only show one width.
Check 4 matters most in white-label work, because class names outlive the project. Finsweet's Client-First, the most documented Webflow convention, marks custom classes with an underscore (header-primary_content) and leaves utility classes without one (padding-global). If your partner uses it, name Figma layers the same way.
Group two: tokens, type and accessibility (checks 8 to 14)
| # | Check | Rule it follows |
|---|---|---|
| 8 | Colours are variables named by role, with modes for any dark theme | Syncs to Webflow variables |
| 9 | A type scale exists as text styles, desktop and mobile | Syncs to Webflow classes |
| 10 | Web font files and a web licence for every weight | Missing fonts show first |
| 11 | Spacing follows a stated scale and base | Client-First: 16px is 1rem |
| 12 | Radius, shadow and effects are saved styles | Syncs to Webflow classes |
| 13 | Container width and gutters are written down | Sets every section's edges |
| 14 | Text contrast at least 4.5:1, controls at least 3:1 | WCAG 2.2, 1.4.3 and 1.4.11 |
Source: Webflow Updates, February 2025; Finsweet Client-First; W3C WCAG 2.2, December 2024
Webflow's February 2025 plugin relaunch split it into Layers, Variables and Styles. Variables can come from Figma libraries, in px, em or rem with a base font size you set. Styles turns Figma text and effect styles into Webflow classes, prefixed "Text" and "Effect" by default. None of that helps if the file uses raw hex values and hand-typed sizes.
Check 14 becomes a client complaint later. A pale grey caption can look refined in Figma and still fail 4.5:1. Fix it in the design, where the designer owns the decision.
Group three: responsive behaviour and states (checks 15 to 21)
This group prevents most second rounds. A frame shows one moment; the build handles every width and interaction.
| # | Check | What to write down |
|---|---|---|
| 15 | Behaviour per section at each breakpoint | What stacks, hides or reorders |
| 16 | Behaviour above the design width | Centre, stretch or scale |
| 17 | Hover, focus and active states | Visible focus (WCAG 2.4.7) |
| 18 | Tap targets at least 24 by 24 CSS pixels | WCAG 2.2, 2.5.8 |
| 19 | Interactions with trigger, timing and easing | And which are essential |
| 20 | Navigation states | Dropdowns, open mobile menu, sticky header |
| 21 | Edge content | Longest headline, missing image, one-item list |
Source: W3C WCAG 2.2, December 2024; W3C Understanding Success Criterion 2.5.8
Check 15 does not need a frame for every page at every width. One sentence per section does it: "Feature grid: three columns on desktop, two on tablet, one on mobile." That saves a review comment on every template using the grid.
Check 19 is where budgets go missing. "Smooth fade on scroll" can be a small job or a large one. Name the trigger, timing and easing, or record a short prototype clip, and mark what the agency would drop if time runs short.
Groups four and five: CMS, content and sign-off (checks 22 to 31)
| # | Check | Why it matters |
|---|---|---|
| 22 | Repeating content marked CMS or static, with a field list | Converting later means rebuilding |
| 23 | Item and Collection counts checked against the plan | CMS plan: 2,000 items, 20 Collections; Business: up to 10,000 and 40 |
| 24 | Final copy, or placeholders with an owner and date | Lorem ipsum hides wrapping |
| 25 | Full-resolution images, alt text assigned | The hero decides LCP, target 2.5 seconds |
| 26 | Form fields, validation, success and error states, destination | Error states are often skipped |
| 27 | Title, description, social image, slug and redirects per page | SEO fields are content |
| 28 | Third-party scripts listed with account owners | Embeds change layout and speed |
| 29 | One approver and one feedback document | Two reviewers means two rounds |
| 30 | "Matches the design" defined: widths, browsers, tolerance | Review has an end |
| 31 | QA record format agreed before the build | Both sides test the same list |
Source: Webflow pricing page, read 2026-10-28; web.dev, Web Vitals, updated 2024-10-31
Check 22 deserves its own conversation. Our post on Webflow CMS Collections for a B2B site sets out a five-Collection model that works as a field-list template. The usual white-label miss is three hand-placed "customer story" cards when the client expected to add a fourth.
Check 25 has a measurable target. Core Web Vitals count Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less as good, at the 75th percentile of page loads. A heavy hero video is a design decision the partner cannot fix alone.
Checks 29 to 31 are the white-label part. The partner never speaks to the end client, so the agency's reviewer is the only voice it hears. The Webflow client handover kit covers what happens after acceptance; this list ends when the agency says yes.
What the Figma to Webflow plugin will and will not do
What it carries. Since February 2025 the plugin syncs components, sections, variables and text and effect styles, and Webflow says some designs process up to 30 times faster. Since October 2024 the person syncing in Figma and the person importing in Webflow need not be online together, which suits a partner in another time zone.
What it cannot decide. Breakpoints, states, interactions, CMS structure, edge content and the definition of done sit outside the layers: checks 15 to 31. Our separate post on Figma to Webflow tools covers the plugin's documented limits.
What it changes. With the plugin, checks 3, 4, 8, 9 and 12 become required, because whatever is in the file becomes what is in Webflow.
What this means for agencies that design and outsource the build
We would expect the 31 checks to take a designer around an afternoon on a typical marketing site, mostly on checks 15, 17 and 21. That replaces the review cycle in which guesses are found, explained and rebuilt. We would rather receive a dozen honest "no" answers than a polished file with no notes, because a "no" can be scoped before the build starts.
Our four-week Webflow build plan puts the design handover at the second decision gate, which is the moment to run this list. Send it with the Figma link, agree checks 29 to 31 in writing, and hold the first staging review against the same list. Our white-label service page explains how we scope a Webflow build from an agency's Figma file.
