One campaign. Every required version.

Campaign versioning is more than resizing.

A 30-second master, a six-second bumper and a vertical story share a campaign, but they do not necessarily share an edit. Versioning can change aspect ratio, timing, copy, offer, language, product imagery and the order of scenes. Resizing addresses only one of those dimensions.

List the intended changes for each output. Keep technical specifications separate from creative decisions: 1080 × 1920 describes a canvas, but it does not tell an editor where the product, headline and call to action belong.

Give every version a clear identity.

Build a version register before production starts. Assign each deliverable a stable identifier, then record its market, placement, duration, language, offer, source revision and approval owner. A filename is useful, but it should not be the only place the production team can find this information.

When the master changes, identify which versions are affected. A global product change may touch everything; a local offer change may touch only one market. Review the affected outputs again rather than assuming a previous approval still applies.

• Define the approved master revision and its source assets.
• Separate fixed brand elements from permitted variations.
• Choose representative formats for the first review.
• Record exceptions and the person who can approve them.
• Deliver the accepted revision with an unambiguous file name.

Stress-test the difficult versions.

Evaluate campaign versioning software with the longest headline, the narrowest crop and the shortest edit in the brief. Inspect safe areas, subtitles, end cards, audio transitions and product visibility. A layout that works in landscape can need a different hierarchy in portrait.

Then request a late change. Can the editor fix one version without disturbing the approved master? Can someone else understand what changed? Can you reopen the source after export? Those questions reveal more than a grid of polished thumbnails.

Start with a representative family of assets.

For a Revolv pilot, bring the master and a small family of related deliverables. Composer provides the editing context; Ops brings the production brief, owners and review work into the wider job. We will confirm which adaptation steps fit your source files and which need creative attention.

Agree acceptance criteria for each version, including the editable handoff. Measure preparation and revision effort alongside export time. Expand the workflow only after the team can reliably finish the representative set.