Your product campaign is approved. A month later, the brand asks its China-based production partner to preserve the product, camera and action while changing the setting for a seasonal release. “We saved the seed” is useful information, but it does not yet define how that revision will be made.
Before buying ongoing AI video updates, specify whether you need another run of the original request, a controlled change to the shot or continued use of the exact approved asset. Each calls for a different handoff.
Read the condition attached to the seed
Checked November 9, 2026, the image-to-video seed field in Runway’s API Reference says the same seed for an identical request produces similar results. Google Cloud’s Veo text-to-video guide says a seed, without changing other parameters, guides the model to produce the same videos.
The wording differs. Apply each description to its own interface; do not turn either into a universal guarantee, or translate “similar” into pixel-identical.
ONCE’s inference is that a request for a changed setting, action or input no longer meets the identical-request condition. A seed can support record keeping and testing. On its own, it does not establish that an artist can change one element while preserving everything else. No model rerun or failure-rate measurement was performed for this article.
Three different purchases hide inside “we can update it later”
| Actual requirement | What to buy | Acceptance question |
|---|---|---|
| Run the original request again | Complete request record, inputs and applicable execution conditions | What consistency is demonstrated under the agreed conditions? |
| Preserve the subject while changing one element | A defined editing or compositing route with the necessary retained assets | Did the changed element pass while protected parts remained acceptable? |
| Use the approved shot in a future edit | Archived approved media, required project files and usage notes | Can the editor reuse that actual file without generating it again? |
This is ONCE’s procurement classification, not a platform’s delivery tier. The three services can coexist. A parameter log should not substitute for editable materials, and a regeneration recipe should not be the sole archive of a finished shot.
Preserve the request and the selected result
Record the service and model identifier, actual prompt, input-file versions, seed, ratio, duration and other settings relevant to the task. Link that record to the selected output and its approval. Mark unavailable or unconfirmed configuration as unknown rather than inventing a value.
Traceability is a useful deliverable. It is not a promise that a future platform environment will remain unchanged indefinitely. If future reruns are part of the purchase, agree the maintenance period, execution dependencies and response to a change. The implementer should verify the actual conditions it can support.
That is a contractual scope recommendation, not a claim that a particular provider has changed its model or that a current documentation statement provides permanent service availability.
Define what must stay fixed before choosing the technique
Break “consistent” into visible requirements: product shape, branding, included accessories, action, camera, lighting and background. Mark which must remain, which may change and which need renewed approval. The brand and product owner should identify details that determine product identity or the meaning of a claim.
Consider a hypothetical headphone campaign. The approved earcup geometry must remain while the background becomes seasonal. First assess retaining the approved shot and editing the environment, or compositing from suitable product layers. If those routes cannot satisfy the visual requirement, review new generation as a separate option. An unchanged seed does not approve the product details in a new output.
A change to camera, action and setting together is closer to developing a new shot. Quote selection and review accordingly. Conversely, a subtitle or end-card change may be straightforward in an existing project; inspect that route before proposing a fresh generation of the whole sequence.
Rehearse one likely revision before buying maintenance
Choose a shot authorized for testing and preserve its approved file first. If rerunning is in scope, repeat the recorded request under the agreed conditions and compare observed differences with the acceptance requirement. If localized editing is in scope, perform a separate, explicit change and review the parts that were meant to remain.
Keep those findings separate. A visually close regeneration does not demonstrate a successful controlled edit. State whether a check is a visual review, selected-frame comparison or file-level identity check; none should be reported as another. Untested models, shots and later time periods remain untested.
If the demonstration supports broad stylistic continuity, scope the service that way. If the requirement is strict preservation of a product and action, assess retained media, compositing preparation or a different shot design. Make that production decision before a revision deadline.
Compare the maintenance promise behind the rate
ONCE proposes four scope categories: approved-media archiving; rerun validation within an agreed scope; editable-project or layer preparation; the actual revision and renewed review. These are purchasing categories, not a rate card or an assumption that every item carries an extra fee.
Give bidders a likely next revision. Ask what files they will reuse, what they must rebuild, how many review rounds are included and when a change becomes a new shot. A handoff containing prompts and seeds has a different scope from one containing editable assets and a defined modification route. A per-second comparison will miss that difference.
For ONCE’s development from project production toward managed content, the reusable asset is a record of which shots can be reused or changed under which conditions. Better margins or reduced rework would need real project evidence. Complete parameter records alone do not establish dependable production capacity.
Explore ONCE’s AI production research for related planning questions. Bring the approved shot, likely next change and protected elements to ONCE so the production plan can allocate generation, practical footage and compositing around the actual maintenance requirement.
Sources and limits
- Runway Dev, API Reference, current documentation checked November 9, 2026; image-to-video seed description for identical requests and similar results.
- Google Cloud Documentation, Generate videos from text prompts, current Veo documentation checked November 9, 2026; seed guidance conditional on unchanged parameters.
This is an evergreen procurement analysis, not a new-release announcement. The scenario and acceptance method are proposals; no client outcome, measured saving or permanent reproducibility guarantee is asserted.
