Client briefs rarely arrive as shots. They arrive as feelings with a logo attached. “Make it feel premium.” “We want energy, but calm energy.” “Something like that reference, but not like that reference.” None of those sentences can be typed into Seedance or Veo. And creators who try end up generating expensive interpretations of adjectives.
In my pipeline the billable craft sits between the brief and the prompt: translation. Words become frames. Frames become a shot list a client can approve. Only then does generation begin — with the argument already settled while it was still cheap.
Briefs Describe Feelings; Shot Lists Describe Frames
Feelings aren’t useless. They tell you what the video must do to the viewer. But a generator can’t film a feeling. It films a subject, in a place, under light, doing one action, seen from somewhere. Every brief sentence has to survive that conversion before it deserves a credit spent on it.
Watch the conversion happen on a typical line. Brief: “Show that mornings feel effortless with our product.” A generator hears nothing usable in that. A shot list hears a sequence: wide of a bright kitchen, medium of the product in hand with no fuss around it, close on the result, reaction beat that reads relaxed rather than rushed. Four frames. Each one promptable. Each one a client can look at and say yes or no with confidence.
Creators sometimes resist this translation because it feels less creative than prompting freely. Honestly, the opposite is true. Free prompting from adjectives burns the budget exploring. Translation concentrates the creativity at the one stage where changing your mind costs nothing, then makes generation an execution task. The client gets the exploration they wanted — on paper and in stills, at paper prices.
The Translation Meeting: Questions That Get To Shots
One focused conversation converts most briefs. Bring the brief, bring reference stills, and ask questions that force frames into existence:
- Who is on screen, exactly? Age, look, wardrobe, and who is definitely not on screen. Casting vagueness becomes wardrobe drift later
- Where are we, at what hour? Location, time of day, and light character. “Nice kitchen” must become a frame the client recognises
- What happens, in one action per beat? Verbs only. If a beat needs the word “and then” twice, it is two shots
- What must the viewer believe at the end? The single takeaway, plus the proof moment that earns it
- What is banned? Competitor looks, claims the client cannot make, colours, settings, styles. Bans written now prevent reshoots later
- Where will this live, and in what shape? Platform, aspect ratio, runtime, sound on or sound off viewing
Take notes in shot language during the meeting. When the client says “premium,” ask what premium looks like in a frame — and show two stills that differ in light rather than in adjectives. Clients are usually excellent at choosing between pictures and poor at choosing between paragraphs. Work with that instead of complaining about it. Right?
The meeting ends with mood references agreed and a beat list in plain sentences. The shot list itself gets built right after, while the conversation is warm. Don’t wait a week.
Mood References And What To Steal From Them
Every brief drags references behind it: a competitor video, a film still, a post the client saved. References are valuable and dangerous in the same way. Valuable because they carry taste decisions words can’t. Dangerous because clients often want the reference’s feeling with none of its literal content — and creators copy the wrong layer.
Read each reference in layers and name what you’re taking:
- Light layer: direction, softness, time of day, contrast
- Camera layer: shot sizes, movement habits, how close the camera lives
- World layer: locations, palette, dressing density
- Pace layer: shot length, where the turns land, how the ending behaves
- Performance layer: energy, stillness, how people occupy frames
Then state, in the shot list notes, which layers this project borrows and which it deliberately doesn’t. “Light and pace from reference A. World and palette are the client’s own café and brand colours. Nothing copied at subject level.” That sentence protects the work creatively and gives the client language they can approve.
It also feeds generation honestly: your look anchors come from chosen layers, while your cast and sets come from reference images for consistent characters and the project’s own location frames — not from somebody else’s finished video.
Shot List As Approval Document
The shot list is where the client signs, and it should be built to be signed. One row per shot, readable by a non-filmmaker in two minutes:
- Shot ID and beat: S03, “product in hand, first use”
- Frame: the storyboard panel or approved still thumbnail. This does more approving work than every other column combined
- Subject and action: one sentence, verbs visible
- Camera: size and movement in plain words. “Slow push-in” approves better than lens talk
- Light and location: named, matched to reference frames
- Sound or line: dialogue, voiceover line, or “ambience only”
- Status: Proposed, Approved, Changed with date
Approval at this stage is the cheapest insurance in client work. A changed mind about a still costs a redraw. A changed mind about generated motion costs the shot. A changed mind after delivery costs the relationship some skin.
Walk the client through the thumbnails, confirm each frame, and record approval against the version of the list they saw. When the brief’s feelings resurface mid-production as new instructions, the approved list is the calm place both sides return to — which is the same discipline that keeps client revision workflow for AI video from turning into open-ended regeneration.
Prompt Writing From Approved Shots
With an approved list, prompt writing stops being invention and becomes translation, shot by shot. Each prompt gets assembled from the row itself: subject and locked wardrobe line from the cast frames, location and light line from the set frames, the row’s one action, the row’s camera sentence, and the project look line. Settings follow the board: duration matched to the beat, aspect ratio set before generation, reference frames attached by filename.
A Row Becomes A Prompt
Approved row: S03, medium shot, café morning, lead takes the cup with both hands and smiles toward window, slow push-in, ambience only. The working prompt grows straight out of it: the character’s locked description, the café’s locked light line, “medium shot, slow push-in, she lifts the cup with both hands, glances toward the window, small relaxed smile,” plus the project’s style line and negative notes from the character’s Never list.
Nothing in that prompt was decided at the keyboard. Every phrase has a parent on the approved list — which means a client note like “less smile in S03” maps to exactly one phrase to change. That’s the whole point.
This traceability also makes revisions survivable. When a shot comes back wrong, you compare render, frame, and prompt in one glance and see which layer moved. Frame problem goes back to stills. Motion problem gets a narrower prompt or a chained approach like the one in prompt chaining for complex scenes. Taste problem goes back to the approved list, where it belongs, with the client’s signature beside the original decision.
When The Brief Asks For The Impossible Shot
Sooner or later a brief requests a shot the tools can’t honestly deliver: six named characters speaking in a crowd while the camera orbits through a doorway carrying a legible logo through changing light. The professional move is to say so at shot list stage — with the reason and the alternative in the same breath.
Split the impossible honestly. Crowd becomes background softness behind one speaker. The orbit becomes two chained shots with a coverage cut. The travelling logo becomes a clean product single, with readable text built in the edit where text belongs.
Clients rarely love the impossible shot itself. They love the feeling it was reaching for — and a split sequence usually reaches it better than one heroic generation bleeding artifacts. Trust me on this one.
Put the limitation and the chosen alternative on the list the client approves. That line, signed early, prevents the delivery-day conversation where the creator explains model limits as if they were excuses. Limits named in pre-production read as expertise. The same limits discovered in delivery read as surprises. And clients bill surprises against trust.
Shot List Mistakes That Resurface As Invoices
Three errors account for most painful client generation days, and all three are visible on the shot list before a credit is spent. The first is the adjective shot, a row that says “hero moment, premium feel” with no subject, action, or frame attached. Rows like that delegate the creative decision to the model’s averages. The second is the compound shot, one row asking for an entrance, a dialogue line, and a product reveal, which guarantees three mediocre beats instead of one strong frame. The third is the unowned approval, where the list circulated, nobody clearly approved it, and generation proceeded on a shrug.
Every one of these reads clearly on paper. That is the point of the document. Paper is where expensive sentences go to be caught.
A healthy list also carries production notes clients never see in the prompt: which shots chain, which need coverage inserts, which hero frames anchor identity for their neighbours. Writing join logic at list stage costs nothing and prevents the edit-stage discovery that two beautiful approved shots refuse to meet. When that discovery happens in Premiere instead, somebody pays for a regeneration to fix what a pencil line could have planned.
Quoting And Scoping From The List
The shot list quietly becomes your scope document. Approved rows define what will be generated, how many hero frames exist, and where revision rounds attach. When a client later asks for “one more quick shot,” the list gives both sides a fair reference: it’s an addition, priced and scheduled as one, rather than a fog of extra effort absorbed silently.
Creators who work from lists stop donating revisions by accident. And clients, in my experience, respect the list — because they signed it when it was frames instead of discovering it as an invoice.
A Quick Self-Check Before Generation Starts
Before the first client generation, read the finished shot list once with a sceptic’s eye. Could a skilled stranger prompt every row without asking you a question? Does every row name its frame, action, camera, and location in words a model can use? Is any row secretly two shots wearing a trench coat? Are bans written where the generator will meet them — in prompt notes — rather than only in meeting memory?
Five minutes of that scepticism is the last cheap defence the budget gets. After it, generation should feel almost clerical. And clerical is a compliment in production.
Takeaway: never prompt from a brief. Translate it. Ask questions that force frames, steal named layers from references, build a thumbnail shot list the client can genuinely approve, and write prompts as transcriptions of approved rows. The generator then does the narrow job it’s good at, inside decisions already made. That’s how client words become generatable shots without the budget leaking out between the adjectives.