Software, systems & independent workToolsAboutNewsletter

Todoist for Freelancers: A Simple System for Client Tasks

Todoist logo beside a client task list organized into Today, Upcoming and Completed.

Build a focused Todoist workflow for freelance tasks, with a sample project structure, weekly review and sharing checks before choosing a plan.

Brand images identify the products discussed. This is independent editorial coverage.

In this article
  1. Start with projects, not a complicated dashboard
  2. A sample setup for a freelance writer
  3. Distinguish a work date from a promise
  4. Run a weekly review
  5. When a different tool may fit better
  6. Before you choose a Todoist plan
  7. Continue reading

AI-assisted editorial illustration. Layouts are conceptual, not product screenshots.

Research basis: official product documentation checked on 25 October 2026. This is a researched guide, not a hands-on performance test. Product links are ordinary links, not affiliate links.

Todoist is worth considering when your problem is remembering and completing next actions across several clients. The useful question is whether a task-focused workflow meets your needs. A list of tasks alone will not replace an agreed project scope, a complete client record or an invoicing process.

Start with projects, not a complicated dashboard

Todoist projects group related tasks. Its official guidance describes personal and team projects, sections, dates and sharing. When you share a project, collaborators can access its tasks, comments and attachments, so project boundaries matter. Consult Todoist’s project documentation for current behavior and plan limits.

For a small freelance practice, trial three projects: Client A, Client B and Business admin. These are suggested organizational labels, not a required template. Keep personal reminders and internal commercial notes outside any project you intend to share.

A sample setup for a freelance writer

Imagine you are delivering two articles for one client and updating a landing page for another. Create tasks that describe an observable action. “Client A article” is vague; “Send Client A the proposed outline” tells you what to do next. Put supporting context in the task or link to the authoritative brief rather than making several competing copies.

ProjectExample actionCompletion check
Client ASend outline for article oneOutline delivered through agreed channel
Client BResolve feedback on headlineDecision recorded in the brief
Business adminReview outstanding proposalsEach proposal has a next action

Use sections only if they help you distinguish kinds of work. A simple Next actions and Waiting structure may be enough. Do not create elaborate labels for a workload you can already understand at a glance.

Distinguish a work date from a promise

When scheduling tasks, distinguish the date you intend to work from the delivery commitment you made to a client. Record the commitment clearly in the task context and your agreed project brief. Do not rely on remembering which meaning you gave a date several weeks earlier.

At the start of a day, select a small set of actions that fits your available time. A long list does not create capacity. Leave room for feedback and interruptions, particularly when work depends on another person’s approval. If a task repeatedly slips, break it into a smaller action or renegotiate the commitment.

Run a weekly review

  1. Check each active client project for an action you can actually take.
  2. Review waiting items and decide whether a follow-up is due.
  3. Compare planned work with the commitments in your briefs.
  4. Remove obsolete tasks and clarify vague ones.
  5. Choose the next week’s essential outcomes before adding optional work.

For example, a waiting item saying “feedback” should identify what feedback you need and who owes the decision. This makes the review actionable without turning every open question into an urgent notification.

When a different tool may fit better

If your main difficulty is coordinating many dependencies, maintaining detailed project documentation or presenting progress to clients, trial a project-management system alongside your task list. Judge it against those needs rather than assuming a paid task-app tier solves them. Avoid entering the same action into two systems unless you establish which one is authoritative.

Before you choose a Todoist plan

Write down how many active projects you need, who needs to collaborate and which views matter to your routine. Check those requirements against current plan entitlements. Do not pay for team administration simply because you work with clients; first establish whether your actual collaboration requires it.

Test with a representative week of work. Note missed actions, time spent reorganizing tasks and any confusion about shared content. Our recommendation is to keep the system only if it makes your commitments easier to manage. A visually tidy list is not enough evidence on its own.

Three-step framework: Capture actions, then Separate projects, then Review commitments.
A practical framework for applying this guide.

Continue reading

Explore Productivity or browse all topics.

Newsletter

One useful idea a week.

AI, productivity and building in public. No spam, unsubscribe anytime.

This field is required.