Feature
Coverage requests
A coverage request moves through a clear set of stages, from a teacher's draft to a completed day. Here's the whole lifecycle, and the one naming rule worth knowing.
Coverage is the heart of SubHub. Every absence is one record that moves through stages as people act on it. Knowing the stages tells you exactly what's happening and what's next.
The lifecycle
Six happy-path stages carry a request from creation to completion:
- CreatedA teacher submits a request, or an admin starts one on their behalf. It's waiting for approval.
- ApprovedAn admin approves it. Now it's real coverage, and it goes out to substitutes.
- Finding a subThe open job is on the board and substitutes can claim it.
- AssignedA substitute claims it. The job is locked to them, and they get the lesson plan.
- CompletedThe date passes and the coverage is done. It stays on the record for the calendar and history.
A request can also be cancelled, declined, or expire before it ever becomes coverage. Those are off-path endings, the record just stops here rather than moving forward.
Request, or coverage?
SubHub uses two words for the same record, depending on where it is in the lifecycle. The rule is simple:
- Before approval (and for anything cancelled, declined, or expired), it's a coverage request, something that was asked for.
- Once approved, assigned, or completed, it's simply coverage, the real thing on the calendar.
The navigation label is Coverage, since that's what the section is about. You'll see "coverage request" on a brand-new submission and "coverage" once an admin signs off.