How an approved AI shot stays approved when you ask for a change
You approve a frame, ask for the jacket in another colour, and a different picture comes back. This is why that happens, and how the work is built so a note changes only what you asked for.
The moment this matters is your first note. A frame has been approved, and now someone wants the jacket in a different colour. Typing a request into an AI tool feels like control, because you type and something appears. But one typed request covers the whole picture, and the system decides most of it for you. Ask again and it can lose the face, the product or the framing you had already agreed.
The answer is to build the shot from separate controls, so the approved parts are locked and only the open part is made again. After reading this you will know what to ask about how your shots are being built, and when the extra build is worth having.
I have written separately about why "change one thing" is the hard request. This article is about the method that answers it.
01 · The Problem
What a text box cannot give you
A prompt compresses intent into a sentence, and the model fills in the rest. That creates three failures once someone is paying for the result. The first is irreproducibility. Change one word, or run the same words later against an updated checkpoint, and the image can move. The second is limited partial editing. A prompt addresses the whole frame, so keeping the composition while changing only a jacket is difficult. The third is a lack of separation of concerns. Pose, lighting, identity, colour and style are entangled in the same sentence, so every adjustment can disturb something else. A prompt can produce a useful starting point; it is a poor record of how to repeat or amend an approved result.
02 · The Surface
A node graph is a wired pipeline
A node-based workflow replaces the single box with a graph of discrete operations you can see, wire and inspect. ComfyUI is the common open tool for it, and hosted node canvases work on the same principle. Generation stops being one event and becomes a sequence of stages, each of which you can hold still or change independently. The controls are separated, so a decision made in one place does not silently rewrite a decision made somewhere else.
The canvas below is from the Gigaclear commercial. That job ran on a hosted node canvas, Freepik / Magnific Spaces, which was the agency's main platform. The same logic applies in ComfyUI: separate nodes, locked inputs, one open region at a time.
What is being locked
- The layout stays where it was approved. ControlNet locks composition against an explicit input: pose from a skeleton, depth from a depth map, edges from a line render, layout from segmentation.
- The same face or product carries from shot to shot. IP-adapters and reference inputs hold identity and look across generations, which limits drift.
- One side of the frame can change without the other. Regional prompting assigns different instructions to different areas of the frame.
- A fix touches only the part that is wrong. Inpainting masks the one region and regenerates only that region, leaving everything approved untouched.
- Resolution, style and randomness become settings you can write down. Seed control, LoRA loading, and dedicated upscale and detail passes are named dials in the graph.
None of this rules out closed video models. Node workflows carry the stills, plates and control passes, and a closed prompt-and-reference video model is used where a shot needs its ceiling. How the model for each shot is chosen is a separate question.
03 · The Method
Freeze what is approved, iterate what is not
In prompt-only work, approval is fragile, because the next generation can lose the thing everyone agreed on. In a graph, approval becomes structural. Once the composition is signed off, the seed and ControlNet input can be fixed. Once identity is right, a reference input helps hold it. You can then work on an unresolved region through inpainting while preserving the approved areas. A revision becomes a contained change rather than a request to remake the whole frame.
04 · The Volume
Controlled variation, not a fresh spin
Once the pipeline is wired, you can batch a controlled set of variations where exactly one parameter moves and everything else is held: several background options against the same locked subject, four wardrobe colours against the same pose, or a matrix of seeds against a fixed composition. Every output shares the same skeleton, so the variation is legible. When a client picks option six, you can identify what makes it different from five, reproduce it, and carry it into the next stage without rebuilding the brief from scratch.
05 · The Handoff
An interface a non-technical team can drive
A graph is powerful and also intimidating, and most of a production team should never have to look at it. The final move is to collapse the pipeline behind a small interface, exposing only the handful of inputs that matter: upload a reference, choose a pose, pick a colour, set the number of variants and run the batch. The complexity stays wired underneath, but an art director or producer operates it without touching a node. This is what turns a personal trick into a team capability. A workflow only one person can operate is a risk for the client. One the team can drive is something they can rely on.
The review stays human. A person still checks every batch before anything leaves, and the interface takes the node work off the team while the judgement stays with them. I build these tools as part of ComfyUI workflow builds and handover.
06 · The Economics
Build once, run again
A prompt is spent the moment it runs. A documented workflow outlives the delivery it was built for. Version the graph, note the models and LoRAs it depends on, record the inputs each stage expects, and the pipeline built for one campaign becomes the starting point for the next. The work of building it is spread across every run that follows, which is why a node workflow can reduce the cost per run. A demonstration has to prove something is possible once. A production has to prove it can be repeated, amended and delivered on schedule, by people other than the person who built it.
A node build is overkill for a one-off social clip or for pure exploration, where a prompt is quicker and nothing has to be repeated. It becomes worth building once something has been approved and has to stay that way.
Frequently Asked Questions
Is prompting enough for professional AI video?
No. A prompt is a single request to a system that decides most of the outcome for you. Commercial work needs separate controls, so an approved frame can be amended without being remade.
What is a node-based AI workflow?
A wired pipeline, such as ComfyUI, where each step (pose, depth, masks, inpainting) is an adjustable node, so you can lock approved elements and change only what needs to change.
How do you get consistent variations instead of random ones?
Freeze the approved parts of the graph and iterate only the rest. That produces controlled variation instead of a new unexplained result each time.
Why can a node-based workflow cost less per run?
Because it is built once and run many times. Reusing a documented workflow can reduce the cost of each later run. A non-technical team can drive it, and a person still reviews every batch.
Send the script or the deck. Within a day you get a written reply: what is realistic and how I would make it. That first read is free, and if AI is not a fit I will say so.
Send the brief → See how the Gigaclear commercial was made →