Substitute and temporary staffing systems for school districts

Reference article · 7 min read

Every school day, a district has to put a qualified adult in front of every group of students, including the classes whose regular teacher is out. The systems that do this sit at the intersection of human resources, payroll, and school operations. They take absence reports, match open assignments to available substitutes, enforce clearance and credential rules, and produce the time records that payroll pays from. When the process works, principals are not making phone calls before dawn. When it does not, schools improvise by splitting classes or pulling staff off planning periods, and the district absorbs the cost in coverage stipends and lost instructional time.

Districts generally buy this capability in one of three shapes: software the district operates itself, a managed service in which a vendor runs dispatch and the call center, or a staffing arrangement in which the substitutes are employed by the vendor and placed in district schools. The contracting questions differ across the three, but the operational questions are the same.

Absence reporting and automated dispatch

The intake side has to accept an absence from a phone call, a web form, and a mobile app, because teachers report at odd hours and from home. Useful systems let the employee classify the absence against the correct leave code, attach it to the right assignment and bell schedule, and indicate whether a substitute is actually needed. Some absences, such as a half day of professional development, may be covered internally.

Dispatch is where districts see the most variation. Ask how the system orders the call or notification list, whether it offers assignments to multiple candidates at once or in sequence, how long an offer stays open before it moves on, and what happens overnight and in the early morning. Confirm that a job can be reserved for a named substitute, released to a school pool, and then released district-wide on a schedule the district controls. Also confirm that a canceled absence retracts the assignment and notifies the substitute, since an uncanceled job produces a pay dispute later.

Preference lists, exclusions, and pool health

Most districts maintain preferred substitute lists at the school or teacher level and exclusion lists that block a substitute from a school, a classroom, or a student population. These lists carry real consequences, so decide in advance who may add an exclusion, what documentation is required, whether the substitute is notified, and how an exclusion is reviewed or removed. An exclusion entered casually by a school secretary can quietly end someone's work in the district.

Watch how the system handles long-term assignments, which behave differently from daily fills: they need a date range, a rate change at a defined threshold, and a way to hold the same person across the span. Reporting should show fill rate by school, by day of week, and by subject area, so the district can see whether a coverage problem is a supply problem or a dispatch problem.

Clearance and credential status as a gate

Substitutes in most states must clear a fingerprint-based criminal history check and hold some form of substitute permit, certificate, or local authorization. Requirements, renewal cycles, and the handling of subsequent arrest notifications vary by state, and they change. Confirm the current rules with your state education agency, the state agency that processes fingerprints, and district counsel.

What matters in the system is that clearance and credential status is a hard gate on assignment, not a report someone reviews later. Require that expiration dates, permit types, mandated training completions, and any hold placed on an individual block dispatch automatically as of the effective date. Ask how the vendor receives status updates, whether that is a file from the state, a manual entry by district staff, or an integration, and how quickly a revocation propagates. Keep the district's ability to place an immediate hold regardless of what any external feed says.

Rates, hours, and benefits eligibility

Pay rules drive more disputes than dispatch does. Districts commonly run multiple rate tables: daily and half day rates, a higher long-term rate that starts after a set number of consecutive days, differentials for hard-to-fill schools or special education assignments, and separate rates for classified substitutes such as paraprofessionals, bus drivers, and food service staff.

Several rules depend on hours worked, and each has its own definitions:

• Health coverage eligibility. Federal employer shared responsibility rules measure hours of service over defined periods. The measurement method and thresholds matter, and they should be set with counsel and your benefits administrator rather than configured by default.
• Retirement system limits. Many states limit how much a retired educator can earn or how many days they can work without affecting a pension. These limits are state specific and change, so confirm them with the retirement system.
• Overtime and classified staff. Substitutes in classified roles are often nonexempt, so hours across multiple assignments in one week have to be totaled, not treated as separate jobs.
• Unemployment and reasonable assurance. Practices around notices between terms vary by state and have been litigated. Treat this as a legal question, not a configuration setting.

The system should report projected hours against whatever thresholds the district has adopted, in time for someone to act.

Integration with student information and payroll systems

Three integrations carry most of the value. First, staff, school, calendar, and bell schedule data from the student information or HR system, so assignments reference real positions and real instructional days. Second, an export to payroll or the ERP that carries approved time, the correct rate, the funding code, and the position, at the cadence your pay calendar requires. Third, identity and access, so substitutes get only the system access an assignment justifies and lose it when the assignment ends.

Decide early who approves time and when. A principal or timekeeper approval step that runs past the payroll cutoff creates off-cycle checks. If the vendor employs the substitutes, the district still needs invoice detail at the assignment level to reconcile against its own records. Because integrations move student and employee data, address FERPA obligations, data ownership, breach notification, and return of data in the contract rather than in a later amendment.

What to ask vendors and put in the contract

• Ask for the specific fill rate definition the vendor reports, including whether internally covered and canceled absences count.
• Ask what happens when an assignment goes unfilled, and what the vendor does before the school day starts.
• Ask how rate tables, long-term thresholds, and exclusion permissions are configured, and whether the district can change them without a service request.
• Ask which integrations are standard, which are custom, and who pays to maintain them when the source system upgrades.
• Require that the district owns its absence, assignment, and time data and can export it in a usable format on demand and at termination.
• Require documented service levels for dispatch availability during early morning hours, and a manual fallback when the platform is down.
• If the vendor employs the substitutes, address who screens and trains them, how the district can remove an individual from its sites, and how the district retains visibility into clearance status.

Choosing between a service and in-house operation

Bringing the function in-house shifts recruiting, screening, onboarding, and early morning coverage back onto district staff. That is workable when the district has a stable applicant pool and enough HR capacity to process clearances quickly. A managed service can absorb volume and recruiting effort, but it does not remove the district's obligations for who is in its classrooms. Before deciding, cost out the internal staff time honestly, including the hours principals currently spend covering gaps, and compare it against the service cost plus the oversight the district would still have to perform.

HQT builds and integrates workforce, HR, and payroll-adjacent systems for state and local government agencies, including districts evaluating whether to operate a substitute management platform internally or through a service.

Frequently asked questions