The most useful asset handoff answers questions before the designer has to ask them. What is this object? Is it the current version? Why was this image selected? Has anything important been altered? Where is the documentation for the intended use? A folder that answers none of these questions transfers uncertainty rather than useful material.
For ChatGPT ads, prepare source assets around one planned creative task. The package should be small enough to inspect and complete enough to support a decision. It does not need every photograph, screenshot and brand file the business owns. It needs the evidence and originals required to show the advertised offer accurately.
Start with a visual requirement
Take a fictional company selling modular desk lamps. The ad will explain how the lamp can be attached to a narrow desk using its clamp. A front-facing beauty shot identifies the product but does little to explain attachment. A photograph of the clamp on an actual desk edge is more relevant, even if the background needs modest preparation.
Write the requirement before searching the library: show the current clamp, its contact with the desk and enough surrounding space to understand the installation. Add the factual boundary: the ad should not imply compatibility with every desk thickness. This keeps the selection tied to a buyer’s question.
If the requirement is vague, work through the use-case image brief first. Otherwise, the best-looking available file can dictate the concept simply because it is easy to find. That is a production convenience, not a reason for the image to serve the ad’s message.
Ask for an original plus a fact note
Request the original usable file rather than a screenshot copied from a slide deck. Where possible, obtain a version without embedded promotional text. Additional space around the subject can help the designer create a crop that retains the attachment mechanism and avoids cutting off the detail the buyer needs.
The accompanying note should identify the model, variant and relevant product version. It should also say what is unknown. A file called latest-lamp does not establish that the clamp matches the version currently sold. Ask someone who knows the product to confirm the detail rather than treating the filename as evidence.
For the fictional lamp, an older photograph might show a different tightening handle. That difference matters because the ad explains installation. The older image could remain useful elsewhere, but it should not quietly become the demonstration for the current mechanism. Selection depends on the intended message, not just resolution.
Build an asset register people will maintain
Use one row for each selected original. Include only fields that support a practical decision. A long register with empty columns tends to obscure the missing facts that really matter.
| Record | Decision it supports |
|---|---|
| Original file and responsible person | Where to find the source and resolve questions |
| Model and version | Whether the pictured product matches the offer |
| Detail shown | Which part of the ad brief the asset can explain |
| Existing edits | Whether alterations affect factual meaning |
| Usage documentation location | Whether the intended use has been checked |
| Unresolved question | What must happen before production proceeds |
Keep factual accuracy separate from usage documentation. A file may show the correct product while the intended advertising use remains unclear. Another file may have clear usage documentation but depict an obsolete variant. Both checks matter, and neither can be inferred merely because the image is stored in a shared folder. For material from a customer project, distinguish a documented case from an illustrative setup before presenting the image as evidence of an experience or result.
Sort by readiness with a next action
Divide the candidates into ready for concept work, needs clarification and outside this brief. Give every item needing clarification a specific question and a person who can answer it. Avoid a general maybe folder that makes the designer repeat the search.
The clamp photograph might need confirmation of the desk thickness shown. The original could also contain an accessory cable that is sold separately. Decide whether that detail is relevant and whether a different image would describe the offer more clearly. Do not automatically plan to erase inconvenient objects if doing so would change how the installation appears to work.
For an image outside the brief, record a brief reason and move on. A beautiful room scene may be useful for a later concept about lighting a workspace. It is simply not the strongest source for explaining a clamp. This preserves useful material without making every production handoff an unfiltered archive.
Preserve the route from source to export
Keep the original distinct from the editable working file and final export. Record meaningful changes such as removing the background, extending the canvas, replacing an embedded label or combining two views. The purpose is to make changes to product meaning visible, not to document every minor colour adjustment.
If two files will become a comparison, check that their relationship is defensible. The before-and-after review covers the different claims created by pairing images. Two accurate originals can imply an unsupported result when one is presented as the improvement caused by the other.
Language versions need the same traceability. Identify text that is editable separately and text that belongs to the pictured product. The creative localisation guide helps distinguish a translation task from a change that would invent an unavailable interface or package version.
From file collection to usable source package
- Specify the detail
The requirement is to see the clamp against the desk edge, not just the lamp front.
- Check the original
Confirm the current model and check that the handle is not from an older design.
- Resolve the gap
The product owner confirms the desk thickness shown in the setup.
- Handoff with traceability
Connect the original, fact note and working file so the crop can be reviewed.
Deliver a recommendation, not a scavenger hunt
Hand over the brief, selected originals, asset register and remaining questions together. Recommend the primary asset and state why it fits. In the lamp example, the reason might be that it shows the current clamp contacting the desk without hiding the tightening handle. That explanation helps the designer preserve the useful detail when composing the ad.
OpenAI’s standard ad includes title, body, image and destination. Campaign Management. An asset package prepares one part of that combination; it is not evidence that the final ad has been approved or published.
Hints add context rather than exact keywords or guaranteed delivery. Targeting. They cannot correct an inaccurate product image for the reader. When the source material cannot support the desired message, obtain the missing material or narrow the message.
End the handoff by asking the designer to describe what can now be produced. The answer should identify the right product, the visible capability and a manageable next step. If the answer requires searching another forgotten drive for a usable original, the source package has not yet done its job.
Sources and scope
Prepare a small, traceable source asset package that lets a designer show the correct offer without guessing product facts or material readiness.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.