← Back to Blog

Rendering Brief Template for Architects and Developers

Rendering Brief Template for Architects and Developers

Rendering Brief Template for Architects and Developers

Architectural sketch elements framing a clear title area

A good rendering brief answers ten questions before the studio opens a file: what the images are for, who will see them, which views you need, what the studio receives from you, which materials are locked, what mood you want, what you get back, when, who approves, and what it costs. Below is a template built on those ten sections, a fill-in version you can paste into an email, and notes on how to adapt it for stills, walkthroughs and VR.

We write this as a studio that receives briefs every week. The projects that go smoothly are rarely the ones with the biggest budgets. They are the ones where the brief settled the decisions early.

Rendimension
rendimension.com
Turn a Clear Brief Into Clear Visuals
Rendimension creates architectural visualizations, renderings, walkthroughs and virtual reality experiences with client involvement from concept to final delivery.
Explore visualization services

TL;DR

  • A brief should state the purpose of the images first (zoning approval, pre-sales, investor deck), because that sets the style, the views and the level of detail.
  • Send drawings, a model if you have one, material callouts and reference images together. Missing inputs are the most common cause of delay.
  • Name every deliverable: scenes, camera views, resolution, file format, delivery method and revision rounds.
  • Match the brief to the design phase. A schematic design brief and a design development brief ask for different things.
  • Follow the written brief with a short call. Email alone rarely carries mood and intent.

Table of Contents

Why a brief decides how many revisions you pay for

Most rework is not a technical problem. It happens when the picture in your head and the picture in the studio’s head were never compared. A brief is the cheapest place to compare them.

The AIA makes the same point about design phases. Its guidance advises that once schematic design or design development begins, the team should set out clearly stated deliverables and share them with all stakeholders, so nobody is surprised by what a phase’s visuals include. The same applies to a visualization studio. If the owner expects a marketing-grade twilight exterior and the studio understood a massing study, no one made a mistake. The brief just did not say.

There is also a scope problem. Clients often have no clear idea of what the final deliverables will be until they are handed over. AIA best practice is for the architect and the visualization team to agree on a list of deliverables consistent with the project’s objectives. Written scopes work the same way in other trades. A scope-of-work guide for roofing projects shows how a written scope heads off disputes about what was and was not included, and the logic carries straight over to renderings.

The rendering brief template

Ten sections. Short answers are fine. Where you do not know yet, write “open” and say who decides and by when. An honest “open” is more useful to a studio than a guess.

1. Project snapshot

Give the basics in four or five lines:

  • Project name, address or city, and building type (multifamily, mixed-use, custom residence, office, hospitality)
  • Size: floors, unit count or square footage
  • Design phase: schematic design, design development, construction documents or built
  • Your role (architect, developer, builder, agency) and who else is on the team
  • A single point of contact who can answer questions within a day

The phase matters more than people expect. In schematic design, the visuals usually illustrate concept, scale and spatial relationships, which is why AIA’s schematic design checklist lists project images and renderings that clearly depict the design among the phase objectives. By design development, the AIA’s description of basic services points to fuller dimensions, material specifications and partition types. A brief that states the phase tells the studio how much detail to trust in your drawings and how much to resolve itself.

2. Purpose and audience

This is the most important section and the one most often skipped. Answer in plain sentences:

  • What decision should these images support? A planning commission hearing, a lender presentation, pre-sales, a leasing brochure, a design review with the owner?
  • Who will look at them, and for how long? A board member who sees one image for ten seconds needs different composition than a buyer browsing a website.
  • Where will they appear? Print, website, billboard, social, a sales gallery screen?

If the images are for marketing, say who the buyer or tenant is. Industry guidance from SMPS says marketing assets work best when they show people and lifestyle cues, not only the structure. A studio cannot add the right people, props and time of day if the brief never mentions the audience.

3. Views and scenes

List every image you want, one line each. For each, give:

  • Type: exterior, interior, aerial, amenity, street-level
  • Location of the camera, ideally marked on a plan or site plan
  • Time of day and season (golden hour, overcast, twilight, winter)
  • Priority: hero image or supporting image

