WINTER ARC · FIELD GUIDE

From daily notes to weekly and 30/60/90-day reviews

A review should leave you with a decision you can try. This workflow connects the evidence you already saved to one weekly adjustment, then looks across three separate 30-day phases. It is not a score for how disciplined you are.

1. Capture a small fact on the day

Check only the actions you actually completed. Save a short note about the cue, obstacle or next attempt. “The book was already on my desk” is easier to use later than “good day.” “I opened the lesson but could not explain the first example” is useful evidence even when the rule is incomplete.

Choose a day state deliberately. Regular tracking uses the rule checkboxes. Planned rest can be set in advance or corrected afterward. Marked missed records that you know the commitment was missed; it cannot be selected for a future date. An empty date remains unrecorded, not automatically missed.

Changing a state never deletes old checks or notes. While a date is labelled rest or missed, those old checks remain visible but are excluded from completion counts. Return it to regular tracking to make them count again or correct them. Undo can reverse the state change in the current tab.

2. Use the right denominator

The main calendar bar stays complete days / 90. The review uses reached dates minus planned rests as its active denominator. Missed, partial and unrecorded dates remain in that denominator. Future dates are excluded. A rest is not a completed day, and zero active dates displays “no active dates” rather than a misleading 100%.

An illustrative seven-day example

This is a made-up teaching example, not a user result. Imagine three reading rules. The dates below represent days 1–7 of an arc; no reading-speed or habit-formation outcome is assumed.

DayRecordUseful note
1All three rulesBook left on desk
2Reading rule onlyCould not summarize in my own words
3Planned restA day intentionally set aside
4Marked missedNo reading attempt
5All three rulesWrote a sentence before closing the book
6UnrecordedNo reliable record
7All three rulesRepeated the same cue

Seven dates have been reached, one is rest, so there are six active dates. Three are fully complete: 3/6, or 50%, for this review. Reading itself is 4/6. The other two rules are 3/6 each. The main calendar bar is still 3/90. The missing record on day 6 is not silently converted into rest to improve a percentage.

3. Write a complete weekly review

Open “Use this week’s notes in a review” below the daily note. Weeks are anchored to your start date: days 1–7, 8–14, and so on. Week 13 has days 85–90, only six dates. The rolling last-seven-day card is a different view and can overlap two of these weeks.

Each field allows 400 characters. Save explicitly. Drafts stay through language and period switches in the same tab. Counts update when a past check-in changes; saved reflection text is not automatically rewritten. Re-read your wording after a correction.

4. Make the 30/60/90-day handoff

The day-30 review covers days 1–30. Day 60 covers 31–60, and day 90 covers 61–90. These are non-overlapping phases, not three different program lengths. Compare your saved weekly decisions within the phase and choose what to keep, adjust or stop in the next one. The underlying 90 dates never move.

A future phase can be viewed and printed as a worksheet. Writing opens when that phase starts. An early review is labelled in progress; do not treat it as an end-of-phase result.

Paper and digital agree when you choose a source

  1. Choose Print saved review / worksheet. The preview includes current counts and saved review text, but excludes daily notes and unsaved review drafts.
  2. Mark ideas on paper. Keep that sheet private if your reflection is personal.
  3. Type the agreed next step back into the same period and save. There is no camera or handwriting import.
  4. If a paper check is corrected, correct the original date, then revisit the review. Export JSON afterward.

Printable records and weekly reviews also exist in other products; this workflow does not claim exclusivity. It is an explicit, local implementation with visible counting rules. Reviewed October 5, 2026; actual printer pagination still needs device verification.