Freelance Time Tracking Calculator: From Tracked Minutes to Real Earnings

Why the number on your rate card is not what you earn

Ask a freelancer what they charge and you get a clean figure — ninety, a hundred and ten, one-fifty an hour. Ask what they earned per hour worked last month and the answer usually arrives after a pause, because the second question requires data most people never collect. The gap between those two numbers is where freelance income quietly disappears, and it is rarely caused by charging too little.

A typical week contains around eight to fourteen hours that never reach an invoice. Some of it is unavoidable: someone has to send the invoices, do the bookkeeping, write the proposals and stay current in the craft. Some of it is entirely avoidable: the fourth revision that was never in scope, the hour spent chasing a logo file the client promised on Monday, the meeting that could have been a paragraph.

Time tracking is how you separate those two piles, and it only works if you track the whole day rather than the parts you intend to bill. This guide covers the buckets to log, the rounding rules that hold up under scrutiny, how to compute an effective hourly rate you can trust, and what to change first when that number comes back lower than you hoped.

How to turn tracked time into a rate you can trust

1. 01

   Track every minute of the working day, not just the billable ones

   Most freelancers track only what they intend to invoice, which makes the data useless for pricing. Log everything under one of four buckets: billable client work, unbilled client work, business admin, and business development. The unbilled client work bucket is the one that surprises people — revisions outside scope, chasing missing assets, meetings that were meant to be five minutes — and it is usually where a healthy rate quietly turns into a poor one.

2. 02

   Convert raw minutes into billable units with a stated rounding rule

   Decide once whether you bill in six-minute, fifteen-minute or thirty-minute increments and write it into your contract. The rule matters more than the size: rounding every task up to fifteen minutes across a day of small interruptions can add two hours a week, while rounding to the nearest unit rather than up is close to neutral. Undocumented rounding is what turns a routine invoice into an awkward conversation.

3. 03

   Calculate your effective hourly rate, not your quoted one

   Effective hourly rate is total invoiced revenue divided by total hours worked, including everything unbilled. A freelancer quoting $110 an hour who bills twenty-six of a forty-hour week is earning $71.50 an hour on the time they actually spend. This single figure explains more about freelance income than any other number, and it is only available if step one was done honestly.

4. 04

   Separate the drag you can bill from the drag you must price in

   Some unbilled time is recoverable: scope creep, extra rounds and client-caused delays belong in the contract as billable or capped. Some is structural — invoicing, bookkeeping, proposals, your own learning — and can never be invoiced, so it has to be recovered inside the rate instead. Splitting the two tells you which conversations to have with clients and which number to change on your rate card.

5. 05

   Turn the tracked total into an invoice line clients can verify

   Multiply billable units by your rate, add any fixed fees or pass-through costs, then attach a short summary by task rather than a raw timesheet. Clients dispute time logs when they read like surveillance and accept them when they read like progress. A line saying eleven hours across three named deliverables settles faster than sixty-two entries, even though the total is identical.

A worked example: a $110 rate that earns $68.57

One tracked week for a freelancer who quotes $110 an hour. Nothing here is unusual — the admin load is modest and the revision time is ordinary — and the effective rate still lands thirty-eight percent below the rate card.

What each rounding rule is worth on a 24-hour billable week

Modelled on twenty-four billable hours at $110 across roughly forty separate task entries. The gain column is the annualised effect on a typical month, and the last column is the conversation each rule invites.

Signs your tracked time is not telling you the truth

Each of these makes the effective rate look better than it is, which is the worst possible direction for an error in a pricing input.

• !You only start the timer once the real work begins
• !Client calls and email are never logged anywhere
• !Your rounding rule is not written in the contract
• !Revisions are tracked but never invoiced
• !You cannot say what your effective hourly rate was last month
• !Admin hours are treated as free rather than priced in
• !Timesheets are reconstructed on Friday from memory
• !Two similar projects show wildly different hours and nobody asked why

Using tracked data to reprice fixed-fee work

Fixed-price work is where tracked time pays for itself fastest. A quote is an estimate of hours dressed up as a number, and without history every estimate repeats the optimism of the last one. Three tracked projects of the same type give you a range, a median and — more useful than either — a sense of which phase consistently overruns.

In practice the overrun is almost never in production. It sits in discovery, in waiting for feedback, and in the final ten percent of a deliverable where small changes accumulate. Once you can see that, the fix is structural rather than financial: a fixed feedback window, a defined number of rounds, and a start condition that requires assets in hand.

Reprice using the effective rate rather than the quoted one. If a $4,000 project consistently takes fifty-two hours across every bucket, it earns $77 an hour, and a target effective rate of $110 makes it a $5,700 project. That is a defensible number with evidence behind it, which is a far stronger position than announcing a general increase.

Making tracking a habit that survives a busy week

Tracking fails for the same reason budgeting fails: it demands attention exactly when attention is scarce. The systems that survive are the ones that require a single action — a timer started at the beginning of a block, not a form filled at the end of one. Reconstructing Friday afternoon from memory produces data that flatters you by roughly fifteen percent, which is enough to invalidate every conclusion drawn from it.

Keep the categories few. Four buckets is enough to compute everything in this guide; twelve buckets guarantees the system is abandoned by the third week. Detail can be added inside a bucket as a note without turning the log into a taxonomy exercise.

Review monthly, not daily. Daily numbers are noise — a day of proposals looks like a disaster and a day of deep production looks like triumph, and neither is informative alone. The monthly effective rate, the billable ratio and the unbilled client work total are the three figures worth an hour of your attention, and they are the ones that change your pricing.

Frequently asked questions