A scene is one space or building condition. A view is a camera angle within it. The distinction matters for budget: a studio typically prices the scene and then each extra angle. Our published pricing follows that logic, with architectural rendering from $850 per scene and an additional camera view from $425 per view. Marking views on a plan lets you see the count before you ask for a quote.

4. Source files

List what you are sending and its status (current, outdated, preliminary):

  • Plans, elevations, sections and the site plan, as PDF and CAD
  • 3D model if you have one: Revit, SketchUp, Rhino, ArchiCAD or similar
  • Survey or topography, landscape plan, and any context photos
  • Material and finish schedules
  • Logo, brand colors and any fonts for overlays

Say which file is the source of truth if drawings and the model disagree. If you have no model, say so. Studios build models from drawings every day, but they need to know at the start.

5. Materials and finishes

Separate the decided from the undecided. For each major surface (facade, roofing, glazing, paving, interior flooring, millwork, countertops) give a manufacturer and product name, a sample photo, or a plain description. Mark anything still being chosen as “studio to propose.”

Architectural finish samples showing varied surfaces

This is also where you list products you must show accurately, such as a specific window system or a sponsor’s fixtures. If a fixture is only decorative, say that too, so the studio does not spend hours matching it.

6. Mood and style

Words are weak here, so send references. Three to six images are enough, each with a one-line note on what you like about it: the light, the camera height, the planting, the color grade, the amount of people.

Then state the direction in plain terms: warm and residential, crisp and corporate, moody evening, bright coastal. Say what to avoid. “No heavy sunset saturation” saves a round of changes. If the project is luxury residential, describe the lifestyle you want the viewer to picture, not just the finishes.

Some firms go further and develop a signature look. Visual designer Luis Bertomeu Sanchez suggests that, with photorealism now standard, a distinctive visual style can help a proposal stand out. If you want that, say so in the brief. It changes the entire approach.

7. Deliverables

Be specific about what comes back:

  • Number of final images and which views
  • Resolution and aspect ratio for each use (print versus web)
  • File format (JPG, PNG, TIFF, layered PSD if you want to edit)
  • Delivery method, such as a secure download link, and how long the link stays active
  • Any extras: alternate times of day, a version without people, a floor plan or site plan rendering

SMPS guidance on visual assets notes that a complete brief should specify format, resolution and delivery method, to reduce rework. Also state usage rights: where and how long you may use the images. We cover that in more detail in our piece on 3D rendering deliverables and use rights.

8. Schedule

Give the hard date and what it is tied to: a hearing, a sales launch, an investor meeting. Work backward and include your own review time. A schedule that assumes feedback in an hour is not a schedule.

A workable skeleton:

  1. Kickoff and brief confirmation
  2. First look: gray-model or draft views to check camera, massing and composition
  3. Material and lighting pass
  4. Final review round
  5. Final delivery

Say in advance if the design may change mid-project. Then the studio can phase the work so the early stages are cheap to redo.

9. Review and approvals

Name the people who give feedback and the one person who consolidates it. Conflicting comments from five reviewers are the most reliable way to burn through revision rounds.

State how many rounds the project includes and what counts as a round. A good rule: early-stage changes (camera, massing, composition) are cheap, late-stage changes (materials, layout) are expensive. Ask reviewers to concentrate their comments in the first look, and to limit the final round to polish.

Early and late rendering changes compared by cost

10. Budget and usage

Share a budget range or a ceiling. It lets the studio recommend the right approach rather than quote a scope you cannot afford. Say whether you expect a single project or an ongoing series, since multi-building programs and multi-location clients are often better served by a retainer than by one-off quotes.

For orientation, our published walkthrough pricing runs from $4,500 to $8,000 depending on scope. VR experiences, product visualization and full packages are quoted per project. Your brief is what makes that quote accurate.

Fill-in version you can paste

