School Bus Student Behavior Incident Report

Use it any time a student’s conduct on the bus disrupts safety, order, or supervision, including fighting, harassment, refusal to follow directions, or unsafe movement while the bus is in motion. It is also useful when a repeated issue needs a paper trail for discipline review or accommodation review. If the event is minor and resolved immediately with no follow-up, you may still document it if your district expects incident tracking.

The bus driver, bus aide, transportation supervisor, or another adult who directly observed the incident should complete it as soon as practical after the event. The best reports come from the person closest to the facts, not from secondhand summaries. If multiple staff witnessed the event, one person can submit the form and list the others as witnesses.

Yes. The Follow-Up and Routing section includes a specific flag for IEP review so the incident can be sent to the right team when behavior may relate to a disability or accommodation need. That helps the school separate discipline review from support planning. Keep the report factual and avoid diagnosing or speculating about the student’s condition.

Only collect the minimum necessary details needed to document the incident and route it for follow-up. Avoid unnecessary PII, medical speculation, or unrelated student history, and do not add sensitive details unless they are directly relevant to the event. If your district allows anonymous submission for certain concerns, this template can be adapted, but bus incident reports usually need the reporter’s identity for audit trail and follow-up.

Report each qualifying incident individually rather than waiting to bundle several events together. Repeated behavior should be noted in the repeated behavior field and linked to a prior incident reference when available. That makes it easier to spot patterns, apply consistent consequences, and determine whether a route or seating change is needed.

Common mistakes include vague summaries, missing route or bus numbers, leaving witness names blank when adults were present, and using free text where a structured behavior type would be clearer. Another frequent issue is skipping the immediate action taken, which makes it hard to see how the situation was stabilized. The report should describe observable behavior, not assumptions about intent.

Yes. You can add district-specific behavior categories, route identifiers, escalation rules, or a field for parent contact if your process requires it. For younger students, you may want simpler behavior labels and more guidance on immediate intervention. For secondary routes, you may want more detail on seat location, peer conflict, or device-related distractions.

An ad hoc message can be fast, but it often misses key fields, creates inconsistent records, and makes follow-up harder to track. This template standardizes the facts, supports an audit trail, and helps ensure the principal or IEP team gets the same core information every time. It also reduces the chance that important details are buried in a long conversation thread.

The report should be reviewed by the designated school contact, usually the principal, transportation lead, or student support team, depending on your workflow. If injury, repeated conduct, or disability-related concerns are indicated, the form should trigger the appropriate follow-up path. The submitter should know whether the report was received, who will review it, and whether additional statements are needed.