The Monthly Reporting Pack for a Small Consulting Firm

Not the client-facing report — the internal one the partners read on the second Tuesday. Six blocks, two pages, and three tempting metrics that are better left out.

This is the internal pack, not the client-facing one. If you are after the report you send to a client, that is the client reporting pack, and it is a different document with a different audience.

This one gets read by two or three partners on the second Tuesday, and its job is to support four decisions: who to put on what, what to charge, which client conversations to have, and whether to hire.

Two files, and only two

Everything below comes from a timesheet export and an invoice line export. Pull both on the same working day each month for the same date range. A pack whose source dates wander cannot be compared with itself, which is most of its value gone.

The six blocks

1. Billable ratio by person, this month and last three. Billable hours over total logged hours, by person, with role beside it. If you have capacity data, use true utilization instead and say which you used. Sorted ascending, so the people with room appear at the top where a staffing conversation can reach them.

2. Realization by client. Invoiced over standard value, with the write-off in currency next to it. Percentages get nodded at; a five-figure write-off next to a client name gets discussed. Full method in the realization piece.

3. Effective hourly rate, firm and by service line. Invoiced divided by hours delivered. This is the number to watch against your rate card, and the one that quietly falls for a year before anyone notices.

4. Margin by service line. Both margins if you have cost rates — delivery margin and project margin, side by side, as covered in project profitability. The gap between them is where the pricing conversation starts.

5. Hours by month, twelve months, billable and total. A chart, not a table. This is the block that shows a slowdown coming, because hours fall before revenue does.

6. Cash and receivables. Invoiced this month, collected this month, and receivables over sixty days. Not strictly a delivery metric, and the first thing anyone asks about, so it belongs in the pack rather than in a separate email.

The page that makes the pack survive

The last page lists, for each metric: the formula, which file it comes from, and which date field it buckets on. Four lines each, at most.

It reads as bureaucracy until the first month two people disagree, at which point it settles the argument in ten seconds instead of a fortnight. The date field is the one that catches people out: hours bucket by the date worked, invoices by the invoice date, so the same engagement lands in different months in blocks 1 and 2. That is correct and it needs saying once, in writing, forever.

The same failure mode, in more detail, in why your team gets different numbers.

Three things to leave out

Work in progress in the main tables. WIP is a balance. Put it beside monthly flow figures and somebody will sum it across the quarter, which produces a number with no meaning. Own page, explicit as-of date, or not at all.

Month-on-month percentage change. Tempting and unreliable on a sparse table. A client with no hours in August is not a row, so a naive comparison lines September up against July and reports a swing that never happened. Show twelve months and let people read the shape.

Anything undefined. If a metric cannot be written in four lines on the definitions page, it is not ready for the pack.

Cadence and delivery

Same working day each month. Third working day is common — late enough that the previous month is invoiced, early enough to act on. Send it as a PDF or a mail rather than a link to a live file, because a pack that changes after it is read is not a record of anything. If it goes to the same people every month, the scheduled emailing walkthrough covers the sending.

Where the hour actually goes

After the first build, the pack should take under an hour. When it takes a day, the day goes into re-doing the joins and re-pointing the formulas at new files — not into the thinking the meeting needs.

Quiriz for professional services is built for that gap. Upload the two exports, and the six blocks are six questions asked in plain English, with the definitions held in the product instead of in the definitions page. Billable ratio by role last quarter. Realization rate by client. Delivery margin by service line. Then schedule the pack so it arrives before the meeting rather than being built the night before.

The boundary, once more, because it decides whether this fits your firm: it works from the exports you have. True utilization needs capacity data your timesheet does not carry, and realization needs invoice line detail with hours. With both, the pack is six sentences. Without invoice detail, blocks 2 and 3 are not calculable by anyone, in any tool.

Frequently asked questions