Fix a prompt that missed the brief

Use this when the video works but the result is wrong

Use this guide when a generated video is poor quality, misses the audience or goal, ignores an explicit instruction, uses the wrong source, invents unsupported detail, or changes the order or appearance of a recorded product workflow. Diagnose the largest mismatch first and preserve the parts that are already correct.

Before you start

You can prepare the brief while signed out. To follow the workflow in Studio, sign in, open Home, and use an account or team context where you are allowed to create. Have approved source material ready before you submit a factual video.

Identify the kind of problem

• Technical failure: the job stopped, an asset is broken, or a completed output is missing.
• Brief mismatch: the video works, but the audience, goal, tone, facts, or format are wrong.
• Source mismatch: the video used the wrong file, invented unsupported detail, or ignored source priority.
• Structural mismatch: the hook, order, pacing, or CTA needs broad changes.
• Local mismatch: one scene, frame, narration line, caption, or transition needs correction.

Repair the result in order

1. For a technical failure, reopen the conversation and use the visible retry or recovery action before changing the prompt.
2. For a brief mismatch, restate the audience and the one outcome the video must achieve.
3. For a source mismatch, attach the approved source and explicitly name which file controls facts, structure, and visuals.
4. For a structural mismatch, request a revised script or storyboard before spending time on individual frames.
5. For a local mismatch, name the scene or click the frame, describe the desired result, and state what must remain unchanged.
6. Play the complete preview after the change and verify narration, captions, transitions, and CTA together.

Turn prohibitions into priorities

A long list of “do not” instructions can hide the actual goal. Rank the two or three non-negotiables and express them positively: use only approved figures; show the recorded workflow in its real order; preserve the current narration except for the named line.

Protect product-demo and screencast fidelity

For a product demo, state which recording or ordered screenshots control the real sequence, which document or URL controls facts, and which approved assets may be used for visuals. If the generated scene changes the interface or action order, request a repair to that named scene and tell ngram to retain the source footage and all approved scenes. Do not ask it to recreate an exact product screen from memory.

A targeted revision pattern

In scene [number], replace [current issue] with [desired result]. Keep [narration, timing, layout, or other approved part] unchanged. Use [named source] for the exact fact or visual. Do not modify the other scenes.

When to start a new version

Fork or start a new version when the audience, format, or core story has changed enough that preserving the current structure would create confusion. Rename both versions clearly. Use a targeted revision when most of the current video is already right.

Expected result

The repaired script, storyboard, or scene should address the named mismatch while keeping the approved audience, facts, structure, visuals, narration, and other scenes unchanged. Play the complete preview and compare it with the source and brief before publishing.

If the same mismatch remains

Keep the current project and do not regenerate the entire video. Restate one observable correction, name its controlling source, and retry only the affected script, storyboard, or scene once. Contact Support if the same explicit instruction or readable source is ignored again, a technical failure prevents the targeted change, or an output is missing after completion. Include the project URL, approximate time, affected scene, last visible state, expected result, and whether credits changed; do not send secrets or private source material in the first message.