How to Plan Properly | Stop Adding Work and Decide What to Drop

Most study plans grow in only one direction.

A weak topic appears.

Add a worksheet.

A mock goes badly.

Add another paper.

A teacher recommends retrieval.

Add flashcards.

A friend is doing more timed practice.

Add timed practice.

A new resource appears online.

Add that too.

Eventually the plan contains every good idea anyone has ever had.

It also contains more work than the learner can actually execute.

At that point the problem is no longer a lack of effort.

The problem is that the plan has no subtraction mechanism.

A plan becomes intelligent when it knows not only what to add, but what must leave.

The 50-Second Read

Time, attention and recovery are finite.

Therefore every meaningful addition to an examination plan should force a trade-off.

When a new task enters, ask:

What problem does this task solve?
How important is that problem?
What evidence says this is the right operation?
What will this task displace?
What is the cost if we do not do it?
What is the cost if we keep doing the task it replaces?

Good drop candidates include:

duplicate resources;
repeated easy practice after the evidence gate has passed;
note rewriting that no longer improves retrieval;
full papers added faster than they can be corrected;
low-value chapter completion;
obsolete tasks from an old diagnosis;
maintenance that has grown larger than necessary;
work carried forward simply because it was once written down.

The central rule is:

No substantial new task enters an already-full plan without another task leaving, shrinking or moving.

This article continues the How to Plan Properly series. Start at the Examination and Work Backwards sets the destination. The Plan Is Not the Schedule separates decision architecture from calendar placement. Turn the Syllabus Into a Performance Map maps current capability. Build a Plan That Survives Real Life protects capacity and buffer. Plan by Marks, Not by Chapters compares opportunities by examination consequence. Find the Critical Path Through What You Need to Learn maps dependency. Plan Around the First Weak Link reorganises work around diagnosis. Know When the Plan Must Change controls replanning. Build Checkpoints Before Problems Become Crises supplies early warning. This page adds subtraction: how to remove work when the system is full.

What This Page Owns

This page owns planned subtraction.

How Prioritisation Works owns the broader question of what deserves scarce attention.

How Work in Progress Works owns the cost of too many active tasks.

How Capacity Planning Works owns the limits of usable capacity.

This page asks a narrower planning question:

When the plan contains more worthwhile work than the learner can carry, what should be removed, reduced, postponed or parked?

That decision is difficult because almost everything on a study plan can be defended as useful.

The challenge is not finding useless work.

It is choosing among useful things.

Aisha Has a Good-Task Problem

Aisha’s week contains only sensible activities.

English timed writing;
Science retrieval;
Mathematics weak-link repair;
History essay planning;
two full papers;
flashcards;
teacher corrections;
vocabulary;
school homework;
one extra worksheet recommended by a friend.

Nothing is obviously ridiculous.

The total is ridiculous.

Her usable evening capacity is about fourteen focused hours across the week.

The plan quietly demands nineteen.

Aisha cannot solve this with motivation.

Someone must decide which good tasks lose.

When capacity is finite, saying yes to one useful task means saying no to another.

The Conservation of Capacity

A new task does not create a new hour.

This sounds obvious.

Study plans violate it constantly.

Monday already contains three hours of work.

A mock reveals a new weakness.

The planner adds forty-five minutes of repair.

Nothing is removed.

Where did the forty-five minutes come from?

Usually from one of four invisible places:

sleep;
buffer;
family or recovery time;
tomorrow.

A proper plan names the source.

If nothing leaves, the plan is not reallocating.

It is borrowing.

Every Addition Needs a Funding Source

Treat time the way a careful budget treats money.

If you add an hour of Science, identify the source:

one hour removed from lower-value Mathematics repetition;
thirty minutes from buffer plus thirty minutes from a completed weak-link priority;
one optional English task deferred;
one full paper replaced by targeted repair.

“I will fit it in” is not a funding source.

“I will sleep later” is usually a loan with interest.

