Every practice system promises reporting and most of them mean a query builder: somewhere you could, in principle, construct the report you wanted. Quantim ships the reports, grouped by subject, with the filters that matter already on them.
Start a free trial Book a demoA library grouped by what the report is about, options beside it, a viewer built for long documents, and a schedule so the regular ones arrive without asking.
Grouped by subject rather than listed alphabetically, because the question people arrive with is about expenses or about fees, not about a report name they half remember.
Each report carries its own options, shown beside the library rather than behind a dialog, so you can see what you are about to run before you run it.
Built for documents that run to hundreds of pages, which practice reports routinely do once they cover a whole team over a year.
The regular ones should not need a person. Set a report running on a schedule and it arrives, with the same options it had when you saved it.
The parts of the viewer that matter once a report stops fitting on a screen. Pick a numbered point.
Four points on this screen.
The reporting cost most practices never count is the person who builds it every month. Set your own numbers.
Assembling means pulling the numbers together and formatting them, not thinking about what they mean. The thinking is the part worth paying for.
An illustration from the figures you entered, not a measured result. Scheduling a report does not remove the work of reading it.
The finance views that sit alongside the library.
What is owed, and how long it has been owed. The ageing is the point: a single total tells you nothing a bank statement would not, while the buckets tell you which conversations are overdue.
It reads from the invoices raised in Quantim, so it is current rather than assembled at month end from a spreadsheet.
Fees forecast to be invoiced, invoices raised and not yet paid, and costs committed through purchase orders. Three streams that between them decide what the practice can afford to do next.
This view is marked beta in the product, and we say so here rather than quietly presenting it as finished.
A library with a hundred reports in it is only useful if you can get back to the four you actually run. Starring them puts them at the top for you rather than for everybody.
It is a small feature that decides whether the library gets used or whether people go back to asking somebody to send them a spreadsheet.
The landing view: the figures a person needs on the way in rather than the ones they would go and look for. What it shows depends on what the person does, because a director and a job runner are not asking the same question.
Reports answer a question you already have. A dashboard is for the question you did not know to ask.
A report builder sounds more flexible and in practice shifts the work onto whoever in the practice is least afraid of it. Most teams end up with two people who can produce a report and a queue behind them.
Shipping the reports, grouped by subject with the filters already on them, is the less impressive answer that more people can actually use.
Nothing here is a separate system. The same job, the same people and the same numbers run through all of it.
A free trial takes a few minutes to set up, and no card. Or let us walk you through it against the reports your practice actually produces.
Start a free trial Book a demo