Tools & templates

Weekly Review Checklist

A 20-minute weekly admin reset checklist for pipeline, delivery, and money so your freelance business doesn’t run on panic.

checklistUpdated Feb 07, 2026

When to use this

  • You want a weekly rhythm that reduces admin and prevents last-minute surprises.
  • You’re behind on follow-ups, invoices, or receipts and want a default reset.

Preview

Progress

0 / 15 complete

A small weekly reset to keep pipeline, delivery, and money from drifting.

Pipeline

Delivery

Money + tax

Admin reset

How to use this checklist (the 20-minute reset)

Freelance chaos is usually "missing small habits," not missing big knowledge. This checklist is a weekly reset you can run in ~20 minutes to keep three systems from drifting:

  • pipeline (so next month isn't a surprise),
  • delivery (so clients don't guess),
  • money + tax (so taxes don't jump-scare you).

Use the interactive checklist in the preview as a repeatable operating procedure. Check items off as you go. Run it once per week on the same day. Consistency beats perfect tools. If you want to reuse it in your own doc, use "Copy as Markdown."

Pairs well with

What this weekly review prevents

A weekly review is boring on purpose. It is not a motivational ritual and it is not a deep strategy session. It is a small set of maintenance habits that prevent predictable failure modes.

  • Pipeline surprises: the calendar looks fine right now, but next month is empty because follow-ups slipped.
  • Delivery ambiguity: you are working, but the client cannot tell what is happening, so they guess (and guessing creates tension).
  • Money and tax jump-scares: you avoided looking for a few weeks, and now invoices, cash, and taxes feel like a crisis.

The checklist is designed to push you back to clarity, even when you do not feel like doing admin. Clarity does not solve every problem, but it usually makes the next step easier to choose. It also helps keep small problems from compounding.

Quick start (the actual 20 minutes)

The point of a weekly review is not to create a perfect system. The point is to prevent drift, week after week, before small problems turn into urgent problems. You are building a habit that keeps your pipeline, delivery, and money from going stale.

Start with the interactive preview

Use the interactive preview to run the checklist in the same order each time. Check items off as you go. When you like how it looks, use "Copy as Markdown" to drop the checklist into your own doc (for example, a weekly notes page). This can give you a simple archive of what you did, without creating extra admin work.

If you only take one thing from this page, take this: pick a day of the week, put a recurring block on your calendar, and run the checklist the same way every time. Repetition makes it faster. If you change the process every week, you will spend the time reorganizing instead of resetting.

An easy way to keep this honest is to treat the weekly review like a short appointment with your business. When the 20 minutes are up, you stop. If you discover a bigger issue (a large scope decision, a project that needs replanning, a pricing rethink), capture it and schedule a separate block. This is how you keep admin from expanding to fill your whole week.

Illustrative timebox (adjust it, do not overthink it): spend a few minutes each on pipeline, delivery, and money + tax. The specific split matters less than the consistency.

Pipeline review (so next month isn't a surprise)

Your pipeline is the set of active conversations that can become work. When it drifts, it rarely fails loudly. It fails quietly: someone you meant to reply to never hears back; a warm lead cools down; a past client forgets you exist; your calendar looks fine this week but empty next month.

This checklist keeps the pipeline system from drifting by pushing you toward two behaviors: sending follow-ups and logging them. That's it. Pipeline rarely improves by accident.

What to do in the pipeline portion

  • Send follow-ups: decide the next message for each active thread and send it.
  • Log what you did: write down the date and what you sent so you don't rely on memory next week.

A minimal follow-up log (keep it lightweight)

"Log it" does not mean you need a heavy CRM. It means you can open one place next week and immediately see what happened. If you are not sure what to record, a minimal log usually includes: who the thread is with, what you sent, when you sent it, and what you expect to happen next (if anything). That is enough to prevent threads from disappearing.

The goal is not to be clever. The goal is to be consistent. A logged follow-up is a small habit that can reduce the mental overhead of worrying.

If your pipeline feels thin, don't panic and start rebuilding your entire marketing strategy in the middle of a weekly review. Capture the observation ("pipeline is thin"), then schedule a separate block to address it. When you do, you may find it helpful to read find clients without a huge audience for a concrete path forward that does not depend on having a huge audience.

Keep the pipeline section simple: follow up, log it, move on. The weekly review is about preventing surprises, not building a complicated CRM.

Delivery review (so clients don't guess)

Delivery drift looks like ambiguity. You are working, but the client cannot tell what is happening. They are unsure whether you are waiting on them, whether you hit a snag, or whether the next milestone is still realistic. When clients don't have clarity, they fill the gap with guesses.

The reset here is simple: if delivery is stalled, ask for the missing input in writing and set a new date. Waiting silently is how timelines die.

What counts as "missing input"?

Missing input is anything you need from the client (or another stakeholder) to move forward without guessing. Examples vary by project, but the pattern is the same: you are blocked, and the block has an owner. If the block has an owner, it can be requested in writing.

How to make the request (without drama)

Keep it short, specific, and written. You are not asking permission to proceed; you are stating what is needed and what it does to the timeline if it is delayed. A good request also creates a clear next date so the work does not float.

Illustrative phrasing you can adapt:
"To deliver [milestone], I need [input]. If I have it by [date], I can deliver by [new date]. If not, the delivery date will move."

The weekly review is a good time to look for any place you are waiting silently. Silence often feels polite in the moment, but it makes the project harder to manage for both sides. Asking in writing keeps the timeline real and helps keep the relationship clean.

Money + tax review (so taxes don't jump-scare you)

Money drift shows up as avoidance. You do not look at invoices, you do not reconcile what is owed, and you do not set aside taxes because you are afraid of what you will see. But the fear usually comes from uncertainty, not from the numbers themselves.

The reset here is also simple: reconcile invoices and set aside taxes first. Clarity reduces panic.

Reconcile invoices (get to a single source of truth)

Reconciling invoices means you can answer basic questions without guessing: what was invoiced, what was paid, what is still outstanding, and what needs a follow-up. You do not need a complex finance system to do this. You need a habit of looking at the same list every week until it matches reality.

If you have overdue invoices and you want a structured follow-up sequence you can reuse, you can pair this weekly review with the invoice template for a late payment sequence. Keep the weekly review focused on identifying what needs attention; use a separate block to send the messages if you need more time.

Set aside taxes (before you spend the cash)

Taxes are often stressful because they feel like a future ambush. The weekly habit that reduces that stress is setting money aside regularly so you are not trying to catch up later. If you want a conservative default rule to get started, use the Tax Set-Aside Calculator.

If you want the full workflow for what to track each week (including notes by country), read Taxes: what to track weekly. The weekly review works best when you can quickly answer "What did I earn? What did I keep? What do I owe?" without turning it into an afternoon.

Decision rules

These rules are here to keep you from getting stuck in analysis. A weekly review is not the time to redesign your business. It is the time to choose the next small action that prevents drift.

  • If you only do one thing: send follow-ups and log them. Pipeline rarely improves by accident. A single consistent follow-up habit beats a complicated system you do not maintain.
  • If delivery is stalled: ask for the missing input in writing and set a new date. Waiting silently is how timelines die. Clarity in writing helps prevent misunderstandings and keeps momentum real.
  • If money feels scary: reconcile invoices and set aside taxes first. Clarity reduces panic. You do not need perfect bookkeeping to reduce stress; you need enough clarity to stop guessing.

FAQ

Do I need to run this every week?

Yes: run it once per week on the same day. The power of this checklist comes from repetition, and a weekly cadence is simple to remember.

What if I miss a week?

Do not try to make up for it by turning the next review into a massive cleanup. Start again, run the checklist, and keep the habit alive. Consistency beats perfect tools (and it also beats perfect streaks).

What if I only have five minutes?

Use the decision rule: send follow-ups and log them. Pipeline rarely improves by accident. If you have extra minutes, ask for missing delivery input in writing or reconcile invoices, but do not overcomplicate it.

Is the interactive preview the checklist, or is this page the checklist?

Use both together. This page explains the intent and the decision rules. The interactive preview is the repeatable operating procedure: check items off as you go, then export it using "Copy as Markdown" if you want it in your own notes.

How do I keep this from becoming more admin work?

Treat the weekly review as a reset, not a project. Stop when the time block ends. If something needs deeper work, capture it and schedule a separate block. This is how you keep admin from expanding while still keeping your systems maintained.

Want the operating system model?

Read your solo operating system for the maintained version of this workflow (tools, SOPs, and how to keep admin from expanding).

How to customize

  1. Pick a fixed weekly day/time and protect it (calendar block).
  2. Adjust the pipeline section to match your lead channel (outbound, referrals, platforms).
  3. Adjust money/tax steps to match your jurisdiction and bookkeeping setup.

Common pitfalls

  • Skipping weeks, then trying to catch up in a panic session.
  • Treating the checklist as a perfection project.
  • Letting admin expand to fill the whole afternoon.

Related Codex pages

Read the explanation

Use the tool with the context, not in isolation.

Read Codex: Solo Operating System Tools

Read the explanation

Use the tool with the context, not in isolation.

Read Codex: Taxes What To Track Weekly

Read the explanation

Use the tool with the context, not in isolation.

Read Codex: Find Clients Without Audience

Comments

Sign in to comment.

Loading comments…