Back to field notes

Ivan Terekhin

Weekly Habit Review: Read Your Log and Choose One Change

Weekly Habit Review: Read Your Log and Choose One Change

Open the week's record, count the opportunities you actually planned, and identify one adjustment for the next week. Keep full actions, partial attempts and missing information separate. A useful review ends with a specific decision, not a verdict on your character.

A daily tracker can show what you logged without telling you what to do next. The weekly review is the short step between the record and the next plan. This guide uses a worked seven-day example, a few clearly labelled counts and a decision table you can reuse with a notebook or Baseline.

It is different from designing a whole 90-day challenge. The longer plan sets the window; this review checks one ordinary week inside it. You do not need to start a challenge, buy a new system or rebuild every routine to use the worksheet.

Start with the rule that was in force

Write the intended action and its schedule before looking at the result. If the rule was “write for twenty minutes on Monday, Tuesday, Thursday and Friday,” the week contained four planned opportunities. Wednesday was not a missed session just because the calendar had an empty square.

If the rule changed during the week, date the change. “Twenty minutes until Thursday, then ten minutes from Friday” is a different plan from seven days under one stable rule. Keep that difference visible rather than rewriting the beginning of the week to match the end.

The same applies to a limit you were tracking. Describe the behaviour and the context precisely enough that an entry has a consistent meaning. Our builds-and-drains guide explains the app's input framework; your review still needs the actual action behind the label.

Before making any judgement about the week, ask whether the rule was clear enough to be recorded. If it was not, clarifying the rule may be the only change you need for next week.

Read a seven-day record without filling the gaps

Here is an invented writing example. The scheduled action is twenty minutes on four specified weekdays. A partial attempt is recorded honestly, without being counted as a complete session.

DayScheduled actionWhat the record saysContext
MondayTwenty-minute sessionFull sessionStarted after clearing the desk
TuesdayTwenty-minute sessionFull sessionUsed the same cue
WednesdayNoneNot scheduledNo session expected
ThursdayTwenty-minute sessionFive-minute attemptAn appointment shortened the available time
FridayTwenty-minute sessionFull sessionStarted later, but completed the planned action
SaturdayNoneNot scheduledNo session expected
SundayNoneNo extra action recordedDo not infer an unlogged session

The record supports three full sessions out of four planned opportunities: 3/4 = 75%. It also supports four attempts out of four opportunities: 4/4 = 100%. Both descriptions can be useful. They should not be collapsed into an unexplained “100% successful week.”

The distinction is not a penalty for the five-minute attempt. It keeps the original plan and the actual behaviour readable. You can value the attempt while still asking whether the twenty-minute version fitted Thursday.

Check what an empty entry means

An empty field can mean several things: an action was not scheduled, it was missed, it happened but was not logged, or you do not remember. Those meanings should not automatically receive the same label.

If you cannot reconstruct an event, mark it unknown. Do not add a precise duration because it seems likely. If your app has no separate unknown status, keep a brief note beside the review rather than treating the missing record as certainty.

Likewise, a checked box tells you what was recorded, not everything about the quality of the work. Twenty minutes of writing could produce a draft, a revision or very little usable material. If the outcome matters, look at the work itself alongside the count.

For ideas about what to record in the first place, see habit-tracker ideas. This review assumes you have chosen a few meaningful actions already; adding more categories is not automatically an improvement.

Use the daily score as one view of the week

Baseline combines logged build and drain inputs into a daily net and shows a trend. That can help you see the record at a glance. The score does not replace the underlying entries when you are deciding why a plan was difficult to follow.

Two days with the same net can contain different actions. One may include the build you care about most and a recorded distraction; another may contain several different inputs. Open the details before deciding that the days were equivalent for your current goal.

Avoid changing the scoring interpretation halfway through the review to make a week look better or worse. If you change what you track, record when the change starts. Compare like with like wherever possible, and keep older records under the rules that produced them.

The useful question is “Which entries explain the pattern I am looking at?” It is more concrete than deciding that a higher weekly total must mean every part of the routine improved.

Choose the smallest decision the record supports

Use this table to move from an observation to a possible next step. These are planning examples, not conclusions that must apply to everyone with the same number of checkmarks.

ObservationA specific adjustment to considerWhat would be an overreach?
Thursday was shortened by a known appointmentMove that planned session or choose a smaller Thursday version in advanceConclude that the entire routine is impossible
The action happened but several entries are missingMake the logging step easier to rememberTreat the unlogged days as proven failures
The sessions were completed but the work did not answer the goalReview the task or feedback used inside the sessionAdd more time without inspecting the work
A distraction repeatedly appeared in the same settingChange one feature of that setting or the planned responseBan every enjoyable activity for the next month
The week was workableKeep the same plan for another weekAdd several new rules just because there is room on the tracker

For the worked example, a reasonable decision is to plan Thursday separately. It could move to a different available time, or its intended version could be shorter. Either way, write the new rule before the next Thursday rather than deciding afterward how to classify it.

If the obstacle is unclear, the next step can be better observation. “Add one note about what interrupted the session” is a valid change. You do not need to invent a mechanism before the record contains enough information.

Write a one-sentence plan for next week

Keep the decision in a form you can act on. For example: “Next Thursday, I will use the shorter version after the appointment; the other three sessions stay the same.” That names the day, the action and the scope of the adjustment.

Another example is: “After each session, I will log it before closing the document.” That addresses a recording problem without changing the actual task. Keep those two kinds of change separate so the next review can tell you which one you tested.

If you use an if-then plan, make the situation specific enough to recognise. “If the meeting runs late, use the version already written in the plan” is clearer than “If life gets difficult, try harder.”

Put the next review at a time you can keep, but do not let arranging the review become the week's main project. The worksheet is finished when you know what you will keep, what you will change and what you still do not know.

Compare later weeks carefully

Suppose one week has three full sessions out of four planned, and another has four out of five. The counts are 3/4 and 4/5, not simply three versus four. A larger number of completions may partly reflect more scheduled opportunities.

Across those two example weeks, the combined count is 7/9, about 77.8%. That describes the nine planned opportunities. It is not evidence that a habit has become automatic or that the plan will work indefinitely. Keep the denominator and the meaning of “full” alongside the number.

Short reviews are most useful when they lead to modest decisions. Continue a workable rule, revise a specific obstacle or gather a missing detail. Leave larger claims about long-term change for a longer, consistent record.

A reusable closing note

End the review with four short lines:

  • Keep: the part of the routine that was usable.
  • Change: one specific adjustment for the coming week.
  • Clarify: an instruction or missing detail you still need.
  • Check next time: the observation that will tell you whether the adjustment helped.

You can keep those lines in the same place as the daily record. The review then becomes a bridge between one week and the next, with enough detail to guide action and enough restraint to avoid turning a few entries into a grand conclusion.

Edited by Ivan Terekhin, drafted with AI tools.