Workflows

    In-Market Review on Picture, Not on a Doc

    Review the localized cut on picture with visible time, using a scorecard that splits language, culture, and legal. A script doc misses collisions.

    Versely Team9 min read

    A native speaker signing off a script in a Google Doc has not reviewed the video. They have reviewed a column of sentences. They did not see the German super cover the speaker's mouth, the CTA sit under TikTok's caption field, the thumb-and-index "OK" in a market that does not use it that way, or the English pack shot still in frame while the VO says a euro price. Those are picture problems. They only exist on the cut.

    In-market review means a reviewer who lives in the target market watches the actual picture, with a visible time reference, and scores three separate things: language, culture, and legal. Mixing those three into one "looks good" is how a legally dangerous line survives because the joke was funny, or a fine joke dies because someone used the legal column to kill tone.

    A script cannot see the cut

    Three classes of defect never appear in a document:

    Type collisions. Translated supers are longer than the English they replaced. A line that fitted the lower third in English now runs across a face, a pack, or a platform control. Line breaks that looked fine in a two-column script wrap on a 9:16 plate. None of this is visible until type is on picture, at the real aspect ratio, against the real background.

    Gesture and performance. The English speaker raises an eyebrow on the punchline. The transcreated line moves the punchline a second later, so the face now emphasizes a preposition. A nod, a shrug, a point at on-screen text, a left-to-right swipe on a phone: all of it was performed against the source. A reviewer reading words cannot catch a mismatch between mouth, hand, and meaning.

    Color, setting, and residual English. A kitchen socket, a school bus, a price sticker, a calendar in MM/DD, a red wax seal that reads as celebration in one market and as something else in another. Burned-in English on a microwave, a laptop UI, a storefront. The script has no row for these. The picture does.

    This is why the review surface has to be the cut, not an export of the dialogue. A client review loop built on previews and share links already treats the video as the object under discussion. In-market review is the same object with a different reviewer and a different scorecard. Do not demote it back to a document because the reviewer happens to be a linguist.

    Visible time, on the actual picture

    Notes that say "around the product shot" are not notes. Notes that say 00:07:12–00:08:00 can be executed in one pass.

    Give the reviewer a copy of the cut with a visible running time. Broadcast teams burn timecode into a review encode so every comment maps to a frame. If you do not have a dedicated review encode, the player clock is the minimum, and every comment still has to cite it. A Slack message with no time attached goes back to the reviewer, it does not go to the editor.

    Send a link, not a file name. A shareable link opens on a phone without an account, which is where a lot of in-market reviewers will actually watch. A WeTransfer of FINAL_v7_DE_for_review.mp4 produces a v8 that nobody can match to the comments.

    Iterate on a preview while the notes are open. Versely's editor 480p preview pass is free and carries a short per-user cooldown; the final export is charged once, regardless of clip count. That is the right economy for "the super is two words too long, try the two-line fallback." The mechanic is spelled out in free 480p previews. Do not cut a new master for every language note.

    What you send for in-market review is the localized picture: dubbed or regenerated audio, target-language supers, target-language captions if they will ship burned in. Do not send the English master plus a script and ask the reviewer to imagine it. They will approve the imagination.

    A scorecard with three columns

    One row per issue. Three columns so a cultural flag cannot hide inside a legal veto, and a typo cannot be argued as "how we speak."

    Time Language Culture Legal Severity
    00:00:02 Hook uses coger (MX vulgar). Replace. Block
    00:00:07 Super overflows the pack. Two-line fallback. Fix
    00:00:09 Pointing at price with left hand, reads rude to reviewer. Recenter the gesture or recut. Fix
    00:00:12 "$29" still on pack. VO says euros. Pack must match offer. Block
    00:00:14 CTA compra ahora is fine. 18+ super shorter than hold required in brief. Block

    Language is grammar, register, variety, and on-screen spelling. Wrong you-form for the market. Spain vosotros in a Mexico cut. A formality that sounds like a bank ad on a snack brand. A missing diacritic that changes a word. Lip-sense: the line is correct and still unspeakable in the time available.

    Culture is everything a fluent outsider will miss. Gestures, jokes, food, dress, color, music-bed energy, the social meaning of a setting. A reviewer in-market is not being precious. They are telling you the shot will be read as foreign, cheap, or insulting. You can overrule them. You cannot pretend the flag was a copy edit.

    Legal is claims, disclaimers, offer match, age gates, prize rules, comparative language, health and finance wording, and anything ad-review flags will catch after you have already spent the media budget. Legal is not "I wouldn't say it that way." If the reviewer is not qualified to make a legal call, they still flag the line and you send it to counsel. They do not silently rewrite a claim.

    Severity is three values, not a paragraph:

    • Block. Cannot publish. Wrong offer, uncleared claim, vulgar in-market reading, residual source-language legal copy.
    • Fix. Publishes after a change. Overflowing super, gesture mismatch, register too stiff.
    • Note. Optional. A nicer idiom, a preference about music. Notes do not delay the cut.

    The reviewer does not propose a new campaign in the legal column. The reviewer does not mark "I prefer a different joke" as a block. If they do, the producer sends it back with the column definitions, not with an argument about taste. Approval workflows that do not stall fail in exactly this way: one undifferentiated comment thread, no owner, no severity, and a cut that sits for a week.

    How to run the session

    A working sequence, for one market, one cut:

    1. Lock the brief first. The reviewer gets the transcreation one-pager (shot jobs, offer, legal locks) plus the picture. Reviewing against a brief they have never seen produces notes that contradict decisions you already signed.
    2. Send the localized cut with visible time. Share link. Player clock or burned-in review clock. No English master as a substitute.
    3. The reviewer watches once without pausing, then once with the scorecard. The first pass catches "this feels foreign." The second pass timestamps it.
    4. Fill the scorecard, not a paragraph. One issue, one row, one column, one severity. A five-line email is not a scorecard.
    5. Producer triages. Blocks go to the person who can actually fix them (legal, editor, adaptor). Fixes go to the editor on the preview pass. Notes wait until blocks are gone.
    6. Re-share only the changed cut. Cite the rows you closed. Do not ask the reviewer to re-watch the whole film to find the one super you moved.
    7. Ship against zero open blocks. Fixes can be argued. Blocks cannot.

    If the cut will run as paid creative, run the same picture through the pre-publish check after in-market review, not instead of it. In-market review catches "this is wrong in Mexico." Pre-publish review catches "this is broken as a file." Auditing generated output against a brand manual is a third pass, for brand, and it is not a substitute for a human in the market.

    Do not sit on a call and "just watch it together" without the scorecard. You will get a vibe. You will not get a list the editor can execute. Time-stamped rows are the deliverable of the session. The conversation is optional.

    Remote reviewers are fine. Offshore reviewers who do not live in the market are not "in-market," even if they are native speakers. A Spaniard in Berlin can review Spain. They cannot review Mexico on the strength of being a Spanish speaker. If you only have one reviewer for "Spanish," you do not have coverage for both.

    FAQ

    Can the translator do the in-market review?

    Only if they are in the market, watching picture, and filling the three columns separately. The person who wrote the lines is a biased reviewer of those lines. A second in-market pair of eyes is cheaper than a recut after the first paid placement.

    Do I need burned-in timecode, or is the player clock enough?

    Either works if every comment cites a time. Burned-in review clocks survive screenshots, WhatsApp screen recordings, and "can you look at this?" forwards. Player clocks disappear the moment someone sends a still. For a two-person team on a share link, the player is enough. For an agency chain, burn a clock on the review encode and never on the ship encode.

    What if language, culture, and legal disagree?

    Legal wins on blocks. Culture wins on whether the joke should exist. Language wins on whether the sentence is speakable. Write the disagreement as two rows, not as one row with three opinions. The producer decides. The scorecard's job is to make the disagreement visible, not to pretend it did not happen.

    How many review rounds?

    One full pass, one confirm pass on the blocks. A third round is a brief problem: the locks were not locked, or the reviewer is now designing the film. If a confirm pass produces new blocks that were visible on pass one, the reviewer did not finish pass one. Send it back. Do not open a new creative conversation.