Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.fabl.studio/llms.txt

Use this file to discover all available pages before exploring further.

Fabl is organized around a set of core concepts that map directly to how professional video productions work. Understanding these building blocks helps you navigate the platform confidently and structure your work in a way that keeps your whole team aligned. This page defines each concept and explains how they fit together inside Fabl.
A Workspace is the top-level environment for your team inside Fabl. Everything your production team creates — rundowns, scripts, shot lists, workflows, and integrations — lives within a workspace.Workspaces are typically organized around a team, a show, or a client. You can create multiple workspaces within a single Fabl account, which makes it easy to keep separate productions or clients cleanly isolated.Key workspace-level settings include:
  • Members and roles — who has access and what they can do
  • Integrations — connections to Slack, Google Drive, Dropbox, Frame.io, Notion, Airtable, Zapier, and Adobe Premiere Pro
  • Export defaults — preferred formats (PDF, Excel, print) and export schedules
Every member you invite to a workspace can see all rundowns and scripts within it, subject to their assigned role (Owner, Editor, or Viewer).
A Rundown is the structured plan for a single production — a sequenced list of segments that defines what happens, in what order, and for how long. Rundowns in Fabl are the central document your entire team works from during pre-production and on the day of the show.Fabl rundowns include:
  • Automatic timing calculations — planned and actual durations update in real time as you build or reorder segments
  • Real-time collaboration — multiple team members can edit the same rundown simultaneously, with changes reflected instantly
  • Status tracking — mark segments as Draft, Ready, In Progress, or Complete to keep the whole team aligned
  • Version history — every save is recorded, and you can roll back to any previous state
Rundowns are tied to a specific show date and start time, making it easy to manage multiple episodes or productions within the same workspace.
A Segment is an individual item within a rundown — a single block of content with its own title, type, duration, assigned team members, and attached assets. Segments are the fundamental unit of production planning in Fabl.Common segment types include Opens, Closes, Interviews, Packages, Live Reports, Commercials, and custom types you define for your workflow.Each segment can have:
  • An attached Script with copy and shot list
  • A planned duration and (after the show) an actual duration
  • Notes for the segment’s crew or contributors
  • Status indicators visible to the full team in real time
Keeping segments granular — one distinct piece of content per segment — gives you the most accurate timing data and makes it easier to reorder your rundown without losing context.
A Script is the written content attached to a segment. In Fabl, scripts are more than a text document — they’re production-ready assets that connect copy, formatting, and visual planning in one place.Fabl scripts support:
  • AI draft generation — describe the segment and let Fabl generate a starting draft
  • Teleprompter formatting — convert your copy into clean, large-type format optimized for on-camera reading
  • Shot list generation — automatically extract shot suggestions from your script content
  • Version history and rollback — every saved version is preserved so you can recover earlier drafts at any time
  • Real-time co-editing — multiple writers or editors can work on the same script simultaneously
Scripts are always linked to a specific segment, so changes to script copy stay connected to the corresponding rundown slot.
A Shot List is an ordered list of camera shots associated with a segment or script. Shot lists in Fabl give directors and camera operators a clear, actionable plan for every part of the production.Shot lists can be:
  • Generated automatically from a script using Fabl’s AI (which analyzes script content and suggests appropriate shots)
  • Built manually by adding shots one by one with descriptions, camera angles, and notes
  • Reordered and edited at any time by anyone with Editor access
Each shot in the list can include a shot type (wide, medium, close-up, cutaway, etc.), a description, and operator assignments.
Shot lists update live, so camera operators and directors always see the latest version — even during active production.
A Cue Point is a time-stamped marker within a production that triggers a specific action or signals a transition. Cue points are used during multi-camera productions and live shows to coordinate the crew in real time.Cue points can mark:
  • Camera switches (e.g., cut from Camera 1 to Camera 2)
  • Graphics or lower-third insertions
  • Audio transitions
  • Custom crew alerts (e.g., “Stand by for live report”)
In Fabl’s Live Show Mode, cue points appear as an operator-facing timeline that advances in real time alongside your rundown, giving directors and technical directors a single view of every upcoming cue.
A Workflow in Fabl is an automated sequence of actions triggered by events, schedules, or status changes in your production. Workflows remove the manual overhead of repetitive handoffs and notifications so your team can focus on the production itself.Examples of what workflows can automate:
  • Scheduled exports — automatically export a rundown to PDF at a set time each day
  • Status-triggered notifications — send a Slack message when a segment’s status changes to “Ready”
  • Integration triggers — push a finalized script to a Google Drive folder or notify a Frame.io project when a script is approved
  • Zapier connections — chain Fabl events into any workflow your team manages outside the platform
Workflows are configured at the workspace level and can be applied to individual productions or across all rundowns in the workspace.
A Production in Fabl is the broader context surrounding a single episode, event, or shoot. While a rundown defines the moment-by-moment plan, a production groups together all the assets — rundowns, scripts, shot lists, notes, and exports — for one complete unit of work.Productions help teams:
  • Keep all related rundowns (e.g., rehearsal, final show) organized together
  • Track overall readiness and status across multiple segments and contributors
  • Archive completed shows with their full version history intact
Use productions to represent a single episode or event, and use the workspace to represent your ongoing show or series. This structure scales cleanly as your production volume grows.

​
How the Concepts Connect

These building blocks fit together in a clear hierarchy:
  • A Workspace contains one or more Productions
  • Each Production has one or more Rundowns
  • Each Rundown is made up of Segments
  • Each Segment can have an attached Script, a Shot List, and one or more Cue Points
  • Workflows run at the workspace level and respond to changes anywhere in the hierarchy
Understanding this structure helps you get the most out of Fabl’s collaboration, automation, and live production features. If you’re ready to put these concepts into practice, follow the Quickstart guide to build your first rundown and script.