Language and EF Systems Aren’t Built During Breaks. They’re Built in Protected Time Blocks.

There’s a quiet agreement many school clinicians make with themselves every year:

“I’ll build my system this summer.”
“Once things calm down after evaluations, I’ll map it out.”
“Over winter break I’ll finally organize everything.”
“Next year will be the year I get ahead.”

And then summer fills with life.
Breaks disappear into recovery.
The school year starts fast.
Referrals pile up.
And you’re back to customizing sessions week-to-week.

This isn’t a motivation problem.

It’s a design flaw.

Language and executive functioning systems aren’t built in leftover time. They’re built in protected time blocks that are intentionally engineered into your calendar.

If you’re analytical, strategic, and serious about building something sustainable, you need more than inspiration. You need a Master Plan protocol that respects the realities of school schedules and cognitive load.

Because here’s the uncomfortable truth:

If you don’t schedule asset-building like it’s part of your job, it will never feel like it is.

Why “I’ll do it during break” doesn’t work

Ask any skilled writer about the painful beginning, when they sit down in front of a blank page.

Prolific author Paulo Coehlo said it best: “Before I write, I have to suffer”.

What he shared was that often when he’s done some of his best work, he’s had a period of painful procrastination and fumbling around before he got started.

He’s been able to push through because he blocked out time to stick with it long enough to get to the finish line.

Steven Pressfield refers to this as the “resistance”.

In education, we often think of this as “transition” time when you go from one task to another (and we often observe our students struggle with it on a daily basis).

When you limit creative work to short time periods, you aren’t sticking with it long enough to work through the “resistance” and be productive.

As a result, you stop and start again repeatedly throughout the year.

What the Master Plan protocol does differently

The simple solution to the “resistance” problem is that you need to give yourself time to get into a flow and start producing.

Instead of frantically cramming it into breaks or waiting for the perfect week that’s never coming, you create protected time you can do consistently right now.

The Master Plan protocol is strategic planning structure that breaks system-building into:

A 12–18 month architectural vision
90-day strategic phases
2-week protected execution cycles

It acknowledges something most clinicians underestimate:

You are not trying to get more efficient at therapy.
You are trying to build infrastructure alongside therapy.

That requires a different kind of planning.

Here are some principles of executing a Master Plan.

Design the 12–18 Month Architecture

Before you block time, you need direction.

Ask yourself:

If I fast-forward 18 months, what do I want my clinical system to include?

Not abstract goals like “be more organized.”

Concrete architecture:

Defined clinical containers (like my Essential 5 or EF Stack)
At least 2–3 stable protocols inside each core container
Student-facing routines that embed EF supports
A small stack of teacher-facing scaffolding tools
Clear documentation language for consultative services

You don’t build it this month in a frantic sprint.

You build toward it.

Break It Into 90-Day Strategic Blocks

You do not build six containers at once.

You choose one focus for the next 90 days.

Examples:

Quarter 1: Build and stabilize one vocabulary/word-level container.
Quarter 2: Create two sharable assets for that container.
Quarter 3: Pilot a consultative model with one teacher using existing assets.

Each 90-day block has one strategic priority.

This prevents two common traps:

The summer overhaul fantasy
The endless micro-optimization loop

You’re not trying to fix everything.

You’re advancing one layer at a time.

Create a 2-Week Task List

The two-week task list is a to-do list that lists specific actions you’re doing to do each day for the next two weeks. I have a Google doc I periodically update that maps out what I’ll do each day, and I aim to have it go two-weeks out.

This is how I avoid waking up and fumbling around trying to decide what to work on each day, and it’s also how I mitigate against forgetting something immediate I need to address.

It’s also literally how I sleep at night, because without it I’d lie awake with my head spinning if I don’t capture things in an easy-to-locate and update document.

Most people make the mistake of writing a to-do list without thinking long-term, which means they start with the most immediate things and push off their long term goals.

But when you define your 12-18 month and 90 day goals FIRST, you can put your long-term tasks on your two-week task list before the immediate fires you need to put out.

I also have a couple things I copy and paste on my task list every day or certain days of the week because they’re part of my ongoing habits.

There have been times when I have something unexpected come up, and the disruption in my routine sometimes makes me forget something I’d normally remember to do with my normal environmental cues.

The task list reduces the chance that I’ll forget part of my routine.

Schedule Protected Time Like It’s a Service

Protected time cannot be “if I finish early.”

It must be:

A recurring calendar block
Small enough to sustain (Ideally 45–90 minutes-but smaller time blocks can work)
Non-negotiable unless there is a true emergency

If you don’t treat asset-building as real work, no one else will either.

When you build systems in protected blocks instead of in emotional bursts, you stop starting over.

Your work compounds.

You’re not redesigning therapy every summer.

You’re layering onto what already exists.

When you have:

Defined containers
Stable protocols
Sharable assets
Consistent documentation language

You can experiment with:

Consultative blocks
Teacher coaching cycles
Collaborative in-class implementation
Student self-monitoring pilots

The Real Shift

Most clinicians assume they don’t have time to build systems.

But the more accurate statement is:

They haven’t built a structure that protects the time required to build systems.

The Master Plan protocol doesn’t add more to your plate.

It organizes your ambition.

It acknowledges that sophisticated systems are built gradually—through repeated, protected execution—not through bursts of motivation during breaks.

If you want to start small, here’s your first move:

Define one 90-day system goal.
Identify one asset you can build in the next 2 weeks.
Schedule one protected 60-minute block on your calendar.

Not during break.

Not “if things calm down.”

I show clinicians how to build language therapy assets using the Essential 5 framework in Language Therapy Advance Foundations, and you’ll learn how to use the “EF Stack” to integrate executive functioning in The School of Clinical Leadership.

But in order to make either of those frameworks possible to implement, you’ve got to block out the time to make it happen, which is what the Master Plan helps you do.

Here’s a breakdown of how the Master Plan works in action:

This video was taken from the School of Clinical Leadership, my program that shows school clinicians how to create and execute an executive functioning implementation for both direct intervention, and across their school team.

It’s important to note here that you do NOT need to be a school administrator to have influence across your team and in your building, and in the School of Clinical Leadership, I show you how that’s possible. The Master Plan is just one tool that makes it happen.