“I will do both tomorrow” is backlog creation.

The Add–Drop Rule

For a plan already near capacity, use this rule:

If a substantial task enters, name the task that leaves, shrinks or moves.

Example:

New evidence: Science causal explanations are losing six marks repeatedly.
Add: two targeted explanation sessions.
Drop: one generic Science chapter review and one optional full-paper attempt.
Keep: short Science retrieval maintenance.

The total workload stays realistic while the plan becomes more intelligent.

The Drop List

Most students keep a to-do list.

Keep a drop list too.

Before the week begins, identify work that should leave first if capacity tightens.

duplicate practice;
low-value note rewriting;
already-secure easy questions;
optional enrichment unrelated to the current examination goal;
another full paper when correction backlog exists;
resource switching;
old tasks from a previous diagnosis;
maintenance above the amount needed to preserve stability.

A drop list protects the learner from making every subtraction decision while already tired.

Dropping Is Not Failure

Students often experience deletion as failure.

“I planned it, therefore I should complete it.”

That is not planning.

That is loyalty to an old decision.

The question is whether the task remains one of the best uses of scarce time now.

If not, deletion can be evidence of better planning.

Do not complete obsolete work merely to prove the old planner was right.

The Sunk-Cost Test

Before keeping a task, ask:

If this task were not already on my list, would I add it today?

If the answer is no, sunk cost may be protecting it.

Examples:

A workbook chapter is half finished but no longer targets the active weakness.
A set of notes is almost complete but retrieval is already strong.
Three full papers were scheduled before a weak link was discovered.
A flashcard deck contains hundreds of low-priority details.

The time already spent is gone.

Protect the next hour.

The Opportunity-Cost Test

Every task competes with an alternative.

Ask:

What is the best thing I cannot do if I keep this task?

A two-hour full paper may cost:

one weak-link repair;
one delayed retrieval cycle;
one essay feedback session;
one hour of sleep;
one later-subject maintenance block.

The paper may still be the better choice.

But the choice should see its price.

The Replacement Test

A task deserves its place only if it beats the best available replacement.

For each large task, ask:

What outcome is this supposed to create?
Is there a cheaper task that creates similar evidence or learning?
Is another task more urgent, more upstream or more recoverable?
Would shrinking the task preserve most of the value?

Sometimes the best subtraction is not deletion.

It is compression.

Delete, Shrink, Delay, Delegate, Merge

Subtraction has several forms.

Delete

The task no longer deserves capacity.

Shrink

Keep the function with less volume.

Example: one timed section instead of a full paper.

Delay

The task is useful but not now.

Delegate

Some administrative work can be supported by a parent, teacher or tutor while the learner protects high-value cognitive work.

Merge

One task can sometimes serve two functions.

A school essay can become the week’s timed writing checkpoint instead of adding a separate full essay.

A tuition diagnostic can replace a duplicate home assessment.

A mixed retrieval set can maintain several topics at once.

Subtraction Should Protect Functions

Do not cut tasks randomly.

Protect the functions the plan needs.

Repair: change a known weakness.
Retrieval: keep knowledge accessible.
Transfer: make performance survive new surfaces.
Timing: test performance under constraint.
Correction: convert mistakes into learning.
Maintenance: keep strong areas from decaying.
Recovery: protect future capacity.
Checkpoint: detect whether the plan still works.

A task can disappear while its function remains.

Example:

Drop a second full paper but keep a timed section so timing is still tested.

Drop a full chapter reread but keep a ten-minute retrieval check so maintenance survives.

Subtraction should remove excess volume before essential function.

Do Not Cut Recovery First

The easiest thing to delete from a crowded plan is often sleep.

It has no chapter name.

It produces no worksheet.

It does not look like exam preparation.

But cutting recovery can reduce the quality of every later task.

Before borrowing from sleep, cut:

