1. The measured file is not the delivered file
A report from yesterday’s bounce tells you nothing certain about today’s export. A limiter change, new tail or altered channel routing can invalidate it. Put the report beside the exact file it describes and compare filenames, duration and revision before making further changes.
For Apple Music Atmos, the published ceiling is −18 LKFS integrated and −1 dBTP. Use the specified measurement method rather than the reading from a convenient stereo downmix. See Apple’s Immersive Audio Source Profile.
2. The timeline follows the wrong brief
An inherited session may use a video frame rate or an export range that differs from the music delivery brief. Check those settings before spending another hour on the mix. Compare the first audible event, song length and fade with the approved reference.
Dolby’s June 2024 Delivery Playbook specifies 24 fps. Apply that when it is the governing brief; do not describe it as the universal rule for every Atmos service or use case.
3. The stereo counterpart belongs to another revision
The stereo file may have the right name and the wrong edit. A pickup moved in the Atmos session, a shortened intro or a different ending is easy to miss when both files came from the same project folder.
Line them up and compare their structure before judging their level. A different integrated loudness reading by itself does not prove the pair is invalid. Save notes about any intentional version difference so the receiving engineer can understand it.
4. File metadata and submission metadata are confused
There are two jobs here: inspect the ADM scene data, and confirm the catalogue information submitted to the distributor. An upload form’s ISRC or engineer credit is not automatically a mandatory embedded ADM field. Follow the destination’s instructions for where each value belongs.
If a parser reports an invalid structure, retain the original export and the exact error. Return to the session or renderer that created it. Renaming a malformed file does not repair its internal relationships.
5. Nobody listened to the headphone version
A mix can satisfy numeric checks and still need another listening pass. Audition important transitions, vocal placement, low-frequency balance and the intended spatial impression. Note the renderer and monitoring path so the result is reproducible.
This is a review task, not a claim that a wide or narrow image automatically causes rejection. Dolby recommends headphone and speaker monitoring, but a meter cannot decide artistic quality or infer an undocumented distributor policy.
Turn each finding into an action
Keep a short record with four columns: finding, evidence, owner and next export. Resolve measurable faults, review advisory findings and mark manual checks complete only after somebody performs them.
UTUVO QC helps inspect the ADM and capture a structured preflight report. It does not verify every distributor account field or guarantee a good binaural mix. Use the full delivery checklist to combine automated checks with the remaining review.