One film, multiple versions: an edit, language and delivery matrix

Short answer. A version matrix lists specific outcomes from one video project. Each row connects purpose, edit, composition, language, sound and delivered objects. All adaptations is not a substitute: it does not identify required combinations, exclusions or what the publishing team will receive.

This guide concerns one film and its derivatives, not a product assortment. Its output is a delivery list connected to editorial decisions and checkable at handover. A shared digital production base can support several uses, but those uses need explicit definitions.

1. Distinguish version, revision and file

Here, a version is an agreed presentation for a purpose, such as a short vertical film with English wording. A revision is its state after changes. A file is a delivered object.

One version may include video and a separate subtitle file. Several technical files may carry the same editorial content. A revision can update an existing purpose row without creating a new purpose.

These are working project definitions. Consistency matters more than the labels themselves. Otherwise, four versions can mean four different edits to the buyer and four exports of one edit to the supplier.

2. Identify the film's shared message

Record the central message retained across the project. Then establish what may be shortened, reordered or replaced for a particular viewing situation.

A main film explaining a device function may become a short edit retaining one argument. Removing a qualification should not accidentally make a different product claim. State the meaning of each editorial branch.

If a new row requires another message and scenes that do not exist, identify it as a separate assignment. Reusing some sources does not turn a new concept into a technical export.

3. Begin with the viewing situation

Record the placement and its role. A website film, presentation asset and advertisement can share material while providing different context.

A website may include surrounding product information. A presentation may rely on a speaker. A standalone advertisement may need to supply its own context. This affects the opening, ending and wording.

Name the person confirming the row's need. A format-language combination should not become mandatory merely because it is easy to add to a spreadsheet.

4. Build the working matrix

ID. Content: Stable result identifier. Decision supported: Locate the row unambiguously.

Purpose. Content: Placement and viewing situation. Decision supported: Explain why it exists.

Edit. Content: Main, short or special. Decision supported: Identify editorial content.

Composition. Content: Wide, vertical or another arrangement. Decision supported: Position important elements.

Language. Content: Voice, titles and subtitles separately. Decision supported: Define localisation.

Sound. Content: Required sound arrangement. Decision supported: State what viewers hear.

Ending. Content: Approved message and action. Decision supported: Define the conclusion.

Delivery. Content: Video and related objects. Decision supported: Identify supplied materials.

State. Content: Row readiness. Decision supported: Determine usability.

Technical parameters can sit in a linked record. Changes to export requirements then remain visible without obscuring the editorial description.

5. A completed example

Consider a hypothetical digital film explaining device P1. It needs a website presentation, short advertising edits and a silent event-screen version. The examples illustrate planning, not customer work.

V01. Purpose: Russian website. Edit: Main. Composition: Wide. Language arrangement: Russian voice and titles.

V02. Purpose: English website. Edit: Main. Composition: Wide. Language arrangement: English voice and titles.

V03. Purpose: Russian advertising. Edit: Short. Composition: Vertical. Language arrangement: Russian voice and titles.

V04. Purpose: English advertising. Edit: Short. Composition: Vertical. Language arrangement: English voice and titles.

V05. Purpose: Meeting screen. Edit: Special silent. Composition: Wide. Language arrangement: Russian screen text.

V06. Purpose: Russian advertising. Edit: Short. Composition: Square. Language arrangement: Russian voice and titles.

The table deliberately excludes some possible combinations. There is no English square version. Confirm that exclusion with the placement owner.

6. Count results before files

The example contains six purpose rows. If V01 and V02 also include separate subtitles, delivery contains six videos plus two related files: eight files.

If each row also needs a cover image, add six objects, producing fourteen files under those assumptions. This does not mean fourteen films or describe production difficulty.

Count independent editorial decisions and delivered objects separately. A cover image then does not appear to be a new edit, while a special silent version does not disappear inside an ordinary export.

7. Do not multiply formats and languages automatically

Two languages and three compositions create six theoretical combinations for one edit. That does not establish a need for all six. In the example, language needs differ by purpose.

