You finish a review with six ideas for next month. All six are reasonable. The projects already occupying the calendar haven't gone anywhere.
Before adding those ideas, look at what the last month asked of you. Decide what deserves another month of attention, what needs a different arrangement and what you can stop or pause.
Tiago Forte's October 14 annual-review Q&A article discusses reviewing actual experience before making further plans. This monthly exercise focuses on one decision you can carry into the calendar. Use the weekly review template when the immediate job is getting your lists current.
Look at the month you actually had
Open the calendar and a few records of your work. Look for what happened: meetings attended, sessions moved, work delivered and commitments that still haven't found time.
You aren't trying to reconstruct every hour. A useful example is enough to challenge an assumption. A side project that was meant to take one evening but occupied several weekends deserves a closer look.
Ask what changed. Was there an unusual deadline? Did a family commitment take more time? Did the task need work you hadn't expected? A month with a one-off disruption doesn't necessarily tell you what every future month will be like.
The calendar isn't complete evidence either. An empty Saturday can contain care work, errands or rest that never became an event. Add the context you need before treating an empty box as unused capacity.
Compare what you meant to do with what the work needed
Suppose you planned a small portfolio update alongside client work. Your notes show that choosing examples took longer than expected, two case studies need permission and the website changes haven't started.
"Be more consistent" doesn't explain those findings. You have decisions to make about scope, permissions and time.
Try a small review table:
| Project | What the month showed | Decision to consider |
|---|---|---|
| Portfolio update | Two examples need permission | Ask for permission before reserving the editing session |
| Weekly newsletter | Preparation used most of Sunday | Reduce the scope or reconsider the frequency |
| Optional course | No sessions happened | Pause it or give it an actual place next month |
These are possible decisions, not recommendations that every newsletter should become shorter or every missed course should be abandoned. Use the record to ask the right question about your work.
Separate stopping, pausing and waiting
Stopping means you no longer intend to continue. Pausing means you might return, with some condition or review point. Waiting means progress depends on information or action you don't currently control.
Record that distinction so a paused project doesn't quietly remain in next week's active list. "Reconsider after the client launch" is a useful condition. "Someday" may be enough for an idea with no current commitment, but it shouldn't conceal something another person expects you to deliver.
If you decide to stop a shared commitment, communicate the decision. Explain what will happen to any part already underway and agree on a handoff where needed. Removing it from your own list doesn't remove someone else's expectation.
For waiting work, name what you're waiting for and when to follow up. Don't reserve repeated drafting sessions for a project that still needs permission to begin.
Make room before adding a goal
Choose the outcome you want to advance next month and estimate what its next stage needs. Compare that with the time already committed.
If you want to spend two evenings a week on a course, identify those evenings. If both are already occupied, decide what will change before calling the course a priority.
You may choose to keep a project at a slower pace instead of dropping it. Define that pace in terms you can use. "One case study this month" is clearer than "make steady progress on the whole portfolio."
If the decision depends on a conversation, make that conversation the next action. Don't wait for a perfect plan to tell a collaborator that the current arrangement isn't working.
Leave the review with one visible change
You don't need to restructure every project. Update the decision that most affects the next few weeks, then make the calendar and task list reflect it.
That might mean cancelling an optional recurring session, setting a review date for paused work or reserving the first session for the smaller agreed project. Keep any real deadline visible while changing work sessions around it.
If you use Dainvo Projects, Pro keeps tasks, a deadline and multiple work blocks together. Those details help you inspect a plan; they don't choose which commitments you should keep. You still need to update the work and communicate any changed agreement.
Keep a short note about the decision and why you made it. Next month's review can then ask whether the change helped, using something more useful than a fresh set of ambitions.
Check the consequence of the decision
Imagine you pause an optional course until a client launch ends. Remove the next study sessions from your active plan, keep the course details somewhere you can find them, and set a review point after the launch. If there is a payment or enrolment deadline, check that separately; pausing your study plan does not pause someone else's terms.
At the review point, ask whether you still want the course and what time you could give it now. You are allowed to decide against restarting. The note preserves the choice without promising that your future month will have unlimited space.



