# Scheduling multi-week training blocks with intentionally unplanned days

Setline · Significant Hobbies · 2026-09-20

Learn how to structure 1–16 week training blocks that accommodate life's interruptions using intentionally unplanned days and rigid Monday-based scheduling.

## Introduction: The reality of multi-week training

When embarking on a new training phase, the instinct is often to plan every single day. A spreadsheet might outline a sequence of workouts stretching out for twelve solid weeks. However, anyone who has trained consistently knows that the perfect sequence rarely survives contact with reality. Work schedules shift, travel happens, and fatigue accumulates at unpredictable rates. The traditional response to these interruptions is either to guiltily skip a day, silently shifting the entire programme forward, or to forcefully cram two sessions into one.

A more realistic approach to structured training involves scheduling multi-week blocks with intentionally unplanned days. Instead of viewing an empty day as a gap to be filled, we treat it as an explicit, structural element of the training block. By defining a programme with deliberate space, we build a system that absorbs life's interruptions without breaking the rhythm of the weeks.

This approach shifts the focus to the precise execution of the sessions that matter. It acknowledges that recovery is as integral to a programme as the working sets themselves. When we schedule training blocks, the goal is not to maximize occupied days, but to execute a planned sequence over a defined timeline. In a dedicated execution tracker like Setline, leaving days explicitly empty is a first-class feature. A scheduled block does not just accept that days will be missed; it requires you to state upfront which days are off-limits for structured training.

## The foundation: Monday-based 1–16 week programming

To implement this effectively, a training block needs boundaries. An open-ended routine without a defined start or end point often leads to stagnation. Structuring training into bounded blocks—ranging from one to sixteen weeks—is a cornerstone of effective programming.

A bounded block provides a clear horizon. It dictates that for a specific duration, you will adhere to a specific set of exercises and progression rules. When configuring a block, anchoring the schedule to a consistent starting point, such as Monday, provides a predictable weekly rhythm. A Monday-based assignment system ensures that the overall structure remains anchored to the seven-day calendar we navigate daily.

In a system like Setline, a user can define a single, named 1–16 week custom programme. By assigning custom workouts to specific days within a Monday-based week, the programme becomes a rigid scaffold. The rigidity means the plan does not silently drift. If Week 3, Day 1 (Monday) is a heavy lower-body session, it remains anchored to that Monday. This predictability is essential for managing fatigue and planning your week. Overlapping or aspirational programmes can be saved and kept in a deferred state, preventing them from polluting the active calendar.

## The role of intentionally unplanned days

An intentionally unplanned day is fundamentally different from a missed workout. A missed workout represents a failure to execute the plan; an intentionally unplanned day is the successful execution of an explicit instruction to do nothing.

When structuring a seven-day week, leaving one or two days explicitly unplanned serves critical functions. First, it provides a buffer for systemic recovery. Explicitly blank days ensure that the body has time to down-regulate. Second, unplanned days accommodate the realities of a busy life. If Thursdays are consistently unpredictable, scheduling an explicit unplanned day removes the friction of trying to force a rushed session.

In a robust execution layer, these days are definitive statements. When you explicitly leave days unplanned, you are telling the system that no structured training is expected. This distinction is vital for maintaining an honest record of execution. Missing history is never treated as missed training. If a day is explicitly unplanned, the lack of a recorded session is the correct outcome. It keeps the analytics clean and the weekly gap analysis accurate, rather than punishing the user for successfully resting.

## Calendar-correct resolution and "Today"

A common issue with automated training applications is the fluid nature of "Today". Some systems will automatically bump a missed Tuesday workout to Wednesday, silently rewriting the programme. While this might feel forgiving, it destroys the integrity of the multi-week block.

When scheduling a structured block, the calendar must be the absolute authority. "Today" should resolve the local calendar date and present exactly what was authored for that day in the current week. If Wednesday is an explicitly unplanned day, opening the execution tool on Wednesday should yield an empty state. It should not silently fall back to a bundled plan or forcefully suggest making up Tuesday's skipped session.

Calendar-correct Today resolution ensures that scheduled sessions retain their programme week and day context. If you are on Week 4, Day 3 of a 12-week block, that context must remain stable regardless of what you did on Day 2. This stability allows for accurate progression tracking. When evaluating a deterministic progression recommendation for a working set, you need to know exactly where you are in the block's timeline. The authored programme is immutable data; the calendar determines what slice of that data is presented today.

## In-session flexibility without breaking the programme

Even with strategically placed unplanned days, in-session flexibility is sometimes necessary. The key is to handle this flexibility without compromising the underlying structure of the block.

When you define a multi-week programme, the exercise and set order is immutable. It is not a suggestion; it is the authored plan. However, physical reality sometimes dictates that a planned set cannot be completed, or that you have capacity for extra work. A robust tool allows for explicit in-session changes that remain distinct from the written programme.

For instance, if a piece of equipment is unavailable, the correct action is to explicitly skip the movement or defer it using a "Do later" function. The system should record this deviation as an execution reality, leaving the authored template untouched.

Similarly, you might decide to add a session-only extra set. This should be recorded in the detailed per-set execution history preserved on the device, but it should not rewrite the programme for future weeks. The authored plan remains the baseline; the execution history reflects the reality of the day. This separation ensures that the multi-week block remains a stable reference point. Recommendations never silently change a programme, and any deviation requires explicit user input. This preserves the distinction between what was planned and what actually occurred.

## Building blocks: Copying weeks forward

Authoring a complete 16-week block from scratch can be daunting. However, training blocks are composed of micro-cycles that repeat with slight variations in volume and intensity.

To efficiently schedule these blocks, the ability to copy a week forward is invaluable. You can author the fundamental structure of Week 1—assigning workouts to Monday, Tuesday, Thursday, and Friday, while explicitly leaving Wednesday, Saturday, and Sunday unplanned. Once this foundational week is built, copying it forward populates the subsequent weeks with the same structure.

This copy-forward authoring drastically reduces the friction of programme creation. It allows you to establish the rhythm of the block—including the intentionally unplanned days—once, and then propagate it across the entire timeline. From there, you can make targeted adjustments to specific weeks without having to rebuild the weekly structure from scratch. This method ensures consistency across the block while maintaining the explicit day assignments that make the schedule predictable. Furthermore, having an enabled or paused state allows you to prepare a block in advance and activate it precisely when ready. The ability to quickly shrink or delete components means mistakes during authoring can be corrected efficiently.

## Practical Next Action

To implement this approach, define a single bounded block, perhaps four to six weeks in duration. Map out your ideal training days against a standard Monday-based week. Critically, select at least one or two days and explicitly mark them as unplanned. Author this single week as your baseline, then copy it forward to complete the block. When you begin execution, commit to the calendar: do exactly what is planned on training days, and actively do nothing on the unplanned days. Keep the plan immutable; if you must deviate during a session, log the explicit skips or extra sets without rewriting the programme itself.