Client delivery

The logo handoff checklist that prevents version chaos

A polished presentation is not a complete handoff. The receiving team needs authoritative files, predictable names, production-ready exports and enough context to choose the right asset.

OutcomeA delivery package that another designer or developer can use without guessing.

Workflow guide. The private comparison tool accepts one master and up to 60 selected reference images from files, a folder or ZIP. Optional saved fingerprints stay in your browser. Export JSON, CSV or a print review; no files are changed or deleted.

Authority and structure

  • One approved primary master is clearly identified.
  • Every retained lockup and colorway has a documented role.
  • Experiments, rejected concepts and obsolete versions are outside the delivery folder.
  • Folders separate source, web, print, icons and social outputs.

Vector and raster files

  • SVG files use an appropriate viewBox and contain no unintended clipping.
  • Raster exports include transparent and intentional-background versions.
  • Pixel dimensions match the stated use rather than arbitrary large exports.
  • Small-size versions have been inspected at realistic display sizes.

Color and accessibility context

  • HEX, RGB, CMYK or spot values match the current brand guide.
  • Dark and light surface behavior is demonstrated.
  • Text and UI colors are checked under the relevant accessibility rules.
  • No claim is made that a logotype itself receives automatic WCAG approval.

Delivery evidence

  • A file inventory and version date are included.
  • Duplicate and stale-file decisions are documented.
  • Favicon, app-icon and social packages use the approved master.
  • Rights, fonts and third-party dependencies are clearly disclosed.

Ask the recipient to confirm that the package opens in their actual workflow. Handoff quality is measured by successful reuse, not by the number of exported files.

Optional usage measurement

Help us understand which catalogues and file formats are useful. We do not record search text, uploaded images, names, email addresses or IP addresses in usage events. Events expire after 30 days. Local, staff and recognised bot traffic is separate.

Measurement is off until you opt in. Downloads have separate operational delivery counts.