# Add a week to an AI training plan without rebuilding it

> TRAI adds new days to an existing plan and builds only those days, rebuilds a single day, refuses to overwrite completed workouts and blocks edits that would empty a plan. Example prompts and limits.

*Author: Trainera Team  |  Published: 2026-10-11  |  Reading time: 8 min*

## How do you add week 5 to an AI training plan without rebuilding weeks 1-4?

In Trainera you ask TRAI, the in-app AI assistant, to add new days to the plan. The plan engine builds only the new days and appends them after the existing ones, so every day the client already has stays exactly as it is. If one day is wrong, TRAI can rebuild that single day instead, and it refuses to rebuild a day the client has already started or completed.

This post is about plan maintenance: the changes coaches make in weeks 3, 6 or 10, after the first version is live. First-time generation is covered in [our AI workout plan generator guide](/blogs/ai-workout-plan-generator).

## Which kinds of plan edits can TRAI make?

There are five, and each one touches only what you asked about.

| What you want                              | What TRAI does                                                          | What stays untouched                                   |
| ------------------------------------------ | ----------------------------------------------------------------------- | ------------------------------------------------------ |
| Add N new days to a client's assigned plan | The engine builds only the new days and appends them after the last day | Every existing day, including logged results           |
| Add N new days to a plan in your library   | Same, on the library template                                           | The existing days of the template                      |
| Add a workout you already saved            | Copies the saved workout into the plan exactly as saved                 | Everything else in the plan                            |
| Rebuild one day                            | The engine rebuilds that one day from your description                  | Every other day; a started or completed day is refused |
| Small edit of an existing day              | Swaps, adds or removes an exercise, or changes sets and reps            | The rest of the day and the plan                       |

For trainers, each of these goes through a confirm card ("Yes, do it" / "No") before anything is saved. Changes to an assigned plan edit the client's own copy; the template in your library stays unchanged. Replacing the whole plan is a separate action: a new plan assigned to the client replaces their current active plan of that type, and TRAI confirms that first.

## Why add days instead of regenerating the plan?

Because the first weeks carry information you do not want to lose.

