Loaded volume from weighted movements. Bodyweight work is tracked separately, not inflated.
RepFast Training Dashboard
Seven months of lifting, made readable.
A real dashboard for the user who kept tracking. Based on the fake KAN-29 export seeded in the app, this view turns local CSV rows into volume trends, exercise contribution, consistency, rest discipline, and a blunt training block verdict.
Each seeded month has three workout dates in one week, enough to satisfy the default consistency target.
December won because Leg Press moved 120 x 10 and 130 x 8 across three sessions.
First logged date through 2026-04-24, with 21 completed workouts total.
Volume trend
Month-by-month work output.
The useful question is not “did I open the app?” It is whether the recorded work shows a direction.
Workout consistency
Showing up is visible.
The KAN-29 seed creates three workout dates per tracked month. This mirrors the app target that unlocks the first consistency badge.
Oct03
Oct04
Oct05
Nov06
Nov07
Nov08
Dec10
Dec11
Dec12
Jan13
Jan14
Jan15
Feb16
Feb17
Feb18
Mar19
Mar20
Mar21
Apr22
Apr23
Apr24
Leg Press drove the block.
10,770 lb of the 23,280 lb loaded volume came from Leg Press work. That is the clearest strength signal in this seed.
Useful tracking starts after repetition.
One workout is a memory. 21 workouts produce patterns: best month, dominant lift, consistency, and rest behavior.
Balance the lower-body spike.
December and March are leg-heavy. A real user could use this to plan the next block instead of guessing from memory.
Download CSV from the app
Local data first. Dashboard second.
This dashboard is intentionally grounded in exported local workout history, not a cloud account. The exact CSV fields used here are the same kind a user exports after tracking for weeks or months.
workout_date
logged_at
session_id
exercise
reps
weight
volume
rest_since_previous_set_seconds