Document · reads report
Reports
Generated summaries.
Long-form text, written and read in place.
Monthly performance
August · Sent 2 Sep · Maison Lauret
Quarterly review
Q2 · Sent 8 Jul · Board
Monthly performance
September · Draft · —
Stock and wastage
August · Sent 4 Sep · Internal
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Numbers with the sentences that explain them, which is the version you can send to somebody who was not watching.
Kept after sending, so last quarter can be compared against what was said about it at the time.
Produced on a schedule rather than rebuilt by hand each month.
How it works
- 1
A report is generated for a period, pulling figures from the modules that hold them.
- 2
The interpretation is written once and kept with the numbers rather than in an email.
- 3
Sending records the date and the recipient; the report itself is immutable afterwards.
- 4
Previous periods stay, so this quarter can be compared with what was said about the last one.
Best for
Briefs, notes, policies, anything read as prose.
Not the right choice for
Structured fields pretending to be prose.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Reportrequired | text | What it is. Usually a standing name repeated each period. |
| Periodrequired | text | What it covers. The field that makes two reports comparable. |
| Statusrequired | choice | Draft, or the date it was sent. A report nobody sent is a draft. |
| Sent to | text | Who received it, so a claim about what was reported can be checked. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- No scheduled delivery. Generating is automatic; sending is a decision somebody makes.
- No templating across clients — a report for two customers is two reports.
- Figures are captured at generation time and do not update afterwards, which is the point and also a trap if you expect otherwise.
- No approval workflow. A draft becomes sent when somebody says it did.
Before it works
What you have to provide, if anything.
- Needs at least one module with figures worth reporting.
- Agree the period and the recipients before the first one, since changing them breaks comparability.
In practice
An agency reporting to a client every month, by hand, badly.
“Send Lauret the August performance report.”
What the agent built
A dated report with the figures and the interpretation, kept alongside the previous three.
What changed
Building it went from half a day to twenty minutes. The kept archive settled a disagreement about what had been promised in Q2.
Better with
These do a different job on the same data. An agent can have all of them.
Questions
What data does the Reports page use?
It reads report records the agent has collected. Generated summaries. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a document the wrong choice?
Structured fields pretending to be prose. It is best for: briefs, notes, policies, anything read as prose.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in Analytics & data
Orders today
23
20
Unanswered messages
4
0
Stock alerts
2
0
Overdue invoices
1
0
KPI page
Headline numbers.
Metrics dashboard
Charts of trends.
Data table
Uploaded rows (elastic data).
Charts
Visualize any dataset.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free