Executive Reporting

Producing volume and activity numbers that hold up when someone asks where they came from.

In the application

The dashboard is the reporting surface. Set the date range, the period and the project, and read:

• Daily usage as a trend across the period.
• Assets: total assets, containers, and chassis.
• Scans: videos recorded, upload volume, and total scan time.

From an assistant

Using SiteTrax.io, compare container volume across my sites for the last two months and show the month-over-month change.

Using SiteTrax.io, break last month down by project and asset type.

Aggregation happens on the SiteTrax.io server, so this works without exporting records anywhere.

Make the number defensible

1. State the filters. Every figure is a function of date range, period and project. Publish them alongside the number.
2. Say what is being counted. Stored readings and distinct identifiers are different measures, and the difference will be noticed.
3. Note coverage changes. A camera added or lost mid-period moves the volume line for reasons that have nothing to do with the business.
4. Keep a path back to the record. A reviewer should be able to open an individual observation.

Watch out for

• A volume drop can be a capture failure. Check camera health and volume gaps before reporting a decline as operational.
• Do not mix measures across periods. Compare like with like.
• Scan time and upload volume describe capture, not throughput. They are useful for health, not for business performance.

If a recurring summary would help, note that alerts and scheduled digests exist as MCP capabilities requiring a separate write permission. See SiteTrax.io MCP Server.