There are two common strategies used to manage a testing schedule for credentialing. Depending on your program’s philosophy about access and availability, and policies for managing your exam item bank, one of the two strategies will likely fit you better than the other. These strategies are pre-defined “Test Windows” and “On Demand Testing”. I thought I would post a brief discussion of each approach and the potential advantages of each one. Both of these strategies describe calendar availability of exams, not eligibility. Exam eligibility management policies may be employed with either strategy.
Test windows are defined calendar periods where a credential sponsor offers exam scheduling. For example, a candidate might be allowed to sit for their exam within the following time periods:
- · Jan 1 – Feb 28
- · May 1 – June 30
- · Sept 1 – October 31
In this case, the three test windows are the only times when a candidate can take the exam at the test service provider.
In on demand testing, a credential sponsor allows a candidate to sit for their exam on any day of the year (per seat availability at the test service provider). On demand testing has no strict time periods where exams may or may not be scheduled.
There are certain advantages to test windows. First, it provides you and your candidates a defined calendar in which to plan and execute the events surrounding testing. Many people work better with deadlines. Test windows, by their nature, provide a series of deadlines for everyone to strive for. A published calendar for everyone to work towards tends to reduce confusion and provide motivation for everyone to complete by the deadline.
Second, it gives your staff well defined periods to expect peak demand for customer service from your candidate population. With test windows you can coordinate you yearly activities for more efficiency. For example, during the testing windows, you can focus your attention on successful exam delivery. Outside the testing windows you team can focus on other program related tasks like CE processing or new applications. These cycles will make your staff more efficient allowing them to seamlessly move from one focused activity to the next.
Finally, a unique benefit of testing windows is to support ongoing item statistics and analysis. With testing windows you can normalize the exam performance, establish the exam cut score for each window, and generally maintain your item bank. If you choose to use testing windows in this way, the test service provider (TSP) holds the results until all tests in the window have been delivered. Then, the TSP or scoring agent runs the item psychometrics on all the results in the test window to eliminate poor items and establish the passing score for the exam. Given a large enough examinee population, this strategy offers you the opportunity to prove and vet the skill set of the entire “class” of examinees. Unfortunately the downside of this approach is timeliness and cost. Candidate’s don’t walk out of the exam room with a final score and the additional steps add time and cost to the scoring process.
I provided the above advantages based on our experiences with clients. I am certain there are others, especially in terms of the relationship with a test service provider. For example, it may be cheaper to contract with a test service provider for test windows than for on demand testing, if the TSP has a better forecast to reserve seats. Can anyone provide more detail regarding test window vs. on demand pricing or around additional advantages?
Next posting – On Demand Testing advantages