A habit tracker example should define the recurring action, preserve each scheduled opportunity, and make uncertainty visible before calculating a streak. The useful question is what the dated records confirm, not whether a run of marks proves a habit is mastered.
This original H1 example uses fictional writing logs for October 5–11, 2026. Its native spreadsheet or printable calendar is the maintained record. The local HTML example illustrates the fictional log; it does not provide persistent personal tracking, and its behavior needs checking in the intended host.
Define the action and the schedule separately
CSU Writes' tracker includes habit descriptions, dated tracking, scheduled-day distinctions and total/goal fields. Adopt that structural purpose without copying its artwork, example counts or claims about mastery and success. Its blank-as-missed convention is not used in this new model. CSU Writes: Habit Tracker
H1's original criterion is Write an outline for at least ten minutes on scheduled weekdays. Plan version 1 schedules Monday through Friday. The review window is October 5 through October 11, with a fixed as-of date of October 11 in the writer's local calendar.
Record the criterion, habit ID, schedule version and effective dates together. A timestamp or minutes field does not establish outline quality. Done means the user confirms the defined action was performed; the elapsed-time note supports that self-report rather than approving it automatically.
Keep personal reasons and reflection in separate fields. The fictional packet does not supply an actual writer's name, private document, health outcome or productivity improvement.
Use four distinct day states
| Original date | Weekday | Plan v1 | Fictional record | Minutes note |
|---|---|---|---|---|
| 2026-10-05 | Monday | Scheduled | Done | 10 |
| 2026-10-06 | Tuesday | Scheduled | Done | 12 |
| 2026-10-07 | Wednesday | Scheduled | Not Done, explicitly recorded | 0 |
| 2026-10-08 | Thursday | Scheduled | Unrecorded | Blank |
| 2026-10-09 | Friday | Scheduled | Done | 15 |
| 2026-10-10 | Saturday | Not scheduled | Not Scheduled | Blank |
| 2026-10-11 | Sunday | Not scheduled | Not Scheduled | Blank |
Done, Not Done, Unrecorded and Not Scheduled answer different questions. Wednesday explicitly records noncompletion. Thursday does not establish either completion or failure. The weekend cells are outside this version's planned opportunities.
For this calendar, Monday is October 5 and Sunday is October 11. Store dates as validated local-calendar keys such as H1/2026-10-05, not as positions in a grid or UTC midnight instants that can display as a different local day.
A row edit updates that habit/date key. Repeatedly selecting Done cannot add another completed day for the same opportunity.
Report three confirmed completions out of five opportunities
There are five scheduled opportunities: Monday through Friday. Three are confirmed Done, one explicitly Not Done, and one Unrecorded. Display all three counts alongside the denominator.
3/5 describes confirmed completions among planned opportunities. It does not mean all five outcomes were observed or that Thursday was a failure. Do not hide the missing record by dropping it from the schedule or converting it into Not Done.
The ten-minute criterion and recorded 10/12/15 minutes do not measure the outlines' quality. A longer note is not a higher-quality output or automatic evidence of improved writing.
If an entry contradicts its stated criterion, flag it for review rather than silently approving or rewriting it. The four example states are internally consistent, but a real record still depends on the user's supplied confirmation.
Define the confirmed streak's endpoint
Count consecutive confirmed Done opportunities in schedule order, skipping days that were not scheduled. A recorded Not Done ends a run. An Unrecorded opportunity prevents an assertion of confirmed continuity without becoming an explicit failed day.
Monday and Tuesday form a fully confirmed run of two. Wednesday ends it. Thursday is unknown; Friday is Done. The longest fully confirmed run in this window is two.
The latest confirmed run ending at the last scheduled opportunity, Friday October 9, is one. Saturday and Sunday do not extend it or count as missing opportunities. Label that endpoint instead of displaying a bare current streak beside Sunday's date.
Do not bridge Thursday's unknown entry to earlier completions. The tracker can say no confirmed continuity across Thursday; it cannot say the writer failed Thursday or that the habit was lost.
If Thursday is later filled with a real confirmed record, recompute from the records. Do not increment a separate streak counter based only on the latest button click.
Keep extra writing outside the planned counts
An optional Saturday writing note may record an extra action. It does not change Saturday into a plan-v1 opportunity, increase the five-day denominator, add a scheduled completion or extend the weekday streak.
Show it in an Extra activity note area. If the writer wants Saturdays scheduled in the future, that is a prospective plan decision with an effective date, not a reinterpretation of the prior week.
An unscheduled Done entry should be held for review as an extra note or schedule issue, not automatically accepted into the scheduled ledger. A future-dated completion beyond the fixed as-of date is likewise held rather than counted.
Change next week's plan without rewriting this week
Plan version 2 schedules Monday, Wednesday and Friday, effective October 12, 2026. It is prospective relative to the October 11 review. It does not remove version 1's Wednesday opportunity or its explicit Not Done record.
Keep the version history: v1 applies to the October 5–11 window; v2 takes effect October 12. When a date is evaluated, use the plan effective on that date. Do not apply the newest three-day schedule retroactively to make an earlier five-day week look different.
Leave next week's actual logs blank. A prospective schedule creates opportunities, not completed actions. The prepared example cannot know whether the writer will perform them.
Maintain the native review record
Keep the habit definition, schedule/effective-date table, dated entries, extra notes and reflection together in the spreadsheet or printable calendar. The review should show the three/five count, explicit unknown and both confirmed-run figures beside their definitions.
The local HTML example uses date/status controls tied to stable keys. Every edit recomputes the view and clears old feedback. Reset Demo restores only this fictional fixture after an explicit confirmation; cancel keeps the current demo edits. It must not reset personal logs or imply a saved record exists.
There is no reminder, automatic tracking, mastery score or health claim. Actual controls, print readability, keyboard access, narrow layout and hosted state need tests.
Copy this prompt to prepare the native example
Prepare a complete original US-English recurring writing-habit spreadsheet/printable calendar, definition/version ledger, and manual review matrix. Reference https://csuwrites.colostate.edu/wp-content/uploads/sites/10/2025/09/CSU-Writes-Habit-Tracker.pdf for explicit action, dated record, and scheduled-goal structure only. No copied artwork/example counts, blank-as-failure convention, health/mastery/success promise, real personal logs, network/storage, or reminders.
Fictional H1: write an outline for at least 10 minutes on scheduled weekdays. Window: 2026-10-05 through 2026-10-11; fixed local-calendar as-of date: October 11. Plan v1 schedules Monday–Friday, five opportunities. October 5 Monday: Done, 10 minutes; October 6 Tuesday: Done, 12; October 7 Wednesday: explicit Not Done, 0; October 8 Thursday: Unrecorded, blank minutes; October 9 Friday: Done, 15; October 10 Saturday and October 11 Sunday: Not Scheduled. Done is user-confirmed criterion completion, not automatic duration/quality approval. Preserve statuses/notes and local date keys, not grid positions or UTC-midnight day shifts.
Show three confirmed Done out of five scheduled, one explicit Not Done, and one Unrecorded. Do not claim all five outcomes observed or turn blank into failure. Longest fully confirmed scheduled-opportunity run: two, Monday/Tuesday. Latest confirmed run ending at the last scheduled Friday, October 9: one. Unrecorded prevents a confirmed-continuity assertion without becoming Not Done; unscheduled weekends are excluded. Recompute from dated records; never increment from repeated status clicks.
Optional Saturday extra writing note stays outside scheduled counts/streak. Never change v1 automatically. Hold unscheduled Done or completion beyond the fixed as-of date for review, without counting it. Flag contradictory criterion entries rather than automatically approving or rewriting them. No outline quality/mastery inference from time.
Plan v2 schedules Monday/Wednesday/Friday, effective 2026-10-12 and prospective relative to this review. Preserve v1's five prior opportunities, including Wednesday Not Done. Use the plan effective on each date, not the newest plan across history. Future logs remain blank; a schedule is not completion. Retain definitions, versions/effective dates, entries, extra notes, and reflection in the native source.
Optional later HTML date/status controls use H1/local-date keys; edits recompute and clear stale feedback. Reset Demo requires explicit confirmation to restore only this fictional fixture; Cancel preserves demo edits. No personal-log reset or saved-record promise. Native calendar/print packet first; controls are not built yet. Test calendar weekdays, counts/runs, unknown versus failure, extra/future guards, repeated status selection, prospective plan history, and reset confirmation/cancel. Actual print, keyboard, article width/360 px and hosted behavior require later checks. No implemented, printed, or captured artifact claim.
End with a separate optional NOS reading-copy area: prepared HTML can be saved/rendered while the native definition/calendar stays authoritative. Actual logging, persistence, and controls require evidence. No export, saved personal records, automatic updates, reminders, or mastery records.
Optional NOS use: a reading copy of the weekly review
Keep the native definition, schedule versions and calendar entries as the maintained record. A prepared HTML reading copy in NOS can present the fictional week's four states and the confirmed-run definitions; NOS supports HTML saving and rendering.
Verify actual logging controls, state behavior and layout before presenting a working example. The reading copy does not supply missing Thursday evidence or promise persistent personal tracking.
Explore NOS with the weekly review. The useful record preserves what was planned, what was confirmed and what the writer has not yet recorded.