At some point, you'll open ATEND after not having used it for a while. Maybe a few days. Maybe a few weeks. Maybe longer. The app knows. And the first thing it does — before showing you anything — is decide how to welcome you back without making you feel worse than you already do.
The moment that matters
When an ADHD user opens the app after an extended absence, they're in one of the most vulnerable states the system will ever encounter. They already feel bad. They already know they've been away. They're probably telling themselves some version of the story they've told themselves every time a system has failed them before: this is how it always goes, I can't keep anything up, there's no point.
The app's response in the first ten seconds either confirms that story or defuses it. Every design decision in the re-engagement flow is oriented toward one outcome: making coming back feel like the right decision.
Coming back is the right decision. Every time. The system is designed to make you feel that — not to show you everything you missed.
Five tiers of absence
ATEND distinguishes five tiers of absence based on how long you've been away. "Days" means workdays — days when you would normally be using the app. A weekend away isn't an absence. A holiday isn't an absence. The system knows your working hours and only counts time within them.
Same day
Under 18 hours
Normal Launchpad. No special handling. You're just back from lunch.
Short
18 hours – 3 days
Gentle acknowledgment. Light triage. Normal flow resumes quickly.
Medium
3 – 14 days
Full re-engagement flow. Backlog handling. Fresh start mode with a structured path back.
Long
14 – 60 days
Extended re-engagement. System reset option offered. Heavier triage of what still matters.
Very long
60+ days
Near-complete reset offered. Treated as a soft re-onboarding. A fresh start is a valid option.
The flow only fires during workday hours. If you open the app at midnight after two weeks away, it waits. The re-engagement flow surfaces when you're in a context where doing something about it is actually possible — not when you're winding down for the night.
The opening screen
The first thing you see is a full-screen welcome. No task list. No inbox count. No numbers. Just a message, calibrated to how long you've been away:
Medium · 3–14 days
"Hey. You've been away for a few days. Good to have you back. Things have been held while you were gone. Let's spend a few minutes getting you back on track."
Let's do it — 5 minutes
Not now — just show me today
Very long · 60+ days
"Welcome back. It's been a while. A lot has changed. Rather than dig through everything, you might want to start fresh. Either way, I've got you."
Start mostly fresh
Sort through what's here
Not now
You can always choose "Not now — just show me today." The system never forces the re-engagement flow on you. But it makes the structured path the easiest choice, and that path is designed to take less than ten minutes.
The five re-engagement steps
1
Clear the expired — silently
Before you see anything, the system quietly processes what accumulated during your absence. Recurring task instances that passed their due date are already in the archive — new instances have already been generated automatically. Stale overdue tasks are flagged internally. Old Big Three outcomes are expired. None of this is shown to you. You never see "12 tasks missed" or "streak broken 5 times." The cleanup happens in the background so you don't have to face it all at once.
2
The inbox — quick pass option
The system tells you how many things arrived in your inbox while you were away and offers two options. A quick pass shows items one at a time with a simplified two-choice fate decision: Keep or Toss. It caps at ten items — the rest move to a quiet processing queue automatically. Or you can defer the whole thing: all items move to the processing queue with a soft badge, not the confronting red inbox number. Nothing is lost. You can process properly whenever you're ready.
3
What still matters
Your active tasks are shown grouped by hat — not by due date, not with their dates visible at all. Just titles and hats. For each task, two options: Still relevant, or Not anymore. Tasks you mark "not anymore" go to Someday — not deleted, just gracefully parked with their context preserved. Tasks you keep stay active. You can stop at any point and sort the rest later. There's no pressure to review everything before getting back to work.
4
A fresh week — one or two things
Not the full Big Three. Just one or two outcomes — what matters most this week. The reduced ask is intentional: you're not being asked to plan a complete week immediately. One or two things is enough to give the day direction. If you skip this entirely, the Launchpad operates without a Big Three until you run the next proper Weekly Architecture Session. It still works — the system just won't apply the Big Three boost to any tasks until you've set new ones.
5
Today — one thing
What's one thing you want to do today? The system suggests a short list filtered by your energy context — same as the morning setup. You pick one. That becomes today's MIT. Then: "That's enough. Let's start there." The Launchpad opens showing only the MIT and a short Now list. No inbox count badge. No streak counter. Just the work.
What the system deliberately doesn't show
On re-engagement, these things are hidden — not because the system is hiding reality from you, but because confronting a returning user with accumulated failure data in the first ten seconds is the single most reliable way to make them close the app and not come back.
✕
The exact number of days absent
✕
The streak counter — hidden for the entire first session back
✕
Missed recurring task count
✕
Any language using the word "overdue"
✕
Red date indicators on tasks
✕
The full task list
✕
The archive of what was missed
All of this information exists in the system. None of it is deleted. You can access the archive, check your streak history, and see everything that accumulated. But the system won't lead with it. It leads with: good to have you back, here's the path forward.
Streaks after a break
Your streaks break when you're away. The system handles this straightforwardly rather than pretending otherwise.
On return, the streak counter shows zero but isn't displayed prominently — it's just not part of the first session back. After your first successful Daily Close since returning, the system acknowledges it: "First close back. Streak restarting."
If you complete three consecutive Daily Closes after returning, the streak is marked as recovered. It's displayed with a small indicator that the streak has a gap in it — more honest than pretending the absence didn't happen, more forgiving than treating a long streak as if it never existed. One break doesn't erase what came before it. Recovery is always available.
The point of all this
Every productivity system you've ever abandoned confronted you with a backlog of failure when you came back. That confrontation is what made not coming back feel easier than coming back. ATEND is designed to invert that dynamic. The system isn't keeping score on you. It held your things while you were gone, it cleaned up what it could, and it's ready to help you take the next step whenever you're ready to take it.
