Reports
The report that arrives on its own, showing each person what they can see
Pick the tiles, the cadence and the hour, and the email goes out. The part that is not usual: every recipient gets it filtered by their own permissions and in their own language, so the same report does not show the same thing to everybody.
A scheduled report is built once and read a hundred and twenty times
The question from the top never changes: how many hours are going in, which projects are drifting, what is sitting unbilled, who has not filled in their timesheet. What changes is who answers it — somebody logs in on Monday, exports three things and pastes them into an email. That works until that somebody goes on holiday.
Here the report is built once — which tiles, in which order, over which period — and given a cadence: daily, weekly or monthly, with its day and its hour. The order of the tiles is data, not decoration: the first thing in the email is the first thing you want read.
Twenty-four tiles, in six groups
You drag them onto the report and put them in order:
- Summary — the period's headline figures, the alerts and the month's utilisation.
- People — variance, timesheet completion, who has not logged their hours, absences pending and upcoming, hours awaiting approval.
- Projects — projects at risk, margin, hours by project, upcoming milestones, overdue tasks.
- Money — invoiced this period, payments outstanding, aged debt, unreconciled bank movements, the sales pipeline, opportunities past their date.
- My space — my hours and my diary, for the report somebody builds for themselves.
- Activity and data — one of your own saved reports, and the audit summary.
The period of the data is not the cadence of the email
They are two different things and they are set separately, because «send it to me on Mondays» and «tell me about last week» are not the same instruction. There are seven periods: yesterday, the last seven days, last week Monday to Sunday, the last thirty days, this month up to yesterday, all of last month, and the year to date.
The range always ends yesterday at the latest. A report whose numbers move after it was sent cannot be quoted in a meeting, and it is the silent fault in half the automated reports out there.
You also choose what happens when it comes out empty: send it anyway, or say nothing. Saying nothing is the default, because a weekly email that says nothing ends up filed unread — and takes the one that did say something with it.
Everyone gets what they are allowed to see
This is what separates it from emailing a PDF to a distribution list. The report is calculated with the permissions of the person receiving it, not those of the person who built it. The same weekly report sent to the board and to a project manager arrives with margins in the first and without them in the second, and the footer says so, so nobody assumes a tile went missing by mistake.
It goes out in the recipient's language, not the language of whoever configured it: labels, table headers, subject line and footer. And if somebody can reach none of the tiles in a report, they do not get an empty email — they do not get one at all.
There are two permissions, and the difference matters: one to build reports for yourself and one to build reports that go to other people. A report of yours is not touched by anybody else, not even by an administrator. Roles and permissions.
One event, one email
Reports are fired by a clock that can be the application's own heartbeat, a cron job on the server or a call from n8n, and all three can coexist. So that coexisting does not mean triplicating, every send carries a stamp — the day, the week or the month — and that stamp is unique per report and per person: if two clocks land together, one email goes out, not two.
Every send leaves its outcome: sent, sent empty, that person could reach no tile, or failed. With its history on the report itself, so «it never arrives on Mondays» can be answered by looking rather than guessing.
Test sends do not spend the day's stamp, so testing a report does not stop the real one going out the same morning.
Frequently asked questions
Can I send a report to an outside address, like my accountant?
Not today: recipients are people inside your account. That follows directly from the point above — the report is calculated with the permissions of whoever receives it, and a loose email address has no permissions. If your accountant needs to see it, the natural answer is a user with the right role.
What if I want to stop receiving one?
Whoever can administer the account's reports removes you, or you do it yourself if the report is yours. The console shows you the reports that reach you even when you cannot edit them, precisely so you know why that email arrives and who to ask. There is no one-click unsubscribe link yet.
What time do they go out?
On the hour, in the local time you choose. The application runs in UTC and the person reading it does not, so the conversion happens when the report is scheduled rather than when it is sent: eight in the morning is eight in the morning in summer and in winter.
Can I put one of my own saved reports in it?
Yes, that is one of the tiles. If you have already built a report with your filters on it, it goes into the email as it is.
What if the account is on trial or suspended?
They stop. An expired or suspended account stops sending scheduled emails, which is the opposite of what half the systems out there do.
Getting started
Fourteen full days, no card and nothing to install. If it has not saved you work by then, there is nothing to cancel. And if you would rather see it first, book a demo and we will set it up with two or three of your real projects, which is where you find out whether it fits.