Utilisation and realisation are different problems

Utilisation is what share of available hours went to client work. Realisation is what share of that work you got paid for. A firm can be busy and unprofitable, and the two numbers tell you which problem you have.

Low utilisation is a sales or resourcing problem. Low realisation is a scoping problem — the work happened but was written off, discounted, or absorbed into a fixed fee that stopped covering it.

Want to know how this works out for your company? Send us the question as you would ask it.

Why timesheets fail, and how they stick

Timesheets fail when the people filling them in never see anything come back — the data goes up and nothing returns, so it reads as surveillance.

They stick where a project lead can see their own project's position without asking anyone; the record then protects them in a scope conversation with a client. Before rolling out timesheets, decide what the person entering the time gets back.

What to record so scope creep shows

Scope creep is not one large request; it is twenty small ones, each easier to absorb than to argue about. The system does not stop it — a conversation does. The system provides the evidence, early enough to matter:

  • Budgeted hours against actual, per phase rather than per project
  • Out-of-scope work recorded as out-of-scope, even when you decide not to bill it
  • A visible burn rate, so the overrun surfaces at 60% rather than at delivery
  • Change requests logged whether or not they are charged
  • Rate per person, so a senior absorbing junior work shows as a margin problem

Run a retainer as a budget of hours

Because a retainer invoice is the same every month, nothing signals when the work behind it has grown. A client who has quietly doubled their demands still produces the same payment.

Treat the retainer as a budget rather than a subscription: a fixed number of hours per period, consumed and reported to the client.

The system you need is small

For most firms under a few dozen people, a full professional-services-automation platform costs more to adopt than it returns. What is needed is time recorded against projects, projects carrying a budget, and invoicing drawn from both. In the Zoho stack that is a small footprint, not the full suite.

The test: can a project lead answer "are we still inside budget" without building a spreadsheet? If a smaller set passes, buy the smaller set.

Measure one quarter before you buy

Record time against projects for one quarter, even roughly in a spreadsheet. Most firms find one or two clients are carrying the losses.