---
title: "Zeplin | Skills We Assign For | Azendo"
description: "Zeplin for design handover — published specifications, versioning, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/zeplin/"
---

[Skills](https://azendo.co/skills/) Design and research 

# Zeplin.

Zeplin is a design handover platform where finished designs are published for engineers with specifications, assets, style guides and version history, separate from the working design file.

## Where Zeplin fits on a long engagement.

Separating the published design from the working file is the useful property. Engineers see a deliberately released version rather than whatever state the designer left the file in, which removes the common problem of someone building a screen that was mid-revision.

That separation adds a publish step, which is a discipline rather than a cost — but a workflow where the working file and the published version routinely diverge is worse than reading the file directly.

## What an assigned team does with Zeplin.

Handover is most effective when it is not a handover at all. Designers and engineers working together through the design, rather than one publishing to the other, catches problems while they are still cheap to change.

That is why both capacities are assigned on the same agreement under [outsourced design team](https://azendo.co/services/ux-ui-design/) rather than sequenced.

## What we use Zeplin for.

* A deliberate published version Engineers building from a released state rather than a file mid-revision.
* Specifications without opening the design tool Measurements and assets available to anyone, not only licence holders.
* Version history for implemented screens What was specified when, for questions raised after the fact.

## How Zeplin capacity is assigned.

Handover tooling sits inside design capacity, with collaboration preferred over publication wherever both capacities are assigned together.

## Service lines it sits in

* [UX/UI design](https://azendo.co/services/ux-ui-design/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in design and research

* [Figma — skill we assign for](https://azendo.co/skills/figma/)
* [Storybook — skill we assign for](https://azendo.co/skills/storybook/)
* [Maze — skill we assign for](https://azendo.co/skills/maze/)
* [Hotjar — skill we assign for](https://azendo.co/skills/hotjar/)
* [usability testing — skill we assign for](https://azendo.co/skills/usability-testing/)
* [design systems — skill we assign for](https://azendo.co/skills/design-systems/)
* [design tokens — skill we assign for](https://azendo.co/skills/design-tokens/)
* [component libraries — skill we assign for](https://azendo.co/skills/component-libraries/)

## Tell us what your roadmap needs Zeplin for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)