Last Modified On: November 5, 2026
Constraints define the scheduling limitations that a project task must operate within. They allow you to control when a task can start or finish, regardless of changes to the project schedule or its predecessor tasks.
By default, a project task’s Start Date or Finish Date is determined by the project’s scheduling direction:
Tasks with predecessors are automatically rescheduled as soon as possible (ASAP) in forward-scheduled projects or as late as possible (ALAP) in backward-scheduled projects, based on the completion or scheduling of their predecessors.
When the project Start Date or End Date is adjusted, or a predecessor task is rescheduled, the scheduling engine automatically recalculates the affected task dates.
However, there may be situations where a task needs to start or finish by a specific date. For example, imagine a task scheduled for a technician to perform an onsite installation on a particular date. To ensure the installation can proceed as planned, the predecessor task (in this case, hardware delivery) must be completed by a specific date.
You can apply a constraint, such as Finish No Later Than or Must Finish On, to the hardware delivery task to ensure it meets the required deadline.
Once a constraint is applied, the scheduling engine respects the specified scheduling limitation when recalculating task dates. This prevents the task from being freely rescheduled based on changes to the project Start Date or End Date or the scheduling of its predecessors.
One important distinction: Constraints do not necessarily prevent a task’s dates from changing altogether. Rather, they limit how the scheduling engine can adjust those dates based on the selected constraint.
By default, the Constraint and Constraint Date columns are hidden in the project schedule. To add them, simply right-click on any column heading, go to Columns and select both Constraint Type and Constraint Date.
There are six (6) constraint types available for you to choose from. They are as follows:
A hard constraint means that the task has to start or finish on a particular date (constraint date) and cannot be rescheduled.
A flexible constraint means that a task can be rescheduled as long as it does not violate the constraint date.
When you add a constraint to a task, it will not be automatically rescheduled if the project's start or end date changes, or if its predecessor tasks are rescheduled.
When you remove a constraint, the task is rescheduled as follows:
As previously mentioned, when you add a constraint to a task, it will not be automatically rescheduled if the project's start or end date changes, or if its predecessor tasks are rescheduled. Instead, if the project start or end date changes, or if its predecessors are rescheduled wherein it's causing the task with a constraint to violate its constraint, you are prompted with a constraint violation message.