Logos52
wiki / Dimensions / Retrieval / Opportunistic Retrieval

Opportunistic Retrieval

Workflow updated 2026-09-11

Opportunistic Retrieval

Opportunistic retrieval is a workflow for a learner who uses studied material at work every day. Each work task that needs the material makes the learner pull it from memory. Each pull is one real retrieval rep. A heart case on Tuesday makes the learner recall Monday’s notes. A ticket, a client, or an afternoon class does the same in other jobs. The job calendar sets the delay between reps, and the day’s run of tasks sets the mix of topics. The learner spends no extra study time on these reps.

The workflow has three parts. The work day is the practice session. After the day, the learner checks which parts of the material the work did not test. Planned study then covers only those parts. When the job uses the material in the same form it was learned, planned study can drop to none.

Core takeaways

  • Every work task that uses studied material is a retrieval rep, spaced by the job calendar and mixed by the day’s tasks, at no study cost.
  • After work, a short note records which order and which knowledge type each task demanded. The note makes the untested slice visible.
  • An untested slice gets one of three responses: a small planned session, a reshaped next task, or nothing.
  • Planned retrieval can drop to none only when the job uses the material in the form it was learned. A learner still inside a course keeps planned sessions.
  • Before the week, the learner studies the material the next few weeks will force into use, whatever order the course teaches.
  • Holding memory above what the goal needs spends the hours this workflow saves. Planned sessions cover only the slices the work days did not touch.

After the day: write down what the task demanded

When a task at work used studied knowledge, the learner writes a short note about what happened. The use counts as a rep with or without the note. The note is what shows which slice the day missed. The note is written after the task, and it records which order and which knowledge type the task demanded. This kind of note is called a retro-label.

After the day: find what the task did not test

The note answers two questions.

The first question is about order. Did the task need higher-order use, such as building a strategy, evaluating a plan, or synthesising a whole picture? Or did it need lower-order use, such as facts and a known procedure? A day of tasks handled only at recall leaves the higher-order memory untested. The order and type labels come from Higher Order Learning; the definitions live there.

The second question is about type. Was the knowledge used declaratively, by stating or explaining it, or procedurally, by doing something with it? And does that type match the way the knowledge must eventually perform?

Whatever the day did not exercise is the open gap. The learner finds it without writing a test question. A gap means the day did not test that slice. It does not mean the memory of that slice is weak.

After the day: fill the gap, or leave it

A labelled gap has three possible responses. Two fill it. One leaves it.

The first response is a targeted planned session: a small block of deliberate study aimed only at the slice the work skipped, usually the higher-order layer. Spaced Interleaved Retrieval and the Interleaving Table cover the choice of study method and format.

The second response is to convert the work: reshape the next task so that it demands the missing order. The learner drafts the strategy instead of running someone else’s. The learner critiques the plan they just wrote. The learner looks at the whole case before acting.

The third response is to leave the gap. Time pressure and job duties often make conversion impossible. The task gets done the one way it can, and the next task starts. The work reps still happened at no cost. Only the extra session for the missing slice was lost.

When planned study can drop to none

A learner inside a course still needs scheduled retrieval. Daily professional use changes the job of scheduling: the practice sessions already happened at work, and what remains is a check of what those sessions missed.

Planned retrieval can fall to none under one condition, called close transfer: the job uses the material in the same form it was learned. Far transfer still costs practice, so the drop to none holds only under close transfer. A learner still inside a course still needs planned Spaced Interleaved Retrieval. Nothing in this workflow permits dropping those sessions.

Encoding and Retrieval sets how many reps the knowledge needs at all. That count can fall. It reaches none only when transfer is close.

Before the week: study what the work is about to test

The learner does not choose the tasks at work. The weekend before is still the learner’s to plan. Study order follows the retrieval chances coming up at work, not the order of the course. The first question is a forecast: what will the next few weeks force the learner to recall, and which knowledge type will those tasks demand? That material is studied first, even when the course teaches another topic first. A learner on a cardiology ward studies heart material now. A learner with a ticket queue coming up studies that material before an elective still months out. Daily cases then supply more reps than any schedule could.

Before the week: add a task that tests the missing level

When routine tasks use only one level, the learner adds an activity to the workweek that tests another level: a review, a write-up, or a design critique. Teaching a junior is the same addition at the higher order. The teacher has to structure the whole topic, answer live questions, and move between the big picture and the details. The team gets something useful besides the learner’s study hour. WPW is the structured form of that teaching. It is optional.

Know when to stop

Holding memory well above what the goal needs spends the hours this workflow is meant to save. A low-stakes topic (one isolated problem, one client talk, a pass-only elective) has a fixed bar: the questions can be answered, leakage is modest, and some retention depth is there. Ordinary daily use on its own may already clear that bar.

Knowledge that will have to become real expertise later still earns a long-horizon hold and depth now, even when today’s assessment asks almost nothing of it.

The habit of labelling each task is the cost of this workflow. Two signs say the learner has gone too far: converting every task, or topping up slices that were only untested. A working week leaves planned sessions only on the slices the days did not touch.

How to practice this

  1. After a task at work that used studied material, write a short note. Record which order the task demanded, higher or lower, and which type, declarative or procedural. Notice which slices of the material appear in no note for the day.
  2. Compare the day’s notes against the way the knowledge must eventually perform. Notice whether the day stayed at recall while the goal needs strategy, evaluation, or a whole picture.
  3. For a slice the day did not test, pick one of three responses. Run a small planned session on it, reshape the next task to demand the missing order, or do nothing. Notice that the day’s reps still count when time pressure forces the third choice.
  4. Before the week, list the material the next few weeks will force you to recall. Note which knowledge type those tasks will demand, and study that material first, whatever the course order. Notice how many reps the week’s tasks then supply without a study session.
  5. When routine tasks use only one level, add a review, a write-up, or a design critique. Teaching a junior is the same addition at the higher order. Notice that teaching forces you to structure the whole topic and field live questions.
  6. Check the topic’s stakes before adding any planned session. For a low-stakes topic, notice whether daily use already lets you answer the questions with modest leakage. Stop if you are converting every task or topping up slices that were only untested.
  • Spaced Interleaved Retrieval: the planned system that work replaces when transfer is close. Academic readers still need it.
  • Interleaving Table: the method menu for the targeted top-up. Study formats are listed there.
  • WPW: the structured form of teaching a junior. Optional.
  • Higher Order Learning: the source of the order and type labels used above.
  • Encoding and Retrieval: how many reps the knowledge needs at all. The count can fall, and it reaches none only when transfer is close.

Open questions

  • How far close transfer can substitute for planned practice when the work varies the form just enough to feel like a new problem.

Sources

  • Cepeda, N. J., Pashler, H., Vul, E., Wixted, J. T., & Rohrer, D. (2006). Distributed practice in verbal recall tasks: A review and quantitative synthesis. Psychological Bulletin. Any gap greater than zero already beats massed practice; delayed use at work is already spaced.
  • Fiorella, L., & Mayer, R. E. (2013). The relative benefits of learning by teaching and teaching expectancy. Contemporary Educational Psychology, 38(4), 281–288.
  • Fiorella, L., & Mayer, R. E. (2014). Role of expectations and explanations in learning by teaching. Contemporary Educational Psychology, 39(2), 75–85. Teaching a junior is a retrieval event.
  • Pan, S. C., & Rickard, T. C. (2018). Transfer of test-enhanced learning: Meta-analytic review and synthesis. Psychological Bulletin. Far transfer is not free; close transfer is the condition under which planned retrieval can fall to none.