Archviz Render Revisions: How to Cut Rounds Without Cutting Quality
Archviz render revisions spiral when the note just says make it warmer. Here is the revision policy, the markup habit and the version compare I would use to keep rounds to two.
"The render of the living room should feel warmer, the evening shot looks a bit flat to me, and the sofa is not the one we picked, thanks!"
That is the whole email, right, typed at eleven at night after MV2 went out and a week after the client signed off on the camera set. It is a composite, to be fair, stitched from what lands in my own video agency every week and the render version archviz studio owners keep describing to me. Each clause is a different amount of work, because warmer is a lighting and grade call, flat is probably composition or exposure, and the sofa is an asset swap that forces a full re-render. That one message is basically why archviz render revisions quietly eat your margin, and to be very honest the client is not being difficult, she simply has no way to point at the thing she means.
I run PlayPause, and alongside it a video-editing agency and a personal-branding agency, so I sit on both sides of this every week, right, and the pattern is always the same one. The studio scopes three rounds, the client sends notes as prose, the artist interprets the prose, half of it is wrong, and you have burned a render pass to discover a misunderstanding. Nobody was rude and nobody argued, and still you end up on round five of a job you priced for three.
So here is how I would set this up if I ran an architectural rendering studio today, and you will notice it is mostly process, because the tooling only pays off once the process is in place.
Why archviz render revisions spiral
In my experience the spiral almost never starts with a demanding client, right, and what actually starts it is ambiguity, which is expensive in archviz because your unit of work is a render pass that takes hours on the farm. Say, purely as illustrative math, that a walkthrough has six cameras and a final-quality pass takes around five hours per camera. A single misread note that touches every camera then costs thirty hours of machine time plus the artist's evening.
There are basically three ambiguities doing the damage. The first is location, where the client says "the plant looks fake" and there are four plants across three cameras, so you either ask and lose a day or guess and maybe lose a night. The second is intent, because "warmer" could mean colour temperature, more practical lights switched on, or the oak tone on the floor. The third is status, where nobody knows whether Tuesday's note belongs to round one or opens round two, so the count drifts until everybody stops counting.
Archviz client feedback also tends to arrive across three channels at once, right, a WhatsApp from the car, an email thread with the architect copied in, and a marked-up PDF from the interior designer. Now you are reconciling three people who have not spoken to each other, which I covered in the piece on reducing rounds by centralising feedback.
Every note that does not name a frame costs you a render pass, so the fix belongs in your process long before it belongs in your invoice.
The catch here is that you cannot fix ambiguity by asking the client to be more thoughtful, because they simply do not have the vocabulary or the tooling, right, and expecting a property developer to write frame-level notes in prose is expecting a job nobody trained them for. You have to hand them a way to point.
Setting an archviz revision policy clients actually understand
Most studios already have a revision policy, and the trouble is that it lives in paragraph fourteen of a proposal PDF that nobody opened again after finding the price on page two. So at the exact moment the client is typing feedback, the policy may as well not exist.
What I would do is write it in plain language, keep it to five short lines, and repeat it in the proposal, on the kickoff call, and in a Playbook page shared right next to every review link. The five lines go something like this. Two rounds of revisions are included per camera. A round means one consolidated set of notes, sent together, on one version. Notes that change something we already agreed become a new request and get quoted separately. A round closes when you approve the version. Anything after approval starts a new round.
That last line matters more than people expect, right, because without it the client can approve MV2, sleep on it and reopen it on Thursday, and you have no clean place to say the round already closed. The long version of the wording is in what goes in a revision policy, and the archviz version is basically the same document with camera counts swapped in for video minutes.
- Name the frame or the timestamp
- Say what you want changed, not only what feels wrong
- Point to a reference if one exists
- Send everything in one pass, not five messages
That checklist lives in the client's Playbook. In PlayPause a Playbook is a per-client document of creative style and direction that you can share as a page the client reads without logging in, with checklists that are not done until someone actually ticks them. Brand playbooks hold the permanent rules, for instance "we never use warm white in the kitchen scenes", folder playbooks hold the rules for this specific development, and so on. Playbooks sit on Agency and up, and the effect is small and boring and very very real, because when those four lines are one click from the player instead of buried in a PDF, the notes that come back are far easier to act on.
Getting precise archviz client feedback by drawing on the frame
If I could change only one habit in an archviz studio it would be this one, right, where instead of asking the client to describe where the problem is, you let them circle it.
In PlayPause the client opens one link in a browser, no account and no install, scrubs the walkthrough, pauses on the exact frame, circles the chair and types "this one, we picked the other fabric". The comment is frame-accurate and timestamped, so it sticks to that frame instead of floating in a thread, and your artist finds the note sitting on the picture. The full toolset is on the drawing and markup tools page, and the archviz version is on the review built for architectural visualization page.
the artist guesses which frame and which chair
the comment sits on the frame with a circle around the chair
Stills take markup the same way, but a walkthrough is where this really pays. The client who says "around the middle it looks off" might mean frames 340 to 395, which at 25 frames per second is a little over two seconds of a dolly move you would never have found from prose, and a range comment covers exactly that stretch. I went deep on that problem in mark up one camera angle, which is worth reading if your deliverables are mostly animation.
A quiet benefit, and I'm pretty sure it is underrated, is that drawing makes clients slower and more deliberate, so you tend to get four real notes instead of eleven vague ones, with threaded replies and @mentions keeping the architect and the designer in one place.
Frame-accurate note, everyone sees the exact same thing.
Separating a revision from a new request
This is where the money is, and to be very honest it is the conversation most studio owners avoid because it feels confrontational, when really it only needs one sentence said early and said calmly.
A revision is a fix to something we already agreed, and anything else is a new job with a new number.
Sorting the eleven o'clock email, clause by clause
Here is how that sentence handles the email I opened with. "Warmer living room" is a revision if the agreed brief was a warm evening mood and the render came out cool, because you are bringing your work back to the agreement, and with split passes you might fix it in the grade without touching the farm. "The evening shot looks flat" is not actionable yet, so it is neither a revision nor a request until the client circles the area and points to a reference, and you say exactly that before anyone renders anything. "The sofa is not the one we picked" sends you to the locked moodboard, where a boucle sofa on the approved board and a leather one in the render means the revision is on you, while a change of heart since approval means a new request with a number.
So the vague round turns into a short reply that confirms the warmth fix, asks her to circle the flat area, and checks the sofa against the board before quoting anything. You see what I mean here, the client usually agrees the moment it is laid out like that, because you are pointing at what was agreed rather than arguing about hours. I keep a running line in each client's folder playbook recording what was locked and when, which is really the same discipline as version control in software applied to creative decisions. The full wording sits in revision versus a new request, and the awkward billing half is in how to charge for extra rounds.
If you outsource part of your pipeline this gets sharper, because your outsourced artist needs the same definition you gave the client, or the ambiguity just moves one layer down, a real scope creep trap I have walked into myself with freelance editors. On Agency and up a freelancer can send their pass through guest version upload, with name and email collected, and the wider argument is in outsourcing architectural rendering without losing control.
Tracking render revision rounds with custom statuses
Counting rounds in your head does not survive contact with four live projects, right, so the count has to live on the card where everyone can see it.
In PlayPause you define your own custom statuses, and I would set them to read something like Internal Review, With Client, Round 1 Notes In, Round 2 Notes In, Approved and Out of Scope Requested. Anyone on your team can tell at a glance where a camera stands, and when the client asks how many rounds are left you read it off the card instead of reconstructing the history from memory. Versions stack on the same card as MV1, MV2, MV3 and MV4, so there is no file called final_final_v3_REAL anywhere.
If you worry about renders leaving the building, password-protected links that you can revoke instantly cover most of it, and the rest is in share 3D renders without downloads, where clients watch from a streaming copy while your original stays untouched.
Proving the fix with side-by-side version compare
Half of round three exists because the client cannot remember what round two looked like, right, so they open MV3, the sofa looks fine, and with no memory of the old one they re-raise a note you already closed.
Side-by-side version compare is how I would end that loop, because on Agency and up you put MV2 and MV3 next to each other on the same frame and the client sees the change for herself. Pair it with who-watched analytics, which shows who opened the link, when, and from which city, and you know whether the architect looked before the Friday meeting.
Does that make sense, right, because every section here is really one idea repeated, which is that you remove the guess, and at the end of the day every guess you remove is a render pass you never spend. The general version of this approach lives on the cut four rounds down to two page, and the animation studio version of the counting question is in how many revisions to offer.
Frequently asked questions
How many revision rounds should an archviz studio include?
Two consolidated rounds per camera is what I would scope, while most of the industry writing you will find quotes three. The number matters far less than the definition, honestly, because two tight rounds with frame-level notes beat three loose rounds of prose, and trust me on any level, the studios complaining loudest about revisions are rarely the ones with a low round count.
Can clients comment on renders without creating an account?
They can, and that is basically the point of the model, because the client opens one share link in a browser with no account and no install, then scrubs, pauses, draws on the frame, leaves a timestamped comment and replies in a thread. Nothing breaks if they never sign up, and the moment you put a signup wall in front of feedback you lose the architect who only ever looks at two frames.
What do I do when a revision is really a new request?
Name it immediately and quote it, because the longer you sit on it the more it feels like you agreed. I point at the Playbook line that recorded what was locked, say the one sentence about fixes versus new jobs, and send a number the same day, and in my experience clients accept this far more often than studio owners expect, since most of the awkwardness sits on our side.
Does PlayPause work for still renders or only animation?
It works for both, so stills upload the same way and take the same frame markup and threaded comments, and bulk upload handles a hundred plus files for a full set of interiors. Animation also gets range comments across a camera move, and since pricing is flat per workspace rather than per member, bringing the architect and the interior designer in as members adds no per-person charge.
If you want to try this on your next set of cameras, every plan has a 7-day free trial, and the pricing page lays out what Creator, Agency and Enterprise each include. Start with one project, put the four-line checklist in that client's Playbook, and count your rounds honestly for a month, because that number on its own will tell you where the margin has been going.
So yeah. That's my way of saying it.
Saumyajit co-founded PlayPause after years watching review and approval quietly eat creative teams' deadlines. He writes about the workflow side of video, feedback, versioning, and getting to a clean sign-off.
Related resources
Keep reading
Bring your team into one review space
Centralize feedback, lock approvals, and deliver faster, start free today.
Sign Up for Free