KULPINSKI-LJUBIŠEVIĆ ATELIER
PROGRESS TRACKER // PRIVATE PERFORMANCE LEDGER

Turn completed workouts into training history you can use.

LuKul tracks progress from the work you actually complete: sets, load, reps, RPE, session volume, readiness context, CSV portability, and macro-cycle movement become part of one private training record.

Completed sessions feed recent history, weekly strain, readiness evidence, key lift e1RM trends, and macro-cycle radar without separating progress from the training block.

Coming soon to App Store + Google Play
Request Early Access View Training App Free tier available. Paid tiers expand advanced use, coaching workflows, and system depth.
Private ledger Plan → Log → Progress
CSV portability Private performance ledger
Macro-cycle movement, readiness context, and completed session history in one performance ledger.
// 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.

[SETS / REPS / LOAD]

The raw work stays legible.

Completed sets keep the basic performance facts attached to the session record.

[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.

// PRIVATE PERFORMANCE LEDGER

Your training history becomes a decision layer.

Recent logs, session summaries, and historical records stay useful after the workout ends. Progress is not a screenshot or a loose note; it is a private ledger that carries context forward.

Mon // Week 04 Lower strength session sealed 18 sets // avg RPE 7.8 VOL 8.4k
Wed // Week 04 Upper hypertrophy work complete 22 sets // comments retained RPE 7.1
Fri // Week 04 Pull protocol logged load, reps, tempo, paused state SEALED
// 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
LuKul macro-cycle radar showing weekly tonnage, readiness, and phase movement
Macro-cycle radar: weekly tonnage, readiness, and phase movement.
LuKul macro-cycle continuity view with strain and readiness context
Block continuity: strain, readiness, and training weeks stay readable.
// READINESS & STRAIN CONTEXT

Progress is clearer when state is visible.

Manual check-ins and connected sources can contribute sleep, soreness, steps, HRV/RHR, readiness, and recent load context. LuKul keeps those signals subordinate to the training record, where they can help explain the work.

Learn more about Total Training Stress in the Training App FAQ.
LuKul readiness ring showing training state context
Readiness context: manual check-ins and connected sources when configured.
LuKul optional connected readiness source selection screen
Optional connected context when configured. Readiness sources support the training record; they do not replace it. Hardware context belongs below the training record, not above it.
// 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.

LuKul CSV import interface for preparing outside records
[CSV IMPORT]

Prepare imported records for continuity.

Prepare outside records for structured continuity.

LuKul CSV export interface for workout log portability
[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.

Planner Workout Log
// 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.

Coaches
// 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
Request Early Access View Full Training App

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.