When you are behind: cognitive load, prioritisation, and recoverable plans

1. Replace global shame with three named wounds

Pick two or three concrete skills or topics whose failure would cost the most on the next assessment. Everything else is temporarily negotiable. This is prioritisation under scarcity — the same logic emergency medicine uses for triage, applied to attention. You are not claiming the other material does not matter; you are admitting finite hours and protecting variance where it hurts most.

2. Executable next steps as extraneous-load reduction

If you cannot start, the unit of work is still too large. “Revise chapter four” loads planning on top of content; “fifteen minutes: list five definitions from memory, then check” reduces extraneous load because the action is bounded. That aligns with how instructional design uses worked examples and segmentation to manage intrinsic load without adding noise (Sweller, 1988). You are effectively segmenting your own session.

3. Honest rescheduling as a memory for the future self

Silent slippage — where the calendar still shows an impossible plan — increases anxiety and steals cycles from retrieval. Moving blocks explicitly is not moral failure; it is updating a model. The goal is a calendar that matches reality enough that practice testing and spaced returns (high-utility techniques per Dunlosky et al., 2013) actually happen instead of living only in intention.

4. Finish lines you can verify in one screen of notes

• → Ten marked questions with a one-line error tag each.
• → One past-paper fragment under time plus a three-line debrief.
• → Twenty self-generated prompts with five answered closed-book.
• → One “teach-back” paragraph on a single mechanism or definition, then compare to source.

What Offload aims to do (without detailing internals)

We are building for the student whose week regularly invalidates a static plan — apprenticeships, clinical hours, care, paid work. The scientific thesis is that high-utility learning strategies only help if the scaffolding around them (what to do next, when to return, how to move blocks when life intervenes) does not consume the same working memory you need for actual retrieval. Offload’s direction is to carry that scaffolding so you can spend cognitive budget on practice testing and spaced returns, not on re-deriving the plan nightly. Specific algorithms and data structures are not the story; the obligation to respect attention economics is.