DPI closely involved in all phases of development: Identifying requirements, design, testing, training, identifying enhancements

Closer collaboration with key stakeholder (DPI) during development should equate to a better product

Critical to understand processes so tools can be aligned accordingly

Based on DPI/ATLAS experience, development of other tools has relied upon tight cross-departmental collaborations

- EL Tab (EL Services)
- Student Engagement (Campus Culture/Athletic Directors, After School Programs)
- Teacher Dashboard (Teachers, REA)
- Graduation Status (Equity and Access, Counselors)
- Assessment reports (REA)

Misbehavior and Suspensions in same system

Multiple students involved in single incident reported as one incident

Social workers and social/emotional support providers can now log their interaction w/ students

SARB Office will utilize Attendance category for better monitoring

Data in single system makes reporting to State more efficient

In-school suspensions largely untracked

Enhancements released this month will allow school admins to specify the dates and periods of in-school suspensions

Attendance will be taken by teacher assigned to in-school suspension

Improved communication to parents is needed (letters and possibly SMS)

Schools have the option to enter Office Referrals in Student Portfolio

Schools use paper process as well as electronic

Electronic process would yield better information

Transparency of office referrals submitted in Student Portfolio will aid in adoption of electronic submission

Ongoing training provided

Early demonstrations and trainings included DPI staff to ensure proper process was communicated

Documentation and communication should include information about underlying process to ensure tools are used effectively

http://www.fresnounified.org/staff/pl/commonlearning/ATLAS/Training%20Scrip...