1. Special Education Discipline

2. Special Education Discipline – Upcoming Webinar
OFFICE HOURS:
Wed May 30 2:00–3:00 pm collection reminders and time for questions
Login Information:
Call-in number:
* reminder will be sent prior to webinars!
Special Education Discipline - Lindsey Heitman - (303)

3. Special Education Discipline Interchange/Snapshot
Special Education Discipline Interchange/Snapshot vs. School Discipline and Attendance (SDA)
Interchange/Snapshot Process
Student Level Data
ONLY students with disabilities subject to disciplinary removal are included
Districts submit data in pipeline; AU’s create and finalize Discipline Snapshot data
Periodic Collection Process
School Level Data
count of incidents
count of students
ALL students disciplined counted and reported
Districts Submit data and finalize data within Pipeline
Special Education Discipline Interchange/Snapshot
School Discipline and Attendance (SDA) 3

4. Special Education Discipline TIMELINE
Monday May 7th Discipline Action File uploaded
Thursday June 7th 1 snapshot created by this date (AUs)
Wed. July 11th Interchange errors cleared
Up Next
If your district has no SPED discipline actions to report so far, please mark exempt in the Pipeline. You can later reverse it and upload a file if an action occurs before the end of school.

5. Disciplines Removals ACTION TYPES
Suspension
In-school (01)
Out of School (02)
Expulsion
(03)
Removals
Unilateral Removal to IAES by school personnel
(01)
Removal by a hearing officer to an IAES
(02) OR
*Incident involving drugs, weapons, or bodily injury
A record will contain a Discipline or a Removal. Not both!

6. Special Education Discipline Reminders
Record Expectation: A record will either contain a Discipline or a Removal but not both.
Report a record in the year in which the Discipline ACTION occurs
Report a record for each action associated with an incident. An Incident can have multiple actions and a record is reported for each action.
Incident Identifier may be duplicated in cases where a student had more than 1 action associated with an incident.
Discipline Action Length - Report number of school days missed
If Discipline Action (days missed from school) spans 2 school years, report that incident/action in both collection years in order to report the school days missed in each school year
Students must be receiving services on an active IEP to be reported in the Sped Discipline collection
Discipline Date should fall between the SPED Participation file Entry and Exit dates (SD024)

7. Special Education Discipline
Scenario
How to Code
Action carries over to next school year. Student was expelled at end of school year 2018 and the actual expulsion begins in August 2018 (next collection period).
Report this incident/action in the collection
Discipline Action Length = school days missed
Exception required for edit DA043 because incident date was in prior school year
Action spans 2 school years. Student expulsion begins in May 2018 and carries over to the following semester.
Report this incident/action in both the and collections.
Report the same Incident Identifier, Incident Date, and Action Identifier for the record in both years
For Discipline Start Date, report the start of the expulsion in each year
Discipline Action Length should be the number of days missed from school each year

8. Special Education Discipline
Error Code
How to Resolve
SD005 LASID must be included in the snapshot. This field is blank because a matching record could not be found in the Student Profile Interchange.
Student’s record/LASID must be included in the Student Interchange. An UNTAGGED Student Demographics file must be uploaded. This must be fixed by the Student Interchange respondent.
SD017 Grade Level must be included in the snapshot and be a valid code. This field is blank because a matching record could not be found in the Student Profile Interchange.
Grade level comes from the Student School Association (SSA) file. Reasons this will trigger-Discipline Action and School Association data not in sync:
A record cannot be found for student in the SSA file with a matching school code to the one reported on the Disc Action record.
Incident date does not fall between the SSA School Entry and Exit dates (i.e. before the entry date)
Grade level, School code on the SSA file and School Code on the Discipline Action file, and the Incident date and School Entry and Exit dates must all coincide.
*Check the Sped Incident and School Enrollment Date Comparison Report . This report only has data if you have SD017 errors. It’ll show you which of the reasons above is causing it to trigger.

9. Discipline Incident and School Enrollment Date Comparison Report
Report provides inconsistent school code and dates between the Discipline Action File and Student School Association File. Used to help resolve edit SD Problem with record below: School Codes don’t match 
SASID
Discipline Action School Code
Incident Date
School Association School Code
Entry Date
Exit Date
1234
4321
08/13/2016
2. Problem with record below:
Incident Date is not between the Entry and Exit date of the Student at the school 
SASID
Discipline Action School Code
Incident Date
School Association School Code
Entry Date
Exit Date
1234

10. Special Education Discipline- No Discipline Actions
How to report your district has no discipline actions:
Under the Discipline Tab choose No Discipline Actions
Select the School Year, Click Submit
Mark Yes under No Discipline Actions and click Save
Be sure you see the “Successful Save” message at the top
*No file is necessary

11. Special Education Discipline – Status Dashboard Screen
AU/SPI role can filter on File Type – Discipline Action and screen will display file and or exempt status of all member districts

12. Special Education Discipline Resources
Timeline, Discipline Action File Layout, Template, Business Rules, and other helpful resources:
Special Education Discipline - Lindsey Heitman - (303)

13. Special Education Discipline Snapshot Resources
Special Education Discipline - Lindsey Heitman - (303)

14. Special Education Discipline