duplicate work;
low-return easy practice;
decorative note-making;
optional resource exploration;
excess maintenance;
nonessential full-paper volume.

A robust plan treats recovery as part of the system rather than the space left after studying.

Do Not Cut Correction First

Another common mistake is to keep practice and delete correction.

This creates completed work without closed learning loops.

If a full paper cannot be marked, diagnosed and acted on, consider dropping the paper before dropping the correction.

Do not preserve measurement by deleting the learning it was meant to produce.

Do Not Cut Every Return

Spaced returns are small and therefore easy to remove.

But deleting all returns can turn strong material into future repair work.

Shrink rather than erase.

Ten minutes may be enough to protect an important retrieval chain.

See How Spaced Practice Works for the wider mechanism.

Do Not Cut the Sensor

When time is tight, students often delete every checkpoint and simply work harder.

That can make the plan blind.

Keep at least small representative sensors alive:

one fresh mixed set;
one delayed retrieval check;
one timed section;
one weekly review.

The checkpoint article Build Checkpoints Before Problems Become Crises explains this sensing architecture in depth.

The Four-Tier Drop Order

A practical drop order is:

Tier 1 — Remove waste

duplicate resources;
repeated low-difficulty work after mastery evidence;
planner decoration;
unnecessary note recopying;
tasks nobody can explain the purpose of.

Tier 2 — Reduce excess volume

three full papers become one full paper plus one section;
twenty maintenance questions become six mixed questions;
two full essays become one essay plus two plans.

Tier 3 — Delay useful but noncritical work

advanced extension;
low-frequency detail;
optional enrichment;
new resource exploration.

Tier 4 — Make strategic trade-offs

When capacity is genuinely insufficient, choose between important tasks using:

exam date;
mark exposure;
dependency;
repairability;
current evidence;
maintenance cost;
opportunity cost.

This final tier is difficult because something valuable will lose.

That is what scarcity means.

Ben’s Full-Paper Problem

Ben schedules four Mathematics papers in one week.

After the first paper, he has ninety minutes of correction and a clear algebra weak link.

The old plan says another full paper tomorrow.

Should he keep it?

Ask what the next paper would add.

If it mainly measures the same error again, its marginal information value is low.

Drop the second paper.

Replace it with:

algebra repair;
fresh local retest;
short downstream mixed set.

Keep one later full paper as an integration checkpoint.

Ben now does fewer papers and more useful preparation.

Aisha’s Note-Rewriting Problem

Aisha has beautiful notes.

Her plan contains three more note-rewriting sessions because unfinished pages remain.

A closed-book checkpoint shows she can retrieve the material well.

The unfinished notes are no longer a learning priority.

Drop them.

Use the recovered time for the actual weak link: keeping written responses relevant under time.

Aisha’s incomplete notebook can coexist with improved examination readiness.

Mira’s Resource Problem

Mira has one textbook, two revision guides, teacher notes, a video playlist and several downloaded worksheets.

Each resource is individually good.

Together they create navigation cost.

She spends fifteen minutes deciding where to study before each Science block.

The plan should subtract resources.

Choose one primary explanation source, one practice source and official materials where relevant.

Park the rest unless a named weak link requires them.

Resource abundance can create decision scarcity.

Ryan’s Carry-Forward Problem

Ryan misses one History task on Tuesday.

He moves it to Wednesday.

Wednesday already has work.

He misses another task.

Both move to Thursday.

By Friday, the plan contains a pile of inherited intentions.

Use the carry-forward rule:

No missed task moves forward automatically. It must compete again with current priorities.

Some tasks should die at the day they were missed.

That prevents backlog from becoming destiny.

Clara’s Maintenance Problem

Clara once struggled with functions.

She now performs strongly across mixed and timed questions.

But her schedule still gives functions two long sessions each week.

The old weakness remains expensive because the plan never released it.

Shrink functions to maintenance.

Use one small mixed return.

Move the recovered capacity to the current bottleneck.

