A finished design file doesn’t explain every decision needed to make the object. The next person may still need the units, material, quantity, intended size, and a clear answer to which version is ready to use.
Put those decisions beside the files in a short handoff note. It should work for someone opening the folder without the conversation that produced it, including you returning to the project later.
Start with one clearly identified version
Choose a project name and revision, then use that revision consistently in the handoff note and the files it describes. A folder containing “final,” “final-new,” and “final-really” leaves the selection to whoever opens it next.
For example, a fictional small display project could use “counter-display-r03” as its revision name. The note would identify the editable source and the specific export intended for production. That example is a naming suggestion, not a finished design or a tested build.
Keep earlier revisions in your project archive. Don’t make the recipient sort through every experiment to find the file you want them to use. If a newer version replaces one you’ve already handed off, say which earlier revision it replaces.
Use this handoff note
Copy the fields below and remove any that don’t apply. A blank field is worth resolving when the answer affects the work.
- Project and revision:
- What this version is intended to make:
- Quantity:
- Finished dimensions and units:
- Material specification and thickness:
- Editable source file:
- Export to use, with its purpose:
- Linked assets or other dependencies:
- Reference image or proof, labeled as a reference:
- Checks completed, with actual results:
- Open questions and the step they affect:
- Person responsible for answering those questions:
Keep a reference picture separate from a production instruction. An attractive mockup may communicate appearance while saying nothing about dimensions, material compatibility, or fit. If a dimension is still an estimate, write that next to the number.
For work that needs a cut list, include the correct revision of that list. Don’t expect a picture of the assembled object to supply part dimensions or quantities.
Gather dependencies deliberately
If the project uses linked graphics, sending the main file alone may leave part of the handoff behind. Adobe’s Illustrator packaging guide explains how File > Package can gather the document, linked graphics, eligible fonts, and a report. Its settings include copying links and relinking the packaged document to that collected location.
Packaging is a collection step. Check the resulting files and report, and review the font license before copying fonts; Adobe specifically directs users to check whether their license permits that copying. Keep any required asset permissions with the handoff rather than assuming the folder itself grants them.
The same planning question applies outside Illustrator: what does this file depend on that isn’t actually traveling with it? Identify the answer for the application you’re using.
Review the folder as a recipient
Open the handoff location and read the note first. Confirm that the named source and export are present, carry the intended revision, and match the stated dimensions and units. Open the export itself rather than assuming it matches the source because its filename looks right.
If a check hasn’t been performed, mark it as pending. A tidy folder doesn’t establish that a material, process, or fit has been tested. The handoff is ready when the recipient can identify the intended files and the remaining questions without guessing what you meant.
Sources and photographs
The handoff note is an original planning template. Adobe’s packaging documentation was checked October 22, 2026. Licensed stock photographs illustrate a design workspace and project notes; they don’t show a completed Replicate handoff or fabrication result.
Found an error or an outdated detail? Send a correction for this article.
