How to Brief a Render Studio (And Get Exactly What You Need)
- Pedro J. López
- 2 days ago
- 7 min read
You've hired a render studio before. You sent the files, explained what you wanted, and waited. And when the first draft arrived, something was off — the atmosphere wasn't right, the materials felt off, the image didn't say what your project says.
The problem probably wasn't the studio. It was the brief.
A clear brief is the single biggest factor in getting renders you're proud of. Not the budget, not the software, not even the studio's portfolio. We've seen modest budgets produce remarkable images when the brief was sharp — and generous ones produce forgettable ones when it wasn't.
After over a decade collaborating with architecture firms across Europe, we've seen every type of brief. This guide breaks down exactly what to include, in what order, so you stop leaving the result to chance.
Why Most Briefs Fail Before the Work Begins
When architects tell us a previous render studio didn't deliver, the complaint is usually about quality. The atmosphere was wrong. The materials felt off. The image didn't capture the project.
But when you trace it back, the root cause is almost always the same: the studio didn't have enough information to make good decisions. So they made assumptions. And assumptions, however reasonable, are rarely what you had in mind.
These are the four gaps we see most often:
Incomplete files. Floor plans without sections, sections without elevations, no site context. The studio has to guess — and guessing leads to corrections that eat up your revision rounds.
No visual references. "We want it to feel warm and contemporary" means something different to everyone. Without references, those words are almost useless.
No stated intent. What is this render for? A competition jury, a client presentation, a real estate brochure? Each requires a fundamentally different approach — and if you don't say, the studio will default to what they think looks good, not what you need.
None of these are failures of talent on either side. They're failures of process. And the good news is that process is entirely within your control.
The Five Things Every Brief Needs
1. The project files — complete and final
Before you send anything, make sure the information is definitive. This sounds obvious, but it's where most projects go off track. If your floor plan is still changing, if the façade hasn't been resolved, if you're still deciding on the structural system — wait until those decisions are made.
Starting a render on an unfinished design almost always means rebuilding it later, which costs time and money that a little patience upfront would have avoided entirely.
When you're ready, send everything: floor plans, sections, elevations, site plan, and your 3D model if you have one. Make sure the model is complete and the geometry is clean — a model with missing faces, inconsistent levels, or unresolved details will slow the process down.
On file formats: before you export anything, tell us what software you used during the design process. Every studio has its own workflow, and the right export format depends on where your files are coming from. We'll guide you through exactly how to export your files to ensure full compatibility with how we work — which saves both of us from the frustration of receiving something we can't open or that loses information in translation.
What to do first: tell us your design software (ArchicadCAD, Revit, Rhino, SketchUp, AutoCAD, etc.) and we'll tell you precisely what to send and how.
2. Visual references — at least five
This is the single most underused part of a brief, and the one that makes the biggest difference.
You don't need to find renders that look exactly like what you want — in fact, it's better if you don't. Instead, find images that capture the feeling you're after. A photograph with the right light. A render from another project with the right atmosphere. An interior from a magazine that shows the materiality you're thinking about.
Send them with a short note on what you like about each one. "I like the quality of light here" or "this is the atmosphere we want, but our building is more restrained" tells us far more than the image alone.
What to send: 5–10 images from any source — renders, photography, collages — with brief annotations.
3. The brief itself — what this render needs to communicate
This is where most architects stop too soon. They describe the project — the typology, the program, the materials. What they don't say is what the render is actually for.
Who is going to see this image? What decision are they making when they see it? What do you want them to feel?
A render for a competition jury needs to communicate concept and atmosphere in seconds — it will be seen alongside dozens of others in a single session. A render for a client presentation needs to make someone feel comfortable spending money. A render for a real estate brochure needs to make someone want to live there.
Same building. Completely different images. If you don't tell us which one you need, you're leaving one of the most important decisions to chance.
What to include: intended audience, purpose of the render, key message you want it to convey.
4. Views and framing — your instincts matter
You know your project better than we do. If you have a sense of which angle shows the building at its best, tell us. If there's a specific moment — a corner, an entrance, a relationship between interior and exterior — that you want to capture, say so.
We'll always suggest alternatives if we think there's a stronger view, but starting from your instinct saves time and gets us closer on the first pass.
What to include: rough sketches or screenshots of the views you have in mind, compass orientation, preferred time of day.
5. Timeline and budget — upfront, not at the end
These two things shape every decision a studio makes about how to approach your project. A generous timeline allows for more iterations and creative exploration. A tight one means fewer revision rounds and more precision from the start.
Budget works exactly the same way. Being clear about what you're working with isn't a negotiation weakness — it's information that helps the studio propose the right scope. If you say you have €800 for two renders, a good studio will tell you honestly what's achievable. That's a far better conversation than discovering the mismatch on day three.
The architects who get the best results are the ones who treat the studio as a collaborator from the first email, not a supplier to be managed.
What to include: delivery deadline, number of revision rounds expected, approximate budget range.
The One Question That Changes Everything
Before you send the brief, ask yourself this: If someone who has never seen this project looks at the render, what do I want them to understand in the first three seconds?
Write down that answer — one sentence. Put it at the top of your brief. Everything else you send supports that sentence.
We call it the key message, and it's the single thing that separates briefs that produce memorable images from briefs that produce technically correct ones. When we have it, we make better decisions at every step — about light, framing, atmosphere, and the human elements that make a render feel alive rather than empty.
When we don't have it, we make our best guess. And our best guess is never as good as your actual intent.
💡 Want a ready-to-use template that covers all of this? Download our free Render Briefing Checklist — a one-page document you can fill in and send directly to any visualization studio. Download it here →
How to Handle Revisions Without Losing Time
Even with a great brief, revisions happen. The difference between a smooth revision round and a frustrating one almost always comes down to how the feedback is delivered.
Be specific. "I don't like the light" gives a studio almost nothing to work with. "The shadows are too harsh — I'd like a softer, more overcast quality, closer to reference image 3 from the brief" is something we can act on immediately.
Consolidate your feedback. Send all revision comments in one message, not across a series of emails over several days. Every round of back-and-forth adds time to the project. One clear, complete note at each stage keeps things moving.
Know the difference between a correction and a change. A correction is something that doesn't match what was agreed in the brief. A change is something new you want to add or modify. Both are valid — but they have different implications for time and sometimes cost. Being clear about which is which prevents misunderstandings that slow everything down.
A Note on Working with Studios Remotely
Most of our collaborations happen entirely online — with firms in Switzerland, Germany, France, the Netherlands, and beyond. Remote workflows work well when the brief is strong. They fall apart quickly when it isn't, because there's no informal conversation to fill the gaps.
If you're working across time zones, invest a little more in the written brief.
A 30-minute video call at the start of the project — to walk through the files, align on references, and agree on the key message — is worth more than any number of revision rounds later. It also builds the kind of working relationship where honest feedback flows both ways.
One habit that consistently makes remote collaborations smoother: build in a checkpoint after the first draft before the project moves to final. A short call or a structured feedback exchange at that stage catches misalignments early, when they're still easy to fix.
FAQs
How detailed does a render brief need to be?
Detailed enough that the studio can make good decisions without having to guess. You don't need to write an essay — a clear set of files, five or more visual references, a one-sentence key message, and the practical details (deadline, budget, number of views) will get you most of the way there.
What if my design isn't finished yet?
Send what you have and be explicit about what's still being developed. A good studio will work with incomplete information and flag what they need. The problem isn't an unfinished design — it's an unfinished design presented as if it were complete.
How many visual references should I include?
At least five, ideally with short annotations. More is fine. The goal is to give the studio a clear sense of the atmosphere and materiality you're after — not to find images that look exactly like your project.
What's the most common briefing mistake architects make?
Not explaining what the render is for. The same project can require very different images depending on whether they're for a competition, a client presentation, or a marketing campaign. Always tell the studio who will see the render and what decision they'll be making.
Should I send a 3D model if I have one?
Yes, always. Even a rough model is useful — it gives the studio a starting point and reduces the risk of misinterpretation. If your model has geometry you're not sure about, flag it. We'd rather know upfront than discover it mid-project.
Related reading:
Comments