Confirm rows first, then use arithmetic as a completeness check. A combination without a real use can remain optional or be excluded.

The reverse problem matters too. A required silent version may never appear in a simple multiplication of languages and frame shapes. Its content is determined by viewing without speech.

8. Separate editorial changes from composition changes

A short edit selects sequence and meaning. A composition adaptation arranges elements within another frame. A version may require both.

Starting with another scene is an editorial decision. Retaining the order while repositioning product and titles changes composition. A technical export packages the agreed result.

Ask the supplier to identify these differences row by row. This reveals which decisions precede delivery without turning the matrix into a complete production estimate.

9. Approve the opening of each editorial branch

A short version need not begin where the main film begins. It should provide enough context for its viewing situation. A pleasing fragment extracted from the middle may not explain itself.

For each branch, note what viewers see first, what they learn before the main action and which argument remains at the end. This is a compact editorial map rather than another full script.

A language change may require reconsideration of the opening too. Base the decision on the actual approved wording and its presentation, not an assumed universal relationship between translation length and timing.

10. Define what a language version contains

Separate voice, screen titles, product marking and subtitles. EN does not say which layers change. V02 may translate voice and advertising titles while retaining the device's original marking.

Assign an owner for final wording. Draft translation can support planning, but delivery needs approved lines. Changes should identify all dependent results.

Avoid several unconnected copies of the same wording. An approved text identifier linked to its uses can establish the authoritative version without prescribing particular software.

11. Define a silent version by its meaning

Silencing a soundtrack may remove essential explanation. Decide whether that information is replaced by screen text, another sequence or clearer action.

For V05, list what must remain understandable without speech. If a speaker accompanies the video, separately identify information intentionally left to that presentation.

Review the result in its actual mode, without listening to explanatory audio. Otherwise, reviewers may find it obvious only because they remember the narration.

12. Specify subtitle delivery

State whether subtitles are separate, embedded or both. Identify language and corresponding edit revision. A subtitle file for the long edit is not automatically ready for a short edit on the same subject.

Separate subtitle filenames and delivery records should connect them to the exact video. For embedded text, identify whether an uncaptioned counterpart exists and is included.

Do not turn the subtitle row into a general accessibility claim. The matrix records supplied materials; any additional accessibility requirements need their own content and usage assessment.

13. Link each placement to current requirements

Assign a technical-requirement source, checking date and owner. The matrix should not become a permanent specification copied from an older campaign.

Google Ads, for example, recommends different video orientations for specified campaign contexts. That is not a universal mandatory package for every website or screen. Google Ads: square and vertical video, checked 27 September 2026.

Distinguish a platform requirement from a team's choice. This explains why square V06 was prepared and why another placement does not require it.

14. Treat endings as separate dependencies

An ending may contain a name, offer, address or request to contact a representative. Connect different endings to their rows instead of assuming one universal screen.

The website example may use one action while the meeting version ends without a link. English may point to an English destination. The communication owner confirms the exact address and wording.

When an offer changes, identify every dependent row. Updating a source text does not establish that all previously delivered videos have been replaced.

15. Give filenames a useful structure

A proposed name might include project, ID, revision, language and purpose: P1_V03_r07_RU_vertical. This is a working convention, not an industry standard.

Do not include so many parameters that names become unreadable. A stable ID and revision can point to the matrix for detail. Avoid several different objects all called final.

Related materials should repeat the video ID and identify their type. Subtitles and covers are then less likely to become associated with another version when a folder is forwarded.

16. Record actual delivery

V01. Video: Main Russian. Related object: Separate Russian subtitles. Revision: r07. Use: Russian website.

V02. Video: Main English. Related object: Separate English subtitles. Revision: r06. Use: English website.

V03. Video: Short vertical Russian. Related object: Cover. Revision: r05. Use: Agreed advertising use.

V05. Video: Silent screen edit. Related object: No audio track as specified. Revision: r04. Use: Meeting.

This records what was supplied, not only what was planned. If V04 remains underway, state that. A partially populated folder should not imply completion.

