Opening scene
Now we're putting the section's five pieces together and writing a twelve-week plan.
Let me say two things up front; both of them make this plan unusual.
First: this plan contains two deliberate lapses. One week, and two weeks.
Why? Because a sample plan that runs twelve weeks without a single break isn't a realistic sample plan. In Y1.75 I said that a lapse is a certainty. So it has to be in the sample plan too.
Second: this plan doesn't get harder every week.
The load drops in the fourth, eighth, and twelfth weeks. And that's not a concession; it's the plan's structure.
Today we build that structure, and you'll see the twelve weeks week by week.
What this lesson covers
First we'll count the plan's five inputs. Then we'll build the block structure; three blocks, four weeks. After that we'll define the deload week and you'll see why it's mandatory. Then we'll separate what changes between blocks from what stays fixed. Next I'll write out the twelve weeks week by week. Then you'll see the two deliberate lapses and how the protocol kicks in. After that we'll place the measurement points. At the very end I'll tell you how to adapt this example to your own log. We'll work through sixteen examples. By the end of the lesson, you'll be able to write your own twelve weeks.
Starting point
This plan uses the output of the section's five lessons.
From Y1.71: frequency, duration, and volume per main skill.
From Y1.72: the measurement window; at least three measurement points.
From Y1.73: the recovery table.
From Y1.74: the weekly distribution; light, moderate, hard.
From Y1.75: the lapse protocol.
And two new concepts.
Mechanism
Block structure: three blocks, four weeks
The twelve weeks are split into three blocks, and each block is four weeks.
Inside each block it looks like this: three weeks of rising load, one deload week.
Why this structure? There are two reasons.
The first reason is recovery. In Y1.74 we placed recovery inside the week; here we're placing it at the block scale too. After three weeks of rising load, one deload week leaves room for accumulated fatigue to clear.
The second reason is measurement. From Y1.72: a trend needs at least three measurement points. Three blocks give three measurement points.
The deload week
The deload week isn't a lapse. It's planned, and its content is specific.
What happens? Frequency stays the same, intensity drops.
Concretely: all three sessions are at the light or moderate level. No hard session.
And it has one more job: the deload week can double as a measurement week.
Why? From Y1.63: measurement is taken in a rested state. A block's third week is the week you're most tired; the fourth week is the right place for deload and measurement.
So the deload week does three jobs: recovery, maintenance, and measurement.
This is the block-scale version of the light session's three jobs from Y1.74.
What changes between blocks
What changes is the main skills and the maintenance items.
What stays fixed is the weekly distribution, the session template, and the log format.
Separating this matters. You're not building a new system in every block; you're only changing what's in the slots. This is the twelve-week-scale counterpart of the slot idea from Y1.45.
And one rule: a main skill stays the same for at least one block — that is, for four weeks.
Why? From Y1.72: a trend needs three measurement points, and within four weeks you can get at least two of them. Someone who changes their main skill every week can't see a trend in any of them.
Twelve weeks, week by week
Setup: three sessions a week, the thirty-minute template. From Y1.68. Distribution: one hard, one moderate, one light. From Y1.74.
First block, weeks one through four. Main skills: the torso line and balance.
Week one is a measurement week. One exploration session; the four comparisons from Y1.36 and the four numbers from Y1.50. The other two sessions are at the light level and set aside for finding your setup.
Week two is the first real week. The hard session is the torso line; Ardha Uttanasana at your own hand height. The moderate session is balance; Vrksasana at your own support step. The light session is maintenance and technique; the wrist sequence, reading the sole, the scapular slide.
Week three is the same structure, with one variable increased. A single one from Y1.65; in the torso line, hand height drops one level.
Week four is deload. Three sessions, no hard one. And one short measurement: leak-free time for the torso line, balance time.
Second block, weeks five through eight. Main skills: arm support and hinge range. Maintenance: balance.
Week five is the new main skills' first week. The load starts one level low; a new main skill always starts low.
Week six is an increase. And week six is also the second measurement point; one short measurement within the block.
Week seven is an increase.
Week eight is deload and measurement.
Third block, weeks nine through twelve. Main skills: prone extension and the single-leg hinge. Maintenance: the wrist and the torso line.
Week nine is the start, at low load.
Week ten is an increase.
Week eleven is an increase.
Week twelve is deload and the third measurement point.
That's the skeleton. Now we place the two lapses.
Two deliberate lapses
The first lapse is in week three. One week; a busy period at work.
The protocol kicks in: the first situation from Y1.75. One week or less; pick up where you left off, do the first session at the moderate level.
Result: week four was going to be the deload week, but week three already went by empty. There are two options.
First option: make week four a normal increase week and move the deload to week five. But week five is the start of a new block and already starts at a low load; so the deload happens on its own.
Second option: do week four as deload, as planned, and accept the loss of one week.
In this plan I'm applying the first option. Reasoning: week three already served a deload function, and week five starts at a low load. So two deloads would come back to back, and that's too much.
Notice: this is a decision, and it has a reason. A principle repeated since Y1.29.
The second lapse is in weeks nine and ten. Two weeks; a trip.
The protocol kicks in: the second situation from Y1.75. Two to four weeks; the return dose, half the weekly volume, back to the previous level within two weeks.
Result: week eleven becomes a return week. Volume is halved, the step is one level lighter, and the order starts from control and balance.
Week twelve brings the volume back, and the measurement is taken.
The honest state of the measurement points
Now there's a problem, and I'm not hiding it.
The measurement in week twelve is taken right after a return week.
So those numbers aren't fully comparable with week six's numbers. From Y1.63: measurement conditions have to stay constant.
What do you do?
The measurement is taken, but a note goes into the log: taken right after a return week.
And a recommendation is added: take one more measurement two weeks later.
So instead of three measurement points, you end up with four, and the fourth one falls in week fourteen.
This is a consequence of the plan breaking down, not a flaw. When a real plan breaks down, the measurement calendar shifts too; recording that is better than acting as if it hadn't shifted.
Adapting this example to yourself
Four steps.
The first step is frequency and duration. From Y1.71: look at your own real week. It might not be three sessions of thirty minutes; two sessions of twenty minutes is also a plan.
The second step is the main skills. Look at your log and find the addresses that repeat; the three inputs from Y1.64. The six main skills I chose are my example; your log may show something different.
The third step is the block structure. Three weeks of increase, one deload week works for most people. If your recovery table keeps breaking down, switch to two weeks of increase, one deload week.
The fourth step is adding the lapse protocol to the plan. The three situations from Y1.75, one page.
And a warning: a plan is a document, not a contract. If you've executed half the plan by the end of twelve weeks, that's not a failure; that's most plans' real execution rate.
Reading the examples
Master layer
Now let's refine this a bit.
First: the three-increase-one-deload structure is common, but it isn't a rule. For someone whose recovery table breaks down often, two-increase-one-deload is more suitable; for someone who recovers fast and works at low load, four-increase-one-deload can also work. The structure is adjusted to the person, and the input for that adjustment is the table. So the structure is an assumption, the table is a measurement; the measurement corrects the assumption.
Second: having the deload week double as a measurement week is an elegant solution, but it has a cost. Because the load is low that week, some measured capacities come out a little higher; endurance measurements especially. So the numbers taken in the deload week can come out systematically a little high. This isn't a problem, because every measurement is taken under the same condition; as long as the condition stays constant, a systematic bias doesn't distort the comparison.
Third: the second lapse shifting the measurement calendar is this lesson's most realistic part, and I put it into the plan on purpose. It would have been easier to write a clean sample plan, and it would have been less useful. Because a person's real plan will break down, and at that moment they need an example in hand; an unbroken example says nothing at that moment. A teaching material's realism is measured by how closely it resembles the conditions it will be used in.
Fourth, and the finest point: this plan works six main skills across twelve weeks, and that doesn't cover all nine sections you learned in the course. That's a deliberate choice. By the rule in Y1.64, a session has at most two main skills, and by the rule in Y1.71, each one needs two sessions; that arithmetic leaves no room for more than six main skills. So the plan doesn't work everything you've learned at the same time, and it shouldn't. By the time a course ends, the material you have on hand is more than fits into one twelve-week plan; keeping what doesn't fit in maintenance and bringing it into the main-skill slot in turn is how you use that material over time.
Common mistakes and misconceptions
Common mistakeFirst mistake: a good plan gets a little harder every week.
Raising the load gradually and lowering it at set intervals is a common practice; low-load periods leave room for accumulated fatigue to drop. The deload week isn't a concession — it's the plan's structure.
Common mistakeSecond mistake: you don't practice in the deload week.
In the deload week, frequency stays the same, intensity drops. That week does three jobs: recovery, maintenance, and measurement; when you don't practice at all, you also lose the habit and the maintenance stimulus.
Common mistakeThird mistake: changing the main skills every week provides variety.
A trend needs at least three measurement points, and a main skill stays the same for at least one block — that is, four weeks. Someone who changes it every week can't see a trend in any capacity.
Common mistakeFourth mistake: the plan is a contract and deviations are failures.
A lapse is a certainty in a twelve-week plan, and the protocol exists for exactly this. Having executed half the plan by the end of twelve weeks is a common outcome, and it doesn't block progress.
Practice
Keep in mind
The twelve weeks split into three blocks, and each block consists of three weeks of increase and one deload week.
In the deload week, frequency stays the same, intensity drops; that week does the jobs of recovery, maintenance, and measurement together.
Between blocks, the main skills and the maintenance items change; the weekly distribution, the template, and the log format stay fixed.
A main skill stays the same for at least one block; someone who changes it every week can't see a trend in any capacity.
Lapses are built into the plan, and the shift in the measurement calendar isn't hidden; when the condition changes, the number is still taken, but the condition is written into the log.
Bridge to the next lesson
Your plan is ready, and you can start running the twelve weeks.
Two lessons remain in the section.
The next lesson is a skill check. You'll see what you've learned across twelve sections not as a list, but as things you can do.
And that check isn't a test; it's an inventory. Because this course's output isn't a pile of knowledge, it's eight or ten tools and the habit of using them.
The check asks whether those tools are in your hands. And every item that comes up missing is a candidate main skill for your next twelve weeks.