How to Brief a Videographer With Staged References
By Khushi Yadav
Briefing a videographer is a transfer of intent. The client has a feeling, a tone, a few reference shots, a product to feature, and a deadline. The videographer needs all of that turned into something they can shoot and edit against. The default workflow — pasting stills and YouTube links into a Slack thread one at a time across two weeks — fails because Slack threads are not briefs. They are chat logs. By the time shoot day arrives, nobody can find the reference that mattered, half the links have expired, and the one still that captured the tone is buried under 38 messages about catering.
This guide lays out a saner pattern: one folder of reference files, three pinned stills that capture the look, a short written brief, and a single shared link. It is written for marketing leads, founders, and creative directors who hire videographers on a project basis. For neighbouring topics, see Creative Cloud Libraries vs local clip staging, accessibility in design handoff: do not copy alt text away, best clipboard setup for Photoshop users, and the Figma desktop vs Figma web paste behavior note on how paste targets change between apps.
Why chat threads fail as briefs
A 40-image Slack thread looks like a brief because it has images and words. It is not a brief because:
- There is no canonical order. The videographer cannot tell which image is the reference and which is a follow-up joke. They scroll, they guess, they miss things.
- Links rot. YouTube clips get taken private. Vimeo links expire. Loom videos get deleted. A reference that worked on Monday is a 404 on Friday.
- Screenshots flatten context. Pasting a screenshot of a frame from a film loses the source, the timestamp, and the audio cue. The videographer has the pixels but not the reference.
- Decisions are not separated from suggestions. "This is the look" and "I quite like this too" end up as adjacent messages with equal visual weight.
- Search is unreliable. Slack search finds keywords, not visual intent. Six weeks later, nobody can find "that shot with the warm window light".
The fix is not better chat. The fix is to move the brief out of chat entirely.
The one-folder pattern
A video brief should live in one folder, with a predictable structure. Example:
projectname-brief/
├── 00-brief.md ← the short written brief
├── 01-references/ ← still frames, named by what they show
├── 02-links/ ← a single file of source links with context
├── 03-product/ ← product stills, logo files, brand colours
└── 04-deliverables/ ← spec: aspect ratios, runtimes, channels
The written brief is short. One page. It covers: the goal of the video, the audience, the tone, the must-have shots, the must-avoid shots, the deliverable spec (aspect ratios, runtimes, channels), the deadline, and the budget. Anything longer than a page is not a brief; it is a treatment, and that is a different document.
The 01-references/ folder holds still frames pulled from films, ads, or stock — named by what they show, not by source. warm-window-light-still.png is useful. screenshot-2026-08-19-3.png is not. Each file gets a one-line caption in the brief: what about this reference matters (lighting, lens, pacing, colour grade, blocking).
The 02-links/ file is a plain text or Markdown list of source URLs with one line of context each. This solves link rot: if a YouTube clip goes private, the videographer at least knows what the clip was supposed to show, and can find a replacement.
Three pinned stills
Of the references in 01-references/, three should be flagged as the ones that capture the look. Not twenty. Three. The constraint forces the client to decide what actually matters.
These three stills are good candidates for a local clipboard shelf — pinned, visible, drag-into-Photoshop-or-Figma ready. The shelf is not the brief; it is the working set of "the look" for the duration of the project. When the project ships, the pins come off.
Why three? Because a videographer can hold three images in mind during a shoot. They cannot hold twenty. Three references give a coherent direction; twenty references cancel each other out. The constraint is a feature, not a limitation.
The written brief itself
A template that works for most short-form video (ads, product demos, brand films under three minutes):
# Project name — video brief
## Goal
One sentence: what should the viewer do or feel after watching?
## Audience
Who they are, what they already know, what they do not.
## Tone
Three adjectives, no more. "Warm, unhurried, confident" beats a paragraph.
## Must-have shots
- Shot 1: ...
- Shot 2: ...
- Shot 3: ...
## Must-avoid
Things that will make this look like the wrong brand.
## Deliverables
- 16:9 master, 60 seconds
- 9:16 cutdown, 30 seconds, for Reels/Shorts
- 1:1 cutdown, 30 seconds, for feed
- Captioned and uncaptioned versions of each
## Deadline
Final delivery: [date]. Rough cut: [date - 1 week].
## Budget
[Number]. Includes: shoot, edit, colour, sound, music licence.
## References
See /01-references/. Pinned stills:
1. warm-window-light-still.png — lighting direction and warmth
2. handheld-follow-still.png — camera movement style
3. grade-cool-shadow-still.png — colour grade reference
The brief is one page. It is the canonical document. Chat is for logistics (scheduling, location scouting, food). Chat is not for creative direction.
Sharing the folder
The folder goes to the videographer as a single link. Cloud drive (Google Drive, Dropbox, OneDrive) is fine for most projects. For work under NDA or with unreleased product, an encrypted zip on a project file server is safer. The videographer gets one link, not 40 messages.
If the videographer needs to add to the references (their own look ideas, location scouts), they add to the same folder. The brief stays canonical; the references grow. When a reference is rejected, it gets a rejected- prefix rather than deletion, so the decision history is preserved.
What does not belong in the brief
- A 40-image moodboard with no captions. The videographer will guess wrong.
- A Loom video of you talking about the references. The references themselves, named and captioned, are faster to consume and easier to refer back to on set.
- A montage of stock footage with a soundtrack. Stock montages imply a pacing that the actual shoot will not match.
- A competitor's video as the only reference. The videographer will reproduce the competitor's video. State what about the competitor's video matters and what does not.
- A 600-word essay on brand values. That belongs in the brand book. The brief is for this specific video.
The handoff moment
The handoff is a 30-minute call where the client walks the videographer through the brief folder, in order. The call is recorded (with permission) and the recording goes in the folder. After that call, the brief folder is the source of truth. If something changes — a deliverable, a deadline, a must-have shot — it gets edited into 00-brief.md with a date stamp, not added as a chat message.
This pattern takes 90 minutes to set up. It saves the videographer a day of guessing and the client a round of reshoots. The math is straightforward.
Common brief failures and how to recover
Even with a clean folder structure, briefs go wrong in predictable ways. Recognising the failure early is half the recovery.
- Scope creep in the brief. The client adds a seventh must-have shot three days before the shoot. Recovery: amend
00-brief.mdwith a date stamp, evaluate whether the budget covers the new shot, and say no if it does not. Briefs that grow without budget grow without permission. - Reference drift. The videographer sends back a rough cut that looks nothing like the pinned stills. Recovery: re-open the brief folder, point at the three pinned stills, and ask which one the rough cut is supposed to match. Sometimes the videographer has a better idea; sometimes they have misread the brief. Either way, the brief folder is the arbiter.
- Asset delivery in the wrong format. The videographer delivers ProRes when the social team wanted H.264. Recovery: the deliverables section of
00-brief.mdshould have specified the codec. If it did not, that is a brief gap to fix on the next project, not a videographer error to charge back. - Pinned stills lost mid-project. The designer's machine crashes and the local shelf pins are gone. Recovery: the canonical kit is in the project folder, not on the shelf. Re-pin from the folder. The shelf is a convenience, not a source of truth.
When the brief is for an internal team
For internal video teams (in-house marketing, internal comms), the brief discipline is the same but the handoff is lighter. The folder can live on the team's shared drive, the videographer is already on the same Slack, and the call can be a 15-minute stand-up rather than a 30-minute kickoff. The discipline that still matters: one folder, one canonical brief, three pinned stills, no chat-based creative direction. Internal teams fail at this more often than agencies do, because the familiarity of the team makes the discipline feel unnecessary. It is not.
That limit is unpacked in Seasonal Campaign Kits: Pin, Ship, Unpin.
Related reading
- Accessibility in Design Handoff: Do Not Copy Alt Text Away
- Seasonal Campaign Kits: Pin, Ship, Unpin
- Best Clipboard Setup for Photoshop Users
- Best Clipboard Habits for Developers in 2026
Sources
- Slack — Organise conversations with lists and sections — Slack's own guidance acknowledges that threads are not a filing system and recommends lists and sections for organisation; relevant context for why chat threads fail as briefs
- Google Drive — Share files and folders — official documentation for sharing a single folder link, the recommended handoff pattern
- Adobe — Creative Cloud Libraries overview — alternative handoff for teams already inside the Adobe ecosystem; libraries are heavier than a folder but work for brand-aligned studios
- Frame.io — Collaboration for video review — industry-standard video review tool; for reviewing cuts, not for the initial brief, but worth knowing about for the rough-cut stage
- Dropbox — File and folder sharing — alternative folder host; the choice of host matters less than the discipline of putting everything in one folder
Khushi Yadav is a B.Tech Computer Science Engineering student interested in technology, software, and exploring practical applications of computer science. She enjoys learning new concepts and contributing to technology-focused projects.
GitHub · LinkedInCopy. Stack. Drop.
Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.
Download for Windows Get from Microsoft Store
How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support
Free · Lightweight · Privacy First