Define the revision the client needs to make
An AI design handoff should let the client perform the revisions agreed in the project scope. That usually means approved exports, editable masters, linked assets, dependency notes, and a short guide to changing the work. A folder full of finished images is useful, but it does not establish that the client can update a headline, replace a photograph, or export another format.
Paul Melcher's 17 September Design Week opinion highlights how AI production complicates the idea of a source file. Some work retains editable layers, some comes from a production pipeline, and some exists mainly as a generated output. My recommendation is to define delivery through the changes a client needs to make, then test those changes before sign-off.
Turn editability into an acceptance checklist
Ask which edits are routine. A social team might need to change prices and dates. A website owner might need to replace case-study images without breaking mobile crops. A packaging project could require changes that belong with a specialist designer. Document those differences before selecting the generation workflow.
For each deliverable, state the supported revision, the application needed, and who is expected to do it. Avoid describing an entire project as fully editable when only the text layers are editable. A generated background may be a perfectly acceptable final asset if the client knows how it can be replaced and what a more substantial revision requires.
Create a small delivery manifest
| Record | What it answers |
|---|---|
| Master and approved export | Which file should I change, and what should it look like? |
| Fonts and linked assets | What else must be available to open the work correctly? |
| Generation notes | Which components depend on a model or external tool? |
| Revision instructions | How do I perform the common change safely? |
| Known limitations | Which changes need a designer or a replacement asset? |
Keep private client references and account credentials out of reusable templates. Record where authorised team members can obtain access rather than putting passwords in the handoff. Font and asset permissions need their own checks; possession of a file does not settle what the recipient is allowed to do with it.
Run a reopening and revision test
The following is a proposed acceptance test, not a completed client benchmark. Give a colleague the delivery package and written instructions. Ask them to open the master without relying on the original designer's machine, make one agreed text change, replace one asset, and produce a new export.
Record what happened: missing font, broken link, unavailable plugin, unclear naming, or successful revision. Compare the export with the approved reference at the actual delivery size. Check wrapping, crop, colour, and accidental movement. A successful open is only the first step; the useful outcome is a correct revision.
A fictional campaign handoff
Imagine a studio delivering a promotional tile with a generated background and an editable date. The recipient changes the date, but the new line wraps over the logo. The source file exists, yet the routine edit fails. The fix could be a constrained text area, an alternate layout for longer copy, and instructions that explain when to switch.
Now suppose the client wants the background subject in a different pose. That is a different task. Label it as a new image-production request unless the agreed workflow supports it. Clear boundaries prevent a normal revision becoming a dispute about what “source included” meant.
Make the package maintainable
Keep the final approved package together, with a version, owner, and review date. When a dependency changes, retest the common revision before replacing the previous package. Our Content Credentials guide covers asset provenance; this checklist covers the practical ability to continue working.
If your team can generate assets quickly but struggles to hand them over, start with one recurring deliverable. JQ's AI-assisted web design work connects brand decisions with usable implementation. A useful assessment asks what the next person needs to change and proves that the delivery supports it.
Link Map
Sources and editorial review
Sources reviewed on 21 September 2026. The practical workflows and illustrative examples are JQ AI SYSTEMS analysis unless explicitly attributed.
- Design Week: What’s Your Source File? (17 September 2026; Paul Melcher, opinion).