A freelancer quotes a client for a five-hour task. Three days later she is still on it, the client has sent two rounds of changes, and she has no idea how long the job really took. She can't say whether the project was a good deal or a bad one. Time tracking fixes exactly this, and it costs nothing to start.
This guide shows you how to track time in a way that survives power cuts, patchy data and a busy week. It also shows you what to do with the numbers afterwards, because a log nobody reads is wasted effort.
Why tracking time matters even if you charge a fixed price
Many beginners think time tracking is only for hourly work. It isn't. If you charge per project, your time log is the only honest way to learn whether your prices are right.
Without it, you guess. Guessing usually leads to underquoting, because we remember the fun parts of a job and forget the emails, the revisions and the file exports. A log gives you evidence for three decisions:
- Pricing: what to quote the next similar job.
- Client choice: which clients take far more time than they pay for.
- Capacity: how many projects you can actually carry in a week.
If you want the pricing side in more detail, read Is Your Online Side Hustle Worth It? Find Your Real Hourly Rate and Hourly or Fixed Price? How to Quote a Freelance Project.
Choose a tracking method that fits your setup
The best method is the one you will still use in week six. Here are the common options.
| Method | Works offline? | Best for | Weakness |
|---|---|---|---|
| Paper notebook | Yes | People with frequent power or data problems | Needs adding up by hand |
| Phone notes or a spreadsheet | Mostly (once the file is saved offline) | Most beginners | You must remember to log |
| Timer app or browser extension | Depends on the app | Hourly clients, long sessions | Timers get left running |
| Client platform tracker | No | Hourly contracts that require it | Rules set by the platform |
Check each app's own website for current features, pricing and whether it works offline. Free versions change often, so don't assume.
My suggestion: start with a notebook or a simple spreadsheet for two weeks. Add an app later only if you find the manual way too slow. Hourly clients on some platforms require the platform's own tracker, so read the contract terms before you begin.
Set up a simple time log in ten minutes
You need only six columns. Build this in Google Sheets or Excel, and make sure the file is available offline on your phone or laptop.
- Date
- Client
- Project
- Task type (research, drafting, revisions, messages, admin, learning)
- Minutes (use minutes, not decimals of hours; it's easier)
- Billable? (yes or no)
The task type column is the one most people skip, and it is the most useful. It shows you that "writing a 1,000-word article" actually includes research, messaging and revisions.
Track small tasks too
The hours that vanish are rarely the main work. They are the small things around it:
- Reading a long brief and asking questions
- Waiting for files to upload on slow data, when you are actively stuck on it
- Revision rounds
- Invoicing and chasing payment
- Calls and their preparation
Log these under their own task types. When you later see that admin and messages take 20% of your hours on a project, you can price for it or set limits.
Handling power cuts and data problems
Unstable power and data costs are normal for many readers in Nigeria, Ghana, Kenya and South Africa, though load-shedding and outage patterns differ by place. Your tracking should not depend on a perfect connection.
- Keep a paper notebook beside your laptop. Write start and stop times when the power drops, then enter them later.
- Decide a rule for outages: time lost to a power cut is not billable and not "worked", but time you spend on a task on battery is.
- Enter your log once a day at a fixed time, for example before you shut down. Ten minutes is enough.
- Back up the file weekly to cloud storage or a second device. See Freelancer Account and File Security: A Practical Setup for a sensible backup habit.
A worked example (hypothetical)
Say a freelance writer quotes $60 for a 1,200-word blog post. She expects it to take three hours. After tracking, her log for that project looks like this:
| Task | Minutes |
|---|---|
| Reading brief and asking questions | 25 |
| Research | 70 |
| Drafting | 90 |
| Editing her own draft | 35 |
| Two revision rounds | 60 |
| Messages and invoice | 20 |
That adds up to 300 minutes, or five hours. At $60, her real rate is $12 an hour before any platform or transfer charges, not the $20 she imagined. These numbers are made up, but the pattern is common.
What can she change? She could quote $90 next time for the same scope, limit revisions to one round and charge for extras, or use a template for research notes to cut that 70 minutes. Her log tells her which lever is cheapest to pull. Research took the most time after drafting, so a better source list might help most.
Review your log every week
Pick a fixed slot, such as Friday afternoon or Sunday evening, and spend fifteen minutes on it. Ask:
- How many billable hours did I work, against hours I planned?
- Which client or project took more time than I priced for?
- Which task type is growing without pay (revisions, messages)?
- What one change will I make next week?
Write the answer to the last question at the top of your sheet. One small change per week is enough. If revisions are the problem, the fix is in your contract, and Scope Creep: How to Stop Unpaid Extra Work From Clients explains how to set limits.
Common mistakes
- Logging from memory at the end of the week. You will round everything down. Log daily.
- Leaving a timer running. A three-hour "task" that included lunch teaches you nothing. Check your timer when you sit down and when you stand up.
- Billing a client for time you only tracked for yourself. Hourly clients should be billed according to your agreement and any platform rules. Never pad hours. Inflated time can breach platform terms and costs you the client's trust.
- Tracking too many categories. Six task types are plenty.
- Treating the log as punishment. It is a measuring tool. Slow weeks are data, not failure.
When the advice changes
If you have a full-time job: track your freelance hours separately and be realistic about evenings. A log may show you have six usable hours a week, not fifteen. That helps you decline work you can't deliver.
If you are a complete beginner: track even practice and portfolio work. Knowing how long a sample takes helps you quote your first paid job.
If you work with an hourly client: follow the client's or platform's required method. Keep your own log as a backup, and share clear notes on what each block of time covered.
Frequently asked questions
Should I tell clients I am tracking my time?
For fixed-price work, you don't need to, since it is for your own planning. For hourly work, agree the tracking method and reporting in your contract.
How long should I track before I trust the numbers?
Aim for at least four weeks and three to five projects of a similar type. One job can be an outlier.
Do I count time spent finding clients?
Track it, but mark it non-billable. It still shows what your business costs you in hours, and it helps you judge whether your outreach is working.
What about time spent learning a new tool?
Log it under "learning". If a client's job forced you to learn it, consider whether future quotes should include that setup time.
Your next step
Open a spreadsheet today, add the six columns, and log everything you do for your next client project, including messages. After four weeks, work out your real hourly rate and compare it with what you thought you earned.
Results from any side hustle or online work vary widely, and nothing here is a promise of income. Be wary of anyone who asks you to pay upfront to start earning.