RAJA7: Registered, Waitlisted and Confirmed Are Different List States

Follow a four-place workshop timeline in RAJA7 information to understand registration, waiting-list movement and confirmation without assuming every entry has a place.

Four places are available, but six people have registered interest. That does not automatically mean somebody's entry is wrong. The list may distinguish registrations from allocated places and place confirmations. A RAJA7 activity reader needs those state definitions before interpreting a total. In the fictional workshop below, capacity is four throughout. What changes over the afternoon is the relationship between a person's registration, their invitation and their response to that invitation.

Six names, four places

At 12:00 IST, the workshop receives registrations from A, B, C, D, E and F in that order. Its written procedure offers places to the first four eligible entries. E and F join the waiting list. Registered therefore applies to all six; offered a place applies to four; waiting applies to two. Listing six registrations does not imply six seats, because these counts describe different sets within the same process.

The procedure requires an explicit confirmation by 16:00. At 13:00, A and B have confirmed. C and D have not yet responded. The page can accurately show six registered, two confirmed and two waitlisted, with C and D still holding pending offers. Adding only the confirmed and waitlisted counts gives four, which leaves two people unexplained until the pending-offer category is included. A partial summary is not necessarily a complete census.

A release changes the queue

At 14:00, C declines the offered place. The written queue rule offers it to E, the first waiting entry. E's state changes from Waitlisted to Offer pending. F remains Waitlisted. C's registration remains part of the historical registration count, but C no longer holds a place. This is why a growing registration history and a fixed capacity can coexist. One counts entries made; the other limits places currently held or confirmed.

At 14:30, E confirms. There are now three confirmed participants: A, B and E. D still has an offer pending, and F waits. If a RAJA7 summary shows the waiting count falling from two to one, that alone does not mean both waiting participants were accepted. We must see who moved and to what state. E first received an offer, then confirmed it. Those two transitions should not be compressed into one assumed event.

The response deadline has a job

At 16:00, D has not responded. Our procedure states that an unconfirmed offer expires at that time. F then receives the released place, with a separately stated response deadline of 17:00. D does not become a confirmed participant merely by remaining registered. F does not inherit an already-expired deadline without notice. Every deadline in this example belongs to a specific offer stage, so the timeline remains meaningful for the person receiving it.

By 16:40, F confirms. Four participants now hold confirmed places: A, B, E and F. The activity's capacity has never increased. C declined and D's offer expired, allowing the queue to move. The six original registrations remain six historical entries. This resolves the apparent puzzle that the “registered” total did not fall when people left the active place list. Historical and current-state counts are allowed to tell different parts of the story.

We would explain waiting position carefully. E being first in the queue meant first consideration under the stated rule when a place became available; it did not create an extra place. In another activity, eligibility or category rules could change queue order, so this example's order must not be exported without its conditions. A waiting number is informative only with the rule that determines how that queue moves and what response is required after an offer.

To test the distinction, ask where each person belongs at 15:00. A, B and E are Confirmed; D is Offer pending; F is Waitlisted; C is Declined. All six have a registration history. The four-place capacity is occupied by three confirmations and one pending offer. This single snapshot proves why “not confirmed yet” cannot automatically mean “waitlisted”: D and F have different rights to the next step despite both lacking a final confirmation.

The afternoon ends with four confirmations and a six-entry registration history. No contradiction remains once the states are named. In RAJA7 list reading, the practical question is what the status allows now: wait for an opening, respond to an offer or attend under a confirmed allocation. The label is part of a process, and the worked timeline shows exactly how a person can move through that process without the capacity number changing.