SUMMARY: Freshness describes the age of evidence. Coverage describes what that evidence includes. A report can satisfy the first question while failing the second.
Define the Expected Scope
In The Missing Platform, five current replies become a claim about six platforms. The arithmetic is not the main defect. The heading silently expands the scope of the evidence.
Keep an explicit account of expected contributors, reporting periods and authorized exclusions. That account also needs an owner and review process: an obsolete inventory can create false alarms or hide newly added services.
Keep Missing Separate From Zero
A received report stating zero is different from no usable report. Preserve the distinction through summaries, exports and user-facing labels. Substituting zero can make an interruption look like an improvement.
Carrying an older value forward is another choice, not a neutral repair. Where a service uses it, identify the older observation and the rule permitting its use. Do not silently mix historical and current contributions beneath a single current timestamp.
Explain What Partial Means
A coverage fraction helps, but it does not tell the whole story. Five of six contributors may sound reassuring even when the missing contributor normally represents most of the activity. Identify the relevant scope without exposing unnecessary personal information.
Partial information may still be useful. Label the subtotal accurately and define which decisions can proceed, which need confirmation and who handles the gap. There is no universal percentage that makes every report dependable.
Reconcile Recovery
When a missing contributor returns, check its reporting period and whether any manual observations overlap with it. Adding both without reconciliation can replace an undercount with a duplicate count.
Use Test a Partial Report alongside the systems accountability guide. This is a conceptual review framework, not a statistical estimation method or a specification for safety-critical monitoring.