A report loses usefulness when two totals disagree and nobody can explain the difference. The correction starts with the meaning of the numbers, before the design of the dashboard.
Write a definition for each measure
Specify what is counted, which states are included and which date controls the reporting period. “Completed work” can mean accepted, delivered or invoiced work. Those totals can all be correct while answering different questions.
Name the source record and the person responsible for the definition. Keep that definition near the report so a new reader does not have to infer it from a chart label.
Make the cutoff visible
A report generated at different times can produce different results. Display the period and the data cutoff. Distinguish a correction to a past period from new activity in the current one.
Use an illustrative reconciliation case: a request was completed yesterday but its record was updated today. Decide which period should contain it and test that rule consistently.
Trace an aggregate to its records
Allow the reported total to be checked against the included records, with suitable access controls. Review a small sample manually and preserve explanations for exclusions.
A report is ready for operational use when readers can explain a change without building a private spreadsheet. Replacing manual reporting covers the implementation sequence behind that result.