Success should remove work.

Ethan’s Sophistication Problem

Ethan likes difficult problems.

His plan contains many challenging extension questions.

His recent papers show something else matters more: he loses routine marks near the end because he stays too long with high-complexity questions.

Extension work is not bad.

Its timing is bad.

Move some extension work to the wait list until whole-paper control stabilises.

The plan is not lowering Ethan’s ceiling.

It is protecting the floor he should already own.

The Wait List

Some tasks do not deserve deletion.

They deserve waiting.

Use a wait list for:

advanced extension;
lower-priority weak topics;
new resources;
another full paper;
extra writing practice;
deep note reconstruction;
secondary bottlenecks that should activate only after the first one moves.

Waiting prevents everything useful from becoming active at once.

This connects to How Work in Progress Works.

Active, Maintenance, Waiting, Dropped

Four states are enough for many plans.

Active: deserves substantial current attention.
Maintenance: strong enough to keep alive cheaply.
Waiting: useful later but not current.
Dropped: no longer deserves capacity in this runway.

The most overloaded students often have only one state: active.

Everything is live.

That is not urgency.

It is a failure to classify.

The Must-Protect List

Subtraction is easier when the plan also knows what should survive.

current high-leverage weak link;
important retrieval returns;
correction of representative practice;
one sensor for important unknowns;
minimum maintenance for later subjects;
sleep and recovery;
fixed examination obligations.

When capacity tightens, cut around the protected functions rather than slicing everything equally.

Do Not Cut Every Subject Equally

If the week loses twenty per cent of capacity, reducing every subject by twenty per cent may feel fair.

It may be strategically poor.

One subject may have a critical weak-link repair.

Another may already be stable and need only maintenance.

A third may have a paper tomorrow.

A fourth may contain deep low-repairability work that can wait.

Subtraction should follow value, not symmetry.

Do Not Cut Every Task Equally

The same applies within a subject.

Suppose Mathematics contains:

algebra weak-link repair;
statistics maintenance;
one timed mixed section;
optional extension;
note rewriting.

If time shrinks, do not shorten every item by ten minutes.

Drop note rewriting first.

Drop or park extension.

Shrink maintenance.

Protect the active weak-link repair and one representative timed sensor.

The Minimum Viable Version

A task can often be shrunk while preserving its core function.

Full task	Minimum viable version
Two-hour full paper	One timed high-value section
Full essay	Unseen prompt + plan + one timed paragraph
Twenty-question maintenance set	Six mixed representative questions
Full chapter reread	Closed-book retrieval + targeted reread only where retrieval fails
One-hour error review	Top three recurring error signatures + one fresh retest each

Minimum viable does not mean permanently adequate.

It means enough function survives when capacity is constrained.

The Marginal-Return Test

The first hour on a task and the fifth hour on the same task do not necessarily have equal value.

Ask:

What will the next unit of work add that the previous unit did not?

If another twenty easy questions mostly confirm what is already known, marginal return is low.

If the first mixed set reveals an untested selection problem, marginal return is high.

Subtraction should attack low marginal return.

The Evidence-Gate Test

Many tasks stay on plans because nobody defined when they would end.

Use evidence gates.

Example:

Continue blocked practice until eight of ten fresh examples are correct without cueing; then move to mixed selection.

Once the gate is passed, the old volume should shrink.

A gate is therefore also a subtraction rule.

The Stop Rule

Every large task should have a stop condition.

Stop easy practice when the relevant performance is stable.
Stop one difficult question after the planned time threshold and return later.
Stop adding full papers when correction debt grows.
Stop note-making when notes no longer improve retrieval or application.
Stop active repair when the weak link passes its local, transfer and delayed gates.
Stop resource searching when one adequate source already does the job.

A plan without stopping rules expands until capacity fails.

The “Why Is This Still Here?” Review

Once a week, look at every substantial task and ask:

Why is this still here?

