Every version.
Every deadline.

Everything your distribution team needs.

Every version type. Every delivery stage. Every stakeholder — all connected in one pipeline.

What's due next, across every title.

The dashboard counts every version by status — not started, in progress, completed, delayed, blocked — and lines up the next deliveries across all your titles, with each production's versions-complete figure beside it.

Every stage on one schedule.

The schedule draws every phase from every version's pipeline onto one Gantt — hour, day, week or month — with festival and trade screenings marked alongside, so a slip shows before it costs a date. Collapse a title, expand a version, jump to now.

Book the right resources at the right time.

Assign people, rooms, and equipment directly to your pipeline stages. The resource timeline keeps everything visible so clashes are caught before they cause problems.

A finished pipeline is not a finished delivery.

A pipeline measures the work your team does. A delivery specification measures the artefacts that have to exist at the end. They are different questions, which is exactly why a pipeline can read 100% while the delivery is short two stems and a CCSL. Routine asks them separately.

Reconcile the package. Don't retype it.

Every material can carry a checksum, file size, package identifier and package type. Point Routine at the manifest your lab or localisation house already produced, and it will tell you whether what arrived is what the version says it holds.

The record a licensee actually asks you for.

Identifiers, a licensee-facing spec sheet and a delivery calendar — the three things that get asked for by email and answered by hand.

Every territory has an opinion about your film.

A logo in shot, a song nobody cleared, a map with a disputed border, a cigarette in close-up: every rights and sensitivity concern lives in one register — where it is in the film to the frame, what kind of issue it is, and what every territory said about it. Clearances replaces the Smartsheet, and imports it.

From the screening room, or from your vendor.

In the screening room, issues are logged from a tablet against the running clock — tap a category at the moment it is on screen, hold to add your own buttons. Or order the review from your vendor: you see when they opened it, when they received it, every issue they log, and when they pressed Complete.

Offices answer in their own language.

Pick the offices and the issues, set a respond-by date, and reminders go out on their own — two days before and after the date, up to three times. Each office answers from its own link, in its own language, with no login: no issue, keep it, replace it, or cut required, with a note on why. An internal office can answer inside the app instead.

Every issue against every territory.

Back at HQ, the matrix fills in as the offices answer — no issue, keep, replace, cut required, awaiting, overdue — so who is holding up delivery shows at a glance. Open any issue and every territory is there, overdue first, with a chase for the ones that are late and the whole thread of circulations, answers and notes underneath.

Classification, territory by version.

Classification works the same way: every territory, every ratings body, every version — what was submitted, what it was rated, and what is still waiting on cuts. When a board asks for a cut, it is linked back to the issue in the register, and the compliant version is recorded against the rating.

Take control of your distribution pipeline.

Try it free for 14 days — or tell us about your slate and we'll walk you through it.

No card needed.