01
Package files and context together
Place the original footage, audio, approved graphics, copy, and references in a structure that another person can follow. Add one brief that explains the goal, intended use, deadline, and requested deliverables.
Keep assumptions separate from confirmed facts. This preparation does not decide which files an editor will accept or what the eventual scope, transfer method, schedule, or deliverables will include.
02
Make feedback easy to locate
When reviewing any shared draft, identify the exact moment or element that needs attention. Write what should change and, when useful, why it matters to the message or placement.
A timestamp can help when the chosen review method supports one, but no tool, number of review rounds, or feedback process is assumed here. Collecting comments before sending them can still reduce conflicting requests.
- Name the exact moment or element
- Describe the requested change
- Include replacement wording when text must change
- Resolve conflicting feedback before sending it
03
List the requested output needs
List the versions requested for web, social, or archive. Orientation, captions, text placement, and file naming may differ across those uses.
Treat that list as an input to the conversation, not a promise of delivery. File transfer, schedule, accepted deliverables, and review points remain open until they are agreed for the individual project.
- List each requested orientation and placement
- State whether text or captions should appear in the image
- Keep source material, review versions, and any approved files in separate folders