Acceptable answers:

it is repairing the current bottleneck;
it is a required checkpoint;
it maintains a valuable strong area;
it is a fixed school obligation;
it supports a dependency that becomes important soon.

Weak answers:

because it was already written down;
because everyone else is doing it;
because there are still pages left;
because I bought the book;
because more feels safer.

The 90-Day Subtraction Strategy

With three months remaining, do not subtract too aggressively.

There is time for deep learning and broad development.

But still remove duplication.

Choose primary resources.
Limit simultaneous weak-link projects.
Move stable areas to maintenance.
Use checkpoints before scaling volume.
Delete tasks whose learning job is already being done elsewhere.

Early subtraction is mainly about clarity.

The 30-Day Subtraction Strategy

Thirty days requires stronger trade-offs.

Stop treating every chapter equally.
Remove duplicate practice after gates pass.
Prioritise high-fan-out weak links.
Protect correction and retrieval.
Move strong subjects to maintenance floors.
Keep only enough full-paper volume to answer meaningful integrated questions.

The plan should become narrower and more representative.

The 14-Day Subtraction Strategy

Two weeks out, every large task should justify its place.

Drop or park:

low-frequency perfectionism;
deep low-repairability projects with weak exam return;
new resource systems;
excess note rewriting;
full papers that cannot be corrected properly;
easy practice after stability is proven.

Protect:

high-return weak-link repair;
retrieval;
transfer;
timing;
maintenance;
sleep.

The 7-Day Subtraction Strategy

One week out, the plan should become simple.

Every active task should answer one of four questions:

Does it recover important marks?
Does it protect important marks already earned?
Does it test an expensive unknown?
Does it protect the learner’s ability to perform?

If not, the task probably belongs on the wait or drop list.

The Final 24 Hours

The final day is where subtraction becomes most important.

There are always more things that could be studied.

Do not try to finish the entire unfinished plan.

Drop:

new deep topics with poor short-term return;
unfamiliar resources;
late-night volume;
low-priority unfinished notes;
old backlog.

Keep:

light retrieval;
known error cues;
logistics;
normal meals;
sleep.

The final day should protect performance, not rescue every abandoned ambition.

Subtraction in Mathematics

Drop full-volume topic repetition when the real problem is a narrow cross-topic weak link.

Drop easy procedural questions once accuracy is stable.

Shrink a full paper to a timed section when the only uncertainty is pacing in one component.

Keep mixed selection, transfer and correction when those are the active risks.

Do not confuse more questions with more progress.

Subtraction in English

Drop full essays when the learner repeatedly fails before the writing even begins.

If prompt interpretation is the weak link, use more unseen planning and fewer full compositions temporarily.

If editing is strong, stop over-allocating to proofreading exercises.

If vocabulary is already adequate, move it to maintenance rather than expanding lists indefinitely.

The plan should follow the current conversion failure.

Subtraction in Science

Drop repetitive factual rereading when retrieval is already strong.

Keep causal explanation training if that is where marks disappear.

Shrink broad chapter work into targeted retrieval plus fresh transfer.

Drop extra model-answer copying if it does not improve independent reasoning.

The plan should remove the activity that looks scientific but no longer changes Science performance.

Subtraction in Humanities

Drop repeated broad reading when organised retrieval is already strong.

Keep evidence selection, argument structure and timed evaluation if those are the weak links.

Shrink full essays to plans or timed paragraphs when the current uncertainty is narrower.

Use the smallest task that trains the actual performance.

The Multiple-Exam Drop Problem

When several exams approach, each subject can justify more work.

The combined plan becomes impossible unless subtraction happens at the portfolio level.

Subject	Active priority	Maintenance	Drop / shrink
Mathematics	Algebra weak-link + timed section	Statistics mixed return	Extra easy worksheets
Science	Causal explanation	Short retrieval	Generic chapter reread
English	Prompt relevance under time	Vocabulary in context	Second full essay
History	Evidence selection	Theme retrieval	Low-frequency note expansion

