Local avails rarely disappear all at once. More often, a small assumption moves from a program format into traffic, then into the log, until sellable time is reduced, misplaced, or treated as unavailable.

The schedule may still total correctly. The program still airs. The loss becomes visible only when sales cannot place inventory that everyone believed existed.

Program duration does not define sellable inventory

A half-hour program can contain several kinds of time: network commercial time, local commercial time, promotional time, IDs, sponsorship elements, and operational events. Traffic needs more than a total running time. It needs a break structure that states what can be sold, where, for how long, and under which restrictions.

If programming receives one format, traffic builds another, and playout executes a third, the avail count can change without a formal decision.

Where the time goes

  • A network break is mistakenly classified as local—or the reverse.
  • A format revision reaches scheduling but not traffic.
  • Break durations are rounded or rebuilt to fit a standard clock.
  • Required promos or IDs consume time that sales assumed was commercial inventory.
  • Short-form content is scheduled without a defined traffic format.
  • Regional or platform-specific versions carry different avail structures.
  • Exception logs are corrected manually without updating the source format.
The reconciliation to request

For a representative week, compare the rights or format document, scheduling clock, traffic inventory, final log, and as-run result. Every change in local commercial time should have an explainable source.

Treat the avail as a cross-functional commitment

Programming determines what must fit. Sales establishes the revenue expectation. Traffic turns that expectation into usable inventory. Playout must execute the events correctly. None of those teams can protect local avails alone.

A durable process gives each format an owner, an effective date, version control, and a documented approval path. It also distinguishes planned reductions from accidental losses.

When local avails disappear, the answer is rarely “traffic lost them” or “programming changed them.” The answer is usually that the handoff allowed the definition of sellable time to change without anyone seeing the full impact.

← All insightsAsk about your avail workflow →