Delivery & Handoffs

Figma Handoff Checklist

Q: Should I give clients edit access to Figma files?

Usually no. View access is safer. Figma's commenting works on view access.

Q: How do I handle handoff for clients without Figma accounts?

Figma allows viewing without an account. Share view links. Alternatively, export to PDF.

Q: What if the client makes changes after handoff?

Use version history or duplicate the file before handoff. Changes should go through change request process.

Q: How detailed should specs be?

Depends on your dev team. Ask what they prefer—some need Dev Mode, others need explicit callouts.

Q: When should I do the handoff walkthrough?

Same day or day after sharing. Schedule 15-30 min for a screen share walkthrough.

A handoff checklist for design teams—files, naming, tokens, exports, specs, prototype links, and what clients/devs need to move fast. Stop answering "where is X?" questions.

What You'll Get

Pre-handoff checklist — File hygiene, component cleanup, naming
Handoff package table — What to include in every handoff
Export specs guide — Formats, sizes, naming conventions
Handoff QA section — Final checks before sharing

Download the Checklist

Get the complete Figma handoff checklist.

Download PDF

No email required. Free to use and share.

File Hygiene Checklist

Pages are named clearly — No "Page 1" or "Untitled"Frames are named logically — Match page names or sectionsHidden/draft work is on a separate page — Not mixed with finalsNo random orphan elements — Everything is in framesLayers are named — No "Rectangle 47" on important elementsAuto-layout is used consistently — Makes responsive intent clear

Component & Style Checklist

All components are published — Or included in handoff fileComponents have clear names — Button/Primary/Large, not "Component 1"Variants are complete — States, sizes, breakpointsColor styles are defined — Named logically (primary, secondary, etc.)Text styles are defined — H1, H2, Body, etc.Effects are styled — Shadows, blurs as reusable effects

Handoff Package Table

Item	Format	Location
Figma file link	View/Edit access	Handoff doc
Prototype link	Figma prototype URL	Handoff doc
Design tokens	JSON, CSS variables, or Figma tokens	GitHub or attached file
Asset exports	PNG, SVG, WebP as needed	Google Drive/Client portal
Icon set	SVG, organized folder	Attached or linked
Font files	OTF/TTF or Google Fonts links	Attached or linked
Specs/redlines	In Figma (Dev Mode) or annotated	Same file, specs page
Accessibility notes	Doc or Figma annotations	Handoff doc or specs page

Export Specs Guide

Images (photos, complex graphics)

PNG or WebP, @1x and @2x, max width 1920px unless specified

Icons

SVG, strokes outlined, consistent viewbox (24x24 typical)

Logos

SVG + PNG fallback, RGB for web, CMYK for print

Naming convention

icon-name.svg, [email protected], logo-primary-dark.svg

Handoff QA Checklist

Before sharing the handoff package:

All links work (Figma, prototype, assets)Recipient has correct access levelAll exported assets match what's in the designResponsive behavior is clear (documented or obvious)Interaction specs are complete (hover, click, etc.)Edge cases are addressed (empty states, errors, loading)

Common Mistakes & Tips

Handing off without a walkthrough

Files alone aren't enough. Schedule 15-30 minutes to walk devs/clients through the design. Answer questions upfront.

Forgetting responsive specs

Desktop looks great, but how does it behave on mobile? Document breakpoints or design multiple sizes.

Unlicensed fonts

Devs can't use fonts they don't have licenses for. Include font files or confirm Google Fonts/web-safe options.

Mixing final and draft versions

Clearly mark what's approved/final vs exploration. Move drafts to a separate page or archive.

How to Run This in Corcava

Attach Figma links to tasks — Design tasks link directly to the file
Share handoff package via client portal — Clients access everything in one place
Create handoff as a milestone — Track handoff as part of project progress

Frequently Asked Questions

Should I give clients edit access to Figma files?

Usually no. View access is safer—prevents accidental changes. If they need to comment, Figma's commenting works on view access. Only give edit to clients who genuinely need to make changes.

How do I handle handoff for clients without Figma accounts?

Figma allows viewing without an account. Share view links. For those who really can't use Figma, export to PDF or use a tool like Zeplin that can provide specs outside Figma.

What if the client makes changes after handoff?

Versioning is critical. Use Figma's version history, or duplicate the file before handoff as a "frozen" snapshot. Any changes after handoff should go through your change request process.

How detailed should specs be?

Depends on your dev team. Experienced devs may just need access to Figma Dev Mode. Less technical clients or offshore teams may need more explicit callouts. Ask what they prefer.

Should I include unused explorations?

No. Handoff = final work only. Put explorations on a separate "Archive" or "Exploration" page. Keeps the handoff clean and prevents confusion about what's approved.

When should I do the handoff walkthrough?

Same day or day after sharing the package. While it's fresh. Schedule 15-30 min for a screen share where you walk through the file, explain decisions, and answer questions.