The portfolio remains broad while each subject becomes leaner.

The “One In, One Out” Rule Is Sometimes Too Simple

One new thirty-minute task does not necessarily require one old thirty-minute task to disappear.

The new task may be cognitively heavier.

It may also generate correction or follow-up work.

Count the whole load.

A full paper includes attempt, marking, diagnosis, repair and retest.

A new essay method includes learning, practice, feedback and rewriting.

Subtraction should match total workload, not visible block length alone.

The Hidden Work Audit

Some tasks create invisible downstream work.

Full paper → marking + correction + repair.
New resource → setup + navigation + decision cost.
New flashcard deck → creation + repeated reviews.
Extra tuition → travel + homework + integration.
New project → coordination + transitions.

Before adding a task, include its tail.

A plan that counts only visible task duration systematically underestimates load.

The Work-in-Progress Limit

Too many active repairs split attention.

Set a limit.

For example:

No more than two major active weak-link repairs across all subjects at once, plus maintenance and fixed school obligations.

The exact number depends on the learner.

The principle is that every new active project increases coordination cost.

Finish, stabilise or park before activating everything else.

The Stop-Starting Rule

Sometimes subtraction means not starting yet.

A new weak topic appears.

Do not automatically activate it.

Ask:

Is it more important than the current active weak link?
Does it have higher mark exposure?
Is the current repair near completion?
Can this new issue wait safely?
Would opening it now increase WIP beyond capacity?

Not starting is one of the cleanest forms of subtraction.

The Weekly Subtraction Review

Once a week, ask:

What was added this week?
What left?
Which tasks have passed their evidence gates?
Which active repairs are no longer active?
Which maintenance tasks are larger than necessary?
Which missed tasks still deserve to exist?
Which resources are duplicated?
Where is correction backlog forming?
Did sleep or buffer pay for hidden overloading?
What one thing can be removed next week?

A subtraction review should make the plan lighter.

If every weekly review only adds work, the review is incomplete.

The Daily Subtraction Question

At the end of the day, ask one question:

What should not come with me into tomorrow?

Sometimes the answer is an unfinished low-value task.

Sometimes it is a completed weak link that now belongs in maintenance.

Sometimes it is guilt about work that no longer matters.

The Subtraction Ladder

When overloaded, reduce in this order:

remove obvious waste;
remove duplication;
stop work after evidence gates are passed;
shrink maintenance to minimum effective dose;
replace large tests with smaller representative tests where appropriate;
park low-priority work;
drop low-return recoveries;
only then make hard trade-offs among high-value work.

This sequence protects important learning before cutting it.

Common Failure 1: Every New Problem Adds Work

The plan expands without reallocating capacity.

Repair: require a funding source for every substantial addition.

Common Failure 2: Nothing Is Ever Deleted

Old tasks survive long after their rationale disappears.

Repair: ask weekly why each large task is still present.

Common Failure 3: Missed Work Automatically Rolls Forward

Backlog compounds.

Repair: make every carried task compete again with current priorities.

Common Failure 4: Sleep Funds Every Addition

The plan appears to fit only because recovery is sacrificed.

Repair: remove low-value work before borrowing from sleep.

Common Failure 5: Correction Is Dropped Before Practice

The plan measures errors without converting them into learning.

Repair: reduce practice volume when correction capacity is insufficient.

Common Failure 6: Maintenance Never Shrinks

Previously weak areas continue consuming active-level time.

Repair: move passed weak links to minimum effective maintenance.

Common Failure 7: New Resources Are Always Added

Every recommendation creates a new workflow.

Repair: new resources must replace or outperform an existing source for a named job.

Common Failure 8: Full Papers Become a Symbol of Seriousness

The student keeps adding papers despite clear unresolved weak links.

Repair: use full papers when the planning question is integrated performance; otherwise use smaller instruments.