The folder link complements the register. It does not replace it, because the folder may contain earlier revisions or working copies while the register identifies usable deliverables.

17. Inspect the package in two passes

First check completeness: every mandatory row has the required objects and a clear state. Mark missing material explicitly rather than inferring it from a similar filename.

Then check correspondence: actual language, edit, ending and intended use in every video. Inspect silent meaning without sound and connect each separate subtitle file to the right revision.

This differs from detailed creative feedback. The handover question is whether the package matches the matrix and can be used without guessing.

18. Update dependencies when the message changes

Suppose the main ending receives a new call to action. Find the rows using that ending and mark which need updating.

A Russian-only request does not automatically establish whether English remains current. Check the semantic dependency: the translation may reflect the former offer even if its file has not changed.

When delivering the update, identify superseded revisions. This helps the publishing team avoid using an earlier downloaded copy from habit.

19. Resolve common ambiguities

All sizes. Ask for actual uses and confirm rows. The phrase does not define delivery.

An English version. Clarify voice, titles, product marking and subtitles separately.

Just trim the short one. Check whether opening, argument and conclusion survive. If not, make an editorial decision.

Without text. Determine whether this means graphic overlays, embedded subtitles or wording on the physical product.

Master accepted. Identify which derivatives have actually been reviewed. Approval of the base does not establish acceptance of every row.

20. Preserve a basis for future adaptations

Retain the matrix, actual-delivery register and approved wording sources. They explain what each version was intended to do.

Separately agree which materials remain available for continuation: finished videos, clean fragments or editable projects. Do not assume every working file is automatically included.

When another format is requested, add its purpose row and assess which existing decisions still fit. The new request can then be discussed through its real differences.

21. Rehearse handover with one row

Before assembling the whole package, follow V01 from approved edit through language arrangement, related materials, filename and register entry. Ask the recipient to find its video and subtitles using only those records.

If spoken explanation is needed, improve the structure before repeating it. The revision may be missing, two similar filenames may be ambiguous or state may be unclear.

Then check an exception such as V05. The recipient should recognise a special silent edit rather than a muted main film.

Do not add fields merely to make the sheet look comprehensive. A field is useful when it changes a decision or helps select material. Explain unused columns or move detail to a linked technical record.

22. Evaluate a new-version request

Suppose an English short meeting-screen film is needed after delivery. Do not simply copy V04: its viewing mode and ending may differ.

The new version may draw its edit from V05, translation from V02 and ending from a separate approval. This reveals actual reuse and new work more clearly than selecting the nearest file by language.

Give the result its own ID and delivery record. If it replaces another asset for the same use, mark the replacement. If both remain active, explain their distinction.

Schedule and price discussions can follow that difference. The matrix does not set a tariff; it establishes the result being discussed.

23. Confirm the package before use

Record which IDs are ready, which revisions are current, which rows are excluded and who received them. Working alternatives can remain separate from the list intended for use.

For staged delivery, name the boundary: first package contains V01 and V02 with subtitles; remaining rows are underway. That is more useful than an unexplained folder link.

Keep the confirmation date. A later update can then identify what was previously supplied and what changes now. The matrix remains useful because it connects decisions with concrete files.

A final reverse check is useful: select an actual file and trace it back to its row, editorial branch and approved wording. Then select a mandatory row and locate all its delivered objects. The two directions reveal different omissions.

If the recipient finds a file outside the register, decide whether it is a working copy, an optional extra or a missing planned result. Do not leave its status to interpretation. If a row has no file, retain its unfinished state rather than marking the package complete because most materials are present.

24. Prepare a matrix for the first discussion

Start with mandatory rows, naming purpose, edit and language arrangement. Add exclusions and questions for the placement owner.

For AI video production or CGI product video, the matrix connects a digital foundation to actual uses. Unknown technical details can remain explicit with a person assigned to confirm them.

Attach it to the brief. The first discussion should produce a clear list of materials, their differences and a handover structure that lets recipients choose the right file.