Observed control coverage
One square per observed check · unavailable data is never scored as safe
Check count tells me how much a product tried to inspect. It does not tell me whether the assessment produced a useful answer.
A large library can be valuable. Coverage matters. But before I celebrate 1,500 checks, I want to know: did they run? Was the source readable? Which permissions and licenses were required? Was the evidence retained? Can I see the affected objects? Can I investigate the condition? Can I explain it? Can I verify it later?
Imagine two assessments. The first lists 1,500 possible checks and marks unavailable sources as clean. The second runs 300 relevant checks, shows exactly which 280 completed, labels 12 as permission-limited, records eight provider errors, and keeps the evidence behind every finding. The smaller number may be the more defensible assessment.
The denominator matters. A score of 47/F, 38.2 percent, or 62/D means very little until we know what was assessed and what could not be assessed. A polished grade without coverage context is theater. It invites the reader to assume completeness the product never earned.
SCOUTz treats check count as a capability measure, not an outcome. The outcome is whether the MSP can trace the conclusion, understand the boundary, prioritize the real condition, perform justified work, and return with proof.
More checks can make a product better. They can also make a brochure louder. The difference is what happens to the evidence after the check runs.