K-12 Student Assessment Scoring and Reporting

1. K-12 Student Assessment Scoring and Reporting Dr. Qian Liu Gabriel Colorado 2018-2019 Annual District Assessment and Accountability Coordinators Meeting

2. Overview – Scoring and Reporting • Scoring and Reporting Resources • Pre-Reporting activities • Late Reporting process

3. Scoring and Reporting Resources • Location: FDOE ShareFile – K-12 Scoring and Reporting -- Resources • Contents include: • District Student Results (DSR) and District/State Aggregated Results (DAR/SAR) file layouts • Guides and Instructions • Caveon-Related Materials

4. Scoring and Reporting Resources • Location: FSA Portal (https://fsassessments.org/) • Discrepancy Resolution System (DRS) User Guide • Spring 2018 District Training Webinar • Understanding FSA Reports, Spring 2018

5. Scoring and Reporting Resources • Location: FDOE Website • Understanding FSA/NGSSS Reports (http://www.fldoe.org/accountability/assessments/k-12-student-assessment) • Reporting Category Results (http://www.fldoe.org/accountability/assessments/k-12-student-assessment/reporting-cat-results.stml)

6. Pre-Reporting Activities To ensure the scores are reported for your students on time: • Provide accurate student information during the PreID process: • FLEID number • Student Grade Level • Use PreID labels • Invalidate a test ASAP when you know there is a duplicate test for your students • Return answer documents to the right vendor

7. PreID Updates/Reminders • Pearson Access Next requires Unique FLEIDs • Starting with Fall 2018, if a student is uploaded with an FLEID that is already being used, PANext will run a check against the student’s last and first name before allowing you to update the student’s organization enrollment. • Remember – corrections made with the School Grades Office do not transfer over to testing data. Make sure that if you notice any critical issues that require new score report to be generated that you reach out to Scoring and Reporting team.

8. PreID Dates – Fall 2018

9. PreID Dates – Winter 2018

10. PreID Dates – Spring 2018 • No dates finalized yet, but we understand the need to prepare so we will let you know as soon as we can. • Last year: • FSA ELA/Math in November • FSA EOC in January • NGSSS in February • With a later testing window, we will try to establish a PreID window as late as possible.

11. FLEID Notes • Private-to-Public Students • Districts must submit student information to FDOE’s Education Data Warehouse (EDW) to request an FLEID assignment for testing. • Private Schools • For private schools approved to test through the application process, FLEID assignments will be addressed through our office – if you have any questions please direct them to Gabriel Colorado or Catherine Altmaier.

12. FLEID Notes Duplicate Issues • False or inaccurate FLEIDs can create duplicates resulting in discrepant records within & across districts. • Ensure your students have been issued an FLEID prior to testing. • Please contact EDW to sort out any FLEIDs that are being claimed by different districts.

13. Late Reporting Process • After regular reporting, To-Be-Scored paper answer documents are often found packaged with Not-To-Be Scored materials. These materials are included in late reporting waves. • Additionally, Not-Reported and/or discrepant records need to be updated. These updates are submitted after the initial release via the Score Inquiry system/Discrepancy Resolution System/ShareFile (for Caveon Appeals). • Spring: two waves of late reporting. Fall/Winter/Summer: one wave of late reporting.

14. Score Flag/Not Reported Code • 1 / 9 = Score Reported (initial vs. late reporting) • 0 = Not Tested (NT) • 2 = Did Not Meet Attemptedness Criteria • 3 = Do Not Score/Invalidated • 4 = Insufficient Match to TIDE • 5 = Below Grade Tester • 6 = Duplicate Record • 7 = FDOE Hold • 8 = Caveon Invalidation

15. Not Reported Codes Score Inquiry System Discrepancy Resolution System/PearsonAccess Next ShareFile(Caveon Appeals) Where to Take Action NT NR2 NR3 NR7 NR4 NR5 NR6 NR8 Not Reported Codes

16. After the initial release of the test results, the Department opens a website called the Score Inquiry System. The Score Inquiry System allows District Assessment Coordinators (DACs) to inquire about missing reports or to ask for a student’s score to be reviewed. A deadline for submitting a score inquiry is established for each test administration. We encourage you to submit score inquiries before the deadline and to periodically check the system for inquiry updates. Score Inquiry System

17. For example: NT: Request to search for missing documents if you believe the student submitted a completed test. NR3: Request to UNDO DNS so the score can be released during late reporting. Please refer to the Score Inquiry System User Guide (posted to FDOE Sharefile) for more details. Score Inquiry System

18. Each test administration, a Not-Reported code of 4, 5, or 6 may be applied to a test record due to incorrect or missing student information. These records are referred to as discrepant records in the FSA system. After the initial test results have been released, FDOE assists districts in resolving these discrepancies to ensure that student results are released in the most timely manner. Discrepant Records

19. The DRS was developed to simplify and streamline this process by providing a user-friendly interface to more easily and efficiently resolve these discrepancies. Once the initial results have been released, the DRS will provide district-level users direct access to the discrepant records in their district. It will also allow them to take the appropriate action needed to resolve them. Discrepancy Resolution System (DRS)

20. For example, if a student receives an NR5, meaning they were flagged as a Below Grade Tester, you can use the DRS to override the NR code and forward the test for scoring if you believe the student grade should be the same as the test grade. Please refer to the DRS user guide/PearsonAccess Next user guide for more details. Discrepancy Resolution System (DRS)

21. ShareFile – Caveon Appeals • Student invalidations are posted to ShareFile following each administration. • The Caveon Appeals Guide & Parent/Guardian Letter templates are available on ShareFile. • All Caveon appeals must be submitted via ShareFile by the designated deadline. • Appeals are reviewed in the order in which they are received. • Any appeals received after the deadline will not be accepted.

22. Common Question and Answer What do writing condition codes mean? • A = Blank Essay There was absolutely nothing in the response field. • B = Insufficient The student may have written one or two sentences, or a few scattered words. • C = Off-topic The student wrote a response long enough to be scored but did not address the prompt.

23. Common Question and Answer What do writing condition codes mean? • D = Foreign Language The student wrote a response long enough to be scored but did not write the response in English. • F = Illegible, Incomprehensible The student wrote a response long enough to be scored, did not write clearly or neatly enough.

24. Common Question and Answer What do writing condition codes mean? • G = Copied The student wrote a response long enough to be scored, but either copied the prompt or the passage for the majority of their response. These responses do not have enough original content in order to assign an ELA Writing score.

25. Common Questions and Answers Writing Condition Codes, Dimension Score and Score Status Flag

26. Contact InformationK-12 Scoring and Reporting Team Qian Liu Gabriel Colorado Jessica Colvin Shukun Fang Seung-Yeon Ha Patrick Herrington Esra Kocyigit Yingru Liu James Low 850-245-0867 850-245-0779 850-245-5048 850-245-0909 850-245-0783 850-245-0524 850-245-0769 850-245-5158 850-245-0085 Qian.Liu@fldoe.org Gabriel.Colorado@fldoe.org Jessica.Colvin@fldoe.org Shukun.Fang@fldoe.org Seung-Yeon.Ha@fldoe.org Patrick.Herrington@fldoe.org Esra.Kocyigit@fldoe.org Yingru.Liu@fldoe.org James.Low@fldoe.org

27. Contact InformationK-12 Scoring and Reporting Team