Define Which Editable Gift Assets Must Be Returned at Handover

Close a custom gift artwork job against the deliverables that were actually agreed. If the list includes an editable layout and a viewing PDF, receiving the PDF settles only its own row. The buyer still needs to establish whether the named editable asset arrived, what dependencies it requires and which future uses are supported by the relevant permissions.

This review starts with already approved gift artwork. It is about the return of digital assets after the decorator’s adaptation work. It does not choose the current printer’s input format, reconstruct missing designs or decide who legally owns the work.

Read the deliverable wording before counting files

Collect the accepted quotation, scope and any subsequent authorised clarification that names the return assets. Quote the relevant deliverable description in the handover record. “Artwork supplied” may leave the role and format unclear; ask the contracting contact to identify what that phrase covers instead of converting it into a promise of every working file.

Connect each listed deliverable to the approved gift and revision. A source layout from before the notebook cover was adapted may not satisfy an agreement to return the final adapted layout. Equally, a newer file should not be treated as approved merely because it arrived at closeout. Record any difference and send it to the person responsible for the artwork decision.

Separate agreed deliverables from newly requested conveniences. If only a viewing copy was agreed, asking for an editable source is an additional request whose scope and terms need a response. If the source was already named, asking where it is addresses an outstanding deliverable. This distinction makes the enquiry more precise without the worksheet issuing a contractual ruling.

Define what the buyer expects to do next

Name the intended future action before using the word “editable.” The buyer might need to change an event date, replace a sponsor mark or supply the approved design to another decorator. These are different purposes, and the received files and applicable permissions need to answer the actual one.

Ask the receiving design contact to describe the relevant edit it could perform with the delivered asset, using the buyer’s authorised software and access. A file opening on one person’s computer does not by itself establish that the buyer has everything required for that future action. Record the application and version reported by the sender where they are needed to interpret the agreed delivery, without prescribing a universal format.

Keep machine-specific output outside the source-deliverable assumption. A returned layout does not establish that another decorator can use it directly for a different process. If that future supplier needs adaptation, it must assess the supplied asset under its own agreed scope. Broader current-job artwork preparation belongs in the gift printing guide.

Reconcile asset roles and dependencies separately

List previews, editable layouts and any other expressly agreed source components by role. Preserve the original filenames and sender’s description alongside the buyer’s stable asset reference. Several exports of one preview do not replace a missing source file, and a folder containing many files is not evidence that every agreed role is covered.

Ask which linked graphics, fonts or other dependencies are required for the stated future action, who supplies or controls them and which are absent. A dependency can be essential to the intended edit without being a deliverable the decorator was authorised to transfer. Leave that distinction visible so the buyer can seek clarification from the correct party.

Adobe’s InDesign guidance gives a limited example: live preflight can identify missing fonts and modified links, among other production issues. The checked scope is configurable. Adobe preflight guidance An appropriate technical check may help find a dependency gap, but it does not establish contractual entitlement or permission to redistribute the material.

Use a hypothetical notebook return record

Assume a fictional notebook job expressly names two deliverables: a viewing PDF and an editable layout of the approved cover. Every entry below is hypothetical. The font row records a dependency question and is not a third agreed file delivery.

The result is one received deliverable out of the two expressly listed, with a separate dependency question still open. It does not follow that the job is half complete in every sense: the remaining source could be the asset the buyer needs most for its next campaign.

The useful request is specific: identify the delivery of the C6 editable layout named in the accepted scope, identify required dependencies, and provide the applicable permission reference for the proposed date edit. “Please resend everything” is less helpful because it leaves both the missing role and the future use ambiguous.

Respond differently to missing files and disputed scope

If the decorator confirms that the source was agreed but omitted, arrange its authorised transfer and check the received item against that promise. If a link was sent but the receiving buyer cannot obtain the file through approved access, retain an access gap rather than reporting successful handover.

If the decorator disputes whether the source was included, preserve its response alongside the actual agreement and ask the buyer’s commercial owner to resolve the difference. Do not relabel the PDF as editable to close the row or instruct someone to recreate the source without approval. A substitute deliverable is a proposed change requiring the appropriate decision.

Paying a setup charge should not be used as the worksheet’s evidence of copyright transfer, font rights, permission to edit or entitlement to machine-ready data. Record those questions against the actual terms and responsible owner. Where interpretation is disputed, seek appropriate advice; this article supplies no legal conclusion.

Close receipt and future-use questions on their own evidence

When the source arrives, have the authorised receiving contact record the artifact received, its relationship to the approved revision and the result of the scoped access or editability check. Preserve any missing dependency or limitation instead of silently substituting an available component and changing the approved artwork.

Receipt may be complete while permission for a proposed later use remains unresolved. Write that outcome plainly, with the permission question assigned to its owner. Conversely, a confirmed future-use permission cannot make an undelivered source file available. Keep the record useful by stating the next decision rather than hiding both states under “assets handed over.”

For an initial gift quote enquiry, describe the return deliverables you want addressed and the gift reference. Use PNG, JPEG, WebP or GIF image references with the form. Arrange original layouts and their authorised dependencies separately with the approved contact; the form is not an upload route for arbitrary source files or font packages.