A one-day sub plan just needs to survive a single period: seating chart, an activity, an emergency contact number. A long-term absence, parental leave, a medical leave, a semester abroad, is a different job entirely. You're not writing a plan for a stranger to improvise from for one day. You're handing your class, your pacing, and your relationships with 150 students to someone else for weeks, and you have to do it before you leave, usually while also dealing with whatever caused the leave in the first place.
The binder has to answer questions you won't be there to answer
A one-day sub can text you if something's unclear. A long-term sub often can't, or shouldn't have to for every small thing. The binder needs to pre-answer the questions that would otherwise come to you:
1. The full pacing calendar for the length of the absence, not just "keep going in the textbook", specific dates, specific lessons, with built-in flex days because plans slip
2. Grading policy and rubrics already in hand, what late work policy applies, how group work is scored, so the sub isn't inventing your grading philosophy from scratch
3. A one-page profile of the class, not individual students, who needs a seating accommodation, which two students shouldn't be paired, what the daily routine looks like from bell to bell
4. Contact protocols, who the sub escalates to for a behavior issue, a parent email, or a scheduling conflict, since it usually shouldn't be you
Write the first two weeks in full detail, then a lighter outline after that
Nobody can fully script six weeks of lessons before they leave, the class won't stay exactly on the pace you predicted, and trying to script everything in exhaustive detail delays your actual departure. Write the first two weeks as complete, ready-to-teach lesson plans. After that, write a lighter unit outline, goals, key activities, assessment points, that a long-term sub or your department can adjust in real time as the actual pace becomes clear.
Our [training manual writer](/training-manual) is built for exactly this kind of handoff document, describe your classroom routines, grading approach, and escalation protocols once, and it drafts the structured reference document a long-term sub actually needs on day one, instead of you writing it from a blank page during the same week you're preparing to leave.
Build in a check-in point, even a light one
If your leave is long enough, plan one structured check-in, a department colleague observes a class midway through and reports back, or the long-term sub sends a short written update at an agreed date. This isn't about micromanaging from afar. It's the same idea as a two-week sub plan versus a six-week one: an open-ended "let me know if anything comes up" invites nothing, while a specific date and a specific two-question update actually gets used.
What belongs in the binder itself
- Pacing calendar with built-in flex days
- First two weeks fully planned; remaining weeks as a unit outline
- Grading policy, rubrics, and current gradebook access instructions
- One-page class profile: routines, seating notes, known accommodations
- Escalation contacts for behavior, parents, and scheduling
- A note about what NOT to change, any accommodation, grouping, or routine that's load-bearing for a specific student
A long-term sub binder is real work up front, but it's the difference between a class that keeps moving coherently while you're out and one that has to be partly rebuilt when you get back. The two-week-detailed-plus-outline structure is what makes it possible to actually finish the binder before you leave, instead of it becoming the thing you never quite got to.
