From the Item Bank |
||
The Professional Testing Blog |
||
Eight Tips for Reporting Failing Test Scores on Licensing and Certification TestsDecember 4, 2015 | |For the people who take your test, after all the studying and stressing out, nothing beats getting a certificate with a shiny gold seal in your mailbox. That makes a passing score report fairly easy to design. It’s going to be a variation on “Hooray! You made it!” Chances are, though, that not every candidate is going to get that letter. What are you going to tell the candidate who fails? Here are eight pro tips: 1. Tell them their score 2. Consider reporting raw scores When different forms have different passing scores, consider using a scale (see below). But if you think your constituency can digest the information, why not give it to them straight? Announce, Your passing score will vary depending on the difficulty of the particular set of questions you get. Then, when someone fails, tell them, You took a form of the test that had a passing score of 72/100. You answered 68 questions correctly. Unfortunately, you did not pass the test. 3. Avoid a scale that can be confused with another scale By the same token, if your test has 180 questions, don’t use a 120-to-180 scale! Someone is sure to confuse scale scores with raw scores. 4. If you’re using a scale, don’t overdo it 5. Plan ahead to report subscores If you intend to provide feedback about performance in a content area, you must make sure you have enough questions in the test to make that feedback meaningful. That takes advance planning. 6. Raw subscores aren’t always helpful Testing standards require us to let score users know about imprecision in scores. I asked Ron Hambleton, Distinguished University Professor at UMass Amherst, how to achieve this without leaving the impression that these subscores are a wild guess. He recommended communicating “the concept of imprecision” without necessarily “being quite explicit about the breadth of the [error] band.” One way of doing that is to use performance-level indicators instead of raw numbers. 7. Use defensible performance-level indicators 8. Include other useful information Categorized in: Industry News |
Comments are closed here.