Reports summarise activity — what was delivered, what failed, what it cost — and can run on a schedule.
Find them under the factory's Reports view.
What a report can cover
- work delivered over a period, and what is still in flight
- 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. Each run adds a new report to the Reports list. Coroid does not send scheduled reports by email or to a chat channel today.
A report nobody opens changes nothing. Schedule the ones someone will read.
Writing a report worth reading
The common failure is reporting everything. A report listing forty metrics is scanned, not read, and the one number that mattered is lost among thirty-nine that did not.
Pick the small number of things that would change a decision:
- Is the queue backing up? Decides whether to add capacity.
- Is rework rising? Decides whether specifications need attention.
- Is spend tracking delivery? Decides whether something is being wasted.
Each of those has an action attached. A metric with no action attached is decoration.
Reports and usage data
For billing and spend specifically, the usage views give you live, filterable data — see Usage and reports. Use a scheduled report when you want a summary produced on a cadence rather than whenever someone remembers to look.