Gravity Forms / Registration Pairing (Event Roommates)

The project is called “RoomMatch”. Basically, we have an event registration form (GF). for employees to attend a multi-day event. Due to limited hotel space, some attendees are required to share a room and we need a system to allow them to pair up. The basic workflow is: 1. Attendee completes registration form 2. On confirmation page is a new form (or link to form) for pairing of roommates. - if there are no entries, it says come back later - a link to the form is also in the notification email the registrant received. 3. The roommate form needs to look at all the entries received and display a potential list of roommates (so all entries except the person viewing the form, or anyone that is already paired) This form has instruction copy at the top (should be customizable), and a dropdown listing unmatched, roommate require First/Last names for the person to select from. statuses of “OPEN” (not paired), “PENDING” (in the process of pairing, see below), “CONFIRMED” (roommates confirmed). “NO PREF” (a selection a person can choose on the form is they have “no preference” and will be assigned a roommate by admin. and “NONE” (executives) So the “selection” of available roommates on the form are only showing “OPEN” and “NOPREF” 4. Process - Once a person has selected a potential roommate from the list, both persons are set to PENDING (to remove them from the list of options) and two emails are sent. The email text should be customizable. 1. To the requestor - “We have sent an email to BBB (person they picked) informing them you’d like to be roommates. If they approve you will receive an email confirmation 2. To the person they selected - “AAA has requested to be roommates. If you approve click here. If you do not approve click here. a. If the person “approves” the match, both are set to “CONFIRMED” and sent a message stating they are matched up. b. If the person “declines” the match, both are set back to “OPEN” and sent emails and he process restarts 5. Exceptions. We need to account for “gender”. In most cases, unless a husband and wife are both employees, the list of roommates will need to be filtered by a field on the original registration form usually “gender: Male / Female”. Executives. Some employees are NOT required to go thru the process, and so we usually have a field, such as “Job Title” that has conditional logic values that will set the roommate status to “NONE” keeping them off the list. 6. Admin/Backend pairing – after a set deadline (configurable) of “self paring”a process for pairing the remaining registrants needs to be done on the backend, this should bypass the “approve/decline” email, and just send they “you’re matched version of an email. To be considered you must have read this description, and include the words gravity forms in your reply so I can filter our the spam responses. There are some other minor details, but this is the core of the requirements. The application needs to be able to be added on to any event/site I want, so it should be basically a Gravity Forms Feeds based plugin