Guide

The weekly review, simplified: how to do one you'll actually keep

Updated November 2026 · by Jerry Liu, Dayflow's founder

Keep it to three questions: what happened, what's unfinished, and what one thing changes next week. Do it in a fixed 20-minute slot with a notebook and your calendar, which is enough for most people. If you can't remember what you did, an automatic record like Dayflow on a Mac helps. If you need blocking or team reports, a different tool wins.

It’s Friday afternoon, or Sunday evening, and you open a blank page titled “Weekly review.” You meant to do this every week. The last one was a month ago. You scroll your calendar, see a stack of meetings on Tuesday, and can’t remember what you did on Wednesday at all. Twenty minutes later you have a list of thirty open tasks, a faint guilty feeling and no idea what to change.

So you skip it next week. Then the week after. The review becomes one more thing you’re behind on, which is the opposite of what it was supposed to do.

This guide offers a smaller weekly review that still works on a tired Friday. It covers why reviews usually fall apart, six things to try (almost all with paper or your calendar), and where an automatic record of your day can help. One note first: Dayflow, the Mac app mentioned near the end, is our product, and we say plainly where it is the wrong pick.

The short version

Why does my weekly review keep falling apart?

Most weekly reviews fail for ordinary reasons, not because of a lack of discipline.

It’s too big. Many people copy a review from a productivity system with a dozen steps: empty every inbox, update every project, check goals for the quarter. That takes an hour on a good day. On a normal Friday it feels like homework, so it gets postponed.

Memory is thin by the end of the week. You remember the loud things: the deadline, the hard meeting, the bug that ate an afternoon. The quiet hours are gone. You sit down to review and find you’re mostly reviewing your calendar, which shows when you were booked, not what you did.

It turns into a guilt list. Looking at everything unfinished all at once is unpleasant. Many people find the review becomes a tally of what they didn’t do, and nobody looks forward to that.

It has no fixed home. If the review happens “sometime on Friday,” real work will always win. It slides to Saturday, then to never.

It doesn’t end in a decision. If you finish the review and nothing changes on Monday, it starts to feel pointless, and pointless things are easy to drop.

Each of the steps below targets one of these. You don’t need all six. Pick the one that matches the reason your reviews stall, and add others later.

What should a simple weekly review include?

Three questions, written at the top of a page:

  1. What actually happened this week? Not what was planned. What happened.
  2. What is still open, and does it still matter? Cross out anything that no longer does.
  3. What is one thing I’ll do differently next week?

That’s the whole review. The first question looks back, the second clears loose ends without turning into a full task audit, and the third gives the review a point.

Use a paper notebook or a single notes file you reuse every week. Keeping old reviews in one place matters, because after a month you can flip back and see patterns you wouldn’t spot in any single week.

Illustration: A product designer writes: “Happened: finished the onboarding flow, two long feedback calls, lost most of Thursday to file exports. Open: icon set (still matters), conference talk idea (drop it). Next week: batch exports into one block on Monday.”

How to tell after a week: Did you finish the review in one sitting, and did you know what your “one thing” was on Monday morning? If yes, the size is right. If you still ran over, drop question two for now and keep only the first and third.

If you also have to report to a manager, do the review first and write the report from it. The weekly status report template and the guide on how to write a weekly status report cover that side. Keep the two documents separate. The review is for you, so it can be honest.

When should you do a weekly review?

Whenever you can protect it. The time slot matters less than the fact that it’s fixed.

What to do: Pick a 20-minute slot and put it on your calendar as a repeating event. Friday afternoon works for many people because the week is still fresh. Others prefer Monday morning so the plan feels immediate. Then attach the review to something you already do: the last coffee of the week, closing your laptop on Friday, the walk back from lunch.

Set a kitchen timer or a phone timer for 20 minutes. When it rings, finish the sentence you’re on and stop. A review that’s allowed to sprawl is a review you’ll dread.

Illustration: A freelance developer sets “Weekly review” for 3:30 pm Fridays, right after the weekly invoice reminder. Same mug, same notebook, same three questions. The calendar event description just says “3 questions, 20 min.”

