Measure a finished master against its delivery spec, check the access, classification and scheduling requirements, and hold anything that fails — a named compliance officer reads the result and signs the transmission release.
Take the finished master, the delivery spec version and the transmission order it is booked against.
02
Read the classification, content warnings and scheduling restrictions already issued for the programme.
Reason
03
Measure loudness, true peak, flash and pattern risk, freeze, black and level against the spec.
04
Read the structure — line-up, clock, part timings, programme start and the audio track layout.
05
Check caption presence, timing and accuracy score, and whether a description track carries content.
Decide
06
Hold the file on any failed check and name the measurement that failed.
07
Route the whole programme to the compliance officer with what was measured and what was not.
Out
08
Hand over the fault list, the measured figures and the spec version each was read against.
09
Retain what was checked, what failed, what a person overturned and what went out anyway.
→Product statement
The agent measures and reports. It does not pass anything for transmission: no programme goes out until a named compliance officer has signed the release.
Example workflow
One master, end to end
AgentHuman
1Master receivedA finished file with the delivery spec version and the transmission order it arrives against
2Structure readLine-up, clock, black, part timings, programme start timecode and the audio track layout the spec asks for
3Measurements runIntegrated loudness and true peak, flash rate and pattern risk, freeze, black, levels and timing
4Access and content checkedCaption presence, timing and accuracy score, description track, classification, warnings and scheduling restrictions
No human action required
Stages 1 to 4 run without a person in the loop — the file is measured and the whole fault list is written before anyone is asked to read it.
5DecisionSplits on the check result
Nothing failed
Reaches the compliance officer clean.
A check failed
Held with the failing measurement named.
Compliance officer and transmission controller
The compliance officer reads the fault list against the programme; the transmission controller confirms the version, the restrictions and the slot before the release is signed.
Accept · Re-check · Send back
Signed — handed back▼
6Transmission releaseOnly after a named compliance officer has read the fault list and signed it
7Outcome evaluatedCheck coverage, disagreement with the compliance viewing, faults found on air and the corrections logged
Overturned calls
Calls a person overturned are counted, by check and by genre.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Passing a programme for transmission.
Clearing or suppressing a photosensitivity flag.
Issuing or changing a classification or content warning.
Overriding a failed delivery-spec check.
Automation boundaryAgent acts unaided
✓Measure the file against the named delivery spec version.
✓Read the structure and check caption and description carriage.
✓Flag photosensitivity risk, classification mismatch and restriction conflicts.
✓Hold the file on a failed check and name the measurement.
Write actions run only inside the approval boundaries agreed during implementation. Transmission is not one of them.
Signing off a territory or compliance version.
Moving a programme across a scheduling restriction.
Changing a loudness, flash or caption threshold.
Notifying a regulator after an on-air fault.
Example output
One master, measured before transmission
Everything the agent measures is attached to the file and the spec version it was read against.
QC output · single masterIllustrative example
Programme
Delivered to
Slot
Checks
Confidence
Transmission
Documentary, one hour
Channel spec v4.2
Pre-watershed
Two failed — held
91%
Not signed
As receivedThe master, the spec version it was booked against and the classification already issued.
Evidence usedIntegrated loudness readFlash sequence at 12:04Caption gap, 40 seconds
Why it is heldA sequence at 12:04 crosses the flash threshold; forty seconds carries no caption.
ActionAcceptRe-checkSend back
What the score decidesIt decides how much the officer re-checks by hand, not whether the programme may go out.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every master deliveredFrom the delivery and the transmission order
03Measurement
Measure what a viewing cannot
Integrated loudness, true peak, flash rate and pattern, caption timing and part structure are figures. They are read off the file rather than judged in the room.
01Approved path
Send the viewing a measured file
The measurements, the structure read and the carriage checks are finished before the compliance officer sits down, so the hour goes on the editorial call rather than on the meters.
02Human review
Catch it in the file, not on air
A loudness, caption or flash fault found after transmission is a complaint, a correction and a regulator-facing record. Found in the file, it is a re-deliver and a slot that still holds.
04Build an evidence trail
Retain the spec version, each measurement, the flags raised, who signed the release and what was found on air afterwards — on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
The wrong calls sit in the speech and in the old masters
Accented and multilingual speech, re-mastered archive and as-live shows carry most of what a compliance officer overturns and most of what reaches air with a fault. Nestack reports performance by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Accented and multilingual speech
6.8%
4.5×
Review
Archive and re-mastered masters
4.1%
2.7×
Review
As-live and live-to-tape
2.7%
1.8×
Watch
Returning-series episodic deliveries
1.1%
0.7×
Normal
Bar: wrong-call rate lift vs. episodic-series baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A check is only as current as the spec behind it
Delivery specs, thresholds and scheduling rules are revised, and a check nobody re-reads keeps measuring against a document that has been replaced.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
On-air faults, overturned calls or held-file counts move on one channel.
02Diagnose
Traced to the spec version, a measurement, a carriage check, a threshold or a restriction rule.
03Improve
The threshold, spec mapping or check is changed with your compliance officer, and version-linked.
04Verify
Re-run against masters already transmitted, including the ones that went out with a fault.
05Learn
The fault is written into the delivery spec your suppliers and the agent both read.
Learn → DetectThe return edge. Each cycle re-reads the spec and the scheduling rules as they now stand — a threshold that passed last quarter may not be the one in force.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, specs and measurement, access-service checks, evaluation, the release workflow, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01QC discovery and automation-boundary definition.
02Delivery-spec and channel-profile mapping.
03Master ingest and structure reading.
04Loudness, level and true-peak measurement.
05Photosensitivity flagging and hold rules.
06Caption presence, timing and accuracy.
07Audio-description and access-service checks.
08Classification, warning and restriction checks.
09Evaluation suite, slices and regression masters.
10Fault report and compliance-review workflow.
11Playout, scheduling and as-run integration.
12Observability, deployment and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne channel, one specProductionProduction QC integrationAdvancedMulti-channel / multi-territory
Introduced at Pilot
Delivery-spec, loudness and true-peak checks✓✓✓
Caption timing and accuracy scoring✓✓✓
Audio-description carriage checks✓✓✓
Classification, warning and scheduling checks✓✓✓
Photosensitivity flagging and hold✓✓✓
Named-officer transmission release✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Playout, scheduling and as-run integration—✓✓
Additional channels, specs and master volume—✓✓
QC observability and evaluation—✓✓
Introduced at Advanced
Multi-territory versions and enterprise controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on the channels and delivery specs in scope, check coverage, access-service depth, volume of masters, release controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01How a programme reaches transmission today, and who signs it→QC discovery and automation-boundary definitionWeek 1
02The delivery specs and channel profiles you deliver against→Delivery-spec and channel-profile mappingWeek 1
03Masters that already transmitted, the clean and the faulty→Master ingest, structure reading and the measurement baselineWeek 2
04Your loudness, flash and caption thresholds as they stand→Measurement thresholds, photosensitivity flagging and hold rulesWeek 2
05Classification records, warnings and scheduling restrictions→Classification, warning and restriction checksWeek 4
06Faults that went out, and how long it took to find out→Evaluation suite, slice reporting and regression mastersWeek 4
07Named compliance officers and transmission controllers→Fault report, review workflow and the release stepWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the evaluation slices and the first releases signed by a named officer.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Programmes in scope, delivery specs and who signs a releaseW2Master ingest, structure reading and the first measurementsW3Caption, description and access-service carriage checksW4Classification, restriction and threshold rules, slices and evaluationW5First releases signed under approval and targeted correctionsW6Production validation, on-air fault review and handover
Reading the bandThe photosensitivity flag and its hold rule are in place in week 2, before any file reaches a compliance officer in week 5. The bars show that order, not a smooth ramp.
At the end of W6Programmes have gone out under a named compliance officer's signature, with the spec version and every measurement behind each one on file, then Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Media AI agent
Build a broadcast-QC agent around your delivery specs and your compliance team.
Show us a programme you delivered last month, the spec and channel profile behind it, and a fault that reached air. We'll measure that master against your own spec and show you what it would have held, what it could only flag, and what no meter would have caught.
