Video Workflow Mapper

Map the steps of a video project and see where delays could build up.

Working Runs in your browser, and nothing is uploaded. Try it below on sample data.

The problem

Every kind of video has its own route to delivery, and delays hide in the handoffs, like motion waiting for a script.

A tool that maps the route for each type of video and level of quality, so dependencies, reviews and the busiest role are clear before work starts.

Features and limits

Four fictional formats (explainer, social cutdowns, webinar, launch film) and three quality tiers (Fast, Standard, Flagship).
Swimlane map by lane (Producer, Editor, Motion, Review) with every dependency respected.
Tiers set the review rounds and the QA gates (spelling, brand, audio, legal, accessibility).
Critical path computed from the durations you enter, highlighted on the map.
Team size per lane shows which lane limits throughput.
Export a checklist SOP (Markdown) or the full map (JSON).

A planning framework, not a measured or automated workflow: durations are starting values to edit, not facts about any team.
No drag-and-drop routing yet; stages and dependencies come from the format templates.
Lane load is total days per person; it does not model calendars, holidays or parallel projects.

Drag/drop routing, reusable SOP templates and handoff analytics.

How to use

Pick a format and a tier. The highlighted bars are the critical path; black ticks mark QA gates.
Open Edit durations and change any stage; the map and the critical path update.
Set the team size per lane to see where the bottleneck moves.
Export the SOP checklist for the team, or the JSON map.

How it works

Stages form a dependency graph; earliest start is the latest finish of its dependencies, and loops are rejected.
The critical path is traced back from the last finish through dependencies that end exactly when the next stage starts.
Review rounds and change rounds are generated per tier, with the gate on the final round.

Download

No download yet. A download appears here only after the package is built from reviewed code, installed and tested.

Tested versions & limits

Pass Unit: every format and tier builds a valid map ending in delivery Node 22, Linux
Pass Unit: tiers set review rounds and QA gates Node 22, Linux
Pass Unit: critical path, bottleneck, loop rejection Node 22, Linux
Pass Unit: SOP checklist export Node 22, Linux
Pass Browser: map, team size, tier, SOP export Chromium (Playwright), 1280px

Last verified 2026-10-31.

A planning framework that works in the browser; durations are inputs, not measurements.

Details