Revisions without reshooting, by structuring round one for round two

The client asks for the product moved slightly, or a warmer grade, or the background simplified. Each is a small request. Each becomes a full regeneration if the frame exists only as a finished flat image — and regeneration means losing everything else that was working.

This is the most predictable cost in generative client work and it is entirely a structural problem. Frames produced as single units cannot be edited; frames produced as separable elements can.

The decision that determines which you have is made in round one, before any feedback exists.

Where a shot allows it, produce it as layers: environment, subject, product, foreground elements, type. Each generated or sourced separately, assembled in a composition that stays editable.

Now the common requests are all local. Move the product: move a layer. Warmer: adjust a grade on the composition. Simplify the background: replace one element.

The cost is setup time in round one. The return arrives in round two and every round after, and there is essentially always a round two.

Store the exact prompt, the seed if exposed, the references used and any non-default settings, alongside each delivered asset.

ex014_hero_4x5/
  final.jpg
  recipe.json     prompt, seed, refs, settings
  layers/

With the recipe you can regenerate a near-identical frame and change one variable deliberately. Without it, a regeneration is a fresh roll of the dice and the client notices that the second version is a different picture rather than an adjusted one.

This takes seconds per asset at production time and is unrecoverable afterwards.

State the number of revision rounds in the agreement, and treat a round as a batch: all feedback collected, then one pass of changes.

The failure mode is drip-fed notes — one change, then another an hour later, then a third the next morning. Each triggers a full cycle of work and review, and three drips cost more than one round of ten changes.

Ask for consolidated feedback explicitly: 'send everything together and I will do one pass'. Most clients prefer this too; they simply default to sending things as they think of them unless asked.

Sort every note into one of two piles. Adjustments — grade, crop, position, small removals — are edits and can be done quickly. Structural — different composition, different location, different treatment — are regenerations.

Do all the adjustments first and send them. Frequently a structural note dissolves once the adjustments are seen, because it was a reaction to something the adjustment fixed.

Where a structural note stands, say what it involves before doing it. 'That is a new shot rather than a change — happy to do it, it moves delivery by two days' is a normal professional sentence and it prevents the expectation that everything costs the same.

Every structural choice in this guide costs a little in the first pass and saves a lot in the second. Layered production, saved recipes, consolidated rounds — none of them help if the job ends after delivery, and jobs do not end after delivery.

Working this way also changes how revisions feel. A note that arrives as a five-minute edit is a normal part of the job; the same note arriving as a lost afternoon is a source of friction that eventually shows in the relationship.

The client experiences responsiveness. What they are actually experiencing is a file structure.