How Revision Works | Revision Maintenance Dose — How Much Practice Does a Graduated Topic Still Need?

A topic is ready to leave the active queue.

That does not mean it should disappear forever.

Revision maintenance dose is the minimum lower-frequency practice needed to keep a previously stable capability accessible, accurate and ready to re-enter intensive revision if evidence of decay appears.

This is the third pillar in the second Revision quartet beneath How Revision Works. The existing Revision Stopping Rules decide when a topic can graduate from active repair. This page owns what happens after graduation.

Quick Read

Stable topics should consume less revision time than weak ones, but zero contact can allow slow decay to go unnoticed. Maintenance solves this by replacing intensive practice with sparse, discriminating checks. Easy, durable knowledge can be sampled rarely. High-value, interference-prone or exam-critical knowledge deserves more frequent maintenance. The goal is not to keep every topic permanently active. It is to preserve enough contact that decay is detected before it becomes a major rebuild.

Maintenance Begins After Graduation

Active queue:

repair, relearn, retest.

Maintenance queue:

sample, verify, extend interval if stable.

The Maintenance Dose Depends on Decay Risk

• frequently used knowledge → lower maintenance need;
• rarely used knowledge → higher maintenance need;
• high-interference topics → more checks;
• exam-critical prerequisites → more checks;
• stable automatic basics → fewer checks.

Maintenance Should Sample the Real Capability

Do not maintain a topic only by rereading.

Use a small receipt:

• one retrieval;
• one changed question;
• one mixed discrimination item;
• one short timed execution where relevant.

A Maintenance Failure Is a Re-Entry Trigger

If the sample reveals slow, inaccurate or cue-dependent performance, the topic returns to the active queue.

This prevents maintenance from becoming ceremonial checking.

Intervals Can Expand With Stability

Stable at one week.

Check later.

Stable again.

Extend further.

Maintenance frequency should respond to evidence rather than a permanent fixed calendar.

A Practical Maintenance Packet

TOPIC: Simultaneous equations
STATUS: Graduated from active queue
LAST STRONG RECEIPT: 1 Sep
MAINTENANCE CHECK: 8 Sep — 2 mixed items
IF BOTH CORRECT + method selected quickly:
next check 22 Sep
IF ERROR / slow cue dependence:
return to active revision

Final Thought: Stable Knowledge Needs Less Attention, Not No Attention

Good revision frees time by letting strong topics become quiet—but not invisible. Maintenance keeps a small light on them so decay can be caught before the road disappears.