Create an account
Product tour · 03 chapters

One story.
Carry it all the way through.

Follow one story without rebuilding it at each handoff. See how approved work becomes a timed rundown, how a rundown event can trigger configured actions, and how the context can continue into configured publishing and archive workflows.

Explore the product tour
01 · Start from agreed work

Keep the story together.

Bring the brief, script, feedback, versions, and approval into one place, so production starts from the agreed story.

  1. 01Bring in the brief and research
  2. 02Review one shared script
  3. 03Approve the production-ready story
Approved storyTimed rundownMove forward without rebuilding the work.
02 · Keep the live team aligned

Make the next cue clear.

Turn approved work into a timed rundown, assign owners, and keep timing, readiness, and late changes visible as the show unfolds.

  1. 01Build one live production plan
  2. 02Keep owners and readiness visible
  3. 03Advance the next cue in Studio Mode
Rundown eventConfigured actionUse the live plan to start what happens next.
03 · Reduce repeat control

Let the cue start what follows.

Use a rundown event to trigger configured studio actions and continue into configured publishing or archive workflows. Fabl Studio Agent executes supported device commands on the production network.

  1. 01Choose the rundown event
  2. 02Configure the next action
  3. 03Execute supported device commands on site
Keep the context moving

The work continues
past the rundown.

01Brief and script
02Live rundown
03Configured actions
04Publishing
05Archive
Your next step

See where Fabl fits your production.

Create an account, or show us the production handoff you want to improve.