How to tell after a week: Did the event survive, or did you drag it somewhere else? If it moved once, that’s normal. If you moved it and then still skipped it, the slot is wrong. Try a time with fewer competing demands, like first thing Monday before you open email.

How do you remember what you did all week?

The review is only as good as what you can recall. Trying to rebuild five days from memory on Friday is where many reviews die.

What to do: At the end of each workday, write two lines: what you mainly worked on, and anything that surprised you (a task that took much longer, an interruption, a good stretch of focus). That’s it. It takes under two minutes, and on Friday you’ll have ten lines to read instead of a blank page.

A paper index card on your desk works well. So does a single running notes file. If you want a structure, the daily work log template gives you a simple one, and the work journal guide explains the habit in more depth.

Illustration: A consultant’s index card for Wednesday reads: “Client deck revisions, most of the day. Surprise: 90 minutes on a spreadsheet I thought would take 15.” On Friday, that second line becomes the review’s most useful note.

How to tell after a week: Count the days with notes. Three or more out of five is plenty to work from. If you managed zero or one, the problem isn’t the review, it’s the capture. Move the two lines to a moment you never miss, like right before you close your laptop, or use the section on automatic records further down.

For more on this specific problem, see how to remember what you worked on.

Look back before you plan

When you sit down to review, the pull is to start planning straight away. Resist it for the first ten minutes. Planning without looking back tends to repeat last week’s plan, including the parts that didn’t work.

What to do: Spend the first half of the review only on question one. Read your daily notes. Scroll your calendar day by day. Glance at your sent messages and the files you edited. Write down where the time actually went, roughly, without judging it.

If you want a quick sense of how your hours divide up before you start, the where does my week go calculator turns rough estimates into a picture of the week. The where did my day go page covers the same question at the scale of a single day.

Illustration: A team lead reads back through the week and notices that every afternoon had “quick” calls added on short notice. None was long, but together they broke up every afternoon. That’s not visible on any one day. It shows up when you look at five days together.

How to tell after a week: Did you find at least one thing you didn’t already know? A surprise, a pattern, a task that took longer than you thought? If the look-back only confirmed what you expected, try a different source next time, such as sent messages instead of the calendar.

If you want to go much deeper than a weekly glance, a one-off time audit is the bigger version of this step. The guide on how to do a time audit on a Mac walks through it.

Change one thing, not ten

The review is only worth doing if something changes because of it. But a list of ten changes rarely survives Monday.

What to do: End every review with one small, specific change for next week. Specific means you’d know by Friday whether you did it. “Be more focused” doesn’t qualify. “No meetings before 11 on Tuesday and Thursday” does.

Write the change somewhere you’ll see it on Monday: a sticky note on the monitor, the first line of next week’s page, or the description of a Monday calendar event.

Illustration: After noticing that exports kept eating afternoons, the designer from earlier writes “Monday 9-10: all exports, then don’t touch them until Friday.” Next Friday, question one has an easy check: did that hour hold?

How to tell after a week: Start the next review by reading last week’s one change and answering yes, partly or no. Don’t add a new change until you’ve answered. If you keep landing on “no,” the change was too big. Halve it.

Do it next to someone

Some weeks, the hardest part is simply starting. Doing the review alongside another person can take most of that friction away.

What to do: Ask a friend, a colleague or a partner to do their own weekly review at the same time as you, in the same room or on a video call with cameras on. You don’t have to share what you write. Spend two minutes at the start saying what you’ll cover, 20 minutes working quietly, and two minutes at the end saying your one change out loud.

This is a version of body doubling, and many people find it makes routine tasks much easier to begin. The body doubling guide has more ways to set it up.

Illustration: Two friends who both freelance meet on a call at 4 pm on Fridays. Each reads their one change for next week aloud before hanging up. Neither checks the other’s work. Just saying it to someone makes it feel more real.

How to tell after a week: Did you do the review when you otherwise might not have? That’s the only measure that matters here. If the call itself became a long chat and the review never happened, keep the conversation to the last five minutes.

Where seeing your actual day helps

The weak point in most weekly reviews is the daily capture from step three. Some weeks you’ll forget by Tuesday, and Friday starts from a blank page again.

