P6 Web Access supports the following types of activity constraints:
- Start On imposes the specific start date you choose. The Start On constraint can delay an activity's early start or move forward an activity's late start to satisfy the constraint date.
- Start On or Before defines the latest date an activity can start. This constraint only affects late dates and may decrease total float. When calculating a schedule, P6 Web Access imposes the start on or before constraint in the backward pass only if the calculated late start date will be later than the imposed date.
- Start On or After defines the earliest date an activity can begin. This constraint affects only early dates. When calculating a schedule, P6 Web Access imposes the start on or after constraint in the forward pass only if the calculated early start date will be earlier than the imposed date.
- Finish On imposes the specific finish date you choose. The Finish On constraint can delay an activity's early finish or move forward an activity's late finish to satisfy the constraint date.
- Finish On or Before defines the latest time an activity can finish. The finish on or before constraint affects only late dates.
- Finish On or After defines the earliest date an activity can finish. The finish on or after constraint reduces float to coordinate parallel activities, ensuring that the finish of an activity is not scheduled before the specified date. It is usually applied to activities with few predecessors that must finish before the next phase of a project.
- As Late As Possible imposes a restriction on an activity with positive float to allow it to start as late as possible without delaying its successors. When calculating a schedule, P6 Web Access sets the activity's early dates as late as possible without affecting successor activities.
- Mandatory Start imposes the early and late start dates you choose. P6 Web Access uses the mandatory early start date regardless of its effect on network logic. A mandatory early start date could affect the late dates for all activities that lead to the constrained activity and all early dates for the activities that lead from the constrained activity.
- Mandatory Finish imposes the early and late finish dates you choose. P6 Web Access uses the mandatory finish date regardless of its effect on network logic. This constraint affects the late dates for all activities that lead to the constrained activity and all early dates for the activities that lead from the constrained activity.
Note: When mandatory constraints are placed on calendar nonworktime, the early date is moved forward to the next valid worktime and the late date is moved back (earlier) to the first valid worktime. This can cause negative float in the schedule.