Why 'I'll Know It When I See It' Is Killing Your Approval Timeline

"I'll know it when I see it" is one of the most expensive sentences in video production, not because it's malicious, most clients genuinely mean it as helpful honesty, but because it hands you zero direction and asks you to burn a full revision round guessing at a moving target. You know exactly what we mean if you've ever delivered a cut you were proud of, gotten that sentence back as the entire note, and then spent the next round making changes you weren't even sure the client wanted, just to have something different to show them.

Vague Feedback Isn't a Client Problem, It's a Format Problem

The instinct is to blame the client for being unclear, but in our experience the real issue is almost always that the feedback tool itself never asked for anything more specific, so a general comment box or a reply-all email thread lets a client write "this doesn't feel right yet" and hit send, because nothing in the interface prompted them toward the timestamp, the frame, or the specific element they meant. Give the same client a tool where a comment has to attach to a moment in the timeline, and the same person who wrote "I'll know it when I see it" will instead write "at 0:47 the cut feels a beat too fast, can we hold on her reaction half a second longer," because the format itself pulled the specificity out of them.

Why Vague Notes Actually Slow Everything Down

It feels counterintuitive, but a vague note takes longer to resolve than a harsh, specific one, because a specific note gives you exactly one thing to fix, while a vague note forces you to generate several hypotheses about what the client might mean, implement your best guess, and wait an entire review cycle to find out if you guessed right. Multiply that across a project with three or four vague notes per round and you can watch a two-round contract quietly stretch into five rounds, not because the client is being difficult, but because every round is really a guessing round instead of a fixing round.

The Four Questions That Turn Vague Into Actionable

When a note comes in soft, we tell producers and editors to run it through a short mental checklist before starting work, and honestly this takes less time than it sounds like once it's a habit.

If a client's note can't answer the first two questions, it's worth a quick reply before you touch the timeline at all, something like "Just want to make sure I fix the right thing, can you drop a comment at the specific moment that felt off?" That thirty-second clarifying question routinely saves an entire wasted revision round, and clients almost never mind being asked, because it signals you're taking their note seriously enough to get it exactly right the first time.

Reframing "I'll Know It When I See It" as a Missing Reference

Sometimes that phrase isn't laziness, it's a client who genuinely can't articulate what they want in editing language, and in that case the fix isn't pressing harder for specifics, it's asking for a reference instead. "No problem, is there another video, ad, or scene that has the energy or pacing you're picturing? Even a rough example helps me get there faster." This works because most people can point at something they like far more easily than they can describe what they want from scratch, and once you have a reference, vague feedback usually becomes concrete within one exchange.

Building Specificity Into the Review Itself

This is the exact problem we built PlayPause around solving, because we kept watching editors and producers lose whole weeks to the gap between what a client felt and what a client could actually describe. When feedback is left directly on the frame, timestamped and pinned to the exact moment in the cut, the format does most of the specificity work automatically, a client dropping a comment at 1:32 has already told you the where, even before they've fully articulated the what. Our Video Feedback and Video Proofing tools are built around exactly this idea, that frame-accurate commenting isn't a nice-to-have feature, it's the single biggest lever for making revisions converge instead of wander.

What Producers Should Do Before the Note Even Arrives

Some of this responsibility sits upstream of the feedback itself. A tight Creative Brief with clear reference points, tone words, and examples up front means a client has language to draw from when they sit down to review a cut, rather than reaching for vague catch-all phrases because nothing more specific comes to mind. We see this constantly with brand and marketing teams, the projects with the tightest, most concrete briefs at the start are almost always the ones with the cleanest, fastest feedback rounds later, because the client has already been trained, gently, to think and speak in specifics before they ever open the review link.

• Ask where, exactly, before making any change based on a vague note
• Ask what "fixed" would look like in the client's own words
• Request a reference when a client can't articulate the direction themselves
• Use a review tool that pins comments to frames, not general threads
• Tighten the creative brief so specific language starts before review begins

A Real Example of the Gap Closing

A post-production house we spoke with runs a steady stream of Corporate Video and Explainer Video Review projects for mid-size B2B clients, and for years their first-round feedback came back almost entirely as general impressions, "needs more energy," "doesn't feel premium enough," notes that gave the editor almost nothing concrete to act on. After switching client reviews over to a frame-pinned commenting flow, the same clients who used to write one vague paragraph started leaving four or five short, specific comments instead, each one tied to an exact second in the cut. The editors didn't get smarter and the clients didn't suddenly develop a film vocabulary overnight, the format simply made it easier to be specific than to be vague, and people generally take the path of least resistance, so specificity became the default rather than the exception.

Training Repeat Clients Over Time

If you work with the same client across multiple projects, and a lot of freelance and agency relationships do, there's a compounding benefit here worth mentioning. Once a client has left three or four rounds of timestamped, specific feedback through a proper review tool, that becomes their new normal, and you'll notice the vague, hard-to-parse notes drop off almost entirely on their second and third projects with you. Basically, you're not just solving the vagueness problem for this one cut, you're training the working relationship itself to run on specifics going forward, which pays off every single project after the first.

When Vagueness Is Actually a Symptom of Too Many Voices

Occasionally what reads as one client's vague feedback is really several people's half-formed opinions getting mashed into a single message before it reaches you, which is a related but distinct problem from the one this piece is solving. If that's closer to what you're dealing with, five different stakeholders each nudging the note in a slightly different direction, our companion piece on handling conflicting stakeholder feedback covers how to get one authoritative note out of a group before it ever lands in your inbox. And if the deeper issue is that your contract never capped how many rounds this guessing game is allowed to run, our piece on setting a revision-round limit is the place to start.

Feedback Quality Is a Workflow Choice, Not a Client Trait

At the end of the day, "I'll know it when I see it" says more about the tool the client is using to give feedback than it says about the client themselves, and that's genuinely good news, because it means the fix is something you control. According to Adobe's video blog, review and approval friction remains one of the most cited slowdowns in modern video production pipelines, and the teams solving it fastest are almost always the ones who moved feedback out of email and into a tool built for frame-level precision.

A Note for Producers Managing the Handoff

If you're the producer or account lead sitting between the client and the editor, part of your job is catching vague notes before they ever reach the timeline, because forwarding "make it pop more" straight to your editor just moves the guessing problem downstream instead of solving it. A quick habit worth building is reading every incoming note once, asking yourself whether an editor could act on it without a follow-up question, and if the answer is no, sending one clarifying question back to the client before you pass anything along. It adds maybe two minutes to your day and it routinely saves your editor a wasted pass, which is a trade worth making on basically every project that comes through your desk.

Stop Guessing, Start Fixing

The gap between "I'll know it when I see it" and a clean, fast revision round is almost always a tooling gap, not a client gap, so give your clients a way to comment directly on the frame and watch how much more specific their notes get without you having to ask twice. Explore PlayPause pricing to see how frame-accurate review works across your projects, or contact PlayPause to see how much faster your approvals move once vague feedback has nowhere left to hide.