XO3D Studio · 3D Rendering
How to Write a 3D Rendering Project Brief
Cheap decisions early. Expensive fixes later.
A tight brief is the single biggest quality lever on a 3D rendering project. Every ambiguity in the brief becomes a revision, and every revision costs time. This guide describes what every brief should contain and why.
Every hour on the brief saves ten on revision.
Studios do not build renders in a vacuum. Everything they produce is a translation of the brief. If the brief is tight, the first render lands close to the target. If the brief is vague, everyone spends the revision budget converging.
The sections below are what a good brief contains. None are hard to write. All of them shorten the project and lift the quality of the final render.
Advantages
Why brands commission it.
Tighter briefs land closer on first render.
The first render on a tight brief is often within one revision of final. On a vague brief it takes three or four.
Review cycles get shorter.
Structured briefs create structured reviews. Feedback becomes objective, sign-off becomes decisive.
Costs stay predictable.
Detailed deliverables and locked scope keep the budget from drifting.
Studios can quote accurately.
Studios cannot quote a project they cannot see. A tight brief gets tight, competitive quotes.
Trade-offs
What to plan for.
Writing the brief takes time.
Real time. A weak brief is often the result of skipping this stage. The time pays back multiple times over.
Some clients resist committing early.
A tight brief locks decisions. Some clients prefer to leave things open. That flexibility has a cost.
Not every decision can be pre-made.
Some choices only become visible after the first draft render. Brief for that: a review window rather than a final answer.
Reference boards need curation.
A messy reference board with contradictory imagery causes more problems than it solves.
Applications
Where the finished asset ships.
Product story.
What the product does, who it is for, and what the launch has to achieve.
Deliverable list.
Exact still count, aspect ratios, resolutions, animation or interactive requirements. No 'a few renders'.
Source data.
CAD, drawings, dimensions, material spec, colourway list. Attached to the brief, not promised later.
Reference and mood.
Mood board and reference imagery describing what good looks like.
Timeline.
Launch day, embargo, review windows, fixed dates. Anything the schedule must fit around.
Success metrics.
How the finished render will be judged. Objective criteria beat subjective preferences.
Process
How the work is produced.
- STAGE 1
Start with product story.
Two paragraphs on the product, the audience and the launch objective.
- STAGE 2
List deliverables.
Exact counts, aspect ratios, resolutions. Every runtime, every runtime spec.
- STAGE 3
Attach source data.
CAD, drawings, dimensions, colourway list, material spec. Attached, not promised.
- STAGE 4
Build the mood board.
12 to 20 curated reference images with short notes on why each is on the board.
- STAGE 5
Lock the timeline.
Launch day, embargo, review windows, key dates.
- STAGE 6
Define success.
Objective criteria the final render will be judged against.
Who this is for
Built for teams making it happen.
Marketing, brand, and creative leads commissioning CGI. Agencies briefing CGI production on behalf of clients.
In-house creative teams sourcing outside CGI capacity. Founders and product leads commissioning launch content.
Case studies
Recent work.
Petalite EV charger. Full launch content set from one CGI build, applying the disciplines in this guide.
View case study
Sony WF-C710 wireless earphones. Techniques from this guide applied to hero animation and product imagery.
View case study
G-Lab gaming keyboard launch. One 3D build driving film, stills, and interactive content.
View case studyTestimonial
The team at XO3D were a pleasure to work with on one of our big product launches. They rendered, batched, and saved out literally thousands of images for us. Every single one came out perfect.
For sibling topics, see the 3D rendering buyer’s guide and mood boards.
FAQ
Common questions, answered.
How long should a project brief be?
As long as it needs to be to remove ambiguity. Typically 2 to 6 pages of structured content plus mood board and source data attachments.
Do I need to solve every design decision upfront?
No. Brief for the review window instead. Structured reviews at agreed milestones catch decisions that only become visible mid-project.
Can I brief without CAD?
Yes, but expect the modelling stage to take longer. Reference photography, drawings and physical samples are all valid sources.
Should I share budget in the brief?
Yes, ideally. Budget-known briefs get budget-appropriate quotes and scope. Budget-secret briefs waste everyone's time.
Working on a project?
Tell us about it.
Thomas or Alex replies personally, usually within one working day.