Constraint Dates

Constraint dates, also known as target dates, act as user-defined constraints on the activity. When the system calculates the dates (early, late and scheduled dates), the calculation uses the constraint dates.

Try not to use constraint dates unless there is a specific requirement such as a customer delivery date because constraint dates affect the critical path calculation by creating immovable “blocks.”

Constraint dates force date constraints onto an activity regardless of subsequent changes that would otherwise affect the activity’s place in the overall project plan. Use constraint dates sparingly, particularly in the early stages of the planning process.

Extensive use of constraint dates often has the effect of artificially distorting the patterns of float within a project, making analysis more difficult. Instead, allow the scheduling software as much flexibility as possible to produce the most efficient set of project dates during your initial calculations.

If possible, use relationships to move the activities in time to where you wish them to occur. Only if you have unavoidable constraints, such as an event date that cannot be moved, should you consider setting a constraint date for an activity.

When you add a new activity to a work package, the start date is set to the start date of the work package. To delay the start of an activity within a work package, consider using relationships instead of constraint dates. Access the Relationship tab and identify the predecessor activity that will delay the start of the activity. After you add the predecessor activity, you will see that the activity start date is calculated the day after the finish of the predecessor activity.

What do you want to do?

Learn more about the Constraint Dates fields on the Change Details view Advanced tab

Add a predecessor or successor activity relationship to define when an activity occurs

Add a constraint date to an activity

Add a relationship to an activity

Learn more about...