Figma handover checklist for agencies
What agencies should check before assuming design work has been properly handed over from a freelancer or supplier.
Figma handover is one of the easiest places for teams to confuse visibility with control. A file can be shared, visible, and even editable for now, while the real dependency still sits in the wrong workspace.
Resource record
Figma source file
Open request
Waiting on design source transfer
The agency has exports, but the editable system still sits in a freelancer-managed workspace.
Checklist
- ✓ Editable source file is in the agency or client workspace
- ✓ Key pages and flows are still present, not just exports or screenshots
- ✓ Component libraries and variables are available, not private to the outgoing designer
- ✓ Prototype links still point to the maintained source
- ✓ Naming and page structure make sense to the next team
Looks fine, but isn’t
The agency has a share link, but edit rights depend on a freelancer workspace.
Looks fine, but isn’t
Exports were provided, but the component system was never transferred.
Looks fine, but isn’t
The final file is visible, but the real working branch sits somewhere else.
Design handover can look tidy while leaving the agency unable to make the next real change.
That usually appears later, when someone needs the component source, the variables, or the underlying structure rather than just a screenshot.
How Custody helps
Custody helps agencies turn handover into a visible record of what is missing, what is still externally held, and what has actually been verified.