Step 2 — Programming

Schedule logic is where FAST channels succeed or fail

Why programming matters more than you think

Most FAST channel teams underestimate programming. A poorly structured schedule creates visible repetition, low completion rates, and viewer drop-off — which FAST platforms track and use to prioritise (or deprioritise) your channel.

Schedule models by library size

Small library (under 40 hours)
Use a rotating wheel with spacing rules — no title repeats within 48 hours. Add promo bumpers between programmes to reduce perceived repetition.

Medium library (40–150 hours)
Block programming: themed blocks by time of day (morning/afternoon/prime/late). Each block has its own content pool. Rotate blocks on a 7-day cycle.

Large library (150+ hours)
Full dayparting with franchise nights, brand partnerships, and thematic lanes. Weekly schedule planning becomes a dedicated editorial function.

Ad break placement

  • Place breaks every 15–20 minutes for long-form content
  • 30-second and 60-second break durations are most common
  • SCTE-35 markers must be within the programme (not at seams)
  • Test break placement in QA before live distribution

Operational cadence

Set a weekly schedule publishing workflow:

  1. Content team confirms available and cleared titles
  2. Programming team builds 7-day forward schedule
  3. SCTE-35 markers validated
  4. EPG feed generated and tested
  5. Published to playout system

Need a schedule template for your library size?

Book a FAST launch call.

See the Programming Guide