Realisation Is Decided Before the Invoice Is Written

Realisation is decided before the invoice is written

Firms discuss billing as though it happens at month end. It does not. By the time an invoice is drafted, most of what will be lost has already been lost — in time that was never recorded, narratives too thin to defend, and work done outside any scope anybody agreed.

The invoice is where the damage becomes visible. It is rarely where it occurs.

The four places money leaks

Time recorded late, or not at all. The gap between doing the work and writing it down is where realisation dies quietly. Entries reconstructed on Friday for a week’s work are estimates, and estimates round down — nobody ever over-claims from memory out of caution.

Narratives that invite the query. “Review of documents — 2.4” is an invitation. “Review of defendant’s supplemental production (312 pp.) for references to the March shipment; index for deposition of R. Hale — 2.4” is not. The work was identical. One gets paid.

Scope drift nobody logged. A call that turns into a new question, a document that turns into a new matter. Recorded as it happens, it is billable or a deliberate write-off. Discovered at month end, it is an argument.

Delay itself. A bill sent six weeks after the work is queried more often than the same bill sent in one. Memory fades on both sides, and the client’s memory fades faster.

What good looks like, in numbers

If you want to manage this rather than discuss it, four metrics are enough:

• Median time-to-record: hours between work performed and the entry existing. Under 24 is healthy. Over 72 and you are billing from memory.
• Realisation rate: billed against recorded. The headline number.
• WIP older than 30 days, in value. Work in progress ages badly.
• Days from period end to invoice out.

Track these per fee earner and the conversation changes from “we should bill more promptly” to “these three matters are eight weeks old.”

Where automation genuinely helps

Capture at the moment of work. The highest-value intervention by a distance. Dictating a note after a hearing and having it arrive as a draft entry against the right matter removes the step that gets skipped. The technology is not the point; the timing is.

Narrative drafting from the work record. A system that knows which documents were opened and which matter was active can propose a specific narrative for a human to accept or correct. Specific narratives get queried less.

Prompting on gaps. A fee earner with a calendar full of meetings and two hours recorded has a gap. A quiet prompt the same day recovers time that a monthly review never will.

Flagging scope drift. Work recorded against a matter that does not match the engagement is a question worth raising while it is still a question.

Where it does not help, and can hurt

Automatic time entries nobody reviews. Software-generated entries that go out unread are a professional risk. Every entry on an invoice is a representation to a client about work performed.

Padding by template. Narrative generators that produce impressive-sounding text disconnected from what happened are worse than terse ones. If the narrative cannot be defended by reference to what was actually done, it should not be sent.

Billing decisions. What to write off, what to discount, when to have a conversation instead of sending a bill — none of that is automatable, and all of it is where the client relationship lives.

The unglamorous sequence

1. One place where time is recorded. Not a spreadsheet for some people and the system for others.
2. Capture on the day. Whatever the mechanism, the target is the same: nothing older than 24 hours.
3. Write narratives that a sceptical client could follow without asking what the work was.
4. Review before sending. A human reads every line.
5. Send promptly, on a fixed cycle nobody has to chase.
6. Measure the four numbers above, per fee earner, monthly.

Most firms know all of this. The difference between the ones who do it and the ones who intend to is almost entirely whether recording time is easy at the moment the work happens.

Where Lawnova fits

Lawnova is built around that sequence: time tracking tied to the matter rather than to a separate timesheet, voice dictation so an entry can be made in the minute after a hearing rather than on Friday, smart billing that assembles invoices from the record, and case management so the work and the time live in the same place.

The design view is the one above: realisation is decided by how easy it is to record work at the moment it is performed, and everything at month end is arithmetic on decisions already made.

For the wider operational picture, see where the hours actually leak.