Salesforce reports and dashboards should answer specific management questions. Start with the decision the viewer needs to make, then choose the records and measures that support it. More charts do not necessarily make the answer clearer.
A useful first question might be: which open opportunities need review this week? That calls for different information from a report on last quarter’s closed sales or the sources of new enquiries.
Understand the report behind the dashboard
Salesforce’s reports and dashboards guidance distinguishes the underlying report from its visual presentation. The report type determines which records and fields are available. Filters and grouping then shape the result.
Salesforce also explains that a dashboard’s running user affects the data displayed to viewers. Review both sharing and data access before publishing a view. A chart that looks correct to an administrator may not be the right view for everyone else.
Write the management question first
Which opportunities need attention?
Show the relevant open opportunities and the information needed to investigate them. That may include the owner, stage, expected close date and next agreed step. Define what qualifies an opportunity for review rather than treating every old record as a problem.
What closed during the period?
State which date and outcome define the population. Distinguish opportunity amount from invoiced or recognised revenue if those are different measures in your business. Label the report so that viewers know what the total represents.
Where are conversion problems appearing?
Define the starting group and the outcome being measured. Check how duplicates, reopened opportunities and incomplete dates affect the calculation. A comparison is useful only when both periods use compatible definitions.
Test Salesforce reports and dashboards against records
Before sharing a report, inspect examples that should appear and examples that should be excluded. Confirm that the filters behave as intended and that the totals can be explained.
Consider a fictional report that claims to show all open opportunities for a region. Its date filter includes only records created this month. Older deals disappear, so the regional total is incomplete even though the chart displays without an error.
A short review with the account owners can reveal this mismatch. Test the question as well as the calculation: a technically valid report may still answer the wrong question.
Choose a view that helps the reader
Use a table when the viewer needs to inspect specific opportunities or exceptions. A bar chart can help compare groups, while a line chart can show a measure over time. Keep labels, units and periods visible.
Avoid combining unrelated questions simply because space is available. Give managers a way to inspect the records behind a total, and check that the people using the view have the access they need.
Agree how current the report must be and make its update status clear. Do not describe a view as real-time without checking how its data and dashboard are refreshed.
Fix data problems at their source
If representatives interpret a stage differently, another chart will not resolve the disagreement. Clarify the definition and check the affected records. The opportunity-stage guide provides an example of that work.
When information comes from billing, support or another system, identify the source and how it connects to the report. Adding a customer data platform does not by itself prove that records are complete, current or correctly matched.
Give each report an owner
Assign someone to maintain the definitions and review changes to fields or processes that affect the result. Keep a short note of the intended question, filters and known limits.
During a pipeline review, use the report to identify questions and agree follow-up work. The chart supports that conversation; it does not replace the evidence needed to make a decision.
