Coral, lilac, navy and yellow swatches beside geometric artwork sheets, a clear frame and a curved black ruler.
Original AI-generated editorial illustration; not a real account, product sale or completed job. View full-size image.

A graphic design asset handover should connect an approved visual to the files a recipient can actually use. Start with the placement and required variants, keep the editable source separate from delivery exports, and check each exported file against a short manifest. A preview alone isn't a complete handover.

The reading-group poster in this guide is a fictional exercise. It demonstrates a proposed service deliverable, not a real client commission, a commercial result or evidence that an artwork has been cleared for every possible use.

1. Describe where the design will appear

Ask what the recipient intends to do with the artwork. A web page image, a printed notice and a small social preview can need different versions. Record the actual placement requirements instead of assuming that one large file will suit every destination.

For the fictional reading group, the exercise calls for a main announcement image and a smaller preview. The requester supplies the wording and the intended destinations. Any dimensions used in a real job should come from that destination or an agreed brief, not from a guessed universal standard.

Name who approves the wording and who approves the visual. If a date changes after approval, identify the affected variants before editing. The website project brief guide offers a related way to record purpose and acceptance, but this handover concerns artwork files rather than a whole website.

2. Separate the source from the delivery set

Keep an editable working file under a clear version name. Build the delivery folder from approved exports, not from everything left on the desktop. Label previews so a recipient can distinguish them from files intended for publication.

Create a manifest with filename, intended placement, format, dimensions and approval state. Add an editable-source entry only when it is part of the agreed handover. Receiving a source file doesn't automatically tell the recipient which application, fonts or linked assets are needed to edit it.

For the practice poster, use descriptive names that distinguish the main announcement from the small preview. Include a version identifier rather than a vague suffix such as final-final. Keep the earlier approved version available while the requester reviews a replacement.

3. Choose formats for the actual requirement

MDN's image format guide distinguishes raster formats from vector SVG. It identifies PNG as an option when precise reproduction or transparency is needed, and SVG as suitable for graphics that must draw accurately at different sizes. Those descriptions support a format decision; they don't prove that a particular receiving application accepts every file you can export.

Record the recipient's actual requirement in the manifest. If a transparent version is requested, inspect it over contrasting backgrounds. If a fixed-size preview is required, open that export at its intended size and check whether the important shapes and text remain usable.

Don't describe an export as print-ready merely because it is a large image. Ask the receiving printer or production owner for their requirements. This workflow doesn't establish a universal color profile, bleed setting or production specification.

4. Check wording and variants together

Compare each export with the approved wording. A change made in the main design may not have reached a separately arranged small version. Review the date, location, contact instruction and any image-based text in every file that contains them.

In the fictional exercise, deliberately change the meeting time in a working copy. Use the manifest to identify every affected variant. The purpose is to test the handover method, not to pretend that a real event has been updated.

Check the edges at the intended placement. A layout can look balanced on a large canvas while its title disappears under a platform crop. Keep a preview that shows the relevant crop boundary and ask the recipient to approve that specific use.

The slide deck preparation guide is useful when artwork will be placed inside a presentation. Confirm whether the recipient needs a flat image or editable elements before packaging the files.

5. Include text alternatives with their context

An artwork file alone cannot determine the right alternative text for every use. W3C's alt decision tree ties the text alternative to the image's role: a meaningful image needs its meaning conveyed, a functional image needs its action or destination explained, and a purely decorative image may use an empty alternative.

Add an intended-use note to the manifest. For the practice announcement, identify which information must also be available as ordinary page text. If the graphic becomes a link, the recipient should review its text alternative in that functional context rather than copying a visual description blindly.

Don't claim that supplying suggested alt text makes the finished page accessible. The receiving page, surrounding text and interaction still need review. Your handover should make that next decision visible instead of treating accessibility as an unchecked export option.

6. Reopen the actual delivery files

Open the files from the delivery folder, not from a recent-files shortcut that may point to a working version. Check dimensions, visible content and the requested background treatment. Confirm that the folder contains the files named in the manifest and no unintended drafts.

Keep usage information for any supplied third-party assets with the project record. Don't invent a license or promise that an artwork is exclusively owned merely because it can be downloaded. If the requester must resolve a permission question, keep the affected file in review status.

The photo editing delivery guide covers a different source material, but its file-reconciliation idea is useful here. Match the actual export to its intended use before reporting the handover complete.

What should the recipient approve?

Ask for approval of the named version, its wording and its stated placements. List open questions separately. A recipient should be able to choose the right file without guessing which preview is authoritative.

Start with a small practice set and follow the manifest as though you had never seen the working design. If that exercise exposes a missing variant or an unclear filename, correct the package before offering it as a repeatable service.