Copy the block below into an email or shared document and replace the bracketed text. Each line maps to one section above.

  • Project: [name, address, building type, size, design phase]
  • Contact and approver: [name, email, phone, who signs off]
  • Purpose: [the decision these images support, and the deadline]
  • Audience and channel: [who sees them, where: print, web, sales gallery, hearing]
  • Views: [number of views, type of each, camera positions marked on the attached plan, time of day]
  • Files attached: [plans, model, survey, landscape, finish schedule, brand assets, and which is the source of truth]
  • Materials: [decided items with product names, items for the studio to propose]
  • Mood references: [3 to 6 images, one note each, plus what to avoid]
  • People and props: [none, light, lifestyle-focused, describe the buyer or tenant]
  • Deliverables: [final image count, resolution, format, delivery method, link lifetime, extras]
  • Schedule: [kickoff date, first look, final deadline, your review turnaround]
  • Reviews: [number of rounds, who consolidates comments]
  • Budget and usage: [range or ceiling, where the images will be used and for how long]

If you want a second reader before you send it, our architectural visualization checklist covers the presentation side of the same decisions.

What changes by project type

The template holds for most projects. A few sections shift depending on what you are making.

Pre-construction marketing for developers. Sections 2 and 6 carry the weight. Describe the buyer, the neighborhood and the lifestyle story. Ask for amenity spaces, street-level views and a twilight hero. Plan the image set alongside the launch calendar.

Approval and entitlement images. Section 3 and the schedule dominate. Planning boards want accuracy, context and clear scale, so send the survey and site plan and ask for views that match the vantage points the board will care about.

Interiors. Section 5 grows. Furniture, fixtures, lighting and finishes need to be itemized or referenced. Say whether the design is final or the studio should style the space.

Walkthroughs and animation. Add the route, the length, the pace, music or voiceover needs, and the output format. The brief should state whether the film is for the sales center, a website or a presentation. For a sense of what is involved, see our 3D walkthrough services. Immersive formats also change how stakeholders respond: VR in design presentations can make a concept clear to people who struggle with plans.

360 tours and VR. Specify the headset or platform, whether the viewer moves freely or follows hotspots, and how clients will access it. Our 360° virtual tours page describes the format.

Product visualization. Replace views with product angles, add CAD or engineering files, and specify backgrounds, colorways and any exploded or cutaway views.

Brief by email, or brief on a call?

Both. The written brief carries facts. The call carries intent.

AIA’s guidance on hiring a photographer, which applies equally to any visual consultant, describes the brief as the way to get your expectations met: the clearer the brief, the better the match. Email alone is rarely enough to settle file formats, mood and the story a picture needs to tell. A 30-minute call covers all of that and gives the studio a chance to repeat back what it heard.

Use the call to settle four things before the first preview: the goal, the views, the style and the materials. Then send a short written recap so everyone has the same version.

Our perspective

We have completed more than 1,000 projects for architects, developers and builders, and the pattern is consistent. Projects go wrong at the start, rarely in production. A brief that says what the image must do, for whom, and by when, removes most of the later friction.

We would rather ask you ten questions on day one than redo a scene on day ten. That is why our process involves you from concept to final delivery, with feedback invited at every stage. We also push clients to hold back material decisions until they are real, because a rushed finish choice in the brief often becomes a late revision.

If you take one thing from this template, take section 2. Tell us what the image is for. Style, views and detail follow from that, and we can propose better options when we know the real goal.

, Rendimension

Ready to send your brief?

If you have a draft brief, or only plans and a deadline, send it to us. We turn it into a clear scope and quote covering architectural rendering, full visualization packages, 3D floor plans and site plan rendering, walkthroughs and VR. Architectural rendering starts from $850 per scene, and we price larger packages per project.

FAQ

How long should a rendering brief be?

One to two pages of text, plus attachments. The goal is to cover all ten sections briefly, not to write an essay. Reference images and marked-up plans do more work than long paragraphs.

Do I need a finished 3D model to brief a studio?

No. Many projects start from drawings, and studios build the model. Say in the brief which files you have and which is the source of truth. If you do have a Revit or SketchUp model, send it with the drawings.

What should I include if the design is still changing?

State what is fixed and what is open, and who decides the open items. Ask for a first look in rough form so changes happen before final lighting and materials. Tell the studio your likely change areas so it can structure the work around them.

Can the same brief be used for stills and a walkthrough?

The core sections are the same: project, purpose, files, materials, mood and schedule. A walkthrough adds the route, duration, pacing and output format. It is best to brief them together if you want a consistent look across both.

Sources