Soft Constraint (Preferred Constraint)

Soft constraints — sometimes called preferred constraints or flexible constraints — are dates that the scheduler would like to achieve but which are not overriding the network logic. A typical example is a 'Start No Earlier Than' constraint applied to the project start date, which prevents the schedule from calculating activity starts before mobilisation can begin. Unlike hard constraints, soft constraints allow negative float to show if the network logic cannot satisfy them, which means the schedule remains analytically honest. The critical path can still flow correctly and float calculations remain valid.

Soft constraints are generally preferable to hard constraints wherever the scheduling tool supports them. A 'Finish No Later Than' soft constraint on a contractual milestone will show negative float if the network logic predicts a late finish — giving the planner a visible signal that the programme is at risk without distorting the rest of the schedule. A hard 'Must Finish On' constraint in the same position will suppress the negative float, making the schedule appear to meet the milestone even when the underlying logic does not support it.

In practice, the distinction between hard and soft constraints is handled differently in different scheduling tools, and not all tools support the full range of constraint types with the same behaviour. Primavera P6, for example, distinguishes between constraint types that affect early dates, late dates, or both. Microsoft Project handles constraints differently depending on whether the project is scheduled from a start or finish date. Planners who switch between tools need to check how constraints behave in the new environment — what counts as 'soft' in one tool may function as 'hard' in another. When inheriting a schedule, always check the constraint types alongside the constraint dates.