What Happens When a Client Approves Your Grade on an Uncalibrated Laptop Screen

A client opens your grade on a MacBook Air at a coffee shop, in direct sunlight, on a screen that's been running at whatever brightness it happened to be set to since the last time they adjusted it, taps approve, and three weeks later the spot airs and their phone starts buzzing because the skin tones look sickly and the blacks look crushed on the broadcast monitor at their office. The grade didn't change between approval and air, the screen did, and now you're explaining why the thing they signed off on doesn't look like the thing that's live, a genuinely unfair position for a colorist, but a predictable one, and we built viewing guardrails into PlayPause because this exact scenario kept showing up in support conversations.

Approved Doesn't Mean Seen Correctly

Here's the thing that's hard to explain to a client who isn't a colorist, a laptop screen at max brightness in a sunlit room and a calibrated broadcast reference monitor in a dim room can show two visibly different images from the exact same file, sometimes different enough that a grade that looks warm and rich on one looks flat and muddy on the other. Rec. 709 and the various broadcast delivery specs exist precisely because color has to travel predictably from the room where it was graded to the room where it's watched, and a client casually reviewing on whatever device is in front of them at the moment skips every part of that chain that makes the prediction hold. Basically, the approval is real, the client did click the button, but what they approved and what they'll eventually judge you against might not be the same image at all.

Why This Almost Never Comes Up Until It's a Problem

Most projects go through review without anyone thinking about viewing conditions at all, because most of the time it doesn't matter enough to notice, a slightly-off preview on a laptop rarely tanks a project. The cases that turn into real disputes tend to be higher stakes ones, broadcast spots, anything airing on a calibrated reference monitor at a network, projects where the client's own brand guidelines are strict about color accuracy. That's exactly why it's easy for a studio to go years without a real incident and then get blindsided the one time it actually counts, on the one client with an in-house broadcast standards team checking the delivered master against what they remember approving.

What a Guardrail Actually Looks Like in the Review Step

The fix isn't asking every client to buy a calibrated monitor, that's never going to happen and it's not a reasonable thing to expect from someone approving a thirty second spot. The fix is building a nudge into the review step itself, a note attached to the approval action that flags the viewing conditions this grade was finished under, dim room, calibrated reference display, and asks the client to at least approximate that, low brightness, no direct light on the screen, before they hit approve on anything going to broadcast. It's a small friction point, but it does two things at once, it improves the odds the client actually sees what you intended, and it creates a documented moment where the studio flagged the risk, which matters enormously if a dispute happens anyway.

The Phone-on-the-Subway Version of This Problem

Laptops in coffee shops are actually the mild case, the harder one is a client approving a grade on their phone during a commute, screen brightness cranked to fight the sun, watching at a fraction of the intended size with compressed streaming quality on top of everything else. We see this constantly with agency clients specifically, they're busy, the approval request lands between meetings, and the fastest path to "approved" is opening it on whatever device is already in their hand. There's nothing wrong with wanting fast approvals, speed matters and a studio shouldn't make clients jump through hoops for routine sign-off, but a broadcast-bound color pass genuinely isn't routine, and treating it like every other approval in the queue is exactly how a studio ends up eating the cost of a color pass that has to be redone, or worse, defending a grade that never actually had a fair viewing in the first place.

Documentation That Protects You After Broadcast

If a client does come back after air claiming the grade looked wrong, the studio's position is entirely different depending on whether there's a record of what was communicated beforehand. "We told you to review in a dim room on your best available display, here's the timestamped note we attached to the approval" is a defensible position. Silence on the topic, with nothing but a stamped approval and a client who's now certain something changed between sign-off and delivery, is not. This is the same instinct behind why studios need timestamped, documented revision rounds for billing, the pattern repeats, whatever a studio can't prove didn't happen, a client will eventually assume didn't happen the way the studio says it did.

Setting the Expectation Before the First Cut, Not After the Complaint

Sound familiar if you've ever had to have this conversation for the first time in the middle of a client dispute, trying to explain color science to someone who's already upset? It goes a lot better when it happens at kickoff instead, as a normal part of explaining how the client approval workflow works for this specific project. A studio that tells every broadcast client upfront, "for the color pass, please review on your best monitor in a dim room, and flag it if that's not possible so we can send a reference clip instead," has already done the hard part before there's ever a reason to be defensive about it.

• Viewing conditions noted in the project kickoff, not just the contract fine print
• A conditions notice attached to the approval step for any broadcast-bound grade
• Timestamped record of when and how that notice was shown to the client
• A reference clip or calibrated proxy offered for clients without a good display
• Studio and client aligned on what "approved" actually means for this delivery

How This Connects to the Rest of Your Color Pipeline

Viewing conditions and version control are honestly the same underlying problem wearing two different hats, because in both cases the question is whether everyone looking at "the grade" is actually looking at the same thing, whether that's the same version of the file or the same rendering of that file on a screen. If your color team spans time zones, the version confusion we cover in our piece on handing a grade between colorists tends to compound this exact issue, because a client reviewing an outdated version on a bad screen has two separate reasons to be unhappy with something that isn't actually the current work. Fixing the Davinci Resolve delivery chain to be consistent end to end, from grading suite to client screen, closes both gaps at once.

Broadcast engineering groups like the NAB and organizations covering the technical side of the industry such as IBC have spent decades building standards precisely because color and brightness don't travel reliably without them, and a lot of that rigor simply doesn't reach the client side of a review unless a studio deliberately builds it into the approval step themselves.

A Reasonable Middle Ground for Clients Who Won't Change Habits

Realistically, some clients are never going to review in a dim room no matter how many times a studio asks nicely, they're busy, the request feels fussy, and asking someone to alter their entire routine for a thirty second spot is a big ask relative to what it's asking in return. The middle ground we point studios toward is separating the casual approval from the technical one, let the client watch on whatever device they want for the general creative sign-off, is the story right, is the pacing right, does the brand come through, but for the final technical color check on anything broadcast-bound, send a short reference clip specifically built to be forgiving of a bad screen, graded slightly toward the safe middle of the range rather than the more extreme choices that look great on a calibrated monitor and rough on a phone. It's not a perfect substitute for a real calibrated review, but it closes most of the gap for the clients who were never going to change their habits anyway, and it's a far better outcome than either fighting that battle every single project or simply hoping it doesn't matter this time.

What This Costs a Studio Beyond the One Dispute

The direct cost of a color dispute is usually a redo, maybe a discounted invoice to keep the client happy, but the quieter cost is what it does to how that client behaves on every project after. Once a client has been burned once by a grade that "looked different" after air, they stop trusting quick approvals entirely, they start asking for extra review cycles on routine work that never needed them, they loop in a second or third person internally just to double check, and suddenly a studio that used to turn around approvals in a day is waiting a week on every single deliverable from that account. That drag is genuinely harder to fix than the original dispute was, because it's not a single conversation, it's a change in how the client relates to your studio going forward, and it tends to persist long after everyone's forgotten the specifics of what actually went wrong the first time.

Protect Your Grade From the Screen It's Judged On

If your studio delivers anything bound for broadcast, an unguided client approval on a random laptop is a dispute waiting for the wrong moment to happen. PlayPause lets you attach viewing condition notices directly to the approval step, timestamps every sign-off, and keeps a documented record you can point to if a client ever claims the grade changed after they approved it. Look at PlayPause pricing and see how a flat per-workspace plan protects a project no matter how many broadcast clients you're delivering to this month.