Excerpt from measureed.com/knowledge/how-do-i-manage-calpads-eoy-3-data-step-1-of-1-student-discipline
How do I manage CALPADS EOY 3 data? (Step 1 of 1 – Student Discipline) / CA Compliance / CALPADS EOY 1-4 / Discipline / Registrar / Student Data / How do I manage CALPADS EOY 3 data? (Step 1 of 1 – Student Discipline)
by Curtis Loo | April 21, 2014 | Article updated: April 8, 2015
EOY 3 is the End of Year CALPADS reports that are focused on Student Discipline.
Student DisciplineEach school should be tracking their disciplinary incidents in a way that is compliant with the CALPADS reporting requirements due at the end of the year. As many local entities often require regular reporting of incidents that merit discipline, we recommend that this data is managed outside of the Student Information System for small and medium sized schools.
There are a few reasons why we recommend this:
1) If a school is required to turn in Monthly Reports to a local agency, it is unlikely that your SIS will support those local reports. Inputting that information into your SIS and then the local reports after that would be double the work! And if you decide to input the data into the SIS for tracking reasons you still can but with less urgency and potentially only once during the summer.
2) Some Student Information Systems have developed Discipline/Incident Management Systems. We find that many of the existing solutions are not easy to use which requires training and is prone to error. We find that using a spreadsheet template is much easier.
3) When managing discipline online in a central database, it is likely that many people are using the system and can have access to the creation of discipline incidents. For legal reasons, it is important that the tracking of discipline incidents and related actions are traceable, managed, and recorded. This is especially true when an expulsion occurs. We have found in our experience that this is much harder to do when multiple users can make the application of disciplinary actions and reporting inconsistant. In this regard, it is advantageous to have a single point of contact that is responsible for issuing disciplinary actions and reporting.
If you are a school that has a large volume of disciplinary incidents or have other compelling reasons to centralize the reporting into a Student Information System, we have solutions for that as well but this article does not cover them. For the most part, our solutions work well for small to medium size schools with small to medium volumes of disciplinary actions (Less than 200 incidents a year).
A Student Discipline LogWe promote the use of a student discipline log which can be downloaded here: 2014-2015 CALPADS EOY 3 Suspensions and Expulsions Log. The discipline log should have a clear owner that is responsible for this log throughout the year. The log consists of several parts.
Part 1: Student Information:
This section covers the basic set of information that needs to be collected for those who participated in the incident. Each row contains the information for each student involved and contains:
This section covers all of the required elements of the incident itself and the consequences.
MBUSD PowerTeacher: https://mbusd.powerschool.com/teachers
PowerTeacher Gradebook: Getting Started
PowerTeacher Gradebook has a way of opening Mac that bypass Java which may cause following error: 'Gradebook is damaged and can't be opened. You should move it to the trash.'
*More information on Mac 101: http://goo.gl/FSnI1
Helpful tips by Chris Co-founder Educreations
Graded Short Answer and how quizzes Integrate with Gradebook