Fix a prompt that missed the brief
First separate a technical failure from an expectation mismatch, then repair the brief or request the smallest useful revision without discarding good work.
Written By Anish Muppalaneni
Last updated 17 days ago
Read before this
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
- For a technical failure, reopen the conversation and use the visible retry or recovery action before changing the prompt.
- For a brief mismatch, restate the audience and the one outcome the video must achieve.
- For a source mismatch, attach the approved source and explicitly name which file controls facts, structure, and visuals.
- For a structural mismatch, request a revised script or storyboard before spending time on individual frames.
- For a local mismatch, name the scene or click the frame, describe the desired result, and state what must remain unchanged.
- 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.
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.
When to contact Support
Contact Support when retries repeatedly fail, an output is missing after completion, or a visible product control does not behave as documented. Include the project URL, approximate time, last visible state, and the smallest reproducible step. Do not send secrets or private source material in the first message.
Keep going
- Write a better video prompt — Write prompts that produce stronger scripts, visuals, pacing, and revisions.
- Revise a generated video — Choose between chat revisions, frame-specific requests, inline editing, and a full-editor copy.
- Understand generation status, retries, and recovery — Troubleshoot slow, stopped, failed, or disconnected video generation without relying on fixed time promises.
- Review scripts and storyboards — Review the pre-start script or storyboard approval step and the finished scene plan.
Continue in ngram
Open the relevant Studio surface and follow the current controls shown in your account.