Delivery packages
Delivery is where an unrecorded decision becomes someone else's problem.
A buyer rejecting a package for a missing caption file, a wrong cover frame, or an unanswerable question about a music cue is not a creative failure. It is a bookkeeping failure, and it is entirely preventable.
01 / Inside the workflow
What is in the package
- Masters
- The accepted primary production in the format the brief specified, per language track.
- Platform versions and cutdowns
- Derived 9:16, 1:1 or 16:9 versions produced from the approved master rather than made separately. For branded work, UGC-style cutdowns are derivatives of the approved campaign, never standalone production.
- Captions
- Per track, checked for accuracy, timing and reading speed, in the format the destination requires.
- Cover frames and thumbnails
- Selected rather than grabbed, because on a vertical feed the cover frame is part of the hook.
- Cue and rights information
- What music, what source assets, under what grant, for which territories and term.
- Provenance
- How the delivered version was made: models, references, canon versions, repairs and the humans who accepted each.
- Delivery manifest
- The index that says what is in the package and that everything the specification required is present.
02 / Inside the workflow
Derived, not remade
A campaign that needs a 9:16 cutdown, a 1:1 version and three platform edits can be produced two ways. Either each is a production, or each is derived from one approved master.
Derivation is the only version that scales, and it is the only version where brand consistency survives. Three separately produced edits are three chances for the product to be shown wrong. One master with three derived versions has a single point of approval and three mechanical outputs.
03 / Inside the workflow
Final delivery acceptance
- Primary master reviewCreative approver named in the briefBlocks: Derivation of platform versions and cutdowns
- Language and market reviewNative reviewer per trackBlocks: That track only, not the master
- Final delivery acceptanceNamed delivery approver, plus brand or legal where requiredBlocks: Handover of the package
Questions
Before you bring it into production
Does Tosheo publish the episodes for me?
No. Automation in Tosheo cannot publish externally - that is part of the human-control rule. Tosheo prepares a delivery package for the destination you specified, and you or your distribution partner publish it.
Can Tosheo deliver to a platform specification?
Delivery-specification management is one of the Phase 1 services: we take a buyer or platform specification and package against it. What we do not do is claim to be a distributor, an agent or a rights representative, because we are none of those things.
What if a platform requires something we did not plan for?
It becomes a scope change with a cost, and it reopens the gates it affects. The reason delivery requirements sit in the greenlight brief is to make this the exception rather than the normal end of a production.
Are cutdowns included?
Derived versions are a commercial unit: a defined number of language, market and platform variants per package. The number is scoped per production. What is not on offer is unlimited derivation, for the same reason unlimited generation is not on offer.
What does the manifest prove?
That the package is complete against the specification, and how each delivered version was produced. For a buyer doing rights or provenance diligence, it is the difference between an answer and an investigation.

