Your dashboard number and your primary record are two different claims

Description and use

The verification method shows that dashboard numbers often count rows, not the intended metric, and provides a checklist for accurate interpretation.

Problem

Dashboard counters often misrepresent the true count of actionable items, leading to inflated or misleading claims.

Outcome

The method uncovers that dashboard numbers often count raw rows, not the intended metric, and provides a checklist to verify and correct such claims.

Workflow

• Find the endpoint behind the number by inspecting XHR/fetch in devtools.
• Pull every page of data, not just page one, and count the rows received.
• Bucket by the field that determines the claim, counting distinct values.
• Recompute monetary values and identify rows with a real counterparty.
• Write the denominator next to the number to clarify the claim.
• Apply the same steps to other contexts (clinical trial, token board).

Evidence

Find the endpoint behind the number. Open devtools, filter the network panel for XHR/fetch, reload the page, and click the thing that changes the counter.

Source

174 rows in the payload

Source

The counter is not lying. It is counting rows. But a visitor reads "174 jobs" as "174 jobs people got paid for", and the payload supports 3.

Source

What the checks have in common: Every one of them had a schema that was internally consistent and a label that oversold it.

Source