For indie film and TV catalogue owners — the buyer the spec names is the catalogue owner's delivery lead — delivering titles to distributors, aggregators, and FAST outlets: Delivery Control keeps one master deliverables package per title, each outlet's requirement set as your own record, the package checked against that set before you submit, submissions and QC bounces tracked as your records, and avails windows surfaced from the dates you enter. No outlet is connected to Delivery Control, and Delivery Control submits nothing anywhere.
How it works
- Build the master package once per title — a master package checklist, an editable starter list of deliverable elements
- Keep each outlet's requirement set and spec notes as your own record — distributors, aggregators, and FAST outlets, each with its own set
- Pre-validate the title against an outlet before you submit — every gap listed; gaps you submit with are recorded as acknowledged exceptions, never hidden; the check runs against the set you maintain, never against a live outlet system
- Track submissions and QC bounces as your records — Not started, Preparing, Submitted, In QC, Bounced, Accepted, Live — with bounce reasons tied to elements and bounce counts per outlet and per element; you submit and transfer files with your own tools
- Watch avails windows from the dates you enter — per title and outlet, ranked by days to expiry, inside-90-days and expired windows flagged — on a catalogue board with title-by-outlet status counts reconciled, bounce work first, and windows closing soonest on top
The master package — one per title
Each title starts with one master deliverables package, built once for that title. The package is worked from a master package checklist — an editable starter list of deliverable elements, kept as your record for that title.
That one master package is what every outlet delivery for the title is prepared from, so a title is assembled once and then checked outlet by outlet, instead of being rebuilt for each outlet.
- One master deliverables package per title
- Master package checklist — an editable starter list of deliverable elements
- The same master package checked against each outlet's own requirement set
Outlets — each with its own requirement set, kept as your record
A title is delivered to distributors, aggregators, and FAST outlets — the spec frames a title as going to 5 to 20 outlets. Each outlet carries its own requirement set and spec notes in Delivery Control, kept as your own record for that outlet.
Requirement sets and statuses in Delivery Control are your own records. The requirement library does not ship with any outlet's requirements built in: its content is maintained from real outlet specs as they are supplied, outlet by outlet, in pilot use. Until a real outlet spec sheet supplies an outlet's set, that outlet's set is only what you enter and keep for it.
- Distributors, aggregators, and FAST outlets — each outlet with its own requirement set and spec notes
- Every requirement set is a record you maintain in the product
- No outlet's requirements are built in — the library is maintained from real outlet specs as they are supplied
Pre-validation — checked against your own set before you submit
Before a title goes to an outlet, pre-validation checks the title's master package against that outlet's requirement set — the set you maintain in the product — and lists every gap before submission. Pre-validated here means exactly that check, and nothing more: it is never a check against a live outlet system.
If you submit with gaps, the gaps are recorded as acknowledged exceptions — they are never hidden. Checking a package against your own set never guarantees that an outlet accepts the package or that it passes QC: acceptance and QC are the outlet's decisions, and no check in Delivery Control can promise them.
- Every gap listed before submission
- Gaps you submit with are recorded as acknowledged exceptions, never hidden
- No acceptance is promised and no QC pass is promised — pre-validation checks your package against your own set only
No outlet is connected — the settled rule
This is settled, and it is stated plainly: no outlet is connected to Delivery Control. Delivery Control submits nothing to any outlet, and it transfers no files to anyone. You submit and deliver with your own tools, in your own way, and Delivery Control keeps the records of that work.
File-transfer and QC integrations are not connected. There is no live connection to any distributor, aggregator, or FAST outlet behind any part of this product, and no part of the product reaches an outlet's system.
Submissions and QC bounces — tracked as your records
Each title's work at each outlet is tracked through its standings, as you record them. When an outlet bounces a package in QC, the bounce reason is tied to the element it concerns, and bounce counts per outlet and per element surface the problems that keep recurring.
The catalogue board reconciles title-by-outlet status counts, with bounce work first — so the work an outlet sent back is the work that leads the board.
- Not started
- Preparing
- Submitted
- In QC
- Bounced
- Accepted
- Live
- QC bounce reasons tied to elements, with bounce counts per outlet and per element
- Catalogue board — title-by-outlet status counts reconciled, bounce work first
Avails windows — surfaced from the dates you enter
Avails windows are kept per title and outlet, from the dates you enter. Windows are ranked by days to expiry, with windows inside 90 days and expired windows flagged, and the catalogue board puts the windows closing soonest on top.
Surfacing a window here means showing you a date you entered, ranked and flagged in time. It is not external monitoring: no outlet is watched, and no window is learned from anywhere but your own records.
- Avails windows per title and outlet, from your entered dates
- Ranked by days to expiry
- Inside-90-days and expired windows flagged
- Windows closing soonest on top of the catalogue board
Where it stands — the honest state
Delivery Control is forming its first producer / distributor pilot group now. The door below is a producer / distributor pilot application — applying starts a pilot conversation; it does not create an account, and it is not a sign-up for a running service.
No outlet is connected, and Delivery Control submits nothing anywhere and transfers no files: requirement sets and statuses are your own records, pre-validation is a check against the requirement set you maintain in the product, and avails windows are surfaced from the dates you enter. You submit and deliver with your own tools.
The requirement library is maintained from real outlet specs as they are supplied — it does not ship with any outlet's requirements built in. File-transfer and QC integrations are not connected.
No price has been set for this door. Prices exist in our market research as hypotheses; they have not been validated and they have not been decided, so no price is shown here and there is nothing to buy on this page.
Producer / distributor pilot application
This is a producer / distributor pilot application — an application to join Delivery Control's first producer / distributor pilot group, not an account sign-up and not a purchase. Tell us who to reach, your company, and how many titles are in your catalog. If you like, tell us how many outlets you deliver to, and how you manage deliveries and outlet requirements today. We will be in touch about the pilot group.