Evidence before escalation

A suspicious row is a starting point, not an accusation. Before anyone raises an issue with a counterparty, the reviewer should be able to say exactly what was expected, what was observed, and why the difference matters.

That takes a small, complete packet: the row itself, the rule text it is measured against, the applicability decision, the source snapshot or checksum, and what was already ruled out. Without those, an escalation invites a reply of show me and a restart from zero.

Assemble the packet before the meeting, not during it. A well-documented question gets answered faster and protects the reviewer when the explanation turns out to be legitimate.

Read the original research: When a zero count has a median.

Sources: CMS FAQ; CMS technical documentation.