Choose a shared home for the plan, a clear place for cut feedback, and a workload your team can actually discuss. A publish date becomes useful when the editing and review time fits before it.
For cards, stages and dated work. Its Premium and Enterprise Calendar view displays a board's cards and checklist dates in week or month views. Cards can have start and end dates; external calendar sync includes the due date, rather than the full start-date and duration span.
Use it to keep the episode's owner, stage and deadline visible. Record the brief and review link beside the card, and check the plan access your workspace actually has.
For sharing media and collecting review feedback. Current V4 Shares support external links, comments and download permissions, version visibility, passphrases and expiration dates. A share's settings determine what a recipient can do; permissions to create shares also matter.
Use a current cut's share link in your planning record, and tell the reviewer which decision is needed. Keep deadline and workload planning explicit beside the feedback workflow.
For keeping ideas, scripts, shot lists and the editor's brief together on a visual board. Its creator workspace documents dated pieces, owners and stages, view-only editor links and free invited collaboration on a paid member's board. Dates sit in tables and tickets; the documented workspace is not a month-grid publishing scheduler.
Use it for creative direction and handoff context. Its current availability is paid early access, with a standalone free plan announced before the end of 2026.
Official workflow documentation reviewed October 5, 2026. This is a documented capability comparison, without a vendor trial or universal ranking.
The brief gives direction. The cut gives context. The capacity plan gives the next deadline a chance.
Before editing
Attach the script, footage location, intended length, must-keep moments and the person who answers questions. Record whether that material is ready.
During review
Choose one current cut and one decision owner. Say which changes are required and which are questions. Keep the next review deadline with that version.
Before release
Check that editing and review effort fits the entered capacity. A feasible allocation still needs the people involved to agree to the work and dates.
Put the estimates against real capacity.
Enter seven-day capacity buckets and video estimates. An actual mixed-integer solver places each video in one allowed bucket, respecting both editing and review capacity. Both efforts occupy the same bucket; this is a workload allocation, not a day-by-day sequence or a promise to deliver.
Capacity buckets
Capacity is the hours you enter, after other commitments. It is not inferred from a calendar or account.
Videos and handoffs
Earliest and latest bucket numbers are inclusive. Manually unready videos block allocation of the complete entered plan; they are never silently dropped.
Load an example or add capacity and videos.
Changing an input cancels pending calculations and invalidates the reviewed allocation. Restoring JSON ignores saved derived results and requires a new calculation. The solver runs locally in a worker; this tool does not sync accounts, send assignments or publish videos. Refresh clears the in-memory project.
One better question for the weekly check-in.
Which estimate changed after the first cut?
Example review prompt. Update the entered effort before relying on the allocation.
What does an infeasible result mean?
No complete allocation satisfies the entered bucket ranges and capacities under this model. It does not identify one unique cause. Revisit estimates, readiness, available hours or deadlines with your team.
Does an allocated plan guarantee delivery?
No. It checks only entered workload and allowed buckets. The model does not order tasks within a bucket, verify footage, infer availability or account for unentered commitments.
What stays in the project file?
The entered title, notes, start date, preference, capacity buckets and every video's details. Restore checks the inputs and recalculates rather than trusting a prior allocation.
Runtime: javascript-lp-solver for binary allocation, Luxon for bucket dates and PapaParse for actual quoted CSV output. The workflow advice and review prompts are original editorial guidance.