Business applications
Agree which work belongs in a report total
A dashboard number should have a definition that staff can reproduce from example records.
A report says there are twelve active requests. The office expects ten because it excludes withdrawn work, while the report includes every record that has not been archived. The number is accurate only according to a definition nobody agreed.
Write the counting rule in ordinary language
For a fictional Estonian organisation, define whether “active” means work needing attention, all open relationships or requests within a selected period. Specify how withdrawn, reopened and duplicate records are treated.
Use a tiny demonstration set. Two requests may be assigned, one waiting for customer information and one withdrawn. Ask the team which belong in its chosen total and why. The point is to agree meaning, not manufacture a performance result.
Make the selection inspectable
Show the date range, relevant filters and when the information was updated. If users can open the records behind the number, the list should use the same rule as the summary. Otherwise the dashboard can contradict itself.
W3C's table guidance supports understandable headers and relationships when reviewing the underlying records. A readable table still needs an agreed business definition for the total.
Reconcile after a change
Reopen the withdrawn example, change an owner and move one request beyond the reporting period. Check the summary and detail view together. Decide whether historical reports reflect the state at the time or the record's current state.
A reporting or application project should leave this definition with the team. It makes later maintenance and disagreement easier to resolve than a dashboard whose numbers are trusted only because they look precise.
Further reading: W3C guidance on meaningful data tables.