Three teachers out.
Covered before first bell.
Every school has one person who holds the morning together — who's out, who's free, who covered last time — mostly in their head. Teacher Coverage turns the absence report into the day's plan, and the heroics into a system.
Forty-five minutes, by the clock.
Coverage lives or dies before homeroom. This is the window the module was built for.
The Aesop export uploads; unmatched names surface for review instead of disappearing.
Every affected period becomes a slot: sub assigned, must-fill, or open.
Free staff get a parallel offer for the open period. First yes wins — settled atomically, no double-booking.
Uncovered slots resolve to substitutes, internal coverage, or sub-study. The office sees the whole day at once.
Per-substitute schedules, one page each — never a student name or a reason on them.
The scramble that used to run on memory and hallway shouting is a printed plan.
The board the office runs the morning from.
Slots, not sticky notes: who's absent, which period, who has it, and what's still open — with internal offers resolving in real time.
Offers settle on the server — the second yes gets a polite “already covered.”
Inside Teacher Coverage.
The absence export becomes structured data in one upload — duplicates detected, unmatched staff queued for review, nothing silently dropped.
More teachers call in after the first upload? Re-upload the updated file — the new absences get added, the classes already handled are left alone, existing sub assignments are kept, and any real change is flagged for review. A second same-day file is a merge, not a mess.
Every absence, every period, every resolution — covered, uncovered, offered, must-fill, sub-study — on one screen the office works from, with what can't wait surfaced first: unfilled required coverage rises to the top, loudest.
Parallel offers to free staff with an atomic first-yes-wins accept — no reply-all, no awkward double-asking. And the server won't let one sub land in two rooms at once, or put a teacher who's out that day on someone else's class: the guardrails hold where the write happens, not just in the screen.
Per-substitute daily schedules from one template — plain text, never a student name or an absence reason on paper.
Assignment methods roll up into pay reports and internal-coverage savings, ready for the business office.
A 40-verifier suite rehearses imports, offers, and reports against test data — and the pilot runs in parallel with the manual process until the checks are boring.
In pilot means in pilot.
Coverage is running against real mornings in a live pilot, with the manual process kept alongside until the verifier suite and the humans agree it's boring. When we say a module is ready, that's what the word has to mean — a district can't run its building on a maybe.
One half of the staff side.
Teacher Coverage is one of two Staff Operations modules. Staff Attendance — swipes, absences, and the payroll export — is the other, on the same staff record and the same Core.
Show us your coverage morning.
Bring the person who runs it. If Coverage wouldn't survive your building, we want to know why — that's what shapes it.