Welcome to Bay.

Producers create a job in Bay and assign it to you. The job carries everything you need: title, brief, due date, pay rate, and the Frame.io folder where the footage lives.

Cut the rough. Drag the card from Rough Cut to Internal Review, or just upload v1 to Frame.io. Bay watches the asset and moves the card forward automatically.

Producers and Alex review inside Frame.io. Their comments flow back into Bay as revisions, and the card slides to the Revisions column with a count bump.

When approved, Bay queues a Wise transfer end of week, batched. You see Paid stamped on the card with the date.

Frame.io stays the editor UI for everything visual: review links, comments, version stacks, frame-precise notes. Bay never tries to replace it.

Bay is the single source of truth for status: who's cutting what, where it sits, what it pays, when it's due. The two are wired together via the Frame.io webhook so neither one drifts.

Practically: drop your cuts in the Frame.io folder linked on the job. Reply to comments inside Frame.io. Bay catches every event and updates the job behind the scenes, so you never double-bookkeep.

Read the full structure doc for folder conventions and naming.

Cut cadence, B-roll rhythm, overlay treatment, pacing. None of these are taste calls. They're patterns. We've curated a library of the references that move the needle for OVO short-form and long-form.

Before you start a cut, scan the references tagged for that owner and format. Match the cadence. Steal the structure. The fastest path to approved-on-v1 is studying what already worked.

The library is at /editing. It's read-only for editors but always live: when Alex or a producer adds a new study, it shows up immediately.