Check whether the report is ready
A report with one matched seed is not complete because the headline happens to show 100%. Read matched versus total, the report status, and the waiting state first. Some providers are slower, and a Missing result should remain distinct from Spam.
Once enough evidence is present, record the test time, sender, provider mix, and message. That context is necessary when a later report moves.
Use the score band for orientation
The segmented score band shows where the result falls across poor, warning, and healthy ranges while preserving the exact value and rating. It is easier to compare than a decorative semicircle, but it is still a summary.
Read Inbox, Promotions, Spam, and Matched beside it. A score driven by incomplete matches is a different operational state from a complete report with a provider spam cluster.
Open seed results and switch the distribution view
Seed results are open so each provider, account segment, placement, seed, and received time can be inspected. Latency and raw internal evidence are deliberately not foregrounded because they rarely help the launch decision.
Use the Providers and Segments tabs rather than viewing two dense breakdowns at once. Discrete outcome blocks show counts without implying continuous precision. Promotions has its own violet treatment rather than borrowing warning amber.
Choose the next fix
Open score drivers and fixes only after understanding the outcome. Prioritize authentication and security, then broad reputation or audience issues, then provider-specific patterns, links, and content. Informational warnings can wait.
Save or share the report, record one meaningful repair, and create a new test. The report has done its job when the team can explain why the next test should be better.