Common Failure 9: Cutting Everything Equally

High-value and low-value tasks are reduced by the same amount.

Repair: protect function and priority, not symmetry.

Common Failure 10: No Wait List

Every useful idea becomes active immediately.

Repair: distinguish waiting from active work.

Common Failure 11: No Work-in-Progress Limit

Too many simultaneous repairs fragment attention.

Repair: cap major active projects.

Common Failure 12: Dropping the Sensor

All checkpoints disappear when time is tight.

Repair: preserve small representative tests.

Common Failure 13: Dropping Retrieval Returns

Old knowledge decays while new work expands.

Repair: shrink returns before deleting them entirely.

Common Failure 14: Keeping Low-Marginal-Return Work

The fifth hour on a stable topic beats the first hour on an important unresolved weak link.

Repair: compare the next unit of value, not the historical importance of the topic.

Common Failure 15: Deleting High-Value Work Because It Is Hard

Subtraction becomes avoidance.

Repair: drop according to value, not discomfort.

Common Failure 16: Keeping Easy Work Because It Feels Productive

Familiar work survives because success feels good.

Repair: require evidence that the task still changes performance.

Common Failure 17: Not Counting Hidden Work

Attempt time is counted, correction and setup are not.

Repair: budget the full workload tail before adding.

Common Failure 18: Subtraction Happens Only After Collapse

The plan waits until exhaustion or backlog forces deletion.

Repair: include weekly subtraction before crisis.

The One-Page Subtraction Template

Field	Question
Task	What are we currently doing?
Job	What performance or uncertainty does it address?
Evidence	What says this job still matters?
Marginal return	What will the next block add?
Opportunity cost	What better task cannot happen if this remains?
State	Active, maintenance, waiting or drop?
Minimum version	Can the function survive with less volume?
Stop rule	What evidence lets this task end?

The One-Sentence Subtraction Rule

This task exists to do this job; current evidence says its next block has this value, while the best alternative is this; therefore I will keep, shrink, delay or drop it and protect this function elsewhere if necessary.

That sentence turns deletion into a reasoned planning decision.

The Five-Minute Subtraction Audit

Circle the three highest-value tasks.
Mark every task whose purpose you cannot explain.
Mark duplicate resources or repetitions.
Identify one task whose gate has already passed.
Identify one maintenance block that can shrink.
Identify one task that should move to the wait list.
Protect sleep and one checkpoint.

The plan should now be lighter without becoming blind.

The Fifteen-Minute Weekly Subtraction Audit

What was added since last week?
What was removed?
Which active weak link passed its gate?
What should move to maintenance?
What is currently waiting?
Which task is low marginal return?
Which task is duplicated?
Which task is creating hidden correction debt?
Which missed task can die rather than roll forward?
Does the revised total fit real capacity?

Then stop managing the plan and return to learning.

What Parents Can Do

Parents often respond to anxiety by adding structure and resources.

Sometimes the better intervention is subtraction.

Which task is creating the most value?
Which task has become redundant?
What can move to maintenance?
What can be postponed?
Is sleep paying for the overloaded plan?
What are we adding that should replace something rather than sit on top?

A child does not need every possible good learning activity at the same time.

What Teachers Can Do

Teachers can help by making task purpose clear.

Is an assignment:

core practice;
diagnostic;
revision;
extension;
optional enrichment?

Clear purpose helps students decide what can shrink when several subjects collide.

What Tutors Can Do

A tutor can create capacity by removing wrong work.

After diagnosing a weak link, say explicitly:

Do this. Stop doing that. Keep this small maintenance return. Bring back this evidence.

High-resolution tutoring should often make the learner’s week smaller, not larger.

What Students Can Do Tonight

Write tomorrow’s planned tasks.
Rank them by actual examination value.
Cross out one duplicate or low-return task.
Shrink one maintenance task.
Move one useful but nonurgent task to a wait list.
Protect one high-value task and one recovery boundary.

