SCHEDULING CONTROL CENTER: 10 DECISIONS + WEEKLY RESET

ALL YEARS | PAGE 77D - CAPACITY -> PRIORITY -> CONTINGENCY -> 10 DECISIONS -> MASTERY GATE

F. 10 HIGH-DISCRIMINATION SCHEDULING DECISIONS

#	Pattern	Best next decision
1	The weekly plan exceeds the hours that remain after mandatory duties and recovery.	Cut scope before cutting sleep; preserve coverage floor, primary practice and top repair targets.
2 3	A mandatory class/clinical/work task removes a planned study block. A strong system still has several hours of broad review scheduled.	Re-rank the queue; move one high-value task and let low-priority passive work drop. Convert it to brief maintenance and redirect deep time to recurring weak domains.
4 5	After a long clinical/school day, concentration is poor. The same error returns after two prior reviews.	Run the minimum viable study day instead of forcing a dedicated-style marathon. Give it a protected high-focus repair window; change the repair method and schedule delayed proof.
6	Two days of the original schedule are now behind.	Discard the outdated calendar and rebuild from current evidence; do not double every remaining day.
7 8	Late-night studying is followed by worse next-day retrieval or timing. Exam is close and a new comprehensive resource looks attractive.	Move the stop time earlier and cut low-output work; protect the next performance cycle. Do not start it unless one precise unresolved gap justifies the switch and there is time to verify transfer.
9	A dual-role learner has work/family duties that vary unpredictably.	Anchor fixed commitments + recovery; use movable repair blocks and a defined minimum viable day.
10	Every hour is scheduled and there is no contingency space.	Create buffer by dropping duplication; robustness is part of the plan, not wasted time.

G. WEEKLY RESET - FIVE BOXES ONLY

Board box	What belongs there
FIXED / PROTECT PRIMARY WORK	Mandatory school/clinical/work/family commitments + recovery floor. One main content/practice lane that owns the week.
REPAIR NOW RE-TEST	Top 1-3 recurring or high-consequence error clusters. Recently repaired rules due for fresh delayed proof.
DEFER / DROP	Low-yield duplication, outdated tasks, broad review no longer justified by evidence.

TOP 10 SCHEDULING-EXECUTION CONCEPT - 10: SCHEDULE QUALITY IS PROVEN BY EXECUTION UNDER DISRUPTION

DEEP EXPLANATION	WHY STUDENTS MISS IT	EASIEST CLUE
A calendar is a capacity hypothesis. It works when the learner preserves the highest-value loops, adapts after	Perfect adherence looks like the goal, so learners overfill the week or treat any deviation as failure.	Ask: when something changes, do I know immediately what stays, what moves and what disappears?
disruption and still reaches assessment with stable retrieval, timing and recovery.

H. FINAL SCHEDULING-EXECUTION MASTERY GATE

Gate	Pass condition
Capacity Coverage floor	My weekly plan fits around actual fixed commitments rather than imaginary free time. Mandatory objectives / rotation goals / blueprint domains remain protected.
Task-energy match Minimum viable day	High-focus windows hold the hardest reasoning, question review and major repair. I have a compressed-day loop that preserves retrieval, fresh application, one repair and spaced continuity.
Delayed proof Contingency	Every major repair has a scheduled fresh retest rather than being marked fixed immediately. I know what to drop or defer when capacity shrinks; missed work does not automatically become schedule debt.
Recovery Weekly reset	The plan protects the sleep/break/recovery pattern required for next-day accuracy and endurance. Current evidence - not the original calendar - determines next week's repair allocation.

H. FINAL SCHEDULING-EXECUTION MASTERY GATE

ACADEMY SOURCE ANCHORS: Page 20A Year 1 cadence; Page 40C weekly review; Page 52C dedicated daily architecture; Page 56A readiness dashboard; Page 74D source governance; Pages 76A-76D adaptive mastery control. 2026/27 schedule-execution expanded edition - use school schedule, attendance requirements and current official assessment guidance as the controlling standards