Rhythm Ledger Template

Copy this ledger into a private note and use one page each week. It is not a streak table or a dashboard for scoring your character. It helps you see what deserves to stay, which condition needs to change, and how to return after an interruption.

Do not write passwords, identity documents, customer data, medical privacy, or unauthorised third-party information. When safety, health, money, or relationship risks are involved, contact a qualified professional or a trusted support person first.

1. One Main Question

Date range:
The one question this week:
Real situation and audience:
Acceptance standard:
Baseline evidence at the start of the week:

The question should be observable, such as “Can I explain a project risk in English without a script and answer a follow-up?” Do not write “be better this week”.

2. Three Capacity Versions

Capacity	When to use it	Minimum action	Evidence that must remain	Stop or downgrade condition
Full day	Time and capacity are relatively stable
Compressed day	Time is short or attention is fragmented
Recovery day	Illness, sleeplessness, grief, or responsibility rises sharply

The three versions serve one direction. A recovery day is not a failure. When safety, sleep, the body, or relationships are clearly affected, protect those limits before completing the plan.

3. Give Repetition an Echo

Date	Action	Recall / variation / output / feedback	What new information appeared?	Which variable changes next time?

If four repetitions produce no new information, change the topic, listener, time limit, number of prompts, or tool permission before simply adding more repetitions.

4. Record One Useful Piece of Feedback

Who or what provided the feedback:
Observation: What did the person actually see, hear, or measure?
Impact: How did it affect understanding, use, or the result?
Next adjustment: Which one important variable will I change?
Evidence location:

When asking AI for feedback, submit your own version first. Ask for no more than three issues that affect the result, and require a distinction between observation, inference, and suggestion. A person decides what to accept.

5. Interruption and Return

What happened, as facts (no character judgment):
Which condition changed: time / capacity / difficulty / environment / responsibility
The smallest return action within 24 hours:
What I will explicitly not make up:
Who I need to contact or which risk needs escalation:

If the same resistance appears three times, change the time box, task size, environment, boundary, or support network. Do not repay an interruption with sleep deprivation or shame.

6. This Week's Decision

One design I will keep:
One demand or entry point I will remove:
One condition I will change next week:
One number I will stop tracking:
Next review date:
First action when I open the file next time:

7. Handover and Evidence Locations

First version:
Revised version:
Feedback or retest:
Next task: owner / date:

Related chapters: Rhythm: Let Small Things Travel Through Time | Daily System: Put Change into the Day | Weekly Review Template