https://www.loom.com/share/d5561fca8ad4452fa0dfffe305884e38?sid=58ed8e9d-1a15-47e1-ab5f-f13263796607 Issue: Currently, NetGym does not detect when a duplicate sub request is created for the same class. This allows different users to unknowingly create and approve multiple sub requests for the same session, leading to confusion and scheduling conflicts. Example: A sub request for a 10:45 AM class was originally created by Lucila on Dec 21. Another sub request for the same class was later created by Jenny on Feb 27, resulting in two separate approvals for the same time slot. Instead of creating a new sub request, Jenny should have reopened the existing request. Current Workaround: The team must manually check for existing sub requests before creating a new one. Now the manager has to delete the duplicate. If a sub needs to withdraw from an approved request, they should reopen the existing request instead of submitting a new one. Proposed Solution: 1️⃣ Duplicate Detection & Prevention: Implement a duplicate check when a user attempts to create a new sub request. If a request already exists for the same class, time, and location, prompt the user with a warning: “A sub request already exists for this class. Do you want to reopen the existing request instead?” Provide a "Reopen" button similar to when we are integrated with the scheduling system 2️⃣ Restrict Multiple Requests for the Same User: If a user is already approved to sub for a class, prevent them from creating a new request for the same class. Display an error message: “You are already approved to sub for this class. If you can no longer teach, please reopen the existing request.” 3️⃣ Improve Reopen Visibility: Ensure the "Reopen Request" option is clearly visible on both web & mobile so users are guided toward the correct workflow. Future Considerations: The double-booking prevention feature (which prevents a sub from being approved across two different requests at the same time) is already in development but does not address duplicate request creation—this ticket is a separate enhancement. Consider adding admin-level controls to merge duplicate requests in case they slip through.