What radio syndication actually is
Radio syndication is the business of one programme playing on stations that do not own it. A show, a format or a live feed originates in one place and airs on affiliates across many markets, each of which keeps its own local commercial breaks and its own identity.
The origin makes its money two ways. Barter means the syndicator keeps some of the advertising positions inside the show and sells them nationally, while the affiliate keeps the rest for its own market — so the affiliate pays in inventory rather than cash. Cash syndication means the station simply buys the right to air it. Most networks run some of both.
The hard part has never been the audio. It is everything around it: making sure 250 affiliates all took delivery of the right version, that the local breaks fire in the right places at each of them, that the national positions inside the show actually ran, and that there is evidence a sponsor will accept when it is time to bill.
Three ways to syndicate, and they are genuinely different
AirWaves does all three from one platform, and which one you want depends on what you are sending.
- Format syndication — you send an entire sound. Clocks, categories, music and imaging travel as one package; affiliates run your format around the clock with their own breaks dropped in, and refreshing it at the origin updates every affiliate.
- Produced syndication — you send finished episodes. Each affiliate pulls clean, tagged, marked, ready-to-air files on schedule, with no manual handoff and nothing to email.
- Live syndication — you send your air, as it happens. The long haul is WebRTC rather than a public Icecast hop, and at the affiliate end it arrives as an ordinary live source their automation already knows how to air.
The apply engine, and why a dry run is the feature
Sending a format to a subscriber station is not copying files. The affiliate has its own scheduler, its own categories, its own library and its own cart numbering, and a format has to be reconciled into all of it.
So AirWaves diffs. A subscriber pulls the latest snapshot of the format, compares it against the local scheduler, and works out exactly what would have to change: which categories are missing, which audio it does not hold yet, what would be imported and where.
A dry run is first-class, not a debug flag. It performs every read and no write, and hands back the precise work list that applying would carry out. A programme director sees what is about to happen to their station before it happens — which is the difference between adopting a format and being handed one. Audio that does have to come down arrives through the station’s own import pipeline, tagger and marker finder, exactly like every other piece of audio in the building.
National avails — the network’s own positions inside the break
A break inside a syndicated show has traditionally belonged entirely to the affiliate: it fills from their traffic log, and whatever runs there is whatever that market sold. That is right for local inventory and wrong for national.
A network sells positions inside the show — the two spots at the top of break one, in every market at once — and in most systems there is nowhere in the clock to say so. The order gets cleared to the affiliate and exported as a flat file, and nothing carries it into the break the show actually contains.
In AirWaves a break slot can be told to fill from the network and name the avail, and the spots the network scheduled for that market land in that position. The rest of the break stays local. Barter stops being a spreadsheet reconciled after the fact.
Affidavits: three proofs, and they are not equal
An affidavit answers the only question a sponsor cares about — did it actually run? Delivery is not that answer. A receipt proves a station took the file, not that it aired it, and no syndicator bills against a receipt.
AirWaves distinguishes the proofs rather than flattening them, and says which one it has:
- Playout — the affiliate runs AirWaves, so the spin appears in its own play history. Machine-verified, no human in the loop. This is the strongest evidence available.
- Log — the affiliate runs foreign automation. NexGen, WideOrbit, OpX or ENCO drops its as-played log in a folder and AirWaves reads it back. Real evidence from the system that actually played it.
- Attested — a human says it ran. Sometimes it is all there is, and it should never be presented as if it were the other two.
Affiliates do not have to run your automation
The assumption that everyone downstream runs the same software is what makes most syndication systems unusable in the real world. AirWaves treats the affiliate’s stack as a given.
A received episode has a delivery target — a watched folder belonging to NexGen, WideOrbit, OpX, ENCO or the AirWaves library itself, each with its own naming rule, its own cart numbering and its own conversion. A building with six services being fed does not need six stations; it needs six targets, which is a far lighter thing.
On the live side the same principle applies to the last inch. The long-haul leg is WebRTC, but at the affiliate the feed is re-encoded locally and registered as an ordinary live source — so it airs through the same mechanism their automation already uses for any network feed, with nothing exotic in the air chain.
One bad render should not reach 250 stations
A watched folder publishes whatever lands in it, and whatever lands in it goes to everyone. The blast radius of one bad export is the entire network: a four-second file, a silent file, a mono file at half the level of everything else on their air.
So between “the file has finished writing” and “publish it”, AirWaves inspects it. A hard failure holds the episode — nothing is uploaded, nothing is registered, and nobody downloads it. One check at the origin costs a single pass over the audio. The same mistake caught after publishing costs 250 downloads, 250 imports and 250 phone calls.
Radio syndication, answered
Radio syndication is one programme airing on stations that do not produce it. A show, a format or a live feed originates in one place and runs on affiliates in many markets, each keeping its own local commercial breaks and station identity. The syndicator is paid either in cash or in barter — keeping some advertising positions inside the show to sell nationally while the affiliate keeps the rest.
In cash syndication the station pays for the right to air the programme. In barter the station pays in inventory instead: the syndicator keeps some of the commercial positions inside the show and sells them nationally, and the affiliate keeps the remaining positions for its own market. Barter is the more common model for daily and weekly radio shows, and it is why national positions inside the break have to be handled properly rather than reconciled on a spreadsheet afterwards.
With an affidavit, and AirWaves distinguishes three grades of it. If the affiliate runs AirWaves, the spin appears in its own play history and the proof is machine-verified with no human involved. If the affiliate runs foreign automation, its as-played log is dropped in a folder and read back — still real evidence, from the system that played it. If neither is available, a human attests, and that is reported as an attestation rather than dressed up as machine proof.
No. A received episode can be delivered into a watched folder belonging to NexGen, WideOrbit, OpX or ENCO, with its own naming rule, cart numbering and audio conversion. A station on foreign automation can still return as-played evidence for affidavits. Affiliates running AirWaves get machine-verified proof and automatic clock handling; everyone else still gets clean, correctly named, ready-to-air files.
The long-haul leg runs over WebRTC rather than a public streaming hop, which keeps latency and packet loss under control across a wide area. At the affiliate the feed is decoded and re-registered locally as an ordinary live source, so the station airs it through the same path its automation already uses for any network feed — a live element in a clock or an entry in the event schedule. Nothing unusual sits in the air chain.
Yes, and it is a different mechanism from sending episodes. Format syndication delivers clocks, categories, music and imaging as one package. A subscribing station pulls the latest snapshot, and AirWaves diffs it against that station’s own scheduler to work out exactly what would change. A dry run performs every read and no write and returns the precise work list, so the affiliate sees what will happen to their station before it happens. Refresh the format at the origin and every affiliate follows.
There is no fixed ceiling in the software; distribution is per-affiliate delivery rather than a fixed satellite path, so adding a market is adding a target. What matters more at scale is the quality gate at the origin: a bad export reaching every affiliate at once is the failure mode that hurts, which is why episodes are inspected before publication and held rather than distributed if they fail.
Explore the rest of the platform
Every AirWaves module shares one engine, one database and one login — and every one of them also runs standalone against the automation system you already own.
Put your show on every affiliate at once
Book a walkthrough with an engineer who has actually run a radio station, or call 1-877-224-1656. No bots, no phone tree.