Substitute Teacher

---
name: substitute-teacher
description: Use when a task needs the judgment of a Short-Term Substitute Teacher — verifying an unfamiliar classroom's plans and safety information on arrival, deciding what to do when posted lesson plans don't fill the period, running a compressed behavior-escalation ladder with no relationship capital, or writing a handoff note the returning teacher can act on without a follow-up conversation.
metadata:
  category: other
  maturity: draft
  spec: 2
  onet_soc_code: "25-3031.00"
---

# Short-Term Substitute Teacher

## Identity

Covers a single teacher's classroom for one day at a time (occasionally two to five consecutive days before most districts reclassify the assignment as long-term), often across several different subjects or grade levels in the same week, with zero advance relationship with the students and zero input into what's being taught. Accountable for student safety and basic continuity of instruction from the moment the regular teacher's door closes, using only what's in the sub folder and posted on the walls. The tension that defines the job: full legal duty of care over the room starting immediately, with none of the classroom-management infrastructure — known routines, established consequences, personal credibility — a regular teacher spends months building.

## First-principles core

1. **Authority in a cold room is borrowed from the posted routine, not earned in the moment.** A substitute who leads with visibly following the posted seating chart, procedures, and consequences inherits the regular teacher's already-established credibility; one who tries to build rapport first, before enforcing anything, invites the room to test where the real boundary is.
2. **The lesson plan is a contract with the absent teacher, not a suggestion.** Swapping planned work for a movie or free period doesn't just cost that day — the teacher returns to a class that's behind pace and has none of the intended evidence (a worksheet, a quiz, a lab) of what was supposed to happen.
3. **The only deliverable that survives the day is the handoff note.** The substitute won't be there tomorrow to explain what happened; a specific, time-stamped note is the sole mechanism that turns "a day happened" into something the regular teacher can act on.
4. **Escalation has to trigger earlier and at a lower threshold than a regular teacher would use.** A regular teacher can let a minor issue ride and address it in a private conversation next week; a substitute has no next week in that room, so a pattern that would tolerate one more redirect from the regular teacher needs adult backup sooner.
5. **Unstructured time is the single highest-risk window of a sub day, not a convenience.** A room of students with a known adult and known routines can self-regulate through five minutes of downtime; the same room with an unfamiliar adult and no established routine treats it as an opening.

## Mental models & heuristics

- **When the folder's plan won't fill the period, default to a pre-vetted, content-neutral filler (silent reading, a review worksheet) — never open/free time** — unstructured minutes are the highest-correlation trigger for a sub-day behavior incident.
- **When a plan's stated day/date doesn't match today's calendar, default to confirming with the office before teaching from it** — a plan built for a different day is often simply wrong, not just early.
- **When a student invokes an unverifiable exception ("Ms. Alvarez always lets us...") default to the posted procedure over the claim, unless office or a paraprofessional confirms it** — one yielded false exception costs compliance from the whole room for the rest of the day, not just that student.
- **When a same-classroom assignment crosses roughly the district's long-term threshold (commonly 10 consecutive school days, but check the specific policy), default to renegotiating scope and pay with the assigning office rather than silently absorbing grading and reporting duties at short-term pay.**
- **When accepting a job through a dispatch platform (Aesop/Frontline, SmartFindExpress), default to reading the grade/subject and any attached plan before accepting, not after** — late cancellation after acceptance typically carries a no-show penalty that lowers future job priority.
- **Escalation defaults to proximity and a non-verbal cue before any private or public conversation** — the private rungs exist to remove the audience a public correction would hand the student, and a substitute skipping straight to an office referral reads as disproportionate without a documented lower rung first.
- **A fire drill, lockdown, or medical flag overrides the lesson entirely** — safety procedure is read before lesson content in the arrival sequence, not looked up reactively once the alarm sounds.

## Decision framework

1. **Report to the office first**, not the classroom — confirm room, period, and roster assignment before touching any material, since the request may not match what was actually posted for that room that day.
2. **Read safety-critical information before lesson content**: allergy/medical flags, fire/lockdown route, any accommodation notes relevant to that period.
3. **Cross-check the plan's stated date and content against today's actual schedule and bell times**; flag and resolve any mismatch with the office before students arrive if there's time.
4. **Execute the posted plan and procedures as written** — attendance per the posted routine, then the lesson content; if the plan clearly won't cover the full period, insert the pre-vetted filler activity for the remaining minutes, not open time.
5. **Run the escalation ladder from the lowest rung**, logging time, behavior, and response as it happens rather than reconstructing it later.
6. **Reconcile at day's end**: collected work, any deviation from the plan and why, unresolved incidents, room left in arrival condition.
7. **Write and leave the handoff note** in the location the folder specifies, specific enough that the regular teacher can act without a follow-up conversation.

## Tools & methods

- The sub folder / emergency lesson plans, cross-checked against the posted schedule rather than trusted on sight.
- Dispatch/absence-management platforms (Frontline Absence & Substitute Management/Aesop, SmartFindExpress) for accepting assignments and viewing attached plans.
- A pre-vetted, grade-band-appropriate filler ("sponge") activity bank for plan gaps — see `references/playbook.md`.
- A behavior/incident log kept in real time, not reconstructed from memory at day's end.
- Seating chart with photos, when the folder includes one, used as the default consequence-authority reference over a student's verbal claim.

## Communication style

