03 · PDF Report Preview — What the physio receives

03 · PDF REPORT PREVIEW

Steady

PHYSIO REPORT

Alex Morgan

17 Feb – 12 Apr 2026

Generated 12 Apr 2026 · 8 week window

Summary

38

Runs

312km

Total

39km

Avg / Week

7

Niggles

Niggle Timeline

Apr 10

Left Hamstring Moderate

During 5×800m Intervals · 9.1km · Eased off after rep 4

Apr 05

Left Hamstring Mild

During 16km Long Run · 16.4km · Ran through it

Apr 01

Left Hamstring Mild

After Easy 8km · 8.2km · Felt during cooldown

Mar 24

Right Calf Niggle

During 8km Tempo · 8.1km · Gone by evening

Mar 18

Left Hamstring Niggle

After 10km Easy · 10.1km · Noticed post-run

Run Log (recent 12 sessions)

Date	Session	Dist	Pace	Effort	Shoe	Niggle
Apr 10	5×800m	9.1km	4:02	8/10	Vomero 18	●
Apr 08	Easy 8km	8.0km	5:32	4/10	Novablast 4	○
Apr 06	Easy 6km	6.2km	5:28	3/10	Novablast 4	○
Apr 05	Long 16km	16.4km	5:18	6/10	Novablast 4	●
Apr 03	Tempo 8km	8.1km	4:22	7/10	Vomero 18	○
Apr 01	Easy 8km	8.2km	5:35	4/10	Vomero 18	●
Mar 29	Long 14km	14.2km	5:25	6/10	Novablast 4	○
Mar 27	6×400m	7.8km	3:52	8/10	Vomero 18	○

Shoe Rotation

Nike Vomero 18

342km

total mileage

68% of 500km lifespan · used for speed work

ASICS Novablast 4

218km

total mileage

36% of 600km lifespan · used for easy & long

Trend Flags · Steady's Analysis

!

Left hamstring severity escalating. Progressed from niggle → mild → mild → moderate over 3 weeks. All instances on the left side. Appeared across easy, long, and interval sessions, not intensity-specific.

↑

Weekly load increased 18% in week 6. Jumped from 36km to 42.5km. This coincides with the first hamstring mild flag on Apr 1. Consider whether the load spike contributed.

👟

Nike Vomero 18 at 342km (68% lifespan). 3 of 4 hamstring niggles occurred in this shoe. The Novablast 4 sessions showed no hamstring issues. Correlation noted, not necessarily causal.

✓

Effort ratings consistent with plan. Easy runs rated 3–4/10, long runs 6/10, speed work 7–8/10. No signs of overreaching beyond the niggle pattern. Recovery between sessions appears adequate.

03 · The Physio Report

This is the feature. Everything else — the niggle tracking, the shoe logging, the effort ratings — was groundwork. This report is where all that quiet data collection pays off. It's the moment the runner thinks: "I'm glad I logged all that."
The physio's first 30 seconds: Summary stats → niggle timeline → trend flags. That's the diagnostic flow. Total load context, injury pattern, and what's notable. A physio can scan this in under a minute and already have more information than 15 minutes of questioning would provide.
Niggle timeline is chronological, not grouped. Physios think in time — "when did this start, how did it progress?" Grouping by body part would hide temporal relationships. The timeline lets them see: hamstring first appeared Mar 18, escalated through three runs, and hit moderate by Apr 10.
The run log table gives biomechanical context the physio can cross-reference. "The moderate hamstring flag was during intervals at 4:02/km, effort 8/10, in a shoe with 342km" — that's three data points a physio would normally have to extract through conversation.
Session-type colour dots in the run log aren't decoration. They let the physio quickly scan for patterns: "Are niggles clustering around a specific session type?" In this example, niggles appear across easy, long, and interval sessions — telling the physio this isn't purely an intensity issue.
Shoe rotation section serves two purposes. First: mileage correlation with injury ("342km shoe, 3 of 4 hamstring issues"). Second: rotation pattern analysis ("speed work always in the worn shoe, easy in the fresh one" — is that contributing?).
Trend flags are the killer feature. These are the patterns that are nearly impossible to spot in conversation. A human can't easily track that weekly load jumped 18% in the same week the first niggle appeared, or that 3/4 hamstring issues were in the same shoe. Steady sees these because it has the structured data. The physio couldn't ask the right questions without knowing the answers first.
"Correlation noted — not necessarily causal" is deliberate language. The report positions Steady as an informed observer, not a diagnostic tool. It raises the questions; the physio answers them. This builds trust with both runners and physio professionals.
For the landing page: This is the hero image. Show the report, not the app. The message: "Every run you log builds towards a moment like this. When you walk into your physio appointment, you don't have to remember anything — Steady already did."