Four Numbers Every Freelance Tracker Should Calculate
Most trackers record hours and send invoices and call that bookkeeping. It is not bookkeeping. It is a diary with time stamps. The actual bookkeeping is the four numbers you can compute from that diary at the end of the month — and the reason almost nobody computes them is that each one says something mildly unpleasant about how the month went.
That is exactly why they matter. A number that flatters you does not need to be tracked. A number that makes you wince is the one running your business.
There are four. Each is simple arithmetic, and each changes a decision.
One: the overage hours — the difference between what you scoped and what you spent
Take every project, and for each one subtract the hours the proposal assumed from the hours actually logged. Sum the positive differences. That total is your overage month.
What it tells you: your estimating error, and where it lives. If the overage is spread evenly, your estimates are consistently optimistic and you already know the fix — add the buffer at the proposal stage. If it is concentrated in one or two projects, the fix is not the estimate, it is the client, or it is the scope, and you should re-read those files before you blame your arithmetic.
The number is not a judgment. It is the difference between two guesses you made at different times, and the only reason it matters is that the later guess was the one you actually lived.
Two: the actual rate — real money divided by real hours
Divide what actually arrived in your account this month by the hours you actually worked this month — not the hours you billed, the hours you spent, including the ones you never invoiced. That is your actual rate.
What it tells you: the gap between the rate you quote and the rate you keep. The two diverge in only a few ways, and this number makes you look at all of them at once: unbilled hours, absorbed scope, unpaid waiting, and the admin time that never lands on any invoice. If your quoted rate is [amount] and your actual rate is half of it, you do not have a pricing problem yet — you first have a leakage problem, and pricing harder while leaking is like raising the tap while the bucket has a hole.
Three: the days-to-payment — invoice date to money date
For each invoice that cleared this month, count the days from the invoice date to the day the money arrived. The middle value of that list — not the average, the middle one — is your realistic payment cycle.
What it tells you: how long your money is actually dead. This is the number with the widest gap between belief and reality, because people remember the fast ones. "Most clients pay within two weeks" is usually true for a minority of clients, and the middle invoice tells you the actual wait. Two consequences follow from the real number: you know how many months of runway you actually need, and you know which invoicing clause to fix. Net terms that you set yourself — like "on receipt" — are more negotiable than you act as if they are.
Four: the vanished-deadline days — promised dates that stopped being dates
Count the days this month by which a deadline moved without a conversation. A deadline that moved because the scope changed after a discussion is a real event and does not count. A deadline that silently slid — yours or the client's — is this number.
What it tells you: the difference between your deadlines being promises and your deadlines being suggestions. This is the diagnosis behind most "the client keeps pushing" complaints, and the diagnosis is usually flattering to no one: a deadline that was never anchored in a concrete cost keeps moving because moving it costs nothing. Once you can count the days, you can see that each slide was free — and you can start charging for the next one, even if the charge is only a conversation.
Why monthly is already too late
These four numbers are all computable weekly, and two of them — overage and vanished deadlines — are computable early enough to act on. A month is enough time for a bad scope to eat three weeks of your calendar. By the time the monthly number shows it, the month is spent.
The Monday check is the version that works for a solo business: before the week starts, look at the four numbers for last week, not the whole month. [Core number] being wrong in week two is information. Being wrong in week four is a story you tell yourself about the weather.
What a tracker should actually do
The failure mode of most tracking setups is that they are built to record rather than to answer. Seven databases, each full, and at the end of the month you still answer the question "how was May?" with a feeling instead of a number.
The fix is a standing calculation, not more data entry. The four numbers above only need the fields you already have: scoped hours, logged hours, invoice date, payment date, and deadline changes. If your system computes these five fields on a schedule instead of waiting to be asked, the monthly version of you gets four answers instead of a diary.
If your system cannot compute them, that is a system problem, not a discipline problem — a list of numbers nobody ever sums is not a dashboard, it is a pile.
The test
Compute the four numbers for the last complete month. Do not adjust anything. Write them down in the order above.
Now answer two questions. Which number is the worst? And is that the number you would have guessed before computing it?
If the worst number is the one you already knew, your problem is not information — it is that you have been watching a known leak and doing nothing, and the number has stopped being news. If the worst number is a surprise, the tracker just earned its keep for the entire month in five minutes.
This note describes four calculations. No outcomes, averages for any population, or "most freelancers" claims are made; the figures in the worked examples are placeholders for your own numbers. [amount] and [core number] are slots to fill from your actual records.
Related notes
- Scope Doesn't Creep. It Gets Invited. — the biggest source of overage hours, and the three-sentence trade that stops absorbing them.
- The Decision Log, Not the Notes — the record that makes the four numbers possible: if the decision isn't written down, the deadline change never happened on paper.
- Define Done Before You Start, or Argue About It Later — what "scoped hours" is actually anchored to, before the month starts leaking.