Data Quality & the Consolidated District Performance Report (CDPR)

1. Data Quality & the Consolidated District Performance Report (CDPR) Jesse Parsons & Russ Sweet, Education Specialists Oregon Department of Education August 2014

2. Agenda • Purpose of data collections • How data flow from LEAs to the USED • Ensuring data quality in the CDPR • Sources of data • Submitting data • Assistance • CDPR changes for 2014-15 • ODE review of the CDPR data collection • Telling your story through data

3. Purpose of Data Collections (General) • Improved educational outcomes for students • Compliance with Section 9303 (Consolidated Reporting) of ESEA

4. Purpose of Data Collections (General) • Provide data to the USED and to Congress • Data are used to estimate program performance • Funding and budget decisions are based on performance results (Government Performance Results Act-GPRA) • Communication Tool

5. Flow of Data from LEAs to the USED

6. What is the CDPR? This is an annual data collection for districts that is used to complete required federal reporting • Title I – A Students & Programs • Title I – D Neglected & Delinquent Academic Achievement • Title I – D Neglected & Delinquent Programs & Facilities

7. Ensuring Data Quality in the CDPR • If data quality is not a priority at the local level, the problems become harder to identify as the data are rolled up-problems can become hidden • If data issues are recognized late in the process, it is more difficult (and less cost effective) to identify where the issues are and correct them in time

8. Ensuring Data Quality in the CDPR • Both ODE and districts have responsibility for ensuring data quality by implementing systems that make this a reality • Using/submitting trustworthy data • Using/submitting accurate data

9. How is this accomplished? • Understand and communicate the collection process • Provide technical assistance in advance • Odyssey training • Training webinars scheduled for each data collection • Develop relationships with LEA and program staff

10. How is this accomplished? • Develop multilevel verification processes • Track problems over time • Use the data • Problem solve together

11. Submitting Data • CDPR data are collected through a web-based application • Set aside a block of time to enter data into the system. It does not allow for partial data saving and then returning later

12. Data challenges from year to year • Performance vs Proficiency • Race and Ethnicity • Counting students (disaggregation) • Program identification (Title I – D)

13. CDPR Assistance • Webinars are held prior to the opening of the collection • The CDPR User Guide explains the data elements • ODE Specialists can assist with questions about the data elements • The ODE Helpdesk can assist with issues about the web application

14. Changes being made by the USED to the CDPR • Title I-A (minor changes) • WHAT ARE THE CHANGES ? • Title I-D (counts of Special Education and LEP students and transitions) • WHAT ARE THE CHANGES ?

15. Data Collections Telling Your story

16. What does the data reveal about: • The strengths of our program(s)? • The challenges of our program(s)? • The priorities we should focus on? • The kind of professional development we need? • Who we are as opposed to who we thought we were?

17. Tips on using Data • Actually use data to tell your story • Share it in language the audience can understand • Anecdotal and Quantifiable both work • Anticipate questions and have answers ready • Be authentic • Others?

18. Questions

19. Contact Information • Russ Sweet (503) 947-5638 russ.sweet@state.or.us • Jesse Parsons (503) 947-5602 jesse.parsons@state.or.us • Emily Swope (CDPR support) (503) 947-5642 emily.swope@state.or.us • ODE Helpdesk (503) 947-5715

20. Thank you for attending today’s session