Arrive at the timeline with the story already mapped

The problem it solves

Everything the app worked out, the beats, which clip serves which moment, what the verdict flagged, normally stops at the edge of the NLE. The editor rebuilds it by watching everything, which is the work you just paid to avoid.

What it needs first

• An organized workspace. Export hands over the structure Organize produced, so it runs after it rather than instead of it.

How it works

1. 1 The structure becomes markers and binsBeats become markers, selects become bins, so the organisation arrives as part of the project rather than as instructions.
2. 2 A manifest travels with itThe handoff describes what is what, so nothing depends on the editor having the app or reading a long message.
3. 3 You still make every cutIt is a handoff, not an edit. Nothing is trimmed, joined or rendered.

What you get back

A reference document

The spine rendered as Markdown in beat order, intents and scripts included, so an editor has the plan beside the footage.

Bin-per-beat folders

The grouping IS the handoff for a non-Resolve editor: import the folders and the story order is already there, with no per-clip manifest to keep in sync.

A Resolve push

For Resolve users, a scripted handoff of markers and bins rather than a folder drag.

What it will not do

• It never cuts. Markers, bins and reference docs go across; the edit is yours.
• It is a handoff, not a live link. Re-export after changing the spine; nothing syncs continuously.

What it buys you

• The structure survives the handoff instead of dying at it.
• Your editor starts from a map rather than from four hours of unknowns.
• Nothing about your NLE workflow has to change.

Questions