Reports summarise activity — what was delivered, what failed, and what it cost — and can run on a schedule and be sent to a channel.
You’ll find them under the factory’s Reports view.
What a report can cover
- Work delivered over a period and what remains in progress.
- Failure and rework rates
- Capacity utilisation and queue depth
- Model spend, attributable by project
Scheduling and delivery
A report can run on a recurring basis and be delivered to the places people already use — email or a connected chat channel. See the Integrations overview.
Delivery matters more than content. A well-designed report that nobody opens changes nothing; a simple report that arrives in the channel where the team already talks gets read.
Writing a report worth reading
The common mistake is reporting everything. A report listing forty metrics is scanned, not read, and the one figure that mattered gets lost among thirty-nine that didn’t.
Pick the few items that would influence a decision:
- Is the queue backing up? This decides whether to add capacity.
- Is rework rising? This decides whether the specifications need attention.
- Is spend tracking delivery? This decides whether resources are being wasted.
Each of these has an associated action. A metric without an attached action is mere decoration.
Reports and usage data
For billing and spend specifically, the Usage views provide live, filterable data — see Usage and reports. Use a scheduled report when you want it sent to people regularly instead of relying on someone remembering to check.