ProductVersioned delivery

Deliver the approved version with its context.

Collect current approved storyboards into a frozen delivery. Keep the reference files, supplied publishing copy and approval record together in a package people can actually use.

Aster / Sample workspaceExample
Versioned delivery

The approved version,
all in one place.

manifest.json
storyboard.html
subtitles.srt
reference files
Frozen storyboard revision 3ZIP package

Freeze what was approved

A delivery checks the project’s current approval and publishing-copy revision. Changes made afterwards do not rewrite the existing package.

A useful, inspectable package

Download a ZIP with a manifest, HTML and JSON storyboards, SRT subtitles and explicitly included reference files. File sizes and SHA256 checks help verify the retained bytes.

A clear delivery history

Create a private client link with an expiry, revoke it when needed and record a manual handoff. Team members retain access to their permitted history.

Put it to work

A useful next step
at every stage.

Read the practical guide
  1. 1

    Choose the current approved projects in a campaign.

  2. 2

    Check the supplied copy and optional reference files, then create the package.

  3. 3

    Copy the private link or download the ZIP and record the handoff.

Better connected.

All product features
Useful answers

A clearer picture.

From the first client brief to the next content plan. Know what is available and how the pieces connect.

Browse all questions
What is inside a versioned delivery?

Current approved storyboard snapshots, their approval records, separately labelled publishing copy, a manifest and selected reference files. The ZIP includes HTML, JSON and SRT. The client does not receive internal tasks or private source profiles; an uploaded MP4 is a supplied reference, not a generated result.

Your next brief

Bring the next brief
into focus.

Keep the facts, drafts, people and approved version in one workspace.

Start a free previewOr explore the sample