Dayflow is a Mac app that builds a record without you starting a timer. It keeps screen recordings and a timeline of your day stored on your Mac, and AI writes what was on your screen into that timeline. You choose how screenshots are analyzed: a local model through Ollama or LM Studio keeps analysis on-device, your own cloud provider processes selected screenshots under its own terms, or Dayflow Pro manages the cloud analysis. The local and cloud processing page explains the differences.

For a weekly review, the look-back step starts with something to read. You can scan the week’s timeline, or export a date range as Markdown from Settings → Export and paste it next to your three questions. The export guide walks through it. AI summaries can miss or misinterpret work, so treat the timeline as a prompt for your memory, and check it before sharing anything from it.

The app is $0 and MIT licensed, needs macOS 14 or later, and has an optional Pro plan at $20 a month (pricing). These details come from Dayflow’s own documentation and settings as reviewed on 2026-09-06.

Dayflow publishes this article, so keep that in mind as you read this section.

Where Dayflow is the wrong pick

Be clear about what it can’t do before you install anything.

If you want to compare other approaches, the roundup of Mac time trackers covers the broader category.

The bottom line

A weekly review doesn’t need a system. It needs three questions, a fixed 20-minute slot and a few notes from the week so you’re not reconstructing it from memory. Look back before you plan, leave with one change, and check that change next Friday.

Start with paper and your calendar. If the daily capture is what keeps breaking, that’s the point where an automatic record on your Mac might be worth trying. Either way, the version you actually keep is better than the thorough one you skip.

Frequently asked questions

What is a weekly review?

A weekly review is a short, regular check-in with yourself about the week that just ended. You look back at what actually happened, note what is still open, and decide what to change for the next week. It doesn't have to be a big planning ritual. A simple version fits on one page and takes about as long as a coffee break.

How long should a weekly review take?

Aim for about 20 minutes and set a timer. A short, fixed length makes the review easier to start and stops it from turning into a full replanning session. If you regularly need more time, the review is probably trying to do too much. Cut it back to three questions and move deeper planning to a separate, occasional session.

What questions should I ask in a weekly review?

Three are enough. What actually happened this week? What is still open, and does it still matter? What is one thing I'll do differently next week? The first looks back, the second clears loose ends, and the third gives the review a point. You can add questions later, but start with these and see if you keep doing it.

What day is best for a weekly review?

The best day is the one you can protect. Friday afternoon works for many people because the week is still fresh and the work brain is still on. Others prefer Sunday evening or Monday morning so the plan feels immediate. Pick one slot, put it on your calendar as a repeating event, and attach it to something you already do, like the last coffee of the week.

What should I do if I skip a week?

Don't try to review two weeks at once. Do this week's review as normal and only look at the current week. Catching up turns a 20-minute habit into a long chore, which makes it more likely you'll skip again. A missed week is information too. Note what got in the way and consider moving the slot to a time that held up better.

How do I remember what I did all week?

Capture a little during the week rather than relying on memory on Friday. Two lines at the end of each day, written on paper or in a notes file, are usually enough. Your calendar, sent messages and recent files can fill gaps. On a Mac, an automatic record such as Dayflow's timeline can help if you often forget to write anything down.

Is a weekly review the same as a weekly status report?

No. A weekly review is for you: it's honest, messy and private, and it includes things that didn't go well. A status report is for someone else and focuses on progress, blockers and next steps. Doing the review first often makes the report quicker, because you've already worked out what happened. Many people write the report straight from their review notes.

Is Dayflow better than a paper notebook for a weekly review?

Often it isn't. If you reliably jot a couple of lines each day, a paper notebook wins: it's free, works anywhere, captures phone calls and offline work, and the act of writing helps you think. Dayflow only sees what's on your Mac's screen. It's more useful for people who keep forgetting to write things down and work mostly at their computer.

Can Dayflow block distracting websites during the week?

No. Dayflow doesn't block websites or apps. It records what was on your Mac's screen and writes a timeline of the day, which you can look back on during your review. If what you need is to stop yourself opening certain sites, a dedicated blocking app is the better choice. Dayflow is a record, not a blocker or a coach.

See where your day actually went

Dayflow is $0 and open source. Full recordings stay on your Mac, with local AI available for on-device analysis.

Download for MacOS macOS 14+ · MIT licensed · no account required