FIGMA-TO-WORDPRESS DESIGN HANDOFF WORKSHEET
WP Growth Labs | Version 1 | 18 October 2026

Use this record before scoping and during staging review. Copy the repeatable sections.
Status options: confirmed / pending / not applicable.
Test results start as NOT TESTED. Record an actual result only after running the check.
This is a planning aid, not a quote, agreement, completed test or client case study.
Keep passwords, licence keys, API keys and personal customer data out of this document.

1. APPROVED REFERENCE
Project: [answer]
Figma file and included frame links: [answer]
Approved version/date: [answer]
Design approver: [answer]
Developer can inspect required layers and obtain permitted assets: [status/evidence]
Copy and mobile design status: [answer]
How later design changes will be recorded and scoped: [answer]

2. TEMPLATE RECORD — repeat per unique layout
Template name/purpose: [answer]
Reference frame(s): [answer]
Pages using it and approximate count: [answer]
Required fields/content source: [answer]
Reusable components: [answer]
Exceptions: [answer]
Owner/status/open decision: [answer]

3. COMPONENT AND RESPONSIVE RECORD — repeat per component
Name and reference frames: [answer]
Variants and states: [answer]
Narrow/middle/wide layout rules: [answer]
Reading and stacking order: [answer]
Long text and missing optional content: [answer]
Image shape/crop: [answer]
Navigation/keyboard behaviour where relevant: [answer]
Motion/reduced-motion behaviour where included: [answer]
Undecided rule, owner and review point: [answer]

ILLUSTRATIVE PROMPT — not a tested design:
A row has three service cards on desktop and one column on a phone.
Agree the middle-width layout, reading order, a three-line title,
the image crop and the behaviour when only two cards exist.
There is no universal breakpoint or assumed completed result in this example.

4. INTERACTION RECORD — repeat per menu/form/feature
Component and trigger: [answer]
Default/open/closed/loading states: [answer]
Expected successful outcome: [answer]
Validation and failure/recovery states: [answer]
Keyboard focus/dismissal: [answer]
For forms: required fields and authorised destination: [answer]
Integration dependency and responsible owner: [answer]
Actual implementation result: NOT TESTED

5. ASSETS AND EDITING
Asset/font/text source and supplier: [answer]
Usage permission and renewal responsibility where applicable: [answer]
Image crop/meaningful or decorative use: [answer]
Everyday editor task: [answer]
Page-only or shared content: [answer]
Required/optional fields and empty-field behaviour: [answer]
Agreed WordPress approach and dependencies: [answer]
Actual editor test: NOT TESTED

6. ACCEPTANCE RECORD — repeat per check
Reference frame/version: [answer]
Staging page/component: [answer]
Screen width/device/input method: [answer]
Steps: [answer]
Expected behaviour: [answer]
Actual result: NOT TESTED
Evidence reference: [answer]
Issue owner/retest action: [answer]
Reviewer/approval/date: [answer]

7. OPEN DECISIONS AND SCOPE
Decision/dependency: [answer]
Owner: [answer]
Next action/review point: [answer]
Effect on scope/timing to discuss: [answer]
Included deliverables and exclusions: [answer]
Review rounds and launch approver: [answer]
Build versus recurring costs to confirm in the proposal: [answer]

Related resources:
https://wpgrowthlabs.com/services/figma-to-wordpress/
https://wpgrowthlabs.com/blog/a-clear-wordpress-brief/
https://wpgrowthlabs.com/blog/wordpress-website-handover-checklist/