How Changing a Project Zero Date Affects Location Task Target Dates

Goal

In some cases, individuals are provided with the ability to manually change a task's Target date at the location/team level. While projects work off of a baseline, which assigns tasks their target dates, it's understandable timelines may vary from the baselines expectation; manually changing the target date of certain tasks allows for a level of customization for that specific location. Later, when the zero date of the project is changed, there are a few ways Pacer will handle the manual changes that have happened. A screen will prompt you with these options when changing the zero date at the Project Control Hub. Below, we'll explain those options and their ramifications. 

Note: This feature is available on Jog, Run, and Sprint plans.

How To

1. Go to the Project Control Hub and select the Locations tab.
2. Click the calendar icon next to a location or use the Bulk Actions dropdown and choose Change Dates.
3. In the modal that appears, update the location’s Zero Date.
4. Select one of the following task update options:
   • Simple Shift (Default) – Shift all tasks by the number of days between the old and new Zero Date. Tasks with static dates remain unchanged.
   • Keep Custom Dates – Shift tasks by the same number of days, but skip any where the Target Date has been manually customized. Tasks with static dates remain unchanged.
   • Full Reset – Recalculate all task dates based on the baseline template and the new Zero Date. Tasks with Static Dates will also reset to the static date that was designated on the baseline.
5. Click Save to apply the date change and task updates.

Tip: If you're unsure whether tasks have been customized, choose "Keep Custom Dates" to avoid overwriting location-specific changes.

Warning: The Full Reset option will overwrite all existing location task dates, including custom edits.

Examples

• Simple Shift: If the original Zero Date was October 1 and it's changed to October 8, all of the location's tasks will move 7 days later. A task originally due on September 15 will now be due on September 22.
• Keep Custom Dates: Using the same date shift example, a task that was manually changed to September 10 (instead of its original September 15 baseline) will stay on September 10. All other tasks shift.
• Full Reset: All location task dates are recalculated as if the project was just published with the new Zero Date of October 8. Custom edits are lost, and all due dates match the baseline rules (e.g., 15 days before Zero Date = September 23).