Do less work on purpose.

Then do the remaining work better.

Frequently Asked Questions

How do I know what to drop from my study plan?

Start with duplication, low-return repetition, obsolete tasks, excessive maintenance and work whose purpose is unclear. Protect active weak-link repair, important retrieval, correction, representative checkpoints and recovery.

Should I drop a subject if I am overloaded?

Usually the first step is not to abandon a whole subject but to reduce low-value work within it. Move strong areas to maintenance, target the biggest weak link and coordinate decisions with the actual requirements of your examination programme.

Should I finish every revision book I start?

No. A book is a resource, not a contract. Continue only while the next section is one of the better uses of your time. Stop when evidence shows the learning job has been completed or another task has higher value.

Is it bad to leave chapters unfinished?

Not necessarily. Official syllabus coverage matters, but equal completion is not always optimal. A strong plan can use diagnostics, mark exposure and dependencies to decide how much attention each area deserves.

How many past papers are enough?

There is no universal number. Use enough to answer important questions about integration, timing, transfer and current mark loss, while preserving enough time to mark, diagnose, repair and retest.

Should missed work always be rescheduled?

No. Re-evaluate it. If it still outranks current tasks, reschedule it. If not, shrink, delay or drop it. Automatic carry-forward creates backlog.

What should I never drop?

There is no universal list for every learner, but core examination obligations, sleep and basic recovery, important weak-link repair, necessary retrieval, correction of meaningful practice and critical checkpoints usually deserve strong protection.

How do I stop feeling guilty about dropping tasks?

Judge the decision by current value, not by the fact that the task was previously planned. A plan is a tool for reaching a goal, not a promise that every earlier intention must survive.

What if everything feels important?

Use mark exposure, dependency, repairability, exam date, evidence quality and opportunity cost. When everything is labelled important, priority has not yet been resolved.

Should I keep buffer when exams are close?

Yes. Near exams, new evidence and overruns can be expensive. Some reserve lets the plan respond without borrowing from sleep or creating backlog.

The Independence Test

A learner is becoming a stronger planner when they can answer:

What is the highest-value task?
What can safely shrink?
What should wait?
What should disappear?
What function must still be protected?
If something new enters, what leaves?
What evidence tells me this task is finished?

This is the difference between carrying a list and operating a plan.

The Rule to Keep

There will always be more useful work than time.

That is not a temporary problem.

It is the permanent condition of serious preparation.

Do not solve it by pretending the day can expand.

Do not solve it by borrowing endlessly from sleep.

Do not solve it by carrying every missed task forward.

Do not solve it by adding every new idea to the same overloaded week.

Choose.

Protect what matters.

Shrink what can be smaller.

Delay what can wait.

Drop what no longer earns its place.

A plan is not strong because it contains everything. It is strong because everything it contains deserves to be there.

Continue Through the Planning and Examination System

How to Plan Properly | Start at the Examination and Work Backwards — define the destination.
How to Plan Properly | The Plan Is Not the Schedule — decide before scheduling.
How to Plan Properly | Plan by Marks, Not by Chapters — compare work by examination consequence.
How to Plan Properly | Find the Critical Path Through What You Need to Learn — protect work that unlocks important downstream performance.
How to Plan Properly | Plan Around the First Weak Link — make diagnosis change the week.
How to Plan Properly | Know When the Plan Must Change — decide when new evidence justifies a replan.
How to Plan Properly | Build Checkpoints Before Problems Become Crises — detect drift early enough to act.
How Prioritisation Works — the wider architecture of scarce attention.
How Work in Progress Works — understand the cost of too many simultaneous tasks.
How Capacity Planning Works — keep the total workload inside real human capacity.
Examinations & Assessment Hub — the wider examination-performance architecture.

eduKateSG — if the plan is full, the next intelligent move may not be another task. It may be a decision about what no longer belongs.