Ten delivered files may represent one finished edit exported ten ways, or ten substantially different pieces. When requesting a quote, describe what changes between versions rather than presenting only a file count. The production work depends on narrative, framing, language, graphics and review requirements, not just the number of filenames.
Begin with the main viewing situations. Identify who will watch, what they need to understand and what action follows. Some versions can share almost everything. Others may need a different opening, a different evidence sequence or a distinct ending to make sense on their own.
Draw the version family
Place the main film at the top of a simple map. Under it, list each proposed derivative and note the elements it shares and changes. Separate technical exports from creative adaptations. A different container or delivery specification is not the same decision as a new story for another audience.
Use clear labels such as “same narrative with alternate closing” or “shorter self-contained customer account”. Avoid vague requests for “social versions” when the intended use has not been defined. That phrase leaves the supplier to guess how much editorial work you expect.
Identify dependencies between versions
A change to the approved core message may affect every derivative. A local change to one closing screen may not. Ask production which elements should be approved first so the family can be developed in a sensible order.
Do not assume that translating words is the only work in a language version. Timing, on-screen text and review may change too. Define the actual deliverable and the specialist responsibilities without treating every language as a simple export setting.
Test whether each version earns its place
For every proposed output, name the placement and the person who will use it. If neither is known, consider whether it should remain an option rather than a committed deliverable. A large package can look efficient while creating assets nobody has a plan to publish or maintain.
Conversely, do not remove a necessary adaptation merely because it increases the count. A film that depends on audio or a particular frame may not serve another placement unchanged. The version map should support a useful decision, not force the smallest possible package.
Hypothetical example
A fictional buyer asks for twelve videos. Discussion reveals that six are technical exports of one film, three need different audience-specific endings and three are standalone short explanations. The initial file count concealed several different kinds of work.
The revised brief identifies the shared core, the alternate endings and the separately structured shorts. The supplier can explain the production and review implications of each group. The buyer can remove an unused ending without assuming that this saves the same effort as cancelling a standalone short film.
Keep the map through delivery
Use the version family as a handover checklist, with clear identifiers and approved purposes. It will also help future updates: a changed claim can be traced to every affected version rather than discovered one file at a time.
See Live Images services and send the proposed version map for scoping. When claims differ between versions, review each independently with reference to ACCC advertising guidance.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.