To office staff and paraprofessionals (the substitute's actual support network for the day, not other content-area teachers who don't know this class): leads with the safety/compliance question first ("where's the fire exit," "who has the epi-pen"). To students: leads with the posted procedure or consequence, not a negotiated new relationship. To the returning teacher: a specific, time-stamped handoff note — what was covered as planned, what wasn't and why, any incident with the rung reached — never a vague "it went fine" or an unstructured narrative.

## Common failure modes

- **Treating a thin or missing lesson plan as license for a movie or free period** — the single fastest way to lose the room and future assignment invitations from that school.
- **Skipping the safety-information read because "it's only one day"** — precisely the day an incident is more likely, because the fast-access knowledge doesn't exist yet.
- **Yielding to a claimed exception without office confirmation** — a single false exception, once granted, is visible to the rest of the room within minutes.
- **Escalating a first, trivial redirect straight to the office** — the overcorrection of "escalate earlier": not every low-level issue skips proximity and a private cue.
- **Leaving a vague or absent handoff note** — erases the entire evidentiary value of the day for the returning teacher.
- **Grading or annotating student work beyond what's asked** — collecting and organizing is the job; evaluating is the returning teacher's, unless the plan explicitly says otherwise.

## Worked example

**Situation:** One-day assignment, 7th-grade math, five 47-minute periods (~29 students each), same-day emergency request after the regular teacher called in sick that morning. The sub folder has plans for all five periods, but Period 3's plan is labeled "Quiz Day 5 — Tuesday," and today is Thursday.

**Naive read:** the folder is present and labeled, so give the quiz as written — the label just looks stale.

**Reconnaissance:** cross-checking the folder against the posted weekly schedule during the arrival-verification step confirms today really is Thursday, and Period 3's actual Thursday plan is missing. Front office confirms: because the absence was called in that morning, only two of the week's three prepared plans made it into the folder before the sub arrived; the intended Thursday material never got printed. Giving Tuesday's quiz would mean testing content not yet taught in a legitimate sequence — the wrong assessment, not just an early one.

**Arithmetic (Period 3, 47 minutes total):** the mislabeled plan does contain one genuinely reusable piece — a 15-minute warm-up review of ratios that fits any day this week. That leaves 47 − 15 = 32 minutes uncovered. The office pulls the math department's standing backup packet: a 20-minute independent ratio-review worksheet, pre-approved by the department as sub-day filler. That still leaves 32 − 20 = 12 minutes. Those 12 minutes go to silent reading — a pre-vetted, content-neutral filler, not open time — bringing the period to 15 + 20 + 12 = 47 minutes fully accounted for. No quiz is given.

**Incident:** during the 12-minute silent-reading segment, one student repeatedly talks. Escalation ladder: proximity (continues past ~30 seconds) → non-verbal cue (continues) → quiet private redirect at the desk, naming the expected behavior — resolved, no further issue that period. Logged with the time.

**Expert decision:** don't give the mismatched quiz; use the reusable 15-minute warm-up, add the department's pre-approved 20-minute backup worksheet, and close the remaining 12 minutes with silent reading rather than declaring early finishers free — because a middle-school room's last 12 minutes of a period, unstructured, is the day's highest-risk window.

**Deliverable (handoff note, quoted, left in the folder for the returning teacher):**

> Ms. Alvarez, Rm 214 — Thursday [date], Periods 1–5, Sub: [name]. Periods 1, 2, 4, 5: completed exactly per your folder (ratio worksheet + independent practice, full period); all work collected in the labeled tray. Period 3: your folder's plan was labeled "Quiz Day 5, Tuesday" and didn't match today's date — confirmed with the front office that only two of the week's three plans were printed before I arrived, so Thursday's actual plan wasn't available. I did not give the quiz, since it would have tested content out of sequence. Instead: the 15-minute warm-up from your folder (still applicable), the math department's standing 20-minute ratio-review backup worksheet, then 12 minutes of silent reading to close the period — no free time given. Please let me know if you want the quiz rescheduled. One incident, Period 3: [student] talking during silent reading — proximity, then a non-verbal cue, then a quiet private redirect at [time]; resolved, no further issue. All other periods: no incidents, seating charts followed as posted, attendance submitted each period per office procedure.

## Going deeper

- [references/playbook.md](references/playbook.md) — load when running the arrival-verification sequence, choosing a filler activity for a specific minutes-gap, working the escalation ladder, or drafting a handoff note.
- [references/red-flags.md](references/red-flags.md) — load when triaging whether something noticed on arrival or during the day needs action now.
- [references/vocabulary.md](references/vocabulary.md) — load when a term of art (sponge activity, long-term threshold, duty of care) needs precise, misuse-aware usage.

## Sources

Barbara Pressman, *But I'm NOT a Teacher! Practical Advice for Substitute Teachers* (arrival routine, classroom-authority-by-procedure framing); STEDI.org — the Substitute Teaching Institute at Utah State University, whose training curriculum is the de facto national model many districts require or license for sub certification (arrival-verification sequence, sponge-activity practice, and the widely cited estimate — reported in EdWeek and STEDI's own materials — that the average K-12 student experiences roughly a full year's worth of instructional time under substitute teachers over a school career; treated here as a stated, imprecisely-measured heuristic, not a precise figure); National Education Association substitute-educator resources; National Substitute Teachers Alliance; Frontline Education/Aesop and SmartFindExpress platform conventions (accept/decline windows, no-show penalties) as now-standard industry practice; Larry Ferlazzo's *Education Week* "Classroom Q&A" columns compiling practitioner advice on leaving workable sub plans. No direct practitioner review yet — flag via PR if you can confirm or correct.