[SETS / REPS / LOAD]
The raw work stays legible.
Completed sets keep the basic performance facts attached to the session record.
Progress tracker
Look back before your next session
Revisit completed sessions, dates and recorded details. Use your own history as context for the next conversation or training decision.
Coming soon to App Store + Google Play Free tier available. Paid tiers expand advanced use, coaching workflows, and system depth.
Training history
Every completed session, by date
Completed sessions stay in your history with their date, number of sets, average RPE and volume. Open any day to read the sets inside it.
Keep the details of the work
Load, reps, effort and notes are easy to forget by the next session. Recording them as you train means the next decision starts from what you actually did, not from memory.
// LOGGED WORK
The signal starts with completed sessions.
LuKul progress begins with completed training, not vanity inputs. Sets, load, reps, RPE, comments, and training days become structured history as the work accumulates.
[RPE + COMMENTS]
Effort and notes remain part of context.
The record can carry perceived exertion and comments alongside the numbers.
[SESSION VOLUME]
Completed work becomes measurable load.
Volume and weekly strain can be read from completed training rather than guessed afterward.
[TRAINING DAYS]
History forms across repeated sessions.
Progress becomes stronger as the private ledger accumulates training days.
// METRICS THAT MATTER
Volume, strain, readiness, and effort stay connected.
[VOLUME]
Loaded work
Total training work can be summarized from completed logs.
[AVERAGE RPE]
Effort context
RPE keeps intensity attached to the session record.
[WEEKLY STRAIN]
Recent pressure
Recent load can become strain context for the current week.
[READINESS]
When data exists
Readiness is context for training state, not diagnosis.
// MACRO-CYCLE RADAR
Progress belongs to the block.
LuKul's macrocycle view helps training history stay connected to the larger training block: weekly tonnage, average intensity/RPE, readiness, phase movement, and mechanical/cardio views.
Weekly tonnage
Average RPE
Readiness
Phase timeline
Mechanical filters
Cardio views
// STRENGTH TREND LAYER
Key lifts can be read across time.
For key strength lifts, LuKul can surface e1RM trend logic and PR flags inside the Analytics Vault. The goal is not noisy universal records; it is a cleaner view of meaningful strength movement.
Training load map
Training load map before data is available
This view has no training data to display.
- It is a view of logged work, not a measure of recovery or readiness.
// CSV PORTABILITY
Your training data should move with you.
LuKul supports CSV portability so training history is not trapped inside a closed view. Export workout logs for review, backup, analysis, or migration, and prepare imported training records for structured continuity.
[CSV IMPORT]
Prepare imported records for continuity.
Prepare outside records for structured continuity.
[CSV EXPORT]
Export is the ownership layer.
Export logged work without trapping the record.
PORTABLE LEDGER FIELDS:
Date
Exercise
Weight
Reps
RPE
Tempo
Paused state
Comments
// PLAN & REALITY
The plan and reality stay in the same record.
The Planner defines the intended structure. The Log captures what happened. Progress sits on top of both, so training history remains connected to the original block instead of becoming detached statistics.
// COACH-AWARE REVIEW
Useful alone. Stronger with human oversight.
LuKul's progress record is useful for individual lifters and compatible with coach/client review contexts. The point is not to replace coaching judgment; it is to give the coach and athlete a cleaner record to review.
// CONTROLLED NATIVE ROLLOUT
Build the record before the noise.
LuKul is preparing a controlled native rollout for athletes and coaches who care about structured planning, live logging, and progress history that remains readable over time.
Coming soon to App Store + Google Play
Free tier available. Paid tiers expand advanced use, coaching workflows, and system depth.
// PROGRESS TRACKER FAQ
Questions before tracking progress.
Is LuKul a progress tracker?
Yes. LuKul tracks completed training history, session volume, RPE, readiness context, CSV portability, and macro-cycle movement so progress remains connected to the training plan.
What progress data does LuKul track?
LuKul tracks logged exercises, weight, reps, RPE, comments, session volume, recent history, weekly strain, and selected analytics views.
Does LuKul track volume and RPE?
Yes. Workout logs include load, reps, and RPE, and dashboard views use those records for volume and strain context.
What is Total Training Stress?
Total Training Stress helps place training load and accumulated effort into context. The Training App FAQ explains the concept in more detail.
Does LuKul show workout history?
Yes. The dashboard includes recent logs and session-level summaries.
Does LuKul track PRs?
LuKul includes e1RM trend and PR flag logic for key strength lifts. It should not be read as universal PR tracking for every exercise.
Does LuKul use readiness or biometric context?
Readiness can come from manual check-ins and connected sources where configured. It is training context, not medical diagnosis.
Can coaches review progress?
LuKul supports coach and client contexts, while the progress record remains useful as the athlete's own training history.
Can I import or export workout logs?
Yes. LuKul supports CSV portability. Export fields can include date, exercise, weight, reps, RPE, tempo, paused state, and comments.
Is LuKul available on iOS and Android?
LuKul is preparing controlled native rollout for iOS and Android. Store links will be added only when official links exist.