Salesforce Report Accuracy and Definition Audit
Check that reports mean what users think they mean.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit these Salesforce reports: names, report type, filters, groupings, and the numbers shown: [REPORT_DETAILS]. Expected figures from finance or another source: [EXPECTED_FIGURES]. How users interpret each metric: [USER_INTERPRETATIONS]. For each report give the definition of the main metric in one sentence, the date field used and the filter scope (owner scope, stage list), and ask whether that matches how users think about it. Check the report type (which objects are included and whether records without related records are dropped; joined reports may lose records without related records and repeat records with several [VERIFY]), duplicates caused by joins, currency conversion, and fiscal versus calendar periods. Recalculate at least three numbers, showing arithmetic with the report total, expected total, difference and percentage, and state what you assumed. Return a table (Report, Number, Expected, Difference, Cause, Fix) and a definitions page that links to each report, with a naming standard that includes the metric and the period. Recommend a monthly check of three key numbers against finance.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.