Task Relation "As Soon As Possible" Does Not Update Start Date Of Succeeding Task When Previous Task Finishes Early

I understand what you are describing, but my question is, should it change the Planned Start for the task that follows it? Does the Projected Start Date for the task that follows show that the task can now start ahead of schedule?

Thanks for this comment. Let me clarify with the colleague who reported this to me. I am not sure he checked the Projected Start Date. I guess the confusion also arises as in the standard/default Views the Planned Start date is shown, not the Projected Start date. Best regards Tanja

Thanks a lot for this hint! I did not get that when creating the ticket previously. The answer there was just that "it works as expected". So I asked the user to switch the View, e.g. "All Dates" and he confirmed that the Projected Start Date is adjusted if a predecessor task finishes early and the succeeding task has constraint "as soon as possible". Best regards Tanja

This would be a nice add for projects when needed. It could be an additional task constraint that allows the tasks to adjust when needed. Some workers might not feel the sense of urgency to work on a task earlier but if the due date adjusts on the calendar automatically it will help them know it's time to GO!

Hi! I just stumbled upon this thread from a few years ago. This is exactly what I am trying to do. Is there a way to have our worker's work lists update with the projected dates instead of the planned dates? As an example, we have a task that finished early on a project, so I would like the next task to show up as the projected date in my coworker's work list instead of just staying at the planned date so that we can get everything completed more quickly. The way it is set up now, tasks could lag for no reason.

Hi @vgoldman, 

As a primer about expediting Projects with Tasks that (often) complete ahead of their plan, I invite you to review our As Soon As Impossible post.

If you're unable to reorient your processes to use the built-in Projected dates (which are indeed "aware" of such opportunities, and the approach I would therefor recommend), you could instead then consider (whether manually using a report, on mass using our Excel Updater solution, or automatically via Fusion if you have it):

• identifying ASAP Tasks whose Actual Completion Date is indeed prior to their Planned Completion Date
• updating the Task Constraint from ASAP to Fixed Dates and setting the Planned Completion Date to the Actual Completion Date
• recalculating the Project Timeline to expedite the subsequent ASAP Tasks that are still (not yet) complete

Regards,

Doug