Overview: When creating scheduled events in L2L you have a few options to set for various event dispatch dates. These dates not only impact the way the event launches but also how it's viewed within the system when it does launch. Below are descriptions of the various functions.
Launch Date: This is the date that the scheduled event will become an open dispatch in the system. It is also the date that the Resources will be able to see it on the dispatch screen.
Scheduled Date: The date you expect the work to be completed. You may launch an event on Monday, for example, and have it due on Friday. If you have planned ahead and scheduled production to be down on Wednesday to physically complete the work, you would set the scheduled date to Wednesday.
Due Date: This is the date that the work is expected to be completed. Not completing the event by the set due date will impact your scheduled on-time completion percentage and may also trigger notifications if configured.
Launch Prior: This is a background event time setting. How it works is that in L2L all scheduled events are based on the due date. So, for example, if you create a new event and set it originally to be due on the 15th of every month and launch on the 1st, than your launch prior would be equal to 15 days. Let's say a few months later, you decide to push the due date out 5 additional days to now be due on the 20th: it will change your launch prior to 20 days.
Note: If your launch prior spans multiple months, your next launch date won't always be the same because not all months have the same number of days. It will still be due on the same day, but the launch date may vary.
Key Point: If you only want to change the due date of one scheduled event and not all subsequent events, than simply change the due date of that specific event within the dispatch itself and not on the scheduled event.
Key Point: If events are launching immediately upon completion, you may want to consider using our "Bring Schedule Current" functionality or investigate the "Schedule History" to ensure the launch prior set point is correct.
Key Point: We often hear that schedules are due at the end of a month, but in months with fewer days, the scheduler then sets the next due date as the last day of whatever the previous month's last day was. For example, if you set your schedule up to be due on the 31st of each month, when February comes around, the due date changes to the 28th and continues to be due on the 28th for each subsequent month.
Changing Due Date in Launched Scheduled Event (Edit Dispatch Screen)