Recurring meetings being scheduled as "Tentative" for one or more attendees (e.g. doesn't align with a shift)

Name of Feature/Request: Recurring meetings being scheduled as “Tentative” for one or more attendees (e.g. doesn’t align with a shift)

What financial, time savings, or quality of life improvements will occur from this: Avoid Tentative meeting Conflict from going un-resolved Things to Consider: When a meeting gets saved, there are some logic checks to determine if all attendees are available (e.g. other confirmed appointments, time off, shifts, holidays). If there are conflicts on one or more attendees’ calendars, it prompts the user when it is being done manually, and the user has the option to save the meeting anyway. IF there are conflicts for one or more attendees, then the appointment will still get saved for them, but it will mark them as “Tentative” for attendance. The problem arises because even if that meeting is something being planned on by the attendees, if they are marked Tentative, then something else can be scheduled over the top without warning of any conflicts.For example, there is a recurring weekly meeting that runs from 7:30 AM - 9:00 AM (https://APP.Striven.com/hr/Appointments/AppointmentInfo.aspx?AppointmentID=1029584&calendarId=42), and for any attendee whose Shift is supposed to start at 8:00, it always creates the meeting and sets the attendees as Tentative. THEN, someone else can schedule a meeting from 8:00 - 9:00 during the same time and it does not show as a conflict because the attendees are not “Confirmed” for the original 7:30 - 9:00 meeting.Suggested Alternative Solutions: Anytime a meeting or a recurring meeting gets scheduled that results in one or more attendees having a conflict and thus being marked as tentative, send a separate notification to all attendees with a conflict so that they can resolve it and/or mark themselves as Confirmed for the meeting. This will have the same effect as the manual method described above.Original Description:

Attempted Solutions So Far: None Listed

Digging deep - Any additional Why behind this request / How was this accomplished before Striven in what system or software: Previously accomplished: Tentative Meeting Conflict can go unresolved

StrivenID: 2258931