


Hi All - wondering about the functionality of this scenario... we have a schedule with predecessors and task constraints of "as soon as possible", but in the generation of the schedule we find we can modify some tasks to happen on specific dates, so we change those tasks to a specific date and task constraint of "must start on" or "must finish on". The Progress Status of that task then typically flips to At Risk, even though it is a date later in the future. Is this because the tool still sees that there is a predecessor identified? Do we need to delete predecessor when we make those types of manual changes?
Thanks all!
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Sign in to like this content
Total Likes
Hi Olivia,
To understand the "At Risk" change, I'd suggest you navigate to the Tasks view on the Project, turn on the Gantt chart, and turn on the option to see the Projected Dates. By doing so, you can visualize how the Progress Status changes (On Time, At Risk, Late) as Projected Dates match and extend past their Planned Dates...particularly when you type in a "Must Finish On". Continuing to observe, recalculate the Project timeline, then notice how doing so might affect both the timing (e.g. in some cases "snapping" Tasks into new positions) and by extension, the Progress Statuses.
Regards,
Doug
Great, thanks for your help Doug!
Views
Replies
Sign in to like this content
Total Likes