1. System Overview October 2013

2. What Is First ACTS? First ACTS (Active Conduct Tracking System) is a web-based system developed by First Student to help its school district customers and operating locations better track and manage school bus student behavior issues. Easy-to-use, yet flexible enough to accommodate diverse local requirements, First ACTS helps identify, review, respond to and resolve school bus student conduct incidents.

3. 3 First ACTS: Application Benefits First Student Location Users Overall Easy-to-use and flexible web-based tool requires no special PC software Real time system-based tracking and notification process will drive consistency, timeliness and better access to information and improve incident management Tracks all bus student behavior incidents; eliminates paper forms (tracking, filing, locating, etc.) Searchable student incident histories Could be setup to feed incident data to existing school discipline platforms A better way to manage school bus student behavior issues Receive e-mail alerts (and reminders) of new incidents; can copy other administrators Administrators can take disciplinary actions as needed: generate email or letters to parents, notify other school staff (e.g. teachers) or First Student School District Users Flexible Incident Report creation and review process supports existing workflows Ability to pre-load Student & Driver info streamlines Incident Report entry Online tracking of school responses and reminders will improve timeliness

4. 4 First ACTS: High-Level Process Parent notification: E-mail Letter Parent notification: E-mail Letter Informational E-mail sent to District/ School staff E-mail notification sent back to FS User 1.Easy-to-use, intuitive tool for FS & schools 2.Flexibility to support a variety of local processes from diverse schools/districts, large and small Design based on two key principles: First ACTS System First ACTS System FS Writer Creates Incident Report (IR) If required, IR viewed at FS, approved Email Notification to School Reviewer Reviewer reads IR, takes action 1 2 3 4 5

5. First ACTS: Creating an Incident Report 1.Student can be entered by Student ID or Name. If the student is found in the database, Grade & School will auto-fill 2.If a student has past incidents in the database, they will be listed here 3.Incident information includes Date & Time, Route info, Infraction Type & Description. Multiple Infraction Types can be added to an incident 4.Files, such as photos or videos can be attached to the Incident Report 1. 2. 3. 4.

6. First ACTS: Reviewing an Incident Report 1.Top portion of Report, including student information, incident description and any supporting file attachments is generally completed by First Student staff 2.Student incident history is maintained by the system and is presented for quick reference 3.Based on the nature of the incident, student history, etc., the School Reviewer decides what, if any, disciplinary action is appropriate. 4.The Reviewer then has a number of system-based notification options 1. 2. 3. 4.

7. First ACTS: Notifications The system has five basic notification options: 1.Parent Letter (see left) – system constructs a parent letter incorporating the description of the incident along with any disciplinary action taken 2.Parent Email - system constructs same communication as letter, but produces email to parent 3.District Email – system generates email to other district users, for instance a teacher or the Transportation Director 4.FS Review Required – system generates email to First Student, informing them of action taken 5.Other Email – Reviewer can send Email of incident to other individuals (teachers, etc.)