Once a client has trained through four weeks, their plan holds the logged sets on finished days and exercises they now know how to perform. Regenerating from scratch throws that structure away and gives the client a new set of movements to learn. Most progression models build on what came before; the [ACSM position stand on progression models in resistance training](https://pubmed.ncbi.nlm.nih.gov/19204579/) is the standard reference trainers cite for changing load, volume and exercise selection over time. Adding days fits that way of working. For background on why, see [progressive overload explained](/blogs/progressive-overload-principle-building-muscle-strength).

There is also a practical reason. When TRAI adds days, the server reads the current plan itself and appends to it, so this works even for long plans, and existing days are preserved automatically.

## How do you phrase a request for week 5?

Name the client, say how many new workout days you want and describe what they should train.

New days are added as workout days, without rest days in between, so give the number of sessions rather than calendar days. Example prompts (examples only, adapt them):

* Example: "Add 4 new days to Client A's current plan: same upper/lower split as weeks 1-4, 50 minutes each, keep the 5-minute bike warm-up."
* Example: "Add 3 days to my 'Beginner full body' library template. Make them a bit harder than the existing days and use dumbbells only."
* Example: "Put my saved workout 'Hotel room circuit' into Client B's plan as the next day."
* Example: "Rebuild day 9 of Client C's plan. She said the lunges hurt her knee, so make it a lower-body day with no lunges, squats or jumps."
* Example: "On day 12 of Client D's plan, swap the barbell bench press for dumbbell bench press and change it to 4 sets of 8."

The engine reads your instructions as free text: split, day kinds, session order, implements to use or avoid, session length and exercises you want. It does not take a numeric progression rule such as "add 2.5 kg to every main lift". If you want exact sets, reps or loads on the new days, add the days first and then ask for a small edit of those days with the numbers you want, or dictate the exercises yourself.

## What stops an edit from wiping a plan?

A guard in TRAI refuses any edit that would leave a plan or workout with no content.

Some edits replace the full content of a day list, a nutrition plan's days or a workout's exercises. If such an edit would erase every workout, meal or exercise, TRAI blocks it and tells you nothing was changed. Adding, reordering or shortening is allowed as long as real content remains. On top of that, TRAI never deletes anything in the app: deletes and removals are blocked, and it tells you to do them yourself.

| Safeguard                                   | What it prevents                                             |
| ------------------------------------------- | ------------------------------------------------------------ |
| Add-days tools append, never rewrite        | Losing weeks 1-4 when you ask for week 5                     |
| Started or completed days cannot be rebuilt | Overwriting the client's logged results                      |
| Empty-content guard                         | An edit that would leave a plan with no workouts or no meals |
| Confirm card for trainers                   | Any data change you did not approve                          |
| No deletes in-app                           | Plans, clients or days removed by the assistant              |

The full list of these limits is in [what TRAI won't do](/blogs/trai-what-it-wont-do), and the safety design in [an AI assistant that cannot delete your data](/blogs/trai-ai-assistant-cannot-delete-data).

## Can solo clients extend their own plans the same way?

Yes. Clients who train without a trainer or gym, on Client Pro or Premium, have TRAI with the same plan engine.

* **Adding days** to their training plan saves directly, without a confirmation step, because nothing is overwritten.
* **Rebuilding one day** asks for confirmation first, because it overwrites that day and resets its progress.
* **Replacing the whole plan** asks first, because the old workouts and their progress are cleared.
* **Nutrition:** TRAI can add days after the last day of the active nutrition plan and keeps the plan's calorie targets, goal and title. Saving a new nutrition plan replaces the active one, so that is confirmed first.

When a client who already has a plan asks for new workouts without saying where they should go, TRAI offers three choices: keep the current plan, add the new workouts to it, or replace it. Details for clients are in [TRAI on Client Pro vs Premium](/blogs/trai-solo-client-pro-vs-premium).

## What about editing a client's nutrition plan?

For trainers, TRAI edits the client's copy of an assigned nutrition plan by reading it first and sending back the complete edited version.

That edit syncs into the client's diet tracker, and the empty-content guard applies: an edit that would remove every meal is blocked. The step-by-step day appending described above, where the engine builds only the new days, is a training-plan tool for trainers. For larger nutrition changes, building a new plan and assigning it (confirmed first) is often the cleaner route.

## How many requests does plan maintenance use?

One request per message, and a plan build inside TRAI does not spend the separate Generate-button quota.

| Plan                                 | TRAI requests per month | Typical maintenance use                                   |
| ------------------------------------ | ----------------------- | --------------------------------------------------------- |
| Trainer Starter ($19.99)             | 20                      | A new block of days for a handful of clients a month      |
| Trainer Pro ($49.99)                 | 50                      | Monthly extensions for most clients plus single-day fixes |
| Trainer Business ($99)               | 100                     | Regular extensions across a larger roster                 |
| Trainer Enterprise (custom)          | 200                     | High-volume teams                                         |
| Client Pro / Premium ($5.99 / $6.99) | 40 / 90                 | Solo clients extending their own plans                    |

The "typical use" column is a planning aid, not a measured figure. Prices are US list prices and differ by country on [trainera.fit/pricing](/pricing). Clicking Yes or No on a confirm card does not cost an extra request, and a run that fails is refunded. A single request can take at most 10 agent steps and 20 tool calls, and a build takes up to half a minute. More in [TRAI request limits explained](/blogs/trai-request-limits-explained).

## Common mistakes when extending AI plans

* **Asking for "another week" without a number.** Say "4 new workout days". Added days do not include rest days.
* **Rebuilding a day the client already did.** It will be refused. Add a new day instead, or rebuild a future day.
* **Using "replace" when you mean "add".** Replacing clears the old content; adding keeps it.
* **Expecting exact load progression from free text.** Add the days, then edit sets and reps explicitly.
* **Forgetting deloads.** The engine builds what you describe. If week 5 is a lighter week, say so; see [deload weeks and active recovery](/blogs/deload-weeks-and-active-recovery).

## A monthly routine for keeping AI plans current

This order keeps edits small and the client's history intact.

1. Check which days the client has finished and how they felt about them (from your own check-ins and conversations).
2. Fix any upcoming day that no longer fits with a single-day rebuild.
3. Add the next block of workout days with clear instructions.
4. Adjust exact sets and reps on the new days with small edits.
5. Read the confirm card each time: right client, right plan, right number of days.

Activity totals are worth a glance when you add days; the [WHO recommendations](https://www.who.int/news-room/fact-sheets/detail/physical-activity) put muscle-strengthening at 2 or more days a week for adults.

_See how plan building and editing work in the [Trainera trainer platform](/platform)._

## FAQ

### Can I add more weeks to an AI-generated workout plan?

Yes. Ask TRAI to add a number of new workout days. The engine builds only the new days and appends them; existing days are kept.

### Can AI change just one day of a training plan?

Yes. TRAI can rebuild one day from your description, or make a small edit such as swapping an exercise or changing sets and reps. A day the client already started or completed cannot be rebuilt.

### Will editing my client's plan change my template?

No. Edits to an assigned plan change the client's copy. The plan in your library stays as it was.

### Can the AI delete a plan by mistake?

No. TRAI cannot delete anything in the app, and it blocks edits that would leave a plan with no workouts or meals.

### Do added days include rest days?

No. Days added to an existing plan are workout days, so give the number of sessions you want.

---
Source: https://trainera.fit/blogs/trai-edit-ai-plan-add-week