Data Tracking & Usability NH RESPONDS Brent Garrett & Pat Mueller, Evaluators Amy Jenks, Project Coordinator

Agenda Evolution of data tracking (Why?) Data collection instrumentation (Who? What? How?) Increasing usability (Tracking Systems) Local site examples (So What?) Lessons Learned (If we had it to do over again…)

Evolution of Data Tracking SPDG reporting requires process and outcome data Selection/Development of Assessments/Tools Frequency and efficiency of data collection Tracking and reporting Sharing and using data for improvement at school/district/state-grant levels Sustainability

Evaluation Workgroup To serve in an advisory capacity to project evaluators. Evolved in role over time.

Data Collection Instruments Assessment/Tools (hand out) Who collects it How is it collected What is collected

How do your projects determine types/frequency of data to be collected and reported?

Increasing Usability NH RESPONDS School Summary of RTI Implementation Sheet (hand out) Assist evaluators, professional development providers, and school/district teams. The more this was used, the better the collection, sharing, and analyses of data.

Local Site Examples Review a completed NH RESPONDS School Summary of RTI Implementation Form NH RESPONDS staff Level: Data collection and reporting Used for improving training & TA; focus on sustainability Use at district Level: Reviewed progress to date Discussed fluctuations in data – what do they mean? Clearly identified next areas of focus Renewal of commitment & resources for stabilization/sustainability Use at school level: One page view of data useful Data needs further discussion and unpacking Consistency of features of model across content areas and tiers Fueled discussions about patterns in data; deepened knowledge of Tiers

How has data been used with your leadership teams and/or school teams?

Lessons Learned What did we do well? Team process (Evaluation Workgroup) for tool review and development. Development of School Summary of RTI Implementation Sheet looking across content areas. Ongoing review of data. What would we do differently? Think about the number of instruments being used – streamlining. The number of people (and staff turnover) involved with data collection – ensuring consistency in data collected (version control, formats, etc.). Accessible repository earlier on for project tools and data.

What lessons have you learned in your project related to data tracking and usability?

Contact Information ( Pat Mueller, Brent Garrett, Amy Jenks, NH