How to Brief an Animation Studio So the First Cut Is Close

Animation

How to Brief an Animation Studio So the First Cut Is Close

Animation has no equivalent of a second take. Everything is built before anyone can look at it, which makes the brief the cheapest and most decisive part of the project.

The first cut is where an animation project either feels right or does not. Everything before it is intention. The first cut is the first time anyone gets to see whether the thing in your head and the thing in the studio’s head were ever the same thing.

When that cut lands close, it is almost never luck. It is the brief.

Animation punishes a vague brief in a way live action does not. On a shoot, if a scene is not working, you can move the camera, ask for another take, or find the answer in the edit. In animation there is nothing to find. Every frame has to be built before anybody can look at it, which means a wrong assumption does not surface until someone has already paid to build it.

So the brief is not paperwork. It is the cheapest part of the whole project and it decides how much of the expensive part gets done twice.

What a brief is actually for

A brief is not a description of the video you want. It is the set of decisions you are making so that the studio does not have to guess at them.

That distinction matters because most briefs we receive are written as descriptions. They describe a finished piece in reasonable detail and leave out the reasoning behind it. A studio reading that has to reverse engineer the reasoning anyway, because the reasoning is what gets applied a hundred times during the build, in decisions nobody wrote down.

The useful test on a draft brief is to go through it line by line and ask what decision each sentence is making. “Modern and clean” makes no decision. “It has to work on a trade show screen from twenty feet away, so nothing small and nothing fast” makes several, and a studio can act on all of them without asking.

You do not need to know what the animation should look like. That is what you are hiring for. You need to know what it has to do.

Abstract orange and black composition of scattered fragments resolving into an ordered grid at the centre
A brief is the set of decisions you have already made. Everything left out is something the studio has to guess at.

Start with the job, not the video

Open the brief with what the finished piece has to achieve, for whom, and in what situation. Everything else in the document should be traceable back to that.

When Lowe’s came to us for the MVP Pro Rewards programme, the job was not “explain the programme”. The job was to reach professional contractors, an audience with no patience for marketing that wastes their time, about a set of benefits that were real but layered. That framing is what produced the structure. We broke the programme apart and gave each benefit its own film, six of them, so that any single benefit could be explained on its own wherever it needed explaining.

Nobody briefed us to make six films. The six came out of the job. If the brief had specified one long film, the answer would have been worse and the reason would never have come up.

So be specific about the situation the piece lives in. Who is watching, on what, and what are they doing thirty seconds before and after. A sales tool that plays on a laptop in a meeting is a different object from a launch film that runs at an event, even when the subject is identical.

Explain the product before you describe the video

If what you are animating is technical, the single most valuable thing in your brief is a plain explanation of how the thing actually works.

This is the section most briefs skip, usually because whoever wrote it has been living with the product for two years and has stopped seeing which parts are hard. It is also the section that makes the difference between an animation that is decorative and one that is persuasive.

For InVue’s OnePOD Max we needed to understand the motorised arms, the speed nut mounting and how the product sits inside the wider OneKEY ecosystem, because those are the strengths and they are exactly the kind of strength that gets lost in translation. Understanding them is what let us build the film around going inside the mechanics, where a camera cannot go, which is the entire argument for animating a product like that rather than filming it. You can see how that resolved on the OnePOD Max project page.

Write the explanation as though you were teaching it to a new colleague. Include the part you find obvious. Include the part customers get wrong, and say what they get wrong, because misconceptions are often the most useful thing in a brief.

Use reference, but say why you picked it

Reference is the fastest way to communicate a visual direction and the easiest way to mislead. Send it, and annotate every piece with what specifically you like about it.

A studio looking at an unannotated reel of five animations sees five different things it could mean. You might have sent one for its colour, one for its pacing, one for a single transition, and one because your CEO likes it. Without the annotation, those all read as equal endorsements of everything in the frame, and the studio averages them into something nobody asked for.

It helps to send anti-reference too. One or two pieces you actively do not want, with the reason. That often lands harder than the positive reference, because it draws a boundary rather than pointing at a target.

Be careful about naming a technique when what you mean is a feeling. The words get used loosely, and the differences between motion graphics, 2D and 3D have real consequences for the schedule and the number. If you are not certain which one your reference actually is, say what you like about it and let the studio name the technique. That is a cheaper conversation to have at brief stage than at build stage.

Abstract orange and black composition of concentric rings with a single ring brightly lit
Unannotated reference points at everything in the frame at once. Say which part you actually meant.

Name the constraints while they are still cheap

Constraints belong in the brief, not in feedback. Every one that arrives late has a cost, and the cost rises the further into the build it lands.

The list is usually shorter than people expect. Deadline and what is driving it. Brand rules, and which ones are genuinely fixed. Anything legal or regulatory that has to appear or cannot. Languages and markets, which is a structural decision rather than a finishing one. Our Centrios explainer series was built knowing a French Canadian version was coming, so the build accommodated it instead of being retrofitted for it. Aspect ratios and where each version runs. Any deliverable your team already knows it will need.

And the budget range. It belongs in the brief for the same reason as everything else in this section, which is that it is a constraint that shapes the work. A studio that knows the range designs to it from the first conversation. A studio that does not know it designs something and then finds out. That second version wastes weeks and it usually ends with a piece of creative getting cut down rather than a better idea getting found. We have written separately about how to set a video budget before you have a concept, which is the part most teams assume they cannot do.

Decide who approves, and what they are approving

Say who signs off, and make sure they know they are signing off. Then make sure everyone understands what each stage is actually for.

An animation moves through stages that exist precisely so you can change your mind cheaply: script, then storyboard, then style frames, then an animatic, then the animation itself. Each one locks something. The stage where a scene can be removed for the price of a conversation is the storyboard. The stage where removing it costs real money is after it has been built.

The failure we see most often is not a bad decision at a stage. It is a stakeholder who was not in the room for the first three stages arriving at the first cut with a view about the script. That view might be right. It is just arriving at the point where acting on it is most expensive, and it arrives there because of how approval was set up, not because of anything anyone did wrong.

So the brief should name the people whose opinion will ultimately matter and commit them to the stage where their input is useful. This is an organisational problem rather than a creative one, which is why it belongs in a document written by you rather than by us.

What a good brief actually buys you

It buys a first cut that is a conversation about refinement rather than a conversation about direction.

That is the whole return. A close first cut means the remaining rounds get spent on timing, on a line of copy, on the pace of a transition, which is where revision time is well spent and where a piece genuinely improves. A distant first cut means the rounds get spent rediscovering what the project was supposed to be, and by the time that is settled the budget for refinement has gone.

None of this requires you to be an expert in animation. It requires you to be clear about your own business, your own audience and your own constraints, which you already are. The brief is just the place you write it down.

If you want to see what comes out the other side when this part goes well, our 2D and 3D animation work is the clearest place to look, and most of those projects started with a document a lot like the one described above.

In summary

  • Animation has no equivalent of a second take, so a vague brief gets paid for in rebuilt work rather than in edit time.
  • A brief should record decisions and reasoning, not describe a finished video.
  • Lead with the job the piece has to do and the situation it lives in, and let the format follow from that.
  • Explain how a technical product actually works, including the parts customers misunderstand.
  • Put constraints, languages, deliverables and the budget range in the brief, and name who approves what at which stage.

Keep reading

All posts

We'll take it from here.

Tell us what you're working on. We'll come back with a plan, and a straight answer on whether we're the right team for it.

Start a project