Consistently document SEL implementation, including ongoing successes and challenges they encounter throughout the year
Collecting data to document SEL implementation and monitoring outcomes throughout implementation helps districts continuously improve.
Below you’ll find an overview of: WHAT high-quality implementation looks like, WHY it’s important, WHEN to engage in this key activity, and WHO to involve. Also see the PROCESS page for step-by-step guidance on how to engage in the work, and the RESOURCES page for additional tools to support your efforts.
Documenting implementation and outcomes means that districts are regularly reviewing their progress toward goals and action plans and collecting implementation and outcome data in a timely manner. This documentation occurs throughout the DO phase of the Plan-Do-Study-Act continuous improvement cycle (read more about PDSA Cycles in Key Activity: Planning for Improvement) and provides rich information for the district to reflect on and learn from.
A strong approach to documenting implementation and outcomes means that districts:
Consistently document SEL implementation, including ongoing successes and challenges they encounter throughout the year
Monitor the implementation process to address challenges that arise.
Follow the timelines established in SEL plans to collect implementation and outcome data.
Use the Rubric to assess your approach to documenting implementation and outcomes.
Even with a high-quality action plan, you may never know whether, how, or why your efforts are succeeding. By documenting ongoing successes and challenges, your district is equipped to problem-solve in real time to support high-quality implementation. Collecting outcome data enables your district to provide information about whether SEL implementation is producing desired changes and can help you decide whether to adjust or deepen your efforts.
Your district’s SEL team will play a key role in documenting implementation and outcomes. In addition, you will want to include:
Documentation ideally occurs on a regular, ongoing basis throughout implementation, though the specific timing will depend on the type of data collected: