Reviewing metric submissions from athletes (coach)

What a metric submission is

When an athlete logs a new threshold (e.g. a new FTP after a test they ran on their own), or submits a body composition reading, the entry lands in a review queue for you.

This is separate from the automatic assessment flow because the athlete is reporting a number without the structured inputs needed to recompute it. You decide whether to accept the number into the canonical zones or ask for the underlying test.

Where the review queue lives

• Pending metric submissions surface on the coach dashboard with a small "needs review" pill.
• Click the pill to open the review page (/coach/metric/<id>/review/).
• The page shows the submitted value, the athlete's previous value, any attached file or note, and the submission timestamp.

What you can do on the review page

• Accept: the submitted value becomes the athlete's canonical zone. A PerformanceRecord is created for trend tracking.
• Decline: the submission is discarded. A note is auto-written on the athlete record explaining why if you fill in the reason.
• Request more info: keeps the submission pending and notifies the athlete to provide a test file or context.

When to accept vs decline

Accept when the number is plausible against recent trends and you trust the athlete's testing protocol. Decline (or request more) when the jump is unusual (e.g. FTP up 15 percent in two weeks) or when there is no supporting evidence.

What the athlete sees

• While pending, the athlete sees a "submitted for review" indicator.
• On accept, the athlete sees the new zone applied.
• On decline, the athlete sees a polite explanation note.