Professional services reporting has one recurring problem. The practice-management system says one thing. The BI tool says another. The partner's spreadsheet says a third. Each number can be defended. None of them agree.
This post is for a finance director, ops lead or data lead at a law firm, accountancy or consultancy. It covers what to report on and how to make every tool give the same answer.
The metrics behind professional services reporting
The billable hour has its own vocabulary. Five measures carry most of the weight in professional services reporting.
- Utilisation. Billable hours as a share of available hours, by fee earner, team and practice.
- Realisation. The value billed and collected, compared with the value of the time recorded at standard rates.
- Lock-up. Work in progress plus unpaid invoices. It is the cash the firm has earned but not yet received.
- Write-off. Recorded time that never reaches an invoice.
- Pipeline. Instructions and proposals that will become future matters, weighted by likelihood.
These metrics interact. Pushing utilisation up can push write-off up, because time recorded is not always time that can be billed. Chasing realisation can slow lock-up if invoices go out late. A report that shows one measure alone will mislead. Show them together, from one set of definitions.
Where the numbers come from
Time, matters and billing usually live in a practice-management platform such as Elite or Aderant. Some firms run a sector configuration of a larger finance system instead. These platforms encode the billing lifecycle. Time entry, matter structure and billing adjustments vary from firm to firm.
Pipeline data sits elsewhere, often in a CRM or a spreadsheet. Headcount and targets sit in a third place. The stack for professional services reporting is the set of tools that pulls these together into one view for finance and partners.
Most firms end up with three layers. The platform holds the source records. A BI tool holds the dashboards. Spreadsheets hold the partner packs and the adjustments nobody has moved into the platform. Each layer needs to be right. The seams between them are where the numbers drift.
Why the numbers stop agreeing
Drift starts with definitions. One team counts realisation against standard rates. Another counts it against the agreed fee. One dashboard treats a write-off as a billing adjustment. A spreadsheet treats it as lost time. Every version is reasonable. Every version gives a different figure.
The fix for messy professional services reporting is not a better dashboard. It is to define each measure once and make every report read that definition. That is the idea behind a single semantic model: utilisation, realisation, lock-up and write-off are written down one time, and every dashboard, document and spreadsheet resolves through them. The general case is covered in the complete guide to analytics dashboards.
Build partner-level views from one model
Partners hold real autonomy over their practices. They resist a single firm-wide league table, especially when it makes cross-practice comparison visible. The same figures framed as decision support for their own practice land far better.
That usually means partner-level views of one underlying model, not one firm-wide dashboard. Done by hand, this multiplies the work. Twelve partner views are twelve artefacts to rebuild every time the data moves. Done from one model, the definitions stay identical and only the filter changes. Who may see which matters is a separate control, and it needs its own decision. Client-level data is often privileged, so the firm should settle access rules before it builds the views.
Why professional services reporting decays
The common failure is not analytical. It is that the output is a static artefact: a deck, a spreadsheet or a dashboard built once. It starts to decay the day the project ends. Someone asks for a refresh and someone rebuilds it by hand. Monthly lock-up, weekly utilisation and the partner pack all get rebuilt on a cycle, and each rebuild is a chance for a number to change.
A steady reporting cycle needs three things. The definitions are fixed in one place. The jobs run on a schedule against live data. Someone can see how each figure was produced. Without the third, the finance director ends up re-checking every pack before it goes to the partners.
A short checklist for the stack
- Write down one definition for each of the five metrics, and name an owner.
- Point every dashboard and every partner spreadsheet at those definitions.
- Schedule the monthly and weekly packs so nobody rebuilds them.
- Keep a record of how each figure was produced, so a partner can trace it.
- Settle who sees client-level data before you build any partner view.
Where Veritly fits
Veritly is an Integrated Analysis Environment. It brings the query, the model, the report and the automation into one workspace. One semantic model resolves every dashboard, document and job, so a metric like realisation is defined once and read everywhere. Veritly shows the SQL behind each answer, and manual reruns become scheduled, audited jobs. That is what stops the monthly pack being rebuilt by hand.
Veritly is in private beta. If you run professional services reporting for a practice, or for firms like it, the tool comparison in best analytics dashboard tools shows where it sits.
Join the waitlist — access opens as capacity does.
See also: client-ready reports, data analytics for law firms and row-level security in practice.
