Skip to content
  • There are no suggestions because the search field is empty.

Sense-check a report before you share it

Run four quick checks on spend, apps, connection health and usage coverage before a report reaches a client or stakeholder.

What you get

A quick final check that the report's most important numbers and conclusions have a sound data basis before you share it.

1. Is the spend matched?

Spend Overview → Needs Review should be empty, and Unmapped should hold only non-software costs. Anything else and the spend total on page one is too low — which is the first number a reader tests.

2. Is the app list confirmed?

Apps → Discovered should be manageable. Review high-impact or unfamiliar records so the report is not relying on an application you have not yet validated.

3. Is the connection history unbroken?

Integrations — check the last sync time. A dropped connection leaves a dip in the spend trend that reads as a saving you did not make.

4. Is usage coverage stated?

Read the extension adoption figure on Organization → Users. If it is low, say so in the covering note rather than let the access section imply certainty. A stated basis is stronger than an unstated one.

The details that embarrass

  • Client name and currency — check both before anything leaves the building.
  • The fiscal year in Settings → Preferences — every budget figure depends on it.
  • The report date — regenerate if the data has moved since.

What you've unlocked

You have a simple pre-share quality check you can repeat every time a report is generated.