1. Defining Behaviors and Establishing a Data System for Behavior SWPBIS Day 3: Universal Curriculum

2. 4 : 1 8/24/2010 2

3. Outcomes Establish importance of data collection for progress-monitoring Define office vs. classroom handle problem behaviors and define how each type of behavior problem is handled in a flow chart display. Review and revise office discipline referral forms. Design Universal system for SWPBIS kickoff. 8/24/2010 3

4. Data Help Us Answer Critical Questions Initial needs o Where should we focus our efforts? Level of implementation o How well are we putting in place? Impact on student outcomes o Are we achieving our valued outcomes? Data Help Us Generate Solutions! 4

5. Improving Decision-Making Problem Solution From To Problem Problem- solving Information Solution 5

6. What Data Should We Collect? Use What You Have o Office referrals o Detentions o Suspensions o Attendance o Tardies o Serious incidents 6

7. Office Discipline Referrals and The BIG 5! Examine office discipline referral rates and patterns o Major Problem events o Minor Problem events Ask the BIG 5 questions: o How often are problem behavior events occurring? o Where are they happening? o What types of problem behaviors? o When are the problems occurring? o Who is contributing? 7

8. Cafeteria Class Commons Hall 12:00 Lang. Defiance Disrespect Harrass Skip 8

9. Building Precise Problem Statements Primary Statements o Indicate a discrepancy between what we have and what we want. Precise Problem Statements: o Indicate the problem with sufficient precision to allow problem solving 9

10. Classroom Managed vs. Office Managed Problem Behaviors Minors vs. Majors 8/24/2010 10

11. Elementary School Example Teacher Managed Behavior Attendance/Tardy – Inform parents on effect on academic performance Profanity directed at student Gum chewing Homework No supplies Tattling Non-compliance Name calling Lying Minor stealing Cheating Dress Code Violations Minor Harassment Office Managed Behavior Attendance/Tardy Vandalism Substances Defiance Weapons Profanity directed at Adults Major disruptions Fighting Verbal/Physical intimidation Major stealing Cutting school Wanderers Gang Related Activity Chronic Dress Code Violation Harassment (including sexual) 8/24/2010 11

12. Middle School Example Teacher Managed Behavior Excessive talking Attendance tardy inform parents Off task (Disruptive) Gum/Food/Candy Drinks Missing Homework Not prepared for class Name calling Dishonesty PDA Running in Hall Passing notes Backtalk directed at Adults Cheating/Plagiarism Writing on school property Office Managed Behavior Attendance Tardy Insubordination Fighting Vandalism Verbal/Physical Intimidation Weapons, threats Gang Representation Cutting class/school/teacher detention Theft Drug Violations Directed Profanity Harassment (incl. sexual) Controlled Substances Security threat/breach Lewd notes Repeated Backtalk (3) Repeated PDA Dress Code 8/24/2010 12

13. High School Example Teacher Managed Behavior Excessive talking Attendance tardy inform parents Off task Drinks/Food/Gum (with clear expectation for your class) Missing Homework Not prepared for class Inappropriate Language Lying Dishonesty Dress code violating PDA Hallway Disruption Passing notes Cheating/Plagiarism Office Managed Behavior Attendance Tardy Insubordination Fighting Vandalism Verbal/Physical Intimidation Weapons Gang Representation Cutting class/school/teacher detention Theft Drug Violations Directed Profanity Arson Harassment Controlled Substances Threats Security threat/breach Lewd notes Repeated/Severe Offenses 8/24/2010 13

14. ACTIVITY Using T-charts: Identify teacher managed behaviors Identify office managed behaviors Identify consequences for teacher managed and office managed behaviors 14

15. T- CHART OF BEHAVIOR Teacher Managed Behavior Office Managed Behavior 8/24/2010 15

16. T- CHART OF CONSEQUENCES Teacher Managed Behavior Office Managed Behavior 8/24/2010 16

17. Code of Conduct vs. SWPBIS Legal and Documented Approach vs. Changing Behavior Approach Which happens more often in your school? 8/24/2010 17

18. Minors vs. Majors Flowchart 8/24/2010 18

19. General Procedure for Dealing with Problem Behaviors Observe problem behavior Problem solve Determine consequence Follow procedure documented File necessary documentation Send referral to office File necessary documentation Determine consequence Follow through with consequences Problem solve Follow documented procedure Write referral and Escort student to office Follow up with student within a week Is behavior major? Does student have 3? NOYES NO YES Find a place to talk with student(s) Ensure safety 19

20. 20

21. Documenting and Defining Minors and Majors 8/24/2010 21

22. Minor Inappropriate language Disruption Property misuse Non- compliance Other_____ Parent contact Out-of-school suspension Time in office Other________________ Avoid work Obtain items Don’t know Other_____ Classroom On bus Special event Common area Other_____ Possible MotivationLocationProblem Behavior Consequence Lose privilege individual instruction Conference In-school suspension Attention from peers Attention from adults Avoid peers Avoid adults Hallway Cafeteria Library Restroom Office Parking lot Major Abusive language Fighting/ physical aggression Harassment Overt defiance Other_____ Office Discipline Referral Form Name: _________________________ Grade: _____ Date: _____ Referring Person: ________________________Time: ________ Others involved: None Peers Staff Teacher Substitute Unknown Other 22

23. ACTIVITY Revise current office discipline referral form Define minors and majors behaviors 23

24. Data System Decide which behaviors are managed in the classroom and which behaviors are sent to the office Support teachers in designing classroom systems Brainstorming continuum of procedures for responding to ODRs: Verbal reprimands Detentions Community service Re-teaching of expected behavior Follow up with increased acknowledgment Additional responses/options for intense/chronic kids 8/24/2010 24

25. Beginning of the Year: Staff & Student Kickoff 8/24/2010 25

26. Team Implementation Checklist 8/24/2010 26