How to Track Time as a Freelancer: Find Your Real Hourly Rate

Six hundred dollars, ten hours: sixty an hour? Add five forgotten hours. Now it is forty. Where did the time go? Let's build a time log that catches those hours before your next quote.

Six hundred dollars for ten hours looks like sixty dollars an hour. But making the work was only part of the job. You also spent two hours on calls, two on revisions, and one arranging delivery. Five more hours. The client still paid six hundred.

Your calendar gave up fifteen hours. That means forty dollars per hour before your business costs. Here's why that matters. A project can look fast while quietly taking over your week. That hidden time matters even when your client pays a fixed fee.

The fee sets the revenue. Your actual hours reveal what the work demanded. This is illustrative math. We'll use the same project throughout. Start with one log for all your work.

A spreadsheet is enough to learn the habit. Give every entry a project, an activity, and a duration. Use the same project name every time, so one job stays together. Split activities into delivery, revisions, and client admin. Keep the labels simple.

General bookkeeping belongs in business admin, separate from a particular client. You can still count that time when reviewing your whole week. For our project, label the design work delivery, label feedback revisions, and label the calls client admin. You don't need twenty categories. You need labels you'll actually use.

Write a short description that your future self can understand. Give different projects for the same client their own names, too. Otherwise a profitable little task can hide a much larger project that overran. Homepage draft is useful. Worked on stuff won't explain an invoice later.

Start the timer when you start the task. Stop it when you switch tasks. The habit has three moves: pick the project, record the work, save the entry before switching. A ten minute client call counts even when you weren't at your desk. Add that entry while you still remember what the call was about.

If you forget a timer, reconstruct the entry from your calendar and notes. Mark estimates clearly. A convincing number is less useful than an honest one. Don't count two tasks at once. A running timer doesn't create extra hours.

Take breaks off the timer. Keep the record close to the actual work. At the end of each day, spend two minutes checking the entries. Look for empty days, overlapping sessions, and timers left running through lunch. Next, decide what's billable.

Track the time first; check the agreement before charging it. A billable entry is work the client agreed to pay for separately. A fixed project fee can already include calls, revisions, and delivery. Tracking those hours doesn't make them extra invoice lines. Keep three decisions separate: did the work happen, is it billable, has it already been invoiced?

That separation helps you avoid billing the same work twice. If a client requests extra scope, agree the price before doing it. Then record it separately. Your time log supports the conversation; it doesn't replace it. Internal rework still costs time even if you choose not to bill it.

Keep it visible so the next estimate reflects how the work actually went. Give yourself a short Friday review before the details fade. Check missing entries, billable status, and invoice status. Open each active project and read the activity descriptions together. Are three short revision sessions really one repeated problem?

Did the approval call take longer because the brief was unclear? The point is to improve the process, not blame someone for a slow day. For this project, ten delivery hours were visible. Five other hours were hidden. Review all fifteen together.

Now your next quote has a better starting point than memory. Choose one change: clearer feedback, fewer meetings, or a tighter scope. Write that change beside the project, then check whether it helped next time. Keep the old entry. Editing history to match your estimate defeats the exercise.

Six hundred dollars for ten hours looks like sixty an hour. Add five hidden hours. Divide by fifteen: forty dollars. Effective rate is revenue per hour of your time on that project. It isn't profit.

Software, contractors, and other costs still have to come out. And one project says less than several similar projects measured consistently. Compare the same kind of work before deciding what to change. If the fee stays fixed, reducing repeat revisions can improve the rate. If the scope stays fixed, your next quote can reflect the actual hours.

Don't promise either result from a timer alone. The decision changes the business. Here's how the billing part looks in Workspace369, with fictional example data. In Workspace369, run the timer for the project. Stop it when the work ends.

Select the unbilled time. Add it to a draft invoice. Review the client, descriptions, hours, and rate before sending that invoice. The demo uses hourly work. Our fixed fee example still needs its agreed billing.

Pick a tool that makes the daily habit easy to keep. For a team, agree the same categories before comparing anyone’s project totals. The useful connection is from recorded work to reviewed billing. Keep your approval step even when software makes the transfer faster. A draft is your checkpoint.

For the next week, capture the whole job, separate tracking from billing, and review the real rate. Start with one active project. Include the calls and revisions you usually forget. Review it on Friday, then change one thing in your next quote. Which disappears from your log more often: calls or revisions?

The checklist and example are in the description.