Check the promise against the package
Read the agreed commission scope before assembling the final files. Confirm whether print exports, web copies, editable sources, and usage documents are included. Do not add unapproved source files merely because they are available in the artist’s folder.
A final handoff is also the place to distinguish included corrections from possible future work, using the studio’s actual agreement. Avoid inventing new terms in the delivery email.
A fictional filled-in handoff sheet
Commission: Fictional greenhouse illustration Order: DEMO-530 Final revision: R2 Start here: 530-handoff.pdf Print export: 530-print-R2.jpg — agreed print use Web export: 530-web-R2.png — agreed online placement Source project: Not included in this example package Usage document: 530-usage-R1.pdf — supplied by rights owner Preview status: Earlier previews superseded by R2 Help: Studio support route listed in the delivery message Different size or new adaptation: Contact the studio to discuss scope
This is a synthetic example, not a real license or customer commission. Replace every field with the actual agreed deliverables before using the structure.
A final acceptance checklist
- Every promised output is present.
- Filenames and revision labels agree with the handoff sheet.
- All exports open independently of the authoring project.
- Dimensions, formats, and background treatment match scope.
- The approved usage document matches the artwork reference.
- The package excludes unrelated files and private production notes.
- The intended customer can download and open it.
Do not substitute a successful upload for the last check. A ZIP must be extracted, an external link needs permission, and an editable file may need a specific application.
Release from the correct order
QuickAttach supports files or links associated with order items. Use the commission reference to confirm the selection before sending. A single package can be useful for one artwork with several exports; verify size and access rather than assuming multiple attachment fields.
Keep the final approval record in the studio’s established process. The app’s download activity is not an approval or acceptance signature.
Leave support a usable record
Record the final package reference, delivered revision, and any external hosting owner. When the buyer later asks for another copy or a new size, support can identify what was originally supplied. Explain access duration accurately and maintain the approved source where your policy requires recovery.
A well-prepared handoff does not need a long message. It needs a clear starting file, an accurate package map, and a support route that distinguishes access problems from new creative requests.
Deliver the right file with the right order
See how QuickAttach connects a customer-specific file or link to a Shopify order item.
See the QuickAttach order-to-download walkthrough