Aniket Bhardwaj Aniket Bhardwaj Blog

A simple weekly review routine for solo builders

Study guide — A simple weekly review routine for solo builders
By Aniket Bhardwaj · 5 November 2026 · Aniket Bhardwaj

This post gives you a weekly review checklist you can finish in about thirty minutes.

I use it on my own projects, and I explain why each step is there.

In short: Once a week, sit down at the same time. Look back at what you did, clean up loose ends, pick a few tasks for next week, and write one line about what you learnt. Keep it small enough that you never skip it.

Why a solo builder needs a review

When you work alone, nobody asks you for a weekly update. There is no manager and no team meeting. So you must ask yourself.

I have been teaching since 2008, and I have run several ventures over the years. One habit has stayed the same. Work that is never looked at again slowly drifts. A weekly review is the point where you look at the work and correct the direction.

A solo builder here means anyone who builds something on their own: a website, a small course, a set of notes, a tool, a book. The checklist below does not depend on what you build.

In a classroom, a test tells the student where they stand. A weekly review does the same job for your own work. It shows you what is done, what is stuck and what to do next.

Before you start: set the ground rules

A review fails when it becomes a big event. Keep these rules.

Why these rules? A short, fixed routine is easy to repeat. A long, flexible one is easy to postpone.

The checklist, step by step

Here is the order I follow. Each step has a purpose, so do not shuffle them.

  1. Collect loose notes (5 minutes). Gather scraps from the week: messages to yourself, half-written ideas, browser tabs you kept open. Put them in one list. Do not judge them yet. The aim is to get everything out of your head and onto paper.
  2. Look back at what you did (5 minutes). Write three to five lines on what you finished. Include small things. This step matters because solo work has no applause, and you need proof that you moved forward.
  3. Find what is stuck (5 minutes). Look at tasks that you planned but did not do. Ask one question for each: is it too big, unclear, or simply not important? Big tasks should be split. Unclear tasks need a clearer first step. Unimportant tasks should be deleted.
  4. Check your projects one by one (5 minutes). If you have more than one project, give each a single line: moving, waiting, or paused. This stops you from forgetting a project that quietly went cold.
  5. Pick next week's tasks (7 minutes). Choose a small number of tasks. I suggest three to five. Write the first physical action for each. For example, write that you will open the file and type the heading, instead of just writing the name of the chapter.
  6. Write one lesson (3 minutes). End with one sentence: what worked, or what you will do differently. Over many weeks, these sentences become your own notes on how you work.

The times add up to thirty minutes. They are a guide. If one step needs more time, take it from another, but do not cross the total.

A worked example

Here is how a review page might look for someone who is building a small website and writing study notes at the same time. The details are made up to show the method.

Collected notes: an idea for a new page, a typo spotted on an old page, a reminder to reorganise folders.

Done this week: wrote two note pages, fixed a broken menu item, tested the site on a phone.

Stuck: a task named "new homepage". It is too big. Split into three smaller tasks: choose the layout, write the headline, replace the picture.

Project status: website – moving. Study notes – moving. Folder cleanup – paused.

Next week: (1) choose the homepage layout on paper, (2) fix the typo, (3) write the outline of one new note page.

Lesson: I finish more when I write the first action, not just the task name.

Notice that the big homepage task did not go into next week as it was. It was broken into steps first. This is the most useful part of the review.

Weekly review versus daily planning

Some people ask whether a daily plan is enough. They do different jobs. This table shows the difference.

PointDaily planningWeekly review
Main questionWhat do I do today?Am I working on the right things?
Looks atToday's tasksThe whole week and all projects
Time neededA few minutesAbout thirty minutes
CatchesForgotten tasksDrift, stuck work, cold projects

Use both if you like, but if you can only keep one habit, keep the weekly review. It gives direction to the daily plan.

Common mistakes and how to fix them

Key takeaways

  • Fix a day, a time and a thirty-minute limit for your review.
  • Follow the order: collect, look back, find stuck work, check projects, plan, write one lesson.
  • Split big tasks and write the first action for each task you plan.
  • Pick only a few tasks for the coming week.
  • If you miss a week, restart with the next one.

Frequently asked questions

How long should a weekly review take?

About thirty minutes is enough for most people. The checklist above is timed to fit that. If it grows longer, you are probably working during the review instead of only deciding.

Which day should I choose for the review?

Any day works if you keep it fixed. Many people like the end of the working week or the evening before a new week starts. Choose the day when you are least likely to be disturbed.

Do I need an app for this?

No. A notebook page is enough. Start with paper or a plain document. Add tools only after the habit is steady.

What if I have only one small project?

Use the same checklist, but you can shorten step four. Even one project can get stuck, so the other steps are still useful.

What should I do if I find that I did very little this week?

Write it down plainly and look for the reason in step three. Often the tasks were too big or unclear. Fix that, and plan a smaller list for next week.

What to do next. Try it yourself on the page below.

Aniket Bhardwaj — Chemistry Educator, Author & Founder of 4AB →

Read next

Related across 4AB

Great Ventures · Section

Explore more