Why rendering reviews go sideways
A rendering review looks simple. The studio sends an image, the team sends comments, the studio sends it back. In practice, a single view can collect notes from the developer, the architect, the interior designer, the landscape architect, the marketing agency and the sales lead. They arrive by email, text and phone, some on a PDF with red circles, some as "make it feel warmer". A few contradict each other.
The studio then has three choices, all bad: make every change and undo half of them next round, stop and ask, which costs days, or guess. Meanwhile, somebody forwards the first draft to a broker, and it turns up in a newsletter.
None of this is about the quality of the image. It is about how a team gives feedback. The fix is a small set of habits, and a place to practise them.
Who looks at what
Developer
Images that sell the project and match what will be built.
One decision-maker who gives the final yes and settles conflicts.
The developer's reviewer sees every comment and approves the version, on the record.
Architect
An accurate building: massing, openings, materials, details.
Accuracy checks early, before styling is polished.
The architect marks errors on the image itself, pinned to the exact window or railing.
Interior designer
Finishes, furniture and lighting as specified.
The finish schedule and selections before the interior is lit.
Comments on a material sit next to the product reference, so the fix is exact.
Landscape architect
Planting, paving and grades that match the landscape plan.
The plan with species and sizes, and realistic growth assumptions.
Planting notes are pinned where the planting is, not described in a paragraph.
Marketing and sales
Mood, lifestyle, crops for each channel, and images that answer buyers' questions.
Styling notes consolidated into one voice.
Marketing comments on the same image as the architect, so style never overrides accuracy by accident.
Studio
One clear list per round, with conflicts resolved before it arrives.
Each change shown on the next version, with a note on what was done.
Each round is a numbered version, compared side by side with the last.
Markup on the image, not in a paragraph
- 01
Pin the comment to the spot
"The railing on the third floor, left balcony, should be glass" takes the studio a minute to find. A pin on that railing takes a second. Markup on the image removes the translation step, and the translation step is where errors come from.
- 02
One comment, one change
Keep each comment to one thing. A pin that says "glass railing, warmer light, lose the car, and is this the right brick" is four comments, and one of them will get missed.
- 03
Say what, and why
"Brighter" can mean exposure, colour or time of day. "Brighter, it reads too gloomy for a spring hero" tells the studio which. Reference images help more than adjectives.
- 04
Separate errors from preferences
An error is when the image does not match the drawings. A preference is taste. Label them. Errors are fixed without debate; preferences go to the decision-maker.
- 05
Comment on video at the moment
For film, pin the comment to the time in the clip, not "about halfway through". Review in StudioLink supports comments pinned to a moment in the film.
One voice per round
The single biggest improvement a team can make is to name one person who consolidates comments before they go to the studio. That person reads every note, removes duplicates, resolves conflicts or escalates them, and sends one list.
Conflicts are normal. Marketing wants the sun low and golden; the architect wants the façade legible. The consolidator's job is not to pick a side quietly. It is to put the conflict in front of the decision-maker once, get an answer, and record it, so it does not come back next round.
Set a comment window. Everyone reviews between the day the version arrives and a fixed close. Late comments go into the next round, not into the middle of this one. Studios can work fast when the list is complete; they slow down when it keeps growing.
When everyone comments on the same image in one place, consolidating becomes reading down a thread instead of merging five emails. That is what the review in our order and review module is for, and it is live today.
Keep the rounds counted and the versions straight
- 01
Agree the rounds in the scope
Most scopes include a set number of revision rounds. Know how many you have and what counts as one. A round is one consolidated list and one new version, not every email.
- 02
Review accuracy first, polish later
Use the first round for the building: massing, openings and materials. Use later rounds for light, landscaping, people and mood. Polishing an image that still has the wrong window pattern wastes both rounds.
- 03
Number every version
Name each version by round, and keep the old ones. When someone asks why the balcony changed, the answer is in the history.
- 04
Compare side by side
Put the new version next to the last and check that every comment was addressed. It is faster than rereading the whole thread.
- 05
Do not reopen closed decisions
If a point was decided and recorded, it stays decided unless the decision-maker reopens it on purpose. Reopened decisions are where extra rounds come from.
Who decides, and how it gets recorded
Someone has to be able to say yes. On most projects that is the developer or their marketing lead for marketing images, with the architect's sign-off on accuracy as a condition. For council images, the architect and planning consultant usually lead, because accuracy is the whole point. Decide this before the first round, write it down and tell the studio.
The approval itself should live on the image: which version, who approved it, and when. An approval in an email reply is hard to find later and easy to dispute. An approval on the record means the approved file is the one everyone uses, from the website to the sales centre screens to the broker kit.
That record matters beyond the launch. When the design changes in construction, you can see exactly which marketing images show the old version and replace them. Marketing images that no longer match the approved design are one of the most common ways a presale loses buyer trust.
When to talk instead of type
Written comments on the image work for most rounds. Some decisions need a conversation: a conflict between marketing and the architect, a camera angle nobody likes, or the first look at a hero view. A short review meeting with the image on screen settles in fifteen minutes what an email thread drags out for a week.
Keep those meetings small: the decision-maker, the architect and whoever raised the issue, with the studio present. Walk the image, agree the change, and have someone type the outcome as pins on the image before the call ends. A decision that lives only in people's memory of a call will be remembered three different ways.
In StudioLink, meetings run in the browser and the notes land on the project, next to the images they are about. Manage is live today.
A review checklist for every round
- ✓Does the building match the current drawings: massing, openings, balconies, rooflines?
- ✓Are the materials and colours the ones in the finish schedule?
- ✓Does the landscaping match the landscape plan, at a believable size?
- ✓Is the camera where a person could stand, at a believable height and lens?
- ✓Do the people, cars and furniture suit the neighbourhood and the buyer?
- ✓Is the time of day and season right for where this image will be used?
- ✓Are there any errors in the context: wrong neighbour, missing street tree, wrong view?
- ✓Is every comment pinned, labelled as an error or a preference, and consolidated?
- ✓Has the decision-maker seen the conflicts and ruled on them?
- ✓Is the version being approved the one that will be published?
Set the review up in five minutes
Before the first image arrives, send the studio three things: the name of the decision-maker, the list of reviewers with what each one is checking, and the comment window. It takes five minutes and saves a round.
Then agree with the studio how many rounds the scope includes and what happens if you need more. Knowing the budget for rounds keeps everyone disciplined. Our guide to what drives the cost of a rendering explains why late and conflicting comments are one of the biggest drivers of cost.
Familiar failures, and the fix
Wrong version in circulation
An early draft gets forwarded and used in a campaign. The finish shown is not the finish being built.
Only approved versions are marked approved, and share links point to the current approved set.
More →Scope changes by phone
A new view is added in a call. Nobody updates the scope, and the invoice surprises everyone.
Changes are re-scoped in StudioLink before work starts, on the same record as the review.
More →The architect never saw it
Marketing approved a view without an accuracy check. The architect finds the error on the hoarding.
Invite the architect to the same review. Their accuracy sign-off is part of the approval.
More →Questions
How many revision rounds are normal for a rendering?+
Most scopes include a set number of rounds, often enough for an accuracy pass and a styling pass. The number matters less than how clean each round is. One consolidated list per round keeps it to the rounds you agreed.
Who should approve architectural renderings?+
One named decision-maker, usually the developer or their marketing lead, with the architect's sign-off on accuracy. For council images, the architect and planning consultant usually lead.
How do I give feedback on a rendering?+
Pin each comment to the exact spot on the image, one change per comment, and say why. Separate errors, where the image does not match the drawings, from preferences.
Can our architect and marketing team comment on the same image?+
Yes. In StudioLink everyone invited comments on the same image, and every comment is kept with the version it was made on.
Can you mark up a video?+
Yes. In StudioLink comments on a film pin to a moment in the clip, so the studio sees exactly which frame you mean.
What counts as a revision round?+
Usually one consolidated set of comments and the new version that answers it. Ask your studio to define it in the scope, so late or scattered comments do not quietly add rounds.
What is the best way to share renderings for team review?+
Put the image in one place where everyone invited can see it and comment on it directly, instead of attaching it to an email. That keeps every comment with the version it was made on, and it means nobody reviews an outdated file by accident.
How do I stop old renderings being used?+
Approve on the record and share links to the current approved set instead of attachments. When a design changes, you can see which images show the old version and replace them.
