Why the delay itself costs money

The idea in short

Most attention on manual work goes to the labor: the minutes somebody spends doing it. But a great deal of administrative work carries a second cost that has nothing to do with how long the task takes. It is the gap between when something happens and when it is recorded.

That gap would exist even if the task were instant and free, because the delay is usually caused by batching: done on Friday, or at month end, or whenever somebody gets to it.

The labor has a cost of its own that is easy to miss. It is often done by one of the most capable people in the business, whose time could go to work that brings in revenue.

Where the gap turns into money

• Money arrives later. Work finished on the 3rd and invoiced on the 30th is paid roughly four weeks later than it needed to be. Nothing was in dispute; the invoice had not been created yet.
• Windows close. Early-payment discounts, return periods, and deadlines that reward being early expire on a calendar that does not care when the paperwork was processed. They are almost never declined on purpose. They lapse because the item was not in the system while the window was open.
• Decisions run on stale figures. Whatever is not yet recorded is not in the total, so the number people plan against is systematically missing the most recent activity.

The error cost of delay

Errors get cheaper the sooner they are found. A discrepancy caught the day it occurs can be resolved by asking someone, and they will remember. The same discrepancy found seven weeks later is an investigation: nobody recalls the specifics, the person may be gone, and the trail is cold. Same error, different cost, determined only by when it surfaced.

Why batching feels efficient

Doing a week of entries in one sitting genuinely is faster per item. The instinct is not wrong about the labor. It is wrong about everything else. The batch is efficient for the person doing it and expensive for the business, and because labor is the only part anybody measures, the trade-off is never made consciously.

What changes

Work that is recorded as it happens removes the gap instead of shortening it. The invoice exists when the job finishes. The figure is current when somebody looks. The discrepancy surfaces while the answer is still in somebody's memory.

None of that shows up as hours saved, which is why it tends to be left out of the case for changing anything, and why it is frequently the larger number of the two.

Questions worth asking about your own operation

• What is recorded weekly or monthly that could be recorded when it happens?
• How long between finishing work and sending the invoice?
• Which deadlines does the business only meet by accident?