How to Read Your Plan Analytics and Momentum Score
Understand the six Plan Analytics metrics — Momentum Score, Weekly Velocity, Overdue Rate, Focus Hours, Goal Progress, Overcommitment Rate — and use them to drive behavioral adjustments.
How to Read Your Plan Analytics and Momentum Score
Plan Analytics turns the invisible pattern of your week into numbers you can act on — how much you are completing, how fast, how much you are carrying, and whether you have quietly over-committed. Read correctly, it is not a scoreboard to feel judged by; it is an early-warning system.
Operational Directive
Every number here is derived from what you actually do — you cannot fake it by editing a field. That is the point: the analytics are only useful because they hold up a true mirror, not a flattering one.
Section ProtocolWhat the metrics mean
| Metric | What it measures | What a bad reading suggests |
|---|---|---|
| Momentum score | Overall completion trend | You are finishing less than you are starting |
| Weekly velocity | How much you complete per week | Capacity is dropping — look at load |
| Overdue rate | Share of tasks past their date | Too many fake deadlines, or genuine overload |
| Focus hours | Logged deep-work time | Little protected attention this week |
| Overcommitment | Planned load vs your velocity | You have promised more than you can deliver |
Section ProtocolReading it well
Look at trend, not a single day. A momentum score dipping for a week is noise; three weeks of decline is a signal worth acting on. When a number looks bad, trace it to a cause rather than trying to fix the number: low velocity usually means either too little focus time or too much load, and a high overdue rate often means fake deadlines rather than genuine failure. The overcommitment reading is the most forward-looking — when planned load outruns your real velocity, that is the moment to cut or defer, before the week collapses.
⚠Common Traps
Section ProtocolWorked example
Ravi's velocity has dropped two weeks running and his focus hours are near zero — the analytics make the cause obvious: he has been reactive, with no protected deep work. He books focus sessions for his top tasks, and the overcommitment reading tells him this week's plan is already 20% over his real capacity, so he defers two non-urgent projects. The next week's numbers recover — not because he chased them, but because he fixed what they were pointing at.
Reflection Prompts
Intelligence Pipeline
Connected Intelligence
Ready to Deploy Your Life OS?
Experience the full power of integrated intelligence. Stop managing apps and start operating your life.
Launch Command Center