Freelance project tracking without project software

It's Tuesday morning. You're three weeks into the Bravo proposal for one client, halfway through Lena's website rebuild for another, and a third client just emailed asking "how are we doing?". You don't need Asana, Jira, or a Gantt chart. You need to answer one question without lying to yourself: how much of each project is actually done.

Most freelancers I've talked to solve this with sticky notes, a Notion page they stopped updating in March, and vibes. It works until a client asks for a status update on a Friday afternoon.

Why most freelancers don't need project software

Project tools assume things solo work doesn't have. They assume teams, dependencies, stakeholders, sprint ceremonies, someone to assign tasks to. When you're one person running four client projects, none of that exists. The actual problem is much smaller: grouping today's task list by client so you can see, in five seconds, which project you're behind on. That's not a roadmap problem. That's a list problem.

What freelance project tracking really means solo

For a freelancer, project tracking is four questions, asked weekly:

• What's left on this project
• What am I doing on it today
• Is it slipping
• What do I need to tell the client on Monday

That's the whole specification. Anything else is software trying to justify its monthly fee. You don't need burndown charts because you don't have a team to burn down with you. You don't need dependencies because you know in your head that you can't ship the homepage before the wireframes are signed off. The tool can't know that, and it doesn't have to.

There's a behavioral mechanism worth naming here: the planning fallacy. It's the well-documented tendency to underestimate how long your own tasks take, even when you've been wrong about the same kind of task many times before. The cure isn't a fancier estimation method. The cure is seeing the actual pile of remaining tasks every day, so the size of what's left becomes obvious instead of imagined.

How to manage multiple clients with a daily planner

The method is boring and it works. You keep one task list, the same one you'd use if you only had one client. You tag each task with the client or project it belongs to. Once a week, you switch from the day view to the project view and look at each pile.

That's the whole system. Daily, you work from one list. Weekly, you zoom out per project. The rest is just discipline about putting tasks in the right place when they land in your inbox.

A typical week for someone with four active clients:

• Monday morning: 10 minutes choosing today's tasks from the combined list
• Tuesday to Thursday: work the day list, add new tasks under the right project as they arrive
• Friday afternoon: scroll through each project group, decide what moves to next week
• Friday before logoff: write one sentence per client to send Monday morning

No standups. No story points. No time tracking unless you bill hourly.

A working setup: tasks, labels, and project groups

Here's how this looks in TaskBerry, which is what I use. Tasks live in your day, the way a normal to-do list works. Labels separate categories of work, usually one per client plus an "admin" label for invoicing and email triage. Then there's a feature called "epics" (which is jargon, sorry; from here on I'll call them project groups) that lets you group tasks under a named project like "Bravo proposal" or "Lena website rebuild".

A project group does one thing well: it shows you the tasks that belong to a specific deliverable, with a count of how many are done versus how many are open. Six of fourteen complete. Three of five complete. No fake percentages. No burndown chart. The progress is just tasks done over tasks total, which is the only honest measure when each task can be any size.

This is where most freelancers actually need help. Not with planning, with seeing. When Mees, a back-end developer in Amsterdam, started grouping his tasks under "Q2 Bravo proposal" and the list grew from 6 items to 17 in three weeks, that wasn't a feeling anymore. That was a visible pile. He sent a scope email that afternoon. The pile is the signal.

Project groups are a Pro feature. Labels and the basic day list are free. If you're running two projects, you can probably get away with just labels. Past three or four, the project view starts paying for itself.

When this approach breaks down

Two honest limits, because pretending they don't exist would waste your time.

This is the wrong setup if you have eight or more active projects, real dependencies between subcontractors, or a client who wants a shared dashboard they can log into. At that point you're running a small studio, not freelancing, and you need software built for that. Asana exists for a reason.

Two specific things this setup does not do:

• No dependencies between tasks. If task B genuinely cannot start until task A is done, the planner won't enforce it. You'll know in your head, the tool won't.
• No shared client view. Your client cannot log in and watch progress. If a client wants a live dashboard or a status page, this is the wrong tool. Send them a Friday email instead.

The second one is usually fine. Most clients don't actually want a dashboard; they want to stop wondering. A short Friday email solves that better than a login they'll never use.

The Friday review that keeps clients calm

The whole system rests on 10 minutes on Friday. Open each project group, look at what's open, decide what moves to next week. Note one thing to tell each client on Monday. That's it.

This is the part that makes "how are we doing?" emails painless, because by the time the email arrives you've already answered the question for yourself. For Roos, a freelance accountant in Den Bosch, Friday at 4pm during quarter-end is six client groups open in tabs, each with its own filing checklist. She doesn't need automation. She needs to know which two of the six still have open items before she logs off, so Monday doesn't start in a panic.

The review pairs naturally with a Monday brain dump. You can turn the pile into a Monday plan in two minutes by reading the open items aloud and letting the assistant pull out the ones that actually need to happen this week. Or you can do it with a notebook. Both work. The thing that doesn't work is skipping the review and hoping you'll remember on Monday morning, because you won't, and then you're back to vibes.

If you've tried Asana, found it too heavy for solo work, and went back to a notes app, this method is built for you. A list, grouped by client, looked at once a week. It removes the part of project tracking that was never your real problem, and leaves the part that was.