Currently, conflict alerts are created only after a schedule is activated. There are cases where some schedules require multiple approvals. While these are being "processed" new schedule requests for the same venue and date/time are submitted. The potential for doublebooking increases. Also, it is counter productive to be manually researching conflicts via calendar when the system can automatically do it. I suggest that the conflict alert be created BEFORE a schedule is activated or finalized. This would be much more helpful in efficiently managing numerous schedule requests.