Positive Behavioral Interventions and Supports (PBIS) Leadership Summit Breakout Sessions March 30, 2009
Positive Behavioral Interventions and Supports (PBIS) Introductory Workshop 1:45 – 2:00 Set Up/Introduction 2:00 – 2:30 School Presentation 2:30 – 3:00 School Presentation 3:00 – 3:15 Question & Answer 3:15 – 3:30 Wrap Up & Evaluation
Planning Phase I (March – July: Year 1) TASKCOMPLETION DATE Administrator agrees to actively support and participate in PBIS activities. Administrator agrees to: attend meetings 90% of the time provide funding for PBIS activities allocate time on staff agenda for PBIS updates actively promote PBIS as priority, and integrate PBIS with other initiatives/improvement activities April 30 Administrator submits “Statement of Intent” form. (Online at April 30 Identify team members and team leader: (Team should be representative of school staff with administrative support and participation.) June 1 Establish 80% staff commitment. Staff agrees to: Provide input in determining what our school’s problems are and what our goals should be Make decisions about rules, expectations, and procedures in the common areas of the school as a school community Follow through with all school-wide decisions, regardless of individual feelings for any particular decision Commit to positive behavior support systems for a full year - allowing performance toward our goal to determine future plans June 1 Identification of Behavior Support Coach. (Appointed by local school system PBIS coordinator). June 1 Schedule at least 2 full days in August for PBIS team meetings & planning. June 1 Register as a team for Maryland Institute **In order to qualify as a TRAINED team, 4 people including an administrator must attend both days of the Summer Institute. (Obtain registration information from LSS Point of Contact- on line registration available April 15 – June 1)) June 1 Complete online PBIS Staff Survey. (Statement of Intent form required for school account to be activated, account numbers will be ed to school administrator) June 1 (or before staff leave for the summer) (Bring summary to Summer Institute 2009) Review SWIS readiness checklist to be SWIS compatible. (Required to utilize SWIS) June 22 Revise/update office referral form. (see compatibility checklist and sample at July 16 (Bring revised form to Summer Institute 2009) Entire team attends Summer Institute Secondary Teams: July 21 and 22 Elementary Teams: July 23 and 24
Obtain 80% Staff Consensus 80% Staff Commitment A “ YES ” vote means that I agree to: Provide input in determining what our school’s problems are and what our goals should be Make decisions about rules, expectations, and procedures in the commons areas of the school as a school community Follow through with all school-wide decisions, regardless of my feelings for any particular decision Commit to positive behavior support systems for a full year - allowing performance toward our goal to determine future plans
To Do Today – Listen, Ask Questions, Get Clarification By April 30, 2009 – Statement of Intent By June 1 – REGISTER –Complete the Staff Survey School account numbers will be ed upon completion of. Contact your system point of contact for assistance. (POC list in folder)
Resources –Click on New Teams Questions – please contact your local school system point of contact
SYSTEMS PRACTICES DATA Supporting Staff Behavior Supporting Student Behavior OUTCOMES Supporting Social Competence & Academic Achievement Supporting Decision Making 4 PBS Elements
Primary Prevention: School-/Classroom- Wide Systems for All Students, Staff, & Settings Secondary Prevention: Specialized Group Systems for Students with At-Risk Behavior Tertiary Prevention: Specialized Individualized Systems for Students with High-Risk Behavior ~80% of Students ~15% ~5% CONTINUUM OF SCHOOL-WIDE INSTRUCTIONAL & POSITIVE BEHAVIOR SUPPORT
CRITICAL FEATURES Establish Commitment Establish and Maintain Team Self-Assessment Establish School-Wide Expectations Establish On-Going System of Rewards Establish System for Responding to Behavioral Violations Establish Information System Build Capacity for Function-Based Support Build District Level Support