ForHosting KIT · Developer Utilities

Progressive overload weight plan calculator

This progressive overload weight plan calculator turns three simple inputs into a clear week-by-week training target.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter the weight you can currently use, choose a non-negative weekly percentage increase, and set the number of weeks in your block. The calculator compounds each increase from the previous week's target, keeps the original unit you entered, and returns a numbered schedule you can copy into a workout log or training application. It is useful for planning ahead while keeping the arithmetic consistent and visible.

Choose a realistic starting point

The starting weight should represent a load you can perform with dependable technique for the exercise, repetition range, and effort target you intend to use. It is not necessarily your one-repetition maximum, your heaviest recent attempt, or the largest number available on the machine. A conservative starting point gives the schedule room to progress before fatigue or form becomes the limiting factor. Enter the number in any weight unit you use consistently, such as kilograms or pounds; the calculator does not convert units, so every planned value remains in that same unit. Week one is exactly the starting weight. This convention makes the plan easy to compare with the first session of a new block and avoids applying an increase before training has begun. If you are returning after illness, changing exercise technique, or beginning a higher-volume phase, consider using the load that matches the new circumstances rather than an older personal best. A mathematical schedule is most useful when its first value reflects what you can actually repeat today.

Understand how weekly compounding works

The weekly percentage is applied to the previous week's planned weight, not repeatedly to the original starting weight. For example, an increase of two percent uses a multiplier of 1.02. Week one is the starting load, week two is the starting load multiplied by 1.02, and week three multiplies the week-two target by 1.02 again. This compounding is why later differences become slightly larger even though the percentage stays constant. The output rounds each displayed target to six decimal places, which keeps results stable while preserving more precision than most gym equipment can provide. In practice, you may need to round the target to the nearest plate, dumbbell, cable-stack increment, or machine setting available to you. Treat that equipment adjustment as a practical decision after generating the schedule. A zero percent increase is valid and produces the same planned load each week. A negative percentage is rejected because this capability specifically creates progressive overload plans rather than deload or taper schedules.

Use the schedule as a plan, not a command

Copy the generated weeks into your training log before the block starts, then record what you actually perform beside each target. The plan gives you a consistent progression rule, but readiness, technique, pain, sleep, and repetition quality still determine whether a particular increase is appropriate. If a target exceeds the equipment increments available, round deliberately and note the choice so later weeks remain understandable. If you miss the required repetitions or your technique changes materially, repeating a weight can be more useful than forcing the next calculated number. The schedule also assumes that the exercise, set structure, repetitions, and effort target remain comparable across weeks. Changing several of those variables at once makes load alone a poor measure of progression. Coaches and software teams can use the API to create draft blocks automatically for multiple exercises, while individual lifters can run it directly in the browser. API requests use the published base price of $0.002; browser use on this page remains available without sending the calculation elsewhere.

Plan a strength block

Generate consistent weekly targets for one lift before a multi-week training block begins.

Populate a workout log

Create numbered planned weights that can be copied into a spreadsheet, notebook, or training application.

Automate coaching drafts

Use the deterministic API output as a starting schedule that a coach can review and adjust for available equipment.

Is week one increased already?

No. Week one equals the starting weight, and the first percentage increase appears in week two.

Is the percentage applied to the starting weight or the previous week?

It is compounded from the previous week's unrounded calculated value, so the absolute increase can grow over time.

Can I enter a negative percentage for a deload?

No. Negative increases return an invalid-input error because this calculator is specifically for progressive overload.

Does the calculator use kilograms or pounds?

It preserves whichever unit you use for the starting weight. Keep the same unit when interpreting every planned value.

What should I do if my gym cannot match the exact weight?

Round to an available equipment increment and record the actual load. The calculated schedule is a planning reference.

What does an API request cost?

Each API request uses the published base price of $0.002. You can also run the calculation in your browser on this page.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/fitness2/progressive-overload-plan

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/fitness2/progressive-overload-plan \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"starting_weight":100,"weekly_percentage_increase":2.5,"weeks":4}'
{
  "starting_weight": 100,
  "weekly_percentage_increase": 2.5,
  "weeks": 4
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "fitness2.progressive_overload_plan",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →