What HyperResponder Can and Can’t Parse

What HyperResponder Can and Can’t Parse

Free-form Logging

HyperResponder can turn natural workout notes into structured sessions, but clearer input gives better results.

Download on the

App Store

HyperResponder free-form logging screen showing workout text converted into structured exercises, sets, reps, and weights.

HyperResponder turns free-form workout notes into structured training data.

It works best when your log includes clear exercise names, sets, reps, weights, time, or distance.

What HyperResponder Can Parse

HyperResponder is built for normal gym logging formats.

Good examples:



These logs give the app enough information to identify the exercise and structure the session.

Exercise Names

Common exercise names and shorthand usually work.

Examples:



Full names are more reliable than very short or personal shorthand.

If an exercise name is unusual, custom, misspelled, or written in a way HyperResponder does not recognise, you may need to correct it after parsing.

Sets, Reps, and Weight

Keep the numbers close to the exercise name.

Examples:



All of these formats describe the same basic information: exercise, load, reps, and sets.

Bodyweight Exercises

HyperResponder can track bodyweight movements such as:

  • push-ups;

  • pull-ups;

  • dips;

  • sit-ups;

  • planks;

  • bodyweight squats.

Examples:



For weighted bodyweight exercises, include the added load clearly:

Cardio and Time-Based Work

Simple cardio and time-based entries can also be logged.

Examples:



For more complex conditioning sessions, check the parsed result before saving.

Supersets and Circuits

Supersets and circuits work best when each exercise is written on its own line.

Better:



Harder to parse:

If a session has several movements in one block, separate them clearly before parsing.

What HyperResponder May Get Wrong

Parsing can be less accurate when a log is vague, incomplete, or heavily customised.

Common problem areas include:

  • missing weights or reps;

  • unclear exercise names;

  • unusual shorthand;

  • multiple exercises on one messy line;

  • mixed units;

  • typos;

  • notes that are not meant to be exercises.

Example of a vague log:

That note is useful context, but it does not contain enough structure to build a detailed workout session.

Notes vs Workout Data

HyperResponder can store notes, but notes are different from workout data.

Examples of notes:



These are useful for context, but they are not exercises, sets, reps, or weights.

If a note gets parsed as an exercise by mistake, edit the session before saving.

Best Format to Use

For the cleanest results, use this structure:

Example:



You do not need to write perfectly. Just make the exercise and numbers easy to read.

If the Parse Is Wrong

Review the parsed session before saving.

Common fixes include:

  • correcting the exercise name;

  • adjusting sets or reps;

  • adding a missing weight;

  • removing something parsed by mistake;

  • splitting a messy line into clearer entries.

HyperResponder is designed to make logging faster, but important sessions are still worth checking before you save them.