Beta We're building & testing the platform. Public sign-up opens within the next two weeks. Get early access →
Worked examples

What it actually looks like
on a normal week.

Four situations most stations recognise — a regulator asking a question, a fault at three in the morning, a listener who says they can't hear you, and a moment somebody needs to find again. Here's how each one plays out.

These are illustrative walkthroughs of the product, built with example data — not accounts of named stations. Every screen and figure shown is something the system does; the station, the times and the show names are made up so we're not putting words in anyone's mouth.

01
Compliance & export

“Please supply your output for 14 June, 08:00–09:00.”

The email every station dreads, usually arriving weeks after the fact. What it takes to answer it: about four minutes, and no digging through a studio machine.

  1. Open the date Pick 14 June on the compliance calendar. The off-air feed is there because the box has been recording continuously since the day it was plugged in.
  2. Set the window Drag or type 08:00 to 09:00. You can play it back in the browser first to check it's the right hour before you send anything.
  3. Export One click produces a single audio file for that window, with a certificate stating the device, its GPS location, the clock source and the unbroken segment chain behind it.
  4. Reply Attach the file and the certificate. It's off-air audio — the actual transmission — which is the source the request is asking about.
Compliance · Export window
FeedOff-air · DAB · Example FM
Window14 Jun 2026 · 08:00:00 – 09:00:00 BST
Segments60 / 60 · no gaps
DeviceASB-0f3a · 53.4084, −2.9916
ClockNTP locked · ±11 ms
Chain intactContinuous off-air capture, tamper-evident

Why the off-air part matters here. A playout log would have answered the same question with a file that looks perfect — even if the mux had dropped you for twenty minutes of that hour. The off-air recording is the one that shows what listeners actually got.

02
Monitoring & alerts

Dead air at 03:12. You knew by 03:13.

Overnight automation stalls. Nobody's in the building, nobody's listening closely, and on a station without off-air monitoring it runs silent until the breakfast presenter walks in.

Alerts · IncidentResolved
  1. 03:12:04 Silence detected Off-air level below −50 dBFS, held 20 s. Signal lock still good — the transmitter is fine, the audio isn't.
  2. 03:12:24 Alert opened · email sent To the station's duty address, with a link straight to 03:11 in the player.
  3. 03:19:41 Acknowledged Duty engineer restarts playout from home.
  4. 03:20:58 Audio restored · alert auto-resolved Level back to normal. The incident closes itself — no stale alert to clear in the morning.
Time off air8m 54s
Time to notify20s
Logged asevidence

What else it watches, the same way

  • Source loss — the signal disappears entirely
  • Low level or clipping — you're on air, but wrong
  • Loudness drift — integrated LUFS off the broadcast target
  • Rising bit-error rate — a mux problem, before it's audible
  • Capture gaps — a segment that never arrived
  • Profanity & keywords — with a jump-to-moment link

Alerts open, acknowledge and resolve on their own. The aim is that a quiet inbox genuinely means a quiet night — not that you've learned to ignore it.

And it's evidence, not just a ping. Because the same box recorded the silence, that incident isn't only an email — it's nine minutes of off-air audio you can play back, export, and hand over if anyone ever asks what happened.

03
Coverage mapping

“We can't get you past the retail park.”

A handful of listeners say the signal breaks up somewhere east of town. Without measurements that's an anecdote. With a box on the passenger seat it's a map you can take to the multiplex operator.

  1. Switch a box to roaming One setting. Power it from the car's USB socket and put the aerial on the dash — no other kit, no rented drive-test rig.
  2. Drive the route As you go it logs signal strength, bit-error rate and audio quality against GPS, once a second, while still recording the audio.
  3. Read the map Green where you're clean, amber where it's marginal, red where it drops. The pattern usually points straight at the cause.
  4. Use it Take it to the mux operator, put it in a funding application, or show an advertiser exactly who you reach.
Coverage · Drive 14 JunRoaming
Transmitter Retail park · drop-out
Route31.4 km · 47 min · 2,812 readings
Clean reception78% of route
Marginal16% · BER rising
Lost service6% · 1.9 km, one stretch
StrongWeakDrop-out
04
Listen again & search

“Someone said something about the bypass. Tuesday? Wednesday?”

A complaint, a clip for social, a quote somebody wants checked. You know roughly what was said and roughly when — which, in a 42-day archive, is normally the start of a very long afternoon.

Four ways to get to a moment

  • By what was said — search the transcript across the whole archive and jump straight to the line
  • By show — recordings tag themselves from the DAB programme data, or from a schedule you upload or sync from a calendar
  • By time — scrub any second of the last 42 days on a timeline
  • By alert — every incident links to the audio around it

Then play it in the browser, share a link to the exact window, or export just that stretch as a file. Nothing to download and scrub through locally.

Listen again
PlayingMid-Morning · Wed 11 Jun
Tagged fromDAB programme data
10:41:12−18:44
  1. 10:40:58 …and the roadworks are finally finishing up this week…
  2. 10:41:12 …the bypass reopens on Friday morning, both carriageways…
  3. 10:41:29 …so that should take the pressure off the high street…

Worth saying plainly: transcription is there to help you find things, not to make legal claims. What stands as evidence is the off-air audio itself — the transcript is the index that gets you to it.

In beta

See it with your own signal.

We're onboarding beta stations now, with public sign-up opening within the next two weeks. Keen to test it against your own transmission? Get in touch.