Event-based prospective memory relies on an external cue; time-based relies on internal monitoring

What it is

Prospective memory splits into two kinds based on what triggers the "remembering to act." Event-based prospective memory fires when a pre-arranged cue turns up in the environment — seeing a particular person reminds you to pass on a message, walking into the kitchen and spotting something reminds you what to do. Time-based prospective memory has no external cue at all; the only way to tell "is it time yet" is to keep track of elapsed time or check the current situation against a target — remembering to make a call at exactly three o'clock.

Why it happens

The two rely on different processing routes. Event-based prospective memory can lean on a sufficiently distinctive external cue to activate the stored intention in a relatively automatic way once the cue appears — the person doesn't have to consciously hold onto the intention the whole time, because the cue itself does most of the reminding. Time-based prospective memory has no such external trigger; the person has to run their own internal monitoring process, periodically checking "what time is it, is it time yet." That checking itself draws on attentional resources and is entirely self-initiated — nobody else presses the button to trigger the check, so once something else crowds out the monitoring, the window gets missed.

Studying it

The classic way to separate the two experimentally is to manipulate the cue: one condition embeds a salient event cue directly tied to the ongoing task, the other only specifies a time target; comparing completion rates and response delay at matched delays typically shows worse and more variable performance in the time-based condition. Researchers also log how often participants check the clock while waiting, as evidence that monitoring itself consumes resources — clock-checking frequency and primary-task performance usually trade off against each other.

Where it stops holding

Whether an event cue actually delivers this relatively automatic advantage depends on the cue's own properties — if the cue is unrelated to whatever the person is currently focused on, activation drops sharply, sometimes down to time-based levels; this account only holds when the cue is salient enough and falls within the person's current span of attention. Also, most real-world to-dos are hybrids of the two — "after I get home, but not before six" — pure event-based or pure time-based sit at two ends of a spectrum that most real cases fall somewhere in between.

Applying it

• Wherever a reminder can be designed as event-triggered, design it that way: bind it to a concrete action or situation the user will necessarily pass through (opening an app, arriving at a place, finishing a preceding step) rather than expecting the user to hold an abstract point in time in mind.
• If a task can only be defined by time (a meeting at a set hour, something expiring in a set number of minutes), don't assume the user will monitor the clock themselves — the system has to proactively surface a prompt near that time and take over the monitoring the user would otherwise have to do.
• How to check: compare on-time completion rates for the same users under event-triggered reminders versus pure time-based ones; a markedly lower rate for time-based confirms that scenario genuinely needs the system to take over monitoring rather than leaving it to self-reminding.

Related

• Same group: A6.19.1 Prospective memory means remembering to act at a future time or occasion, distinct from recalling the past · A6.19.3 Without an explicit reminder, time-based intentions are the ones most likely to be forgotten outright · A6.19.4 Interrupting the current task drains prospective-memory resources, so more frequent interruption raises the odds of a missed to-do · A6.19.5 System reminders should bind to the triggering context, not just record to-do text
• Nearby: A6.08 Retrieval cues and context dependence · A6.09 Procedural memory and automaticity
• Search terms: event-based prospective memory · time-based prospective memory · self-initiated retrieval