Skip to main content

If you already have a program written down, the useful thing is keeping its structure. Rackd's import flow is there to help you bring that plan into the training record instead of starting again from a blank screen.

Start with the source

Use the import entry point shown by the release you are using. A structured JSON program gives the matcher more to work with, but the source still needs a review before you run it.

Review exercise matches

The selected exercise source contains 448 exercises. The matcher checks names and aliases, then flags anything that needs your decision. A row that cannot be placed should stay visible in the review step rather than quietly turning into a different movement.

Choose the closest existing exercise when it is genuinely the same movement. If the source uses a custom exercise, keep the name and description clear enough that you will recognise it in the session.

Review the progression rule

Importing exercise names is not the same as importing the progression logic. Check the week structure, targets, increments, and deload behaviour before you commit the program. Rackd's engine contains 11 progression systems, but an imported program still needs a rule that matches its own intent.

Run the first session

Set the training inputs the program expects, open the first workout, and compare the target with your original plan. If something looks wrong, stop at the review step and correct it there.

A clean import preserves the plan you meant to run. The app's job is to make the next session legible, not to rewrite your programming without asking.