Information fragments
The date, eligibility rules, documents, and application link often live in different parts of the same page—or across several pages.
PRODUCT CASE STUDY · 2026
Designing a memory for moving deadlines.
Recall is a browser-based deadline intelligence system for opportunities found online. It captures what matters, organizes when it matters, and keeps watching after the tab is closed.
THE PROBLEM
Finding the opportunity is only half the work.
Important applications arrive as scattered web pages: fellowships, internships, scholarships, grants, programs, and competitions. A bookmark preserves the address, but not the urgency, requirements, or later changes to the source.
Dates are not static
Organizations extend windows, change cycles, close listings, or publish next year's date without contacting everyone who saw the original.
Memory carries the load
The user must remember both that an opportunity exists and when to return, often while managing many other commitments.
BEHAVIORAL BASIS
Research supports the problem, not the hype.
The relevant literature calls this prospective memory: remembering to carry out an intention later. Recall applies that evidence carefully without claiming that software can eliminate procrastination.
1,196
External reminders improve intention completion.
Across four online experiments, participants could move delayed intentions into the environment by setting reminders. Reminder use improved performance.
Gilbert, 2015 ↗2024
People offload what feels valuable.
A value-based model suggests that memory load, the importance of remembering, the effort required to set a reminder, and trust in its reliability shape offloading decisions.
Gilbert, Cognition ↗ACCESSIBILITY LENS
Reduce the executive burden, not the person's agency.
Recall may be especially useful when planning, initiation, working memory, or prospective memory are under strain. That includes some people with ADHD or depression—but the design goal is broadly accessible support, not diagnosis or treatment.
“Knowing the deadline” and starting in time are different cognitive jobs.
Prospective memory involves forming an intention, retaining it, noticing the right cue, and executing it. Opportunity applications add planning, prioritization, and task initiation on top.
A strong tool should therefore do more than issue an alarm. It should lower capture friction, preserve the source, make the next action visible, and avoid turning a long task list into another source of overwhelm.
Complex prospective memory can break at the planning stage.
A study comparing 45 adults with ADHD and 45 matched controls found a specific impairment in task planning rather than a uniform deficit across every prospective-memory component. View study ↗
Encoding the future action may matter.
In a 2026 experiment with 196 adults, the ADHD group showed lower everyday prospective-memory performance; episodic future-thinking instructions improved performance across groups. This does not test Recall itself. View study ↗
If saving is laborious, people save less.
Two preregistered experiments found that increasing the physical effort required to set a reminder reduced reminder use and weakened its ability to compensate for memory load. View study ↗
Prospective-memory difficulty is not unique to ADHD.
A meta-analysis of 10 case-control studies found impairments in both event- and time-based prospective memory among participants with depression, with substantial heterogeneity across studies. View meta-analysis ↗
One-step capture
Save the intention at the moment of discovery, before context switching erases it.
Visible next action
Translate a distant deadline into the first small, concrete step required now.
Calm escalation
Use layered reminders and urgency cues without flooding the user with noise.
Editable automation
Let the system propose structure while keeping the person in control of the plan.
Important: Recall is an organizational tool, not a medical device or treatment for ADHD, depression, or any other condition. These findings motivate inclusive design hypotheses that still need to be tested with users who have relevant lived experience.
COMPETITIVE LANDSCAPE
A crowded market with an open intersection.
The concept is not entirely new. Existing products validate pieces of the workflow, but they generally specialize in either tracking applications or monitoring pages.
| PRODUCT TYPE | SAVE A LINK | STRUCTURE THE OPPORTUNITY | MONITOR THE SOURCE | CROSS-CATEGORY SCHEDULE |
|---|---|---|---|---|
| Recall | Yes | Automated + reviewed | Daily semantic check | Yes |
| Teal / Simplify | Yes | Jobs | Not core | Jobs only |
| Distill / Visualping | Yes | No | Generic change alerts | No |
| Link Organizer | Yes | Manual | No stated monitoring | Manual |
| Calendar / bookmarks | Manual | Manual | No | Manual |
This comparison reflects publicly described product behavior as of August 2026. “Not core” does not mean technically impossible; it identifies the workflow each product is designed around.
THE PRODUCT RESPONSE
From one link to a living schedule.
The key design decision was to treat a deadline as a monitored relationship with its source—not a static date copied into a calendar.
Capture
Save the current page, a link, or a manually entered opportunity.
Extract
Identify the title, organization, deadline, and explicit requirements.
Plan
Review an editable backward plan built from the confirmed date and source requirements.
Watch
Revisit the source daily and move unfinished suggested steps when the deadline changes.
Resurface
Show the next action, send reminders, or bring recurring opportunities into the next cycle.
DESIGN PRINCIPLES
Trust is the interface.
A deadline tool is only useful when users understand what it knows, what changed, and where uncertainty remains.
Source before summary
Every extracted field stays connected to the original page so critical details remain verifiable.
Changes should be legible
Show the previous and current date instead of silently overwriting history.
Automation proposes
Extraction reduces effort, but the user can correct ambiguous or incorrect information.
Quiet until useful
Reminders should protect attention, not create another stream of notification noise.
CURRENT STATUS
No invented traction.
Recall is in private beta. The behavioral problem has research support and the competitive gap is plausible, but pricing, retention, extraction accuracy, and willingness to trust automated monitoring still require real-world validation.
SUPPORTEDPeople benefit from external intention reminders.
IMPLEMENTEDCapture, extraction, editable backward plans, chronological tracking, and source rechecks.
TO VALIDATECorrection rate, deadlines caught, plan completion, return behavior, and willingness to pay.
NORTH-STAR QUESTIONWould a user be seriously disappointed if Recall disappeared?
THE THESIS
Bookmarks remember pages. Recall remembers when they matter.
Join the private beta and help test the next version of deadline intelligence.
Join the private beta