# data[].attributes.body
PLC-
Quarterly Check Protocol questions to guide discussions
Eureka mid and end of module data discussions
IRLA problem solving each month
Problem solving meetings each Friday
Lowest 35% intervention data
Compare to region, district and peer
Post conference conversations

I didn't see our show up, so here it is again... Might have 2

# data[].attributes.body
Admin. Met with individual teachers and grade level teams. We created a plan to address standards not mastered.

# data[].attributes.body
Grade level teams went through the quarterly data for the entire school.  They reflected on standards that needed to be addressed again and ideas to improve learning across the grade levels.

# data[].attributes.body
Individual data chats, then data analysis school-wide, followed up with school-wide action plan. Coaching support is also included in plans.

# data[].attributes.headline
GSES- Grade Level PLCs use quarterly protocol as a guide

# data[].attributes.subject
GSES- Grade Level PLCs use quarterly protocol as a guide

# data[].attributes.body
Weekly Problem solving meetings  with each team

Admin and coaches pulled data, did comparisons, problem solving discussions

Lowest 35% data being monitored through problem solving meetings

# data[].attributes.body
Admin reviewed data

Grade level PLC's reviewed their own data using Quarterly Check Protocols

Overview of data discussed with Leasership team.

IRLA checks-LDC meeting with PLC's to discuss IRLA and how to move students forward.

# data[].attributes.body
In PLC's grade level teams compared their individual data with their team and then compared their team data to the district. Teams created one or two action steps to consider for the upcoming quarter.
As an administration team we looked at the data prior to the PLC meetings.

# data[].attributes.body
Scheduled Progress Monitoring Days, 2 hours per team. During this time
Admin Team and grade level view a powerpoint presentation. Analyze the lowest 25%,
Guided T-Bit to discuss individuals students.

# data[].attributes.body
Data chats with individual teachers quarterly.  Weekly progress monitoring of any student that is below grade level based on IRLA.  PLCs review quarterly data and use flexible grouping of students based on standards.

# data[].attributes.body
Admin team meets with each PLC to review ELA and Math data using the Quarterly Check Protocol.  As a grade level team, we problem solve and develop plans to intervene or provide enrichment, especially with standards that are only taught during quarter 1.

Admin team reviews with PBS team school-wide discipline behavior.

Admin team monitoring the bottom 25% in each grade level and meets with grade level teams each quarter to monitor students' progress towards standards.

# data[].attributes.body
Data chats with IRLA each month where the team sets a goal, teams looked at Quarterly Checks and reviewed questions and completed the Quarterly Check protocols, meetings set up with Larry Porter this month to dive deeper into data discussions and develop goals, will be looking at FSA data and learning gains needed. Summative & formative assessments to reflect on Oakie Time (intervention/enrichment)

