The problem
Reports that cannot show you what the screens will not.
The trade
What changes, and what it costs you today
Today
What this looks like before
- Reporting is a separate tool with its own copy of the data and its own idea of who may see what.
- Two dashboards disagree, and the meeting is spent deciding which to believe.
- Nobody can say who exported what.
None of this is anybody being careless. It is what happens when the record lives in more than one place.
Instead
Management reporting off the rows, not off a copy
One scope predicateA report runs under the same rule the screen does. There is no second permission model to keep in step.
Export is a governed verbExporting is its own permission, and every run is on the record.
Operational to strategicToday's queue and the quarter's shape, off the same rows.
All of it on Starter and above. Security is on every plan.
On the screen
Not a mockup
The report library
The modules behind it
What is actually doing the work
Named, so this page cannot promise something your plan will refuse — each one links to what it does and which tier holds it.
InsightAnalytics & ReportingThe same scope rules the screens use, applied to the numbers.DeliveryProjects & DeliveryHours booked, work delivered, and what has not been billed.MoneyFinance & AccountingGST invoices, receivables and a ledger that balances.PeopleHR & PeopleThe record every other module reads.