Match the tool to the question
Financial statements and comparative reports are built with the financial report builder, which understands accounting periods and can present balances in a formal layout. Saved searches suit lists and operational queries: open orders, overdue invoices, items below reorder point. Analytics workbooks let analysts combine and pivot data more flexibly for exploration. Dashboards show a selection of these for quick monitoring. Choosing the tool by the question prevents forcing one to do another's job.
- Use financial reports for statements and period comparisons.
- Use saved searches for operational lists and exceptions.
- Use workbooks for analysis and ad hoc exploration.
- Use dashboards for what people need to see every day.
Design saved searches that last
Saved searches are powerful and easy to create, which is also why they multiply. Give each a clear name that says what it shows, a description of its purpose, and an owner. Limit the number of columns to what readers use, since extra fields slow performance. Where a search feeds a dashboard or an email, test it with realistic data volumes to ensure it still performs when the account grows.
Dashboards people actually open
A dashboard crowded with every metric helps nobody. Build role-based dashboards with a handful of measures each: for a sales manager, open orders and quotes; for a controller, cash, receivables aging, and close status; for a warehouse lead, orders to pick and stock exceptions. Each item should prompt an action. If a number never leads anyone to do anything, remove it.
Training and user enablement →Performance, data volume and the cost of a slow report
A report that runs in seconds on a small account can take minutes when transaction volume grows, and slow searches affect everyone using the system. Filter by date and subsidiary wherever possible, avoid pulling every transaction ever recorded, and prefer summary views for dashboards. If a report truly needs to process a very large dataset, schedule it to run overnight and deliver the result, instead of asking users to wait. Review the slowest searches each quarter and simplify or retire them.
Governance: ownership, naming and cleanup
Set simple rules: reports are named with a standard format, each has an owner, and anything unused for a year is reviewed for removal. Separate shared, approved reports from personal ones, so people know which to trust. When the definition of a metric changes, such as how revenue is counted in a dashboard, update every place it appears and note the change date, or trends will mislead.
Scheduling, sharing and permissions
Scheduled emails deliver reports to people who would not log in, and permissions determine who can see what. Check that scheduled reports respect the recipient's access, so sensitive figures are not sent to the wrong audience. Be careful with exports containing personal or financial information, and decide which roles may download data in bulk.
Managed and advisory services →Decisions to settle before building reports
- Key measures. Define the ten or so numbers leadership reviews regularly and how each is calculated.
- Naming convention. Agree a format that makes reports easy to find and sort.
- Ownership and review. Name who maintains each shared report and how often it is reviewed.
- Data access. Decide which roles can see which data and who may export it.
Pitfalls to avoid
- Report sprawl. Hundreds of near-duplicates make it impossible to know which is right. Retire the extras.
- Undefined metrics. If two reports calculate the same measure differently, trust collapses. Define and document.
- Heavy searches on dashboards. Complex searches on a busy dashboard slow the account for everyone. Simplify or schedule them.
- No training. People who do not know a report exists will build their own. Train and publish a catalogue.
