Prospective Memory¶

Version: v1 · 2026-08-24 · History
Prime #: 1093
Origin domain: Cognitive Science
Subdomain: memory and executive function → Cognitive Science

Core Idea¶

An intended future action is encoded paired with a triggering cue, persists latently without rehearsal, and is retrieved and executed when a parallel cue-detection process fires the trigger.

How would you explain it like I'm…

Remember to Remember

Sometimes you have to remember to do something *later* — like give Mom a note when you get home. You don't think about it the whole way home; instead, seeing the front door reminds you. Prospective memory is parking a plan in your head with a 'when this happens, do that' tag, so it pops back up at the right moment.

When-This-Then-That Memory

Prospective memory is remembering to do something in the future when a certain cue shows up, without thinking about it the whole time in between. You pair a plan with a trigger, like 'when the timer beeps, take the cookies out' or 'when I see Mom, tell her the message.' Then the plan sits quietly in the background so your brain is free for other stuff, until the trigger fires and the plan jumps back to the front to be done. It can fail in a few ways: you never set the trigger clearly, you notice the trigger but forget the plan, you miss the trigger completely, or you remember but still don't do it. The same idea shows up in computers as alarms and reminders, and even in seeds that wait for rain to sprout.

Encode Now, Trigger Later

Prospective Memory is the pattern by which an agent encodes an intended future action paired with a triggering cue, then later retrieves that intention when the cue is detected and executes the deferred action — without continuously rehearsing it in between. It has a clean shape: encode-now, retrieve-on-cue, execute-later. The cue can be time-based (a clock) or event-based (a signal or context). Between encoding and execution there's a latent storage phase where the intention persists without active maintenance, which frees up working memory for other tasks, while a cue-detection process runs quietly in the background. When the cue fires, the intention returns to active processing and the action is performed. The characteristic failures map onto these stages: a cue not encoded clearly enough, a cue detected but the intention not retrieved, a cue missed entirely, or retrieval without action. The same loop appears far beyond the brain — a software cron job is the time-based version, an event handler the event-based version.

Prospective Memory is the structural pattern by which an agent or system encodes an intended future action paired with a triggering cue, and later retrieves the intention when the cue is detected, executing the deferred action — without continuous active rehearsal in between. Six commitments define it: there is an intention, an action to perform later; a triggering cue paired with the intention at encoding, which may be time-based (a clock) or event-based (a perceived signal or context); a latent storage phase in which the intention persists without active maintenance, freeing working capacity for other tasks; a cue-detection process that runs as ongoing background work and recognizes the trigger when it occurs; a retrieval-and-execution event at which the intention returns to active processing and the deferred action is performed; and a characteristic set of failure modes — a cue not encoded clearly enough, a cue detected but the intention not retrieved, a cue missed entirely, or retrieval without action, where the intention is recognized but neglected. The pattern recurs across substrates as the encode-now / retrieve-on-cue / execute-later loop. In individual cognition, its originating substrate, it remembers to take pills, mail letters, and keep appointments. In software it is the deferred-execution pattern: cron jobs (time-based), event handlers and listeners (event-based), callbacks, promises, message queues with delay timers, workflow engines with sleep states. In organizations it is commitment-and-reminder infrastructure: tickler files, follow-up systems, calendars. In physical engineering it is the triggered-action pattern: deadman switches, sprinklers waiting for a temperature trigger. In ecology it is seed dormancy: a seed encodes a developmental program and detects moisture, light, or temperature cues to germinate. Stripped of substrate vocabulary, what remains is a stored intention bound to a triggering cue, a latent maintenance phase, a cue-detection process running in parallel with other work, and a triggered retrieval-and-execution event when the cue fires.

Broad Use¶

Cognitive psychology: Remembering to take pills, mail letters, and keep appointments; the spontaneous-retrieval-versus-monitoring distinction.
Software: Cron jobs (time-based), event handlers and pub-sub (event-based), promises, message queues with delay timers.
Organizations: Calendar reminders, tickler files, follow-up cadences, action-item tracking.
Engineering: Deadman switches, dose timers, temperature-triggered sprinklers, circuit breakers.
Biology: Seed dormancy detecting moisture, light, or fire cues to germinate; hibernation triggered by environmental cues.
Law: Contingent obligations (act on condition X), event-triggered termination clauses, deadline-based rights.

Clarity¶

Separates forming the intention from carrying it out and names the latent phase in between, where most failures live — not failures of deciding or acting but of cue-detection and retrieval.

Manages Complexity¶

Collapses missed medication doses, failed cron runs, and dropped action items onto one anatomy, so a single intervention menu (specify cues, externalize, add redundancy, monitor) applies across all.

Abstract Reasoning¶

The externalization move — storing the intention-cue pair in a system with independent failure modes — is the primary reliability intervention everywhere, at the cost of inheriting that system's reliability.

Knowledge Transfer¶

Cognition → software: Gollwitzer's implementation intentions ("when X, do Y") map onto event-driven design, carrying "recognition beats recall."
Organizations ↔ software: The tickler file and the cron job are structurally identical — an external system resurfacing deferred items on schedule.
Ecology → scheduling: Seed dormancy shows latency is a designable parameter, porting to deliberately pacing deferred jobs.

Example¶

A patient misses antibiotic doses not by deciding to skip them but because cue-detection fails in the latent inter-dose hours; a reminder app, a labeled pill organizer, and a smart cap that alerts on misses each repair a different point in the chain.

Relationships to Other Abstractions¶

Current abstraction Prospective Memory Prime

Parents (1) — more general patterns this builds on

Prospective Memory is a kind of Associative Memory Prime

Prospective memory is associative memory specialized to retrieving an encoded future intention when its event or time cue is encountered.

Children (1) — more specific cases that build on this

Implementation Intention Prime is a kind of Prospective Memory

An implementation intention is prospective memory specialized by pre-binding a future cue to a particular action.

Not to Be Confused With¶

Prospective Memory is not Associative Memory because it is a deferred-action loop retrieved when a cue fires, whereas associative memory is retrieval-by-content on demand.
Prospective Memory is not Implementation Intention because it is the whole architecture including the latent phase and failure taxonomy, whereas an implementation intention is the cue-action binding technique strengthening one stage.
Prospective Memory is not Priming because it requires an explicitly encoded intention and a triggered execution, whereas priming merely lowers a response threshold through prior exposure.