# TVC Timing Desk > A commercial is two timelines running at once - pictures and voiceover - and almost every > real failure is a relationship between them. Five lanes over one brief, plus a free > browser-side auditor that schedules both tracks against each other. URL: https://tvc-timing-desk.skillsafe.ai/ API: https://tvc-timing-desk.skillsafe.ai/api.html Derived from nutllwhy/seedance-tvc-director (https://github.com/nutllwhy/seedance-tvc-director), MIT: its 15 and 30 second phase tables, voiceover scheduling rules, shot-role duration bands and delivery quality checklist. Every number this app enforces is one that reference states outright. Not affiliated with or endorsed by nutllwhy, ByteDance or any brand named in an example. ## What the free auditor enforces All of it runs in the browser, on text you paste, with no account and no credits. **Between the two tracks:** - Voiceover windows must not overlap. One narrator cannot say two things at once, and a model handed overlapping windows will pick one or slur both. - No window longer than 2.5s may be empty of events across BOTH tracks. An event is a cut, a described movement, or a line starting. A shot whose description carries a verb of movement is live for its whole span; a shot that only describes a state contributes its own cut and nothing more. - The last line hard-stops before 29s on a thirty, leaving at least 1s of music and product sound - otherwise the tail is clipped at the generation boundary. - A gap longer than 2.5s between two lines, over shots that are all holding still, is dead air: compress the picture rather than writing more copy. **On the picture track:** - The track must tile the spot - no gap, no overlap, starting at zero. - Something must trigger inside 0.7s and something must visibly change inside 3s. - Each shot declares a role, and each role has a duration band. Past its band a shot has to show a second visible state. - Never two `reaction` or two `logistics` shots in a row. **On the voiceover track:** - Every line must be sayable in its window: 3-6.5 Chinese characters a second, or 1.8-3.6 latin words a second. Time it aloud rather than counting characters. - The same sentence written twice with no declared repeat count is a scheduling error. - Superiority and efficacy claims need an approval marker. ## Shot roles and their bands - `hook` - 0.3-3s. the opening question or desire (layer: Visual hook) - `world` - 0.8-4s. situation, space, audience (layer: World establishing) - `trigger` - 0.5-3s. the product entering the causal chain (layer: Product trigger) - `proof` - 0.8-4s. texture, mechanism, macro observation (layer: Mechanism or texture proof) - `reaction` - 0.8-1.2s. a single reaction, and a longer one needs a second state (layer: Emotional or functional payoff) - `logistics` - 0.6-1.2s. pushing, handing, placing, moving a cup - never its own beat - `transition` - 0.2-1s. completed inside about a second, never a floating tunnel - `payoff` - 0.8-4s. the changed state, shown (layer: Emotional or functional payoff) - `packshot` - 1-4s. hero shot, pack, logo, CTA (layer: Brand recovery) ## The two documented formats ### 15 seconds 3-5 effective shots, 1-3 voiceover lines. - 0-3s: strong visual hook and a visible change / connect to the product, the pain or the claim immediately - 3-7s: widen the situation, product trigger / put the product into the causal chain - 7-11s: result and proof / the clearest experience or evidence shot - 11-15s: close, packshot, endboard / recover the brand, the claim and the call to action ### 30 seconds 8-12 effective shots (or 5-8 in a restrained cut, each developing inside itself), 3-5 voiceover lines, at least 5 of the six richness layers. - 0-3s: strong hook and the first change / take attention and plant the product claim - 3-8s: open out the world or the character behind the hook / lock the audience situation and the desire - 8-14s: product trigger / put the product into the causal chain - 14-21s: texture, mechanism or experience proof / give the product enough time to be observed - 21-26s: emotional or functional payoff / answer the question the first three seconds asked - 26-30s: hero shot, packshot, endboard / claim, pack, logo, CTA ## The six richness layers - **Visual hook** - a visual question or desire in the first three seconds that an ordinary product shot could not stand in for - **World establishing** - after the hook, the time, space, audience situation or brand world - **Product trigger** - the product entering the causal chain through use, texture, sound or physical change - **Mechanism or texture proof** - macro, motion, light or real feedback giving the product time to be observed - **Emotional or functional payoff** - the changed state shown, rather than announced by the voiceover - **Brand recovery** - hero shot, packshot and endboard each doing their own job ## The five lanes ### `brief` - Brief and single claim Separate what the client actually said from what you are assuming, pick the one core claim, and mark every figure that still needs approval. A spot with two claims has none. Sections: `Summary`, `Single Claim`, `Facts and Assumptions`, `Proof Plan`, `Next Step`. Fields: `brief`*, `product`*, `seconds`, `sound`, `proof`, `language`. ### `shots` - Picture track The shot track alone: every shot with a span, a role and what happens in it. The auditor below checks the bands, the phases and whether anything at all happens in the first seven-tenths of a second. Sections: `Summary`, `Shot Track`, `Phase Map`, `Structure Check`, `Next Step`. Fields: `claim`*, `seconds`*, `scene`, `draft`, `language`. ### `vo` - Master voiceover list One list, one narrator, one place the words appear. Each line gets an ID, a start and a hard stop - and the audit checks none of them overlaps, none is unsayable in its window, and the last one leaves a tail. Sections: `Summary`, `VO Track`, `Timing Notes`, `Sound Check`, `Next Step`. Fields: `shots`*, `seconds`*, `claim`, `draft`, `language`. ### `timeline` - Merged timeline Both tracks in one document, scheduled against each other. This is where the failures live: a line still running when the packshot lands, two and a half seconds where neither track is doing anything, a tail that gets clipped. Sections: `Summary`, `Timeline`, `Density Check`, `Sound Map`, `Next Step`. Fields: `claim`*, `seconds`*, `sound`, `draft`, `language`. ### `qc` - Delivery audit Paste a spot you already have. Every finding names the rule and the second it happens at, and the lane returns a repaired timeline rather than a list of complaints. Sections: `Summary`, `Verdict`, `Findings`, `Repaired Timeline`, `Next Step`. Fields: `timeline`*, `seconds`, `focus`. ## What this app does not do It writes briefs, tracks and timelines. It does not generate video or audio, it calls no generation API on your behalf, and it delivers nothing. The timelines are yours to take into Seedance or anywhere else.