School Bus Attendant & Monitor Duties Checklist

It covers the daily tasks an attendant or monitor performs before, during, and after a route. That includes pre-route preparation, student boarding assistance, in-transit supervision, securement verification, and post-route procedures. It is designed for recurring route work, especially where students need extra assistance or supervision. It does not replace district policy, driver procedures, or individualized student plans.

This template is meant for school bus attendants, bus monitors, and other support staff assigned to student transport. A transportation supervisor or route lead can also use it to standardize expectations across routes. If your district assigns different duties by route, the template can be cloned and adjusted for each assignment. The DRI should be the person actually responsible for completing and verifying the checklist on the route.

This is typically a daily recurring checklist tied to each route or shift. Many teams run it before the morning route, before the afternoon route, or both if the attendant works split shifts. If your operation has field trips, special education transport, or mid-day shuttles, create separate recurrence settings for those assignments. The key is to match the checklist to the actual route cadence, not a generic weekly schedule.

Yes, this template is especially useful for special-needs routes because it emphasizes securement, supervision, and verification steps. It can be customized to reflect mobility aids, behavior supports, communication needs, and individualized boarding or unloading procedures. You should align it with student-specific plans and district procedures before use. If a student’s support needs change, update the checklist so it still matches the route reality.

The most common mistake is making items too broad, such as combining boarding help, securement, and documentation into one checklist item. Another pitfall is treating every issue as critical, which makes it harder to prioritize true safety or compliance problems. Teams also sometimes forget a verification step for securement or fail to record exceptions when a student is absent or a device is not available. Keep each item independently verifiable so the answer is clearly yes, no, or not applicable.

An ad-hoc route sheet often depends on memory and can vary by person or day. This template turns the work into a repeatable task type with clear checklist items, which makes handoffs, audits, and training easier. It also helps supervisors see blocking issues, such as missing securement equipment or a route exception that needs follow-up. Paper notes can still be attached, but the checklist gives the route a consistent operating standard.

Yes, it should be customized for your district rules, vehicle layout, and student population. You can add items for wheelchair securement, harness checks, communication devices, medication handoff, or aide-to-driver coordination if those are part of the route. You can also remove items that do not apply to a given bus or program. The best version is the one that matches the actual route and can be completed without guesswork.

This checklist works well alongside route manifests, student support plans, incident logs, and maintenance or defect reporting. If your workflow supports it, link the checklist to a route record so supervisors can review completion and follow-up in one place. It can also connect to escalation workflows when a blocking issue is found, such as a missing restraint, broken latch, or student safety concern. Integrations should support the route process, not add extra steps that slow boarding or supervision.