{"id":26951,"date":"2026-08-18T05:00:00","date_gmt":"2026-08-18T12:00:00","guid":{"rendered":"https:\/\/www.nwea.org\/blog\/?p=26951"},"modified":"2026-08-14T09:41:12","modified_gmt":"2026-08-14T16:41:12","slug":"is-your-school-schedule-built-for-mtss-or-just-around-it","status":"publish","type":"post","link":"https:\/\/www.nwea.org\/blog\/2026\/is-your-school-schedule-built-for-mtss-or-just-around-it\/","title":{"rendered":"Is your school schedule built for MTSS, or just around it?"},"content":{"rendered":"

\"\"In most schools, multi-tiered system of supports (MTSS) conversations quickly turn to the visible parts of the system: intervention blocks, data meetings, progress monitoring, team routines, student support plans, extension opportunities, and enrichment pathways. Those pieces matter. They give shape to the work and help teams respond more intentionally to learner needs across the full continuum. But there is another part of MTSS that often hides in plain sight: the schedule.<\/p>\n

The schedule is more than a container for the school day. It is one of the clearest signals of what the system has actually protected. It shows whether every learner is treated as entitled to strong Tier 1 instruction, whether teams have time to make decisions, whether learners have time to receive support, extension, enrichment, and feedback without losing access to that instructional anchor, and whether movement across pathways is built into the rhythm of the week or left to individual effort.<\/p>\n

Your school schedule is critical<\/h2>\n

If you have ever left a team meeting thinking, \u201cThat was exactly the right decision,\u201d only to watch the response happen too late, too unevenly, or not at all, you have seen why a daily schedule built for MTSS matters. Many schools experience some version of this moment. The team looks carefully at the evidence, names what learners need next, and agrees on a thoughtful instructional response. Everyone leaves with clarity. Then the school day takes over.<\/p>\n

The response may depend on which teacher can find time to plan it, which classroom has a flexible block soon enough, or which student can receive support without missing something else that matters. That \u201csomething else\u201d is often Tier 1 instruction<\/a>, which should never become the thing students lose in order to get help. When that happens, the problem is usually not commitment. It is not that teachers do not care, teams are not working hard enough, or leaders have failed to prioritize MTSS. More often, the schedule has not been designed to support the work the system is asking people to do.<\/p>\n

In a multi-tiered system of supports, or MTSS, time is not just a logistical constraint. Time is infrastructure. The schedule either makes instruction, collaboration, support, extension, enrichment, and movement possible, or it makes those things harder to sustain.<\/p>\n

Most MTSS implementation problems do not announce themselves as scheduling problems at first. They show up as inconsistent intervention, delayed response, weak follow-through, fixed groups, overburdened PLCs, students missing core instruction to receive support, or extension and enrichment becoming informal opportunities rather than intentional parts of the system. Underneath many of those patterns is a practical design question: has the system created protected space for the work it says matters, or has it added new expectations to a schedule that was never built to hold them?<\/p>\n

That shift can change the leadership conversation. Instead of asking only, \u201cWhere can we fit an intervention block?\u201d leaders begin asking, \u201cWhat does our schedule make possible for learners and educators?\u201d Instead of treating collaboration time as a meeting slot, leaders ask whether that time is close enough to instruction to influence what students experience next. Instead of celebrating the existence of a flexible block, leaders ask whether that block actually protects access to support, extension, enrichment, feedback, and movement across pathways.<\/p>\n

Time reveals what the system has actually designed<\/h2>\n

It is easy to talk about MTSS as a set of practices: evidence use, intervention, progress monitoring, collaborative planning, flexible grouping<\/a>, and movement across levels of support. But those practices do not live in a binder, on a slide, or in a decision rule. They live in minutes, blocks, meetings, transitions, coverage decisions, and protected instructional time.<\/p>\n

If teams are expected to use evidence well, they need protected time to interpret it. If learners are expected to receive timely support, meaningful extension, authentic enrichment, or targeted feedback, they need a place in the instructional day to experience it. If movement is supposed to happen across pathways, teams need review points where they can ask whether a response should continue, shift, fade, intensify, extend, enrich, or be paired with something different.<\/p>\n

Without that protected time, strong decisions become fragile. A team may know exactly which students need a different representation, scaffold<\/a>, feedback moment, extension task, or enrichment opportunity, but if the schedule does not create space for planning and response, the decision depends on individual improvisation. One teacher may be able to act quickly while another has to wait. One learner may receive support while another misses the window when the support would have mattered most. One learner may be ready for deeper application, but enrichment may never become more than an optional add-on.<\/p>\n

That is why time deserves to be studied as evidence. The schedule shows where the system has protected its priorities and where it is still asking people to make MTSS work around the edges.<\/p>\n

You may have seen this happen in a weekly team meeting. A team analyzes exit tickets on Friday and identifies a need for short-cycle support, but the next common planning meeting is not until the following Thursday. By then, the class has moved into new content, the support is less connected to the original learning, and students who needed a timely bridge are now carrying confusion into the next part of the unit. The decision was sound. The schedule weakened its usefulness.<\/p>\n

The same thing can happen with extension and enrichment. A team may notice that several learners are ready for deeper application, but if there is no shared flexible time for that challenge to happen without pulling students away from new Tier 1 instruction, enrichment becomes informal. It may go to the students whose teacher has time to prepare it, or to the students who finish early, rather than being treated as a deliberate pathway within the system.<\/p>\n

This is why schedule design is not separate from equity or access. When time is inconsistent, learners experience the system differently based on classroom, grade level, adult capacity, or competing demands. When time is protected, the system has a better chance of making responsiveness ordinary rather than exceptional.<\/p>\n

Common planning time is the engine and WIN time is the runway<\/h2>\n

In many schools, two kinds of time carry much of the practical weight in MTSS: the time educators use to design responses and the time learners use to experience those responses. Common planning time and WIN time<\/a> are often discussed separately. In practice, they are much stronger when they are designed together.<\/p>\n

Common planning time is the protected block where teams can clarify the Tier 1 learning destination, examine current evidence, anticipate access points and readiness signals, design connected support, extension, and enrichment pathways, and name when they will review the response. PLC practice is what teams do inside that time. That distinction matters. A schedule can create a meeting without creating the conditions for disciplined instructional decision-making across the full continuum of learner needs.<\/p>\n

WIN time, often described as \u201cWhat I Need\u201d time, is the flexible instructional block where learners receive support, extension, enrichment, practice, feedback, or application connected to current learning. When WIN time is designed well<\/a>, it is not simply an intervention period, a study hall, or a place for students to finish work. It becomes a runway for evidence-informed responses.<\/p>\n

That connection to Tier 1 is not a minor detail. WIN time should not operate as a separate track beside grade-level instruction. It should help learners access, extend, enrich, apply, or deepen the same Tier 1 standards, concepts, skills, texts, problems, and tasks that anchor the current unit of study. When WIN time is disconnected from Tier 1, it can easily become a parallel system. When it is connected, it becomes a way to strengthen access to the learning every student is entitled to experience.<\/p>\n

This is where the two blocks need each other. Common planning time without flexible instructional time can produce thoughtful plans that are difficult to enact, whether those plans involve support, extension, enrichment, feedback, or application. WIN time without strong PLC practice can become a general activity block. When the two are aligned, teams have time to make decisions and learners have time to experience the response.<\/p>\n

A helpful rhythm is simple: plan, respond, review, and adjust. During common planning time, the team clarifies the Tier 1 standards, concepts, skills, texts, tasks, or learning destination all students are working toward and studies evidence that is close enough to instruction to matter. During WIN time, students experience the support, extension, enrichment, feedback, or application the team designed in direct connection to that Tier 1 learning. At the next planning point, the team reviews what happened and makes the next decision. The power is not in any single meeting or block. The power is in the rhythm connecting them.<\/p>\n

That rhythm also helps teams avoid a common trap: asking every data source to answer every question. Universal screeners<\/a>, benchmark assessments, student work, exit tickets, learner reflections, and progress monitoring can all matter, but they do not serve the same purpose. Some evidence is best for immediate instructional decisions. Other evidence is better for studying larger patterns over time. Common planning time becomes more useful when teams are clear about which evidence belongs in the decision cycle in front of them.<\/p>\n

If a team is deciding what students should experience during WIN time tomorrow, student work from the current lesson may be more helpful than a benchmark report from several months earlier. If leaders are studying whether certain groups of learners are consistently overrepresented in support pathways, underrepresented in extension opportunities, or missing from enrichment pathways, longer-cycle evidence may be the better tool. Both matter. The leadership move is to match the evidence to the decision.<\/p>\n

WIN time should support movement across the full continuum<\/h2>\n

Flexible time only strengthens MTSS when it is designed for movement. Without that clarity, WIN time can quietly recreate fixed placement inside a schedule that looks flexible from the outside. A support group formed for one access point can become a standing intervention group. An enrichment group formed around one readiness signal can become a fixed advanced group. Students may move to different rooms or groups, but the pathway can become more stable than the evidence that created it.<\/p>\n

In a coherent MTSS design, groups are temporary responses tied to a Tier 1 learning purpose. A learner may need short-cycle support for a current concept, an opportunity to extend thinking with greater complexity, or an enrichment pathway that invites authentic application of the same learning. Those responses should not become labels, and they should not pull students away from the instructional standards they are entitled to learn. They should remain connected to current evidence, current Tier 1 learning, and planned review points.<\/p>\n

A few questions can help leaders and teams examine whether WIN time is supporting movement:<\/p>\n