Prepare an image handoff a collaborator can use
A manual asset manifest covering intended placement, descriptions, versions, permissions questions, and handoff status.
Start with the destination
An image folder tells a collaborator what files exist, but may not explain which one belongs where. Before sending a batch, list the planned placements: a page banner, a product detail, or a team introduction. Agree on what the recipient needs, including dimensions, format, and whether an editable original is required. Record requirements you still need to confirm.
This TITAN-owned resource is a static manual worksheet. It does not upload, convert, inspect, or verify image permissions. Copy the fields into your own document. Keep private material out of public handoff notes, and share files only with the intended recipients.
Build a small, readable manifest
Give each asset a stable identifier and a descriptive filename. Separate approved choices from alternatives, and label versions so the recipient does not have to guess which file is current. Keep the original intact when preparing a crop. If two placements need different crops, list each output separately and connect both to the original identifier.
Record what the image shows and why it is included. Describe any important area that must remain visible, such as a product label. Draft alternative text for the intended page context and ask the page editor to review it. A filename or general caption is not automatically the right alternative text.
Copy this asset record for each image
Asset ID: ____
Exact filename and version: ____
Folder or approved sharing location: ____
Intended page and placement: ____
What the image shows: ____
Purpose in that placement: ____
Proposed alternative text for review: ____
Crop or focal-point instructions: ____
Requested format and dimensions: ____
Actual format and dimensions, checked by: ____
Original file reference: ____
Creator or source recorded: ____
Permission evidence location and usage restrictions to check: ____
Unresolved ownership or permission question: ____
Reviewer: ____
Status: proposed / awaiting clarification / approved for stated use
Next action, owner, and date: ____
Fictional worked example: a ceramics banner
Fern Table, a fictional ceramics studio, is preparing a workshop page. Asset FT-03 is “workshop-table-banner-v2.jpg,” stored in the agreed draft folder. Intended placement: workshop page introduction. Description: a table with three unfinished bowls and hand tools. Purpose: show the workshop setup. Proposed alternative text: “Three unfinished bowls and clay tools on the workshop table.” The page editor will review whether that description fits the final context.
The requested export is 1600 by 900 pixels; the designer still needs to check the delivered file. Crop instruction: keep all three bowls visible. Source: the studio’s original photograph, referenced as FT-03-original. Permission question: has the studio approved website use? Status: awaiting clarification. Owner Jules will ask the studio manager before the final handoff. These fictional notes do not establish real usage rights.
Close the handoff loop
Before sharing, open each listed file and compare its name with the manifest. Confirm the recipient can access the approved location. Send a short summary of approved assets, unresolved questions, and the review deadline. Ask the recipient to flag missing files or mismatched versions before placing them. Keep unresolved assets separate until their questions are answered.