Reading your weekly progress report
People stare at weekly reports the way they stare at dashboards — hoping the right number will jump out. Reports work better when you read them looking for one thing.
- The confidence band is load-bearing. Read it first; everything else is conditional on it.
- Three numbers worth remembering: best block, riskiest hour, top driver.
- Change attribution names what shifted, not what caused it. Causation needs an experiment.
Reports are arguments, not dashboards
Most weekly reports fail because they were built to be looked at, not read. A grid of metrics, a few sparklines, color codes. You open the tab on Monday, scroll, close it. Nothing changed.
A Sarenica weekly report is built differently. It is a short written argument about your last week, structured to end in a single decision: what to try this week. Every section is either supporting that decision or admitting the report does not have enough data to make one.
That framing changes how you read it. You are not hunting for the most interesting bar on the chart. You are checking whether the report has earned the right to recommend something — and if it has, what.
“The job of a weekly report is to leave you with one decision. If you walk away with seven, the report failed.”
Start with the confidence band
Every report opens with a date window and a confidence band: strong, moderate, directional, or insufficient. The band is load-bearing — if you skip it, everything below means less than you think.
Most people glance past it and start interpreting numbers as if every chart is hard evidence. They are not. The same chart means something different at "strong" than at "directional". You should be reading the band first and the rest second.
- Strong — at least 4 active workdays with stable coverage. Recommendations hold up.
- Moderate — enough for a useful read, but treat the recommendation as an experiment, not a rule.
- Directional — a hint about where to look, not a call to act.
- Insufficient — not enough reliable minutes. The report skips the recommendation entirely, which is the right move.
Three numbers worth remembering
Three tiles sit near the top of every report. If you remember anything from the week, remember these.
Best block — the session length where your fatigue stayed lowest and your productive density stayed highest. For most people it lands at 15-30 minutes. A few hold strong through 45. Below 15 you are usually context-switching; above 45 the fatigue tax starts to show.
Riskiest hour — the hour where fatigue burden was highest. Midday and late afternoon are common. If you start your day late, sometimes the pre-lunch hour shows up — usually a sign you are under-recovered at the start.
Top driver — the one signal the report believes most explains the week. Session length, posture, eye strain, recovery, timing. It is the answer to "if I had to fix one thing." Sometimes it is boring. Boring is fine.
Findings are written carefully on purpose
Below the chart is a short list of findings — two to four sentences with the report's own read of what happened. The wording is deliberately cautious.
You will see "associated with" or "tracked alongside" rather than "caused". That is not hedging for its own sake. The signals support correlation cleanly; causation is a separate claim that needs a separate test.
If you want the report to say something stronger, you have to give it stronger evidence — usually by deliberately running a one-variable change for a week, labeling it, and comparing the labeled window against the rest.
Change attribution: what shifted, not what caused
Once you have one prior weekly report saved, a new section appears: change attribution. It compares this week against last week and names what most likely shifted.
A typical entry: *"Session duration shift, directional: 30-45 minute blocks rose from 22% to 48% of sessions; fatigue rose 0.18 in those buckets."* Notice what it does not say. It does not claim the session change caused the fatigue rise. It gives you the magnitude, the direction, and the confidence, and trusts you to draw the conclusion — or to run an experiment if you want one with more confidence than that.
Confidence escalates only when at least two independent metrics agree on direction. An explicit experiment label can promote a finding to "confirmed". For normal weekly reads, "directional" or "probable" is the honest top end, and that is on purpose.
Leave with one decision
The footer is a recommended verification — usually one concrete change to try for the coming week, framed as an experiment.
That is what the whole report is for. Not a feeling, not a score, not a dashboard. One decision, applied for a week, then read back against next Monday's report.
That is how the system gets sharper over time. It is also how you do.
