What Are Reversions
Programs with multiple tracks will submit a separate Rank Order List of applicants for each track in order to fill their position(s). However, one or more of the tracks may not ultimately be successful in filling all of their positions in the matching process. In this situation, a program may wish to move the unfilled position(s) from one track to another track where the position(s) may be able to be filled, in order to increase the likelihood of filling all available positions in the program.
To address this situation, a mechanism is available in the matching algorithm to move one or more positions that remain unfilled from one track to a second track, so that an attempt can be made to fill the available position(s) with applicants on the Rank Order List for the second track.
This is referred to as "reverting" unfilled positions from one track (the "Donor") to another (the "Receiver"). The decision to move the position from one track to another using a reversion depends on whether or not the attempt to fill the position in the original track within the matching process is successful.
Reverting an unfilled position within the matching process is different from deciding before the Rank Order List deadline to move a position from one track to another.
For example, a program offering multiple tracks in the Match may decide, in advance of the Rank Order List deadline, to move a position from one track (e.g., a "Scholarship" track that does not receive anticipated funding) to another track (e.g., a "Full Tuition/No Funding" track). In this case, no attempt will be made to fill that position in the funded track within the matching process. Program Directors can adjust the number of positions to be offered by each track at any time prior to the Rank Order List deadline.
On the other hand, reverting a position within the matching process applies when an attempt is made to fill the position in the original track within the matching process but the position remains unfilled.
The option to revert an unfilled position within the matching process should be used only when the final decision to move the position from one track to another cannot be made in advance of the Rank Order List deadline, but depends on whether or not the position is filled in the original (Donor) track within the matching process.
Examples of Reversions
Any type of track can revert unfilled positions to any other type of track. Some situations where reversions of unfilled positions within the matching process might be used are described below.
Reversions From Funded Tracks to Unfunded Tracks
A program can offer one track where applicants receive a scholarship and another track where applicants pay full tuition. You can specify that some or all of the positions that remain unfilled in the scholarship track should revert to the full tuition track, and an attempt should be made to fill the positions in the full tuition track.
Reversions From a Track in One Location to a Track in Another Location
A program offering more than one track in different locations may choose to revert unfilled positions from one location to the other. For example, a program offering one track in Location A and another track in Location B, may choose to revert some or all of the positions that remain unfilled in Location A to Location B, and an attempt should be made to fill the positions in Location B.
Obtaining a Specific Distribution of Applicants Based on Characteristics of the Applicants
There may be a small number of programs that have unique needs that require them to match with a particular "mix" or distribution of applicants based on specific applicant characteristics (e.g. a mix of applicants based on location of residence or school of graduation). In this case, the program would need to submit multiple Rank Order Lists for a single track and may wish to specify reversions between those multiple lists.
Contact NMS at email@example.com or by phone at 800-461-6322 if you would like to discuss whether or not reversions would be useful for your program.
To request the reversion of unfilled positions within the matching process, a track must provide written instructions to NMS.
Forms must be completed, signed and submitted to NMS by April 13, 2018, either as a scanned e-mail attachment to firstname.lastname@example.org or by fax to 844-977-0555. After sending the form to NMS, please wait at least one business hour (9:00 a.m. to 5:00 p.m. ET Monday to Friday) and then contact NMS by telephone to confirm that the form has been received and is legible.
Rules For Reverting Unfilled Positions Between Lists
Please note the following rules when submitting a request to revert unfilled positions between Rank Order Lists.
A) Reporting of Unfilled Positions After the Match
Any position that is reverted from one track to another will be reported after the Match as belonging to the Receiver track to which it was finally reverted (even if the position remains unfilled in the Receiver track).
For example, suppose Track A enters the Match with 3 positions, Track B starts with 2 positions, and Track A is to revert all unfilled positions to Track B. Then if Track A fills only 1 position in the Match, the 2 remaining unfilled positions will revert to Track B. In that case, after the Match, Track A will be reported as having 1 filled position and no unfilled positions, and Track B will be reported as having 4 positions (whether or not all 4 were filled in Track B).
B) Number of Positions To Revert
A Donor can revert some or all of its unfilled positions. It can also revert unfilled positions to more than one Receiver.
For example, if Track A has 3 unfilled positions it can choose to revert its first unfilled position to Track B, its second unfilled position to Track C, and it can choose not to revert the third unfilled position to any other track.
C) Chained Reversions
Reversions of unfilled positions can be "chained"; for example, List A can revert unfilled positions to List B, and if some positions remain unfilled on List B, then these positions can revert to List C, and so on.
However, a chain of reversions cannot "loop back" to the beginning. For example, if you request that List A revert unfilled positions to List B, then you cannot also request that List B revert unfilled positions to List A. Similarly you cannot request a chain of reversions that moves unfilled positions from List A to List B, then from List B to List C, and then from List C back to List A.