Guide
Block one hour near the start of the month. Gather evidence first: your calendar, sent messages, a few weekly notes on paper, or an automatic screen record like Dayflow on a Mac. Then answer the same four questions every month: what happened, what mattered, what drained you, and what one thing you will change. Paper and a calendar are enough for most people.
It’s the first of the month and someone asks how the last one went. You open your calendar, scroll back, and the weeks look like rows of nearly identical boxes. You remember the deadline that ran late, the week you were sick, one good dinner. The rest is a smudge. You know you were busy every day. You just can’t say on what.
So you sit down to “do a monthly review,” maybe with a fresh notebook page and good intentions. Twenty minutes later you have three vague bullets and a faint bad feeling. Next month you skip it.
This guide covers why months blur, how to run a review in about an hour, and seven things to try. Most need nothing more than paper and a calendar. A note up front: this article is published by Dayflow, a Mac app we make. It comes up once, near the end, along with an honest section on when it is the wrong choice.
Memory isn’t a recording. It keeps the peaks, the endings and the surprises, and it quietly folds ordinary days together. A Tuesday spent answering messages and nudging a project forward looks almost exactly like the Wednesday after it, so your mind stores them as one blurry “busy” stretch. By the end of the month, most of what you actually did lives in that blur.
There’s also a timing problem. Most people only think hard about how a month went when something forces it: a missed deadline, a performance review, a moment of feeling stuck. Reflection that only happens under pressure tends to be harsh and lopsided. You remember the thing that went wrong and forget the twelve things that went fine.
Then there’s the blank page. “How was my month?” is too big a question to answer from scratch. Without prompts, people drift toward feelings (“it was stressful”) instead of facts (“I spent most afternoons in meetings that started late”). Feelings matter, but they are hard to act on. Facts give you something to change.
Finally, reviews often fail because they are open-ended. With no time limit and no fixed questions, a review can easily stretch on, wander, and end without a decision. After one or two of those, skipping it feels reasonable.
The fixes below address each of these: leave a trail so the blur has something to anchor to, use evidence instead of memory, ask fixed questions, and end every review with one decision.
What to do. Every Friday, before you close your laptop or leave work, write three lines in a notebook: what you finished, what took longer than expected, and one thing you want to remember. That’s it. No reflection, no scoring. If you want a structure to copy, the weekly work log template has a simple layout.
An illustration. Imagine a freelance designer whose Friday notes for one week read: “Finished the logo round for the bakery. Client feedback call ran an hour over. Remember: I work best on illustration before lunch.” Four of those entries turn a vague month into something with edges.
How to tell after a week. You’ll know it’s working if writing the note takes under five minutes and you didn’t dread it. If you skipped it, make it smaller: one line instead of three, or a sticky note on your monitor instead of a notebook. If you want to go further, a daily version is covered in what a work journal is and how to keep one.
What to do. Block one hour on a fixed day in the first week of the month and make it a recurring calendar event. Put your four questions (see step 4) in the event notes so you never have to reinvent the plan. When the hour comes, use a kitchen timer and split it into three twenty-minute parts: gather, answer, decide. When the timer goes off, move on even if a part feels unfinished.
An illustration. Picture someone who reviews on the first Sunday morning of the month, with coffee, at the kitchen table. The first timer covers scrolling the calendar and the notebook. The second covers writing answers. The third covers choosing one change and adding it to next month’s calendar. They’re done before lunch.
How to tell after a week. Look at whether the next review is still on your calendar and whether you feel neutral, not dread, about it. If an hour felt like too much, try thirty minutes with ten per part. A short review you do every month is worth more than a thorough one you keep moving.
What to do. Spend the first part of the review collecting facts, with a rule: no conclusions yet. Go through your calendar week by week, then your sent email or messages, your Friday notes, any documents or projects you touched, photos on your phone, and receipts if they’re relevant. Jot down what you find as plain bullets. “Three client calls. Moved apartments. Rewrote the onboarding doc twice.”
If you’re not sure where your hours went at all, the where does my week go calculator is a quick way to rough out a typical week before you start. And where did my day go walks through the same reconstruction at the scale of a single day.
An illustration. Imagine someone who felt the month was “a waste.” Their evidence list shows two finished projects, a week of travel, and a steady stream of small requests from one colleague. The month wasn’t wasted. It was fragmented, which is a different problem with a different fix.
How to tell after a week. The real test is whether your answers in step 4 got more specific. If they still sound like “it was busy,” you probably skipped ahead to judging. Next time, finish the evidence list fully before writing a single opinion.
What to do. Use the same four questions every month, written in the same order:
Keeping the questions fixed is the point. After a few months you can line up the answers and notice that “client calls running over” shows up every time, or that the months you felt best were the ones with fewer evening commitments. If you need to share a version with a manager, the monthly status report template turns question 1 and 2 into something presentable.
An illustration. Here’s how one month might look on a single page:
| Question | Example answer |
|---|---|
| What happened? | Launched the new pricing page, onboarded two new clients, helped my sister move |
| What mattered? | The launch went out on time; the move was worth the lost weekend |
| What drained me? | Status meetings that could have been messages; the inbox after lunch |
| One change? | Ask to turn the Thursday status meeting into a written update for one month |
How to tell after a week. Check whether your answers fit on one page and whether question 4 is concrete enough that a friend could tell you did it. If your answers run long, set a limit of three bullets per question.
What to do. The review ends with a single decision. Write it as a small experiment with a time attached: “For the next four Mondays, I won’t open email until 10.” Then put it somewhere you’ll see it, like a recurring calendar reminder or a note taped inside your notebook cover. At next month’s review, the first question is simply: did I try it, and what happened?
Calling it an experiment matters. If it doesn’t work, you haven’t failed. You’ve learned something, and you can try something else next month.
An illustration. Picture someone whose review keeps showing meetings eating their afternoons. Their change: “Decline any new meeting after 3 p.m. for one month, unless it’s with a client.” The following month’s review notes that they declined four meetings, nobody was upset, and two afternoons turned into real work.
How to tell after a week. After seven days, ask yourself one thing: have you actually done the experiment at least once? If not, it was too big or too vague. Shrink it until it’s almost silly, like “No email before 10 on Mondays only.” You can always grow it.
What to do. Find a friend, partner or coworker who’d also like to review their month, and spend twenty minutes trading answers to the four questions over coffee or a call. You don’t need advice from each other. Just saying “this month I kept pushing the same task” to another person tends to make it clearer, and knowing someone will ask about your experiment next month makes it more likely to happen.
An illustration. Imagine two former classmates who call each other on the first Saturday of every month. Each gets ten minutes. One talks about a side project that keeps stalling; the other mentions finally fixing their sleep schedule. They don’t solve anything for each other. They just listen and ask, “So what’s the one change?”
How to tell after a week. It’s working if you’re looking forward to the next call and you remember what you said your change would be. If it turned into a venting session, add a rule: end every call by each person stating their one experiment.
What to do. On a single sheet of paper, or the back page of your notebook, give each month one line. After each review, write the single most important thing that happened and the one change you chose. That’s twelve lines for the whole year.
This page becomes surprisingly useful. When someone asks what you worked on this year, or when it’s time to prepare for a review at work, you have the answer in one place instead of rebuilding it from scattered notes.
An illustration. A line might read: “March - Shipped the redesign. Change: no meetings Friday mornings (kept it).” By December, scanning the page shows which changes stuck and which you quietly dropped.
How to tell after a week. After one review it’ll only have one line, which is fine. The test is whether you added it right after the review, before closing the notebook. If you forgot, attach it to the end of your review checklist as the final step.
The hardest part of a monthly review is step 3: finding evidence for weeks you barely remember. A Friday note helps, but you have to remember to write it, and a calendar only shows what was scheduled, not what you actually did between meetings.
If you work on a Mac, Dayflow is one way to fill that gap. It records your screen at one frame every 10 seconds and has AI write each day into a readable timeline, so there is no timer to start and no day to rebuild from memory. Recordings and the timeline are stored on your Mac. You can keep screenshot analysis on-device with a supported local model, use your own cloud provider, or use Dayflow Pro, which manages cloud analysis for you. The details are in local and cloud processing.
For a monthly review, the useful part is export: in Settings → Export you can export a date range as Markdown, so the whole month becomes a text file you can skim during your twenty minutes of evidence gathering. The export work history workflow shows how.
Dayflow is $0 and MIT licensed, with an optional Pro plan at $20 a month (see pricing). It requires macOS 14 or later. The AI summaries can miss or misinterpret work, so treat them as a starting point and check them before sharing.
Dayflow publishes this article. Product details here come from its published documentation and settings as of September 6, 2026.
Be honest with yourself about whether you need software at all. For many people, a notebook with Friday notes and a fixed review hour does the whole job, and adding an app just adds something to maintain.
Dayflow is also the wrong choice if:
A monthly review doesn’t need to be long or deep to be useful. It needs a fixed hour, some evidence, the same four questions, and one decision at the end. Months blur because ordinary days fold together in memory, so the most helpful thing you can do is leave yourself a small trail during the month and look at facts before feelings.
Start with paper. Write three lines this Friday, put a one-hour review on your calendar for the first week of next month, and end it with a single experiment. If you find that gathering evidence is the part you keep skipping, that’s the point where an automatic record might be worth trying.
About an hour is a good starting point for most people. Split it into three parts: twenty minutes gathering evidence, twenty answering a fixed set of questions, and twenty choosing one change and putting it on your calendar. A kitchen timer keeps each part from swallowing the others. If an hour feels like too much, a thirty-minute version that you actually do beats a two-hour version that you keep postponing.
Keep the list short and identical each month so you can compare answers over time. Four questions work well: What actually happened this month? What mattered most? What drained me or kept getting pushed? What is one thing I will change next month? Answering the same questions every time makes patterns visible, which is most of the value of reviewing monthly instead of only reflecting when something goes wrong.
A weekly review is mostly maintenance: clearing loose ends, checking next week's calendar, and deciding priorities. A monthly review steps back further. It looks for patterns across several weeks, such as where time went, what kept slipping, and whether your days match what you say matters. Many people find weekly notes make the monthly review far easier, because the month is already partly written down.
Do not rely on memory alone, because ordinary days blur together. Pull evidence instead: your calendar, sent email and messages, commits or documents you changed, photos, receipts, and any notes you kept. Going forward, write three lines every Friday about what happened that week. Four or five short entries give a monthly review something solid to work from, and they take only a few minutes each.
Yes, and for many people paper works better than an app. Use one page per month with the same four headings, plus a single year-at-a-glance page where each month gets one line. Paper is quick, has no notifications, and is easy to flip through when you want to compare months. The only thing paper cannot do is fill itself in, so a short Friday note during the month helps.
Not really. Dayflow records one person's own Mac screen and writes a personal timeline. It has no team reports, shared dashboards, invoicing or payroll approvals. For a team monthly report, a shared document or the project tracker your team already uses is the better choice, because everyone can add their own updates and see the same picture. Dayflow can still help you write your own section.
Change the order. Start with plain facts about what happened, then name at least two things that went fine, and only then look at what drained you. Frame the change as an experiment rather than a fix for a flaw. A review is a look at how the month went, not a grade on you. If it keeps feeling heavy, shorten it and talk it through with a friend instead.
It can, but keep it small. One change for the next month is easier to test than a list of five goals, and it gives next month's review something clear to check. Write the change as a specific experiment with a time attached, like moving one recurring meeting or protecting two mornings a week, so you can tell honestly whether you tried it and whether it helped.
Pick a day you can protect and keep it fixed, like the first Sunday or the first working Monday afternoon. The exact day matters less than consistency. Put it on your calendar as a recurring event with a short note listing your four questions, so you do not have to rebuild the plan each time. Doing it within the first few days keeps last month fresh.
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