# data[].attributes.headline
TES- Data Round Up day (during extended planning time)...Teachers and admin Looked at Quarterly data and IRLA data compared to feeder pattern data, looked at our data in relation to district data, looked at data team wide and them by class. Looked for what we were doing well, areas of weakness across grade level (what could we compress and what needed reteach, what was coming back around and what did we need to address because it wasn't). Looked at lowest quartile, reviewed tiers of support and what needed to be adjusted and added.  So performance, curriculum, pacing and MTSS addressed.

# data[].attributes.subject
TES- Data Round Up day (during extended planning time)...Teachers and admin Looked at Quarterly data and IRLA data compared to feeder pattern data, looked at our data in relation to district data, looked at data team wide and them by class. Looked for what we were doing well, areas of weakness across grade level (what could we compress and what needed reteach, what was coming back around and what did we need to address because it wasn't). Looked at lowest quartile, reviewed tiers of support and what needed to be adjusted and added.  So performance, curriculum, pacing and MTSS addressed.

# data[].attributes.body
-We met with our regional team and analyzed school wide data looking for trends.
-We met with our leadership team and coaches and created a hot list as to where they would need to focus their attention and provided individual teacher support.
-We presented school wide trend data to the staff and discussed
- We met with individual teams and completed the QC Protocol GO and created an action plan for our lowest quartile as well as a team action plan for next quarter.

# data[].attributes.body
Admin:  Pulled schoolwide/grade level/classroom data to analyze weaknesses and strengths - created action plan for admin on addressing coaches, then teams and finally individual teachers on data. Had 1/2 day data discussions with teams and coaches to analyze data, create plans for addressing targets.  Created action plan for coaches with IPG tools, data targets.  Finally met with SLT to address supports required to move our students.

# data[].attributes.body
-Data chats in grade level PLCs; half day planning days for teams of teachers to analyze focus standards and plan forward with them.
-Spreadsheets on GoogleDocs or OneDrive where teams analyze formative assessment data compared to QC data.
-Spreadsheet also helps identify individual students in need of Tier II/III support
-We broke down regional grade level data and gave to teams as benchmark data.
-MTSS team looks at grade level trends and individual student data to see which areas our teams need assistance in.

# data[].attributes.body
As an Admin team we looked at each grade level and then focused on our specific classrooms to identify which rooms we needed to place on our Tier II & III of supports.
We walked them through the Math Quarterly Data in their Math Data PLC and then asked them to complete the form for their ELA assessment on their own. From there we scheduled individual meetings with each teacher, coaching team, and admin to review this data.

# data[].attributes.body
Admin Team reviewed data schoolwide, grade and individual, looked at the standards for strengths, areas of need, shared with leadership and coaches
Grade Level Team: analyzed data by individual students-planned for interventions and spiraling for quarter 2; high performing teachers shared what strategies they used; conversations and reflections with individual teachers-action planning and resources, as well as what learnings needed (ex. text dependent questions, quick formatives..) Identified students in red in all 3 areas--some were motivation--ACTION: coaches club

# data[].attributes.body
Admin and Leadership- IRLA, Quarterly Check, student data sheets, bottom 35%, Grade level action plan development and review, IPG targeted walkthroughs, Regional team support, Intentional Questioning PD

Teams - Data Chats, prioritized standards work, intervention groupings, Bottom 35% support and data review to make support adjustments, IPG training, participate in walkthroughs, connections to DP,

Coaching - data outliers - one-on-one meetings, coaching cycles, support for new/beginning teachers, Optional PD offered based on data trends,

# data[].attributes.body
We looked at trends as an admin team.  We used the data as a SIT team to monitor students.  We conducted data chats w/ each PLC and had conversations around trends as well as individual class performance.

# data[].attributes.body
We problem solved around our quarterly assessments at the grade level team.  PLC teams dove down to the standard and student levels.  Action plans were created to build on areas of opportunities. Teachers are working on matching the rigor of the standards to their every day student learning.
Celebrations were had for areas of strengths.
Our school based leadership team, POW, also analyzed our data.

# data[].attributes.body
Admin sent out a guide for teachers to reflect on their results prior to team meetings.
Admin and Coaches met with teams to review tiers of data. First teacher, then grade level, followed by school-wide and then region and districtwide. We then created action plans to focus our instruction for the next quarter.

# data[].attributes.body
We review the data as a leadership team.  We also have grade level teams review the data, reflect, and create goals for the next quarter.  Grade level teams complete the Quarterly Check Protocol.  The leadership team is there as they reflect and coaching follows.

# data[].attributes.body
Data chats with each grade level using the QC Discussion Protocol in conjunction with the data pulled from the Unify Scoreboard and Student Item Analysis. We looked at the district, regional, school and teacher data.
We review IRLA data every other week with teams during EPLC
Also meeting with our SIT to problem solve Tier 3 students.
Teachers also have half day planning opportunities to focus on priority standards and plan ahead.

# data[].attributes.body
We met with members of central regional team to create a guide for teachers to use during school wide, team level and individual classroom data disaggregation.  PD has focused on ensuring that PLC's focus more on data based discussions in order to plan based on the results of previous data.

# data[].attributes.body
Each grade level team met for a full day to review and analyze student data.  They were supported by instructional coaches as they worked through the quarterly check protocol.

Our SLT is currently problem solving around IRLA data to set goals for student proficiency.

# data[].attributes.body
Met as Admin team to review data. Reviewed data with each grade level PLC and looked for teacher trends too. Discussed what teachers were doing that helped their student score well. We also spent time going through each child to ensure that we didn't miss anything after the first quarter. Then the SIT team looked at all indicators and problem solved how to build in Tier 3 services.

# data[].attributes.body
Data Chats, Coaching Meetings, grade level action planning, one on one team meetings, regional team meetings with teams to action plan, SIT meetings

# data[].attributes.body
Leadership team analyzes the data
School leadership team analyzes the data
PLC's do an item analysis of the data to determine which standards were mastered/not mastered. Determine a hypothesis and create an action plan. The focus is on the prioritized standards in terms of mastery. We also look at whether or not the standard is in the scope and sequence throughout the remainder of the year.

# data[].attributes.body
We have use the quarterly check protocol with each grade level.  We have used this along with the facilitation grids to help identify specific targets within the standards to identify how we can support students in intervention.

# data[].attributes.body
PLC Facilitators: School and grade-wide data; IPG Regional team walkthrough data
SIT: Student specific Quarterly data, FSA data, SAT 10, identify Lowest 35%, ESE/Intervention PLC- work with coaches and SIT, design interventions based on the data, Admin and Coaches -during grade level PLCs, guiding through Protocol for looking at and digging deeper into the Quarterly data, identify trends, standards;  Monthly team data meetings, IRLA trajectory.

# data[].attributes.body
Admin team plus LDC's met with teachers one on one to look at their individual class data. We looked at the standards that were addressed as a whole then chose 2-3 that were a struggle for students and a standard or two in which students did very well. We analyzed the questions and came up with a plan to reteach, or enrich depending on the standard. Then as a grade level an Action plan was created so that groups of students from different classrooms could be instructed or enriched together.

# data[].attributes.body
Review IRLA, Quarterly, and EWS at School Intervention Team and School Leadership Team. Reviewed and action planned with cycles of CFAs around Quarterly and IPG walkthrough at Data Chats with PLC/Grade Level Teams

# data[].attributes.body
Data reviewed with each PLC by admin and LDC through quarterly check protocol.
Reflected on how students responded and created action plan per PLC.
3rd grade action plan in motion with connections to IRLA and quarterly checks.
Lowest 35% reviewed with leadership team and school-based intervention team for action planning.

# data[].attributes.body
Individual teacher data discussions were held reflecting on growth and trends for teachers (and teams).  Data was used to plan support and professional development for teams and/or whole instructional staff.  Grade level data chats were used to reflect on progress towards standards and refine instructional calendars. PLCs engage in inquire cycle work with essential standards. SIT engages in bi-weekly problem solving around attendance and behavioral data. Forecast center is electronic database for intervention data and grade level assessment data. Leadership team charts lowest 35% and retaineed student's data and levels of support in reading and mathematics.

# data[].attributes.body
Grade Level Data Chats
SBLT- Reviewed next steps for all grades
SBIT - discussed/planned lowest quartile

# data[].attributes.body
Data Review with teachers:
Student by student, standard by standard. Analyzed scores, misconceptions and created an action plan with each teacher to remediate or bring skills back into core. Used upcoming units of instruction to plan actions.

# data[].attributes.body
As an admin team we reviewed the data, made a plan to deliver the data to grade level teams and then met with our coaches to further narrow our data analysis with our teachers. We met with grade level teams during a full day planning we provided to select specific standards we wanted to target and strategize how we could reteach and reassess students using CFAs.

# data[].attributes.body
1.  Admin Team reviewed data from IPG Walkthroughs.  Getting ready for Narrow Walkthroughs tomorrow.
2. IRLA Checks
3.  Grade Level Data Chats reviewing CFAs.
4.  PLC work creating CFAs
5.  review of Quarterly Assessments.
6.  Math Fluency checks
7.  Student Data Binders
8. Attendance Data

# data[].attributes.body
As an admin team with our coaches we spent a day with each grade level team using the quarterly data to build action plans. We then went to 1-on-1 coaching with each teacher to build individual action plans. The afternoon of the data chat days were spent diving into the IPG tool, going on an intentionally planned walkthrough and providing a praise and polish to the observed grade level (each grade level was observed).

# data[].attributes.body
Data sources:
IRLA, Quarterly Check Data, Lowest 35%, Walkthrough Data
We are having Data Chats with each grade level team to review the data above and create action plans. All teams are being asked to plan for at least one standard in ELA or Math to teach and monitor through mastery. Learning gains have been calculated for our lowest 35% and mentors will be goal setting and monitoring monthly with those students. Teachers are given weekly reports on their IRLA conferencing to monitor.

# data[].attributes.body
~Admin & LDC reviewed all data, looked for trends and patterns compared to Central and district.
~SIT Team used quarterlies & IRLA to identify our most at-risk by grade level.  Next we will look at current supports for those students & problem-solve next steps.
~During Data Chats, we analyzed the questions by standards, reflected on practice & lesson designs, and discussed & identified action plans for Tier I and II.

# data[].attributes.body
We used EPLC time to review Q1 data with all teams using the quarterly protocol as a guide.

# data[].attributes.body
*Admin holds one-on-one data chats with teachers monthly
*Grade level IRLA chats
*IPG walkthrough trends with SLT
*Lowest 35% with SLT

# data[].attributes.body
Admin: pulled QC schoolwide, regional and district data; broke down scores by standard and determined areas that were weak; this included pulling lowest 35% students and how they scored overall and by standard; reviewed items that were below 70% average to identify misconceptions for ELA, Math and Science; pulled IRLA data too; facilitated school based leadership team meeting to review data; provided staff with summary of data and trends as well as next steps.

School Leadership Team: did a schoolwide problem analysis based on information above; went back to meet with their PLC's to do problem solving charts for actionable steps for ELA, Math and Science

PLC's: collaboratively completed problem solving charts and determined next steps for addressing areas of need for intervention times, do standards spiral back, etc

# data[].attributes.body
Admin reviewed all data.
We conducted 1/2 day data reviews with all grade level teams to review all results with teachers. We compared data by individual teacher and also looked at how we compared with our regional team and district.

# data[].attributes.body
SLT - problem solved school wide data related to Academics, behavior and attendance, monitors SUP goals

PLC's - problem solved team data related to academics, behavior and attendance, monitor team SUP goal

SIT - problem solved lowest 35% data related to academics, behavior and attendance

# data[].attributes.body
*Admin team reviewed all data and compared to 'like' schools as well as region. Created plan for Progress Monitoring Days.
*Grade Level PLCs had full day of progress monitoring with admin and LDC. Reviewed data and planned for instruction. The Quarterly Checks protocols were used.
*Admin team created priorities based on data and individual teacher data. These priorities will assist us in providing professional development, coaching, and more frequent monitoring.