Project management in a company and project management as a freelancer have little in common.
In a company, a project involves teams, dependencies, status meetings, and reporting. The tools are built for that. They're powerful. They're also designed for dozens of people working together.
You work alone. You don't need a Gantt chart. You need to know where each project stands, what's left to do, and what's already been delivered. That's a much simpler problem.
What a project database needs to do
A freelancer's project database needs to answer three questions:
- Which projects are in progress right now?
- Where does each project stand in its progress?
- What was agreed, produced, delivered?
If your system answers those three questions quickly, it works. Everything else is optional.
Essential properties for a project
Placeholder: project database with essential properties and statuses visible.
A project database works with seven to nine properties. The essentials:
- Project name: descriptive, not generic
- Linked client: the relation to your client database
- Status: Brief received, In progress, Awaiting feedback, Delivered, Archived
- Start date and planned delivery date
- Project type: if your work covers several service types
- Amount: for a quick overview without opening an invoicing tool
Properties to avoid at the start: auto-calculated completion percentage, priority on a 1-to-5 scale, estimated versus actual hours. These require constant updates to stay reliable. If you don't maintain them, they become noise.
Freelance project phases
A freelance project moves through predictable phases. Five statuses cover the vast majority of situations:
- Brief received: the project is signed, work hasn't started yet
- In progress: active production
- Awaiting feedback: you've delivered something, you're waiting on client input
- Delivered: the project is complete
- Archived: closed, invoice paid
Placeholder: horizontal pipeline with 5 stages — Brief received / In progress / Awaiting feedback / Delivered / Archived. Coloured rectangles on dark background.
A Board view with these phases gives you an immediate overview of your project portfolio. You see at a glance what's moving, what's waiting, what's stuck.
The projects and tasks relation: when to add it
If you work on short projects with few steps, a checklist inside the project record is more than enough. Not a full database.
If you work on long projects with many distinct steps, a linked task database can make sense.
Add a task database only if you regularly find yourself wondering "what do I need to do today on this project?" If the checklist in the record answers that, keep the checklist.
What a well-built project record contains
Placeholder: open project record with brief, deliverables, and notes sections.
The project record is the central document of a project. It needs to answer one simple question: if you reread this record in six months, do you understand what happened?
A useful project record contains: the initial brief, agreed deliverables, important decisions made along the way, links to related files, and end-of-project notes.
It's not an exhaustive log. It's enough context to reconstruct the situation quickly.
Want a concrete starting point? The "Manage your business" Notion template includes a pre-configured project database with the phases and views described in this article. See the template →
