Hours That Were Written Off
An hour recorded, billed and then waived still counts in most definitions. The gap between the ratio and revenue has a name.
An hour recorded against a client, invoiced, then reduced or waived counts in the numerator at almost every firm. The ratio treats it as identical to an hour that was paid in full.
The data-quality issue in “Hours That Were Written Off” begins at the moment an hour is recorded or reconstructed. For organisations researching job costing with accurate hours, read the supporting platform guidance can organise project-linked time entries, provided people can see, explain and correct their records before those entries affect billing or management decisions.
That treatment is the largest single gap between this measure and the firm's money, and it is usually not visible on the same page.
Additional context for “Hours That Were Written Off” is available from UAE Ministry of Human Resources resources. Current legal, employment, tax and accounting requirements should be confirmed with a qualified adviser where necessary.
What a write-off is
A reduction between recorded value and invoiced value, or between invoiced value and collected value. It happens for several reasons that are worth keeping separate.
- Overrun — the work took more hours than the fee assumed.
- Quality — the output needed correcting and was not charged for twice.
- Negotiation — the client disputed the invoice and a reduction was agreed.
- Goodwill — the reduction was offered to protect the relationship.
- Fee cap — the ceiling was agreed before the work started.
The engagement was overrun. The work was below standard. The client negotiated. The partner chose goodwill. The fee was capped from the start.
Why the ratio cannot see it
Because utilisation is a count of hours and a write-off is a reduction in value. The two live in different systems and are reported by different people.
A firm can therefore show a rising utilisation figure through a quarter in which revenue per hour fell, and both reports are correct.
The combination that looks best and is worst
High utilisation, low realisation. Everybody is busy, the hours are recorded, and a large share of them are waived at invoice.
This state is stable because the measure everybody watches is going up. It can run for a year before anybody connects the two reports.
The combination that looks worst and is fine
Moderate utilisation, high realisation. Fewer hours booked, almost all of them paid.
Judged on utilisation alone this is a problem to be fixed, and fixing it reliably makes the firm worse off.
Counting written-off hours: the case for
The hours were worked. Excluding them means a person's figure depends on a billing decision made by somebody else, often months later.
It also makes the figure impossible to produce promptly, because write-offs settle slowly.
Counting them: the case against
The numerator stops being a measure of value and becomes a measure of recording. Anything that can be coded to a client counts, whatever happens to it afterwards.
Both cases are good, which is why the practical answer is to count them and publish realisation beside the ratio.
The two-number report
Utilisation and realisation on the same line, for the same population, for the same period. Their product is the share of available hours that turned into money.
That product is the figure a firm actually cares about and almost nobody reports.
Who the write-off belongs to
Not usually the person who recorded the hours. Overrun on a fixed fee is a scoping decision. A negotiated reduction is a commercial decision. Goodwill is a relationship decision.
Attributing write-offs to the individual who booked the time moves blame to the only person in the chain who did not make the decision.
What to look at instead
The write-off rate by engagement and by cause. Five causes, a percentage each.
That table identifies the scoping and pricing problems that a bare realisation figure averages away, and it points at decisions somebody can change.
The timing problem
Write-offs are known late. A monthly utilisation report is current and a monthly realisation report is a quarter stale.
The honest version reports utilisation monthly and realisation on a rolling quarter, labelled as such, rather than pretending both are current.
The write-off that was decided before the work
A fee cap agreed at the start is not a write-off in any meaningful sense. The firm knew the ceiling and chose to work past it.
Treating planned overrun as a write-off makes realisation look like a billing failure when it was a pricing decision, and it puts the consequence in the wrong report.
Separating capped-fee overrun from genuine reductions is one coding change and it stops a pricing question being discussed as a collections question.
Reading the two measures through a quarter
The pattern worth watching is not the level of either but their relationship over several quarters. Both rising is growth. Both falling is contraction. Utilisation rising while realisation falls is the state this note is about.
That divergence is detectable from two columns and a chart, and it is the single most useful thing a firm can extract from data it already has.
Firms usually find at least one period of divergence in any three-year window, and the explanation is usually a specific engagement or account rather than anything general.
What the product is called
Nothing, in most firms, which is part of why it is not reported. Utilisation and realisation both have names and their product does not.
Giving it one — converted capacity, or realised utilisation — makes it a thing that can appear on a page and be asked about.
Unnamed figures do not get reported, however simple they are to compute, and this one is a single multiplication of two numbers the firm already publishes.
What the note on realisation adds
A fuller account of the companion measure sits later in this collection. The short version is that utilisation counts hours offered and realisation counts hours paid for.
Reporting either one alone leaves out half the transaction.