Inside the FeedVision Playlist Builder: A Broadcast Day in Minutes

Every linear channel starts its day the same way: a grid of empty minutes to be filled, precisely, from midnight to midnight. Traditionally that meant a scheduler, a spreadsheet and an afternoon of arithmetic — start times cascading down a column, ad breaks counted by hand, episode numbers tracked in someone's head. One slip at 09:00 ripples through to closedown, and the whole column shifts.

The FeedVision Playlist Builder replaces that ritual with a system that assembles a complete broadcast day in minutes. It is not a black box: every decision it makes is deterministic, inspectable and reversible. The Builder remembers where each series left off, what traffic has been booked and which dates carry exceptions — and it forgets none of it between builds.

Everything begins with clocks: templates that describe the shape of a day rather than its contents. A weekday clock might run children's programming from 06:00, documentaries through the afternoon and films after 20:00, with replays overnight. Each hour is built from blocks — a programme slot, a break pattern, interstitials — and clocks can differ by weekday, month or season. You define the rhythm of your channel once; the Builder plays it every day.

Because clocks are structural, changing them is cheap. Move a block, tighten a break pattern, swap a strip of programming, and every future day built from that clock inherits the change. There is no copying yesterday into tomorrow, so there is no drift and no fossilised mistake propagating quietly through the month. The template is the single source of truth for how the channel sounds and feels.

A clock decides that a slot belongs to a series; the rotation engine decides which episode airs. Every series in the media library — FeedVision indexes more than 20,000 clips with codes, episodes, ratings and categories — carries a rotation position. When the Builder fills a slot it takes the next episode in sequence, advances the pointer, and when a season's final episode airs, wraps cleanly back to the first. No repeats, no gaps, no episode three arriving before episode two.

The subtle part is what happens when you rebuild. Because rotation is deterministic, rebuilding the same day always yields the same episodes — the pointer advances with the airing sequence, not with the number of times you pressed the button. Rebuild Tuesday five times while you fine-tune the breaks and rotation does not lurch five episodes ahead. It holds its place, the way a librarian keeps a finger in the book.

Commercial traffic arrives the way sales houses actually send it: as a CSV. The Builder imports the file and distributes spots across up to 49 break slots in the broadcast day, checking every placement against the airtime actually available. If a break is oversold — 240 seconds of copy squeezed into a 180-second window — duration-conflict detection flags it before the day is built, not after it has gone to air.

Breaks rarely sell out exactly, so the Builder closes the gap itself. House-ad campaigns and promos are managed alongside paid spots, and an exact-fit fill pass selects material that lands each break — and therefore each hour — on time to the second. Mid-show wedges extend the same logic inside programmes: mark where a long-form show should break and the Builder splits it there, inserts the break, and keeps every downstream start time honest.

Broadcast compliance is usually a checklist; in FeedVision it is a property of the media itself. Every clip carries an age rating in the library, and the Builder attaches the matching on-screen rating overlay as a secondary event when the day is assembled. The right symbol appears at the right moment on every airing, because nobody had to remember to add it.

The same secondary-event machinery drives timed popup graphics: a coming-up-next promo twenty minutes into a film, a sponsorship bug at the top of the hour. Each is defined once, resolved against real programme timings at build, and travels to the playout server inside the playlist itself — no separate graphics schedule to maintain, and no way for pictures and playlist to fall out of step.

Real schedules have exceptions. Christmas morning does not look like an ordinary Thursday, and a special can displace an entire evening. Date-specific overrides handle both: pin a particular clock, block or title to a single date and the Builder uses it for that day only, then returns to the regular pattern with no manual restoration. The exception never becomes the accidental new rule.

Underpinning everything is the property schedulers come to trust most: rebuilds are idempotent. Change one break at 15:00 and rebuild, and the Builder reconciles the day rather than duplicating it — identical inputs produce an identical day, byte for byte. Rotation positions hold, traffic stays placed, overlays stay attached. Rebuilding stops being something you do with held breath and becomes something you do a dozen times before lunch.

When the day is right, delivery is a single action. FeedVision exports a byte-perfect playlist for any professional workflow, or pushes the day directly to playout servers of the VSN and SL NEO class in real time — including live appends to the on-air queue while the channel is transmitting. What you approved on screen is what the server receives, with no re-keying in between.

Then there is Autopilot. Every night it builds the next full 24-hour day from your clocks, rotations and traffic — and, if you allow it, sends it to air, logging every transmission in an audit trail. As-run reporting closes the loop, recording each airing for aggregate and drill-down analysis. Channels running FeedVision around the clock today wake up to a finished, delivered schedule. The scheduler's job stops being data entry and becomes what it always should have been: editorial judgement.