Your Progress Dashboard
The dashboard is where you step back and look at patterns instead of individual tasks. It doesn't tell you what to do. It shows you what's actually been happening — how your time is being spent, where your estimates diverge from reality, which hats are getting attention, and how consistently you're showing up for the daily and weekly rituals that make the system work.
What the dashboard is not
The dashboard contains no productivity score. No streak-based shame. No comparison to anyone else. No aggregate efficiency rating. These design choices are deliberate — not because metrics are bad, but because the wrong metrics reinforce the wrong things.
Everything in the dashboard is either a pattern observation ("here is what your Tuesday mornings have looked like for the past four weeks") or an honest measurement ("your Deep Work estimates are typically off by about 60%"). It never tells you those patterns are good or bad — it shows you what they are and trusts you to draw your own conclusions.
This week at a glance
The top section of the dashboard shows the current week in summary: your Big Three outcomes with progress indicators (Not Started, In Progress, Done), a simple bar chart of tasks completed by day, and your MIT completion rate for the week — the percentage of days where your Most Important Task actually got done.
The day-by-day completion chart is the most honest view of how your weeks actually flow. Most people discover patterns they didn't know they had: a consistent Thursday dip, a reliable Monday burst, a midweek accumulation of completions. The pattern isn't a verdict — it's information you can use when scheduling the work that matters most.
MIT completion rate is not a test to pass. A rate of 60% means you completed your most important task three out of every five days. For most people with ADHD, that's a significant achievement — not a C grade. The number is meaningful as a trend: is it going up, going down, or staying flat?
Time estimation accuracy
Every time you complete a task, ATEND records how long it actually took versus how long you estimated. Over time, this builds a calibration profile — a personal picture of how your estimates tend to diverge from reality, broken down by energy type.
The dashboard shows this in plain language, not percentages or multipliers:
The calibration data requires at least five completed tasks in a category before it's shown — before that threshold, the dashboard says simply: "Complete a few more tasks to see your calibration." It gets more accurate over time as your history grows.
The system also shows a trend indicator: whether your accuracy is improving, stable, or worsening over the past four weeks. Most people see improvement just from being aware of the pattern — the act of knowing you underestimate Deep Work changes how you schedule it.
How calibration affects the system
The calibration data doesn't automatically change your time estimates when you create new tasks — you always enter your own estimate, and that's kept separate from what the system has learned. What it does is inform the pre-focus-session time check: if you estimate a task at 90 minutes but your calibration shows Deep Work tasks typically take 60% longer, the system will flag it before you start: "This task usually takes you about 2.5 hours. You have 90 minutes before your next commitment. Want to set a 75-minute timer and continue later?"
The purpose of this is not to correct you — it's to give you better information in the moment when you're deciding whether to start. The estimate is yours. The history is real.
Hat balance
The hat balance section shows a four-week activity bar for each of your hats, colored by their current neglect status. Green is active. Amber is quiet or fading. Red is neglected or critically neglected. It's the same data that drives Screen 4 of the Weekly Architecture Session — here it's always visible rather than surfacing only once a week.
Tap any hat bar to see the activity breakdown: which tasks and focus sessions contributed to that hat's score, and how the score has moved over the past eight weeks. This is the view that makes the "silent drift" pattern visible — you can see exactly when a hat started going quiet and trace it back to specific weeks.
Not all hats should be equally active. The Vehicles hat might legitimately go amber for six weeks and that's fine. What matters is whether the pattern matches your intentions. If Book is amber and you said it was important to you this quarter, that's a signal worth looking at. If Vehicles is amber and you have no open vehicle work, that's just an accurate reflection of reality.
Streaks
Three streaks are tracked: consecutive days completing the Daily Close, consecutive weeks completing the Weekly Architecture Session, and consecutive days completing your MIT.
days in a row
weeks in a row
days in a row
Streaks are designed to be recoverable. Missing a day breaks the streak — but a Recovery mode restores it if the next three days are complete. This prevents the common failure pattern where a single missed day triggers complete abandonment: "I broke my streak, so there's no point." One missed day is not a reason to stop. Recovery is always available.
Streaks are not the goal. They're a proxy for the real goal, which is consistent use of the daily and weekly rituals that make the system work. A streak of 30 Daily Closes is meaningful not because the number is large, but because 30 daily closes means 30 evenings where you offloaded your open loops before sleep. The streak is just evidence of something real happening underneath it.
Insight cards
Once a week, the system generates one insight card based on your recent patterns. One card, not five. It appears in the dashboard and nowhere else — never as a push notification, never interrupting the Launchpad.
Examples of what an insight card might say:
Insight cards are observations, not instructions. The system noticed a pattern and named it. What you do with that information is yours.
How to actually use the dashboard
The dashboard works best as a weekly check-in, not a daily habit. Most people look at it naturally during or after the Weekly Architecture Session — it's the data layer behind the planning session. What does the hat pulse show? What patterns appeared this week that might inform what goes into the Big Three?
Looking at it daily tends to make numbers feel like grades. Looking at it weekly, in the context of planning, makes them feel like information. That's the distinction the dashboard is designed to support.
The one exception is the time calibration data — that's worth checking after you've been using Focus Mode consistently for a few weeks. The moment you see your first calibration reading and realize you've been systematically underestimating your Deep Work tasks by 60%, you'll start scheduling them differently. That's the dashboard doing exactly what it's for.