The board already knows what is due where
Your delivery list, with each destination’s spec, owner and timing, is already in the system. Handing that to a transcoder you also control removes the step where somebody re-enters it.
Integrations
What it connects to, and what gets built for you
Every item below says which of three things it is: working today, being built, or built on request. Nothing is listed as available when it is not.
6 working today. 1 being built. 15 built on request.
Most of this list is the third kind, and it is written that way on purpose. If you need one of them, it gets built for your show — see what that actually means before you take our word for it.
Why that is not just a promise
The board never knew which platform it was talking to
From the beginning, an episode carries a link to where its cut can be watched, and Wheelhouse stores that link without caring who issued it.
That means connecting a review platform is filling a seam that already exists — not changing how the board works, and not a rewrite of anything. The same is true of storage: the program that runs inside your facility already reports “this file landed”, and pointing it at a different kind of location is a connector, not a new product.
It is still real work, and it is still honest to call it unbuilt until it is built. But it is the difference between a feature request and an architecture change.
Where people watch the cut
Every card can carry a link straight to the cut it is about, so nobody hunts for it. The board stores a link and does not care who issued it — which is why a new platform here is a connector rather than a rebuild.
- Frame.ioBuilt on request
Put the review link on the card, and open the right version from the handoff.
- Sony CiBuilt on request
Open the cut from the card, and stream the proxy without a second copy.
- MediaSiloBuilt on request
Carry the review link per episode and per deliverable.
- Vimeo / WipsterBuilt on request
Same seam. A link on the card that goes to the right cut.
Where your cuts are tracked
This is what lets the board CONFIRM which version somebody handed over, rather than repeating back what they typed. It is deliberately source-agnostic: whatever system knows which cuts exist pushes that in, and the board takes the same shape from all of them.
- Avid MediaCentral / Production ManagementWorking today
Reports which versions exist, so a handoff is marked verified, superseded or not found.
- PilotWareWorking today
A PilotWare export feeds the same version check. No Avid Production Management needed.
- A nightly export, or a pasted listWorking today
Genuinely supported. If a person pastes the list of cuts, the check still works.
- DaVinci ResolveBuilt on request
Read version and timeline state from a Resolve-based post, and carry it onto the card.
- Adobe Premiere / ProductionsBuilt on request
The same version check, against a Premiere-based post.
Where the files live
This is what turns estimated dates into confirmed ones. A program inside your facility sees a master land and tells the board, so nobody types it in.
- Your own storageWorking today
Watches your volumes and masters, and reports what exists. Confirmed dates come from here.
- BoxBuilt on request
Watch a delivery folder and mark a deliverable as arrived when it appears.
- DropboxBuilt on request
Same: watch the folder that matters, report what landed.
- Aspera / SigniantBuilt on request
Confirm a delivery actually completed, rather than that somebody started one.
- Amazon S3Built on request
Watch a bucket or prefix used as a delivery destination.
Where the media is catalogued
Read from your asset management rather than making people re-key what it already knows. Nothing is copied or duplicated.
- IconikBuilt on request
Read asset and proxy records so the board can point at them.
- Dalet / AteliereBuilt on request
Read catalogue state for episodes and masters.
How people get told
One line, addressed to a person, naming the show and the cut. Everything here is optional — activity works with nothing connected at all.
- SlackWorking today
Posts the handoff message to the person or channel.
- EmailWorking today
Same message, for people who do not live in Slack.
- Microsoft TeamsBuilt on request
The same message, in Teams.
- SMS / pushBeing built
Per-person choice, so nobody gets pinged three ways for one thing.
Somebody else’s transcode and delivery
If you already run a transcode farm, the board reports on it rather than replacing it. If you would rather not run one at all, see the section below.
- Telestream VantageBuilt on request
Report job state per deliverable, including failures.
- Your network’s delivery portalBuilt on request
Whatever the network makes you use. These are usually bespoke.
Not listed? Ask. The answer is often yes, and when it is genuinely no — because the platform does not expose what would be needed — you get told that instead of a maybe.
Not an integration — ours
Our own cloud transcode and delivery
Transcode and delivery run on our own cloud platform, so a show that does not want to buy, run and babysit a transcode farm does not have to.
Delivered means delivered, not submitted
Because the job is ours, the board sees it finish or fail. That is the difference between a deliverable marked done and a deliverable somebody pressed go on.
Nothing about it is compulsory
If you already run Vantage or a facility farm, keep it. The board reports on that instead. This exists for shows that would rather not own one.
Switching
Moving off what you run now
If you are already on something, you do not have to start from an empty board — and you do not have to switch mid-season to find out whether this works.
- PilotWareWorking today
Run alongside it or move off it. A PilotWare export already feeds the version check, so the same export that keeps the two in step is the one that brings your season across.
- SpreadsheetsWorking today
The most common starting point by a distance. Episodes, air dates, packages and the delivery list come across from the sheets you already keep.
- Airtable, Monday, NotionBuilt on request
Export-led, same as a spreadsheet. What transfers depends on how you shaped it.
You can run both for a stretch. Nothing about this requires a cutover date, and a season already in flight is the worst possible time to be forced into one.
Terms
What “built on request” actually means
Four things, so it is not a word that means whatever is convenient later.
It is scoped against your show, not in the abstract
What you want it to do decides the work. "Connect to Box" can mean watching one delivery folder or reconciling a whole library, and those are not the same job.
You are told what it will take before it starts
Including when the honest answer is that the platform does not expose what would be needed.
It becomes part of the product
A connector built for one show is maintained like everything else and is available to the next one. Your show does not end up on a private fork that stops getting updates.
Nothing is required to start
The board works with none of this connected. Connectors make dates confirmed rather than estimated; they are not a prerequisite for using it.
Before you worry about any of it
None of this is required to start
The board runs a season with nothing connected. That is exactly how the live demo runs.
What connectors buy you is fewer things typed in and more dates that are confirmed rather than estimated. Every card already says which of the two it is showing, so an unconnected board is honest rather than empty.
Tell us what you already run
Bring the list of what your post is on today. You will get a straight answer about what connects, what would be built, and what is not worth doing.
Walkthroughs are with Kevin Kelsey — 15 years an assistant editor, Children's & Family Emmy-nominated, and the person who built this. More about him.
Product names above belong to their respective owners and are used only to describe what this connects to. No partnership, endorsement or certification is implied.