Constraints in Primavera P6 are imposed dates that limit when an activity can start or finish, overriding or capping the dates the scheduling engine would otherwise calculate from logic and calendars. They are sometimes necessary, for contract milestones or genuine external dates, but used in place of logic they distort float, hide the true critical path and fail the DCMA hard constraints check.
This guide explains each P6 constraint type, the difference between hard and soft constraints, how mandatory constraints behave, and how to audit constraints in a live schedule.
What are the constraint types in Primavera P6?
Each activity can carry a primary constraint and, for some combinations, a secondary constraint. The table shows what each one does.
| P6 constraint | What it does | Affects | DCMA class |
|---|---|---|---|
| Start On or After | The activity cannot start before the date. Logic can still push it later. | Early start | Soft |
| Finish On or After | The activity cannot finish before the date. | Early finish | Soft |
| Start On or Before | Caps the late start. If logic cannot meet it, negative float appears. | Late start | Hard |
| Finish On or Before | Caps the late finish (a deadline). It does not move the early dates. | Late finish | Hard |
| Start On | Sets both early and late start to the date. Predecessors can still push it later, which produces negative float. | Early and late start | Hard |
| Finish On | Sets both early and late finish to the date, with the same behaviour as Start On. | Early and late finish | Hard |
| Mandatory Start | Fixes the start date regardless of logic. Can schedule the activity in breach of its predecessors. | Early and late start | Hard |
| Mandatory Finish | Fixes the finish date regardless of logic. | Early and late finish | Hard |
| As Late As Possible | Schedules the activity as late as it can go without delaying its successors, using up its free float. | Early dates | Soft |
The DCMA guidance was written in Microsoft Project terms (Must Start On, Must Finish On, Start No Later Than, Finish No Later Than as hard). The P6 mapping above is the one reviewers commonly apply. Agree the mapping with the reviewing party before a formal assessment, because some reviewers treat Start On and Finish On differently.
What is the difference between hard and soft constraints in P6?
A soft constraint sets an earliest date but still lets logic move the activity later. Start On or After and Finish On or After are soft: if a predecessor slips, the activity moves with it and float behaves normally.
A hard constraint fixes a date or caps the late dates, so the schedule cannot respond freely to delay. It either produces negative float when logic cannot meet the date (Start On or Before, Finish On or Before, Start On, Finish On) or overrides the logic altogether (Mandatory Start, Mandatory Finish). Hard constraints are what the DCMA check counts.
What does a Mandatory Start constraint do?
A Mandatory Start constraint sets the activity's early and late start to the constraint date, whatever its predecessors say. If a predecessor finishes later than that date, P6 still starts the activity on the imposed date, so the schedule shows work starting before the work it depends on is complete. The backward pass also takes the imposed date, so predecessors that cannot meet it show negative float. Mandatory Finish behaves the same way on the finish date.
This is why mandatory constraints are the most damaging type. They can make a schedule look as if it meets its dates when the logic says it cannot, and the logic breach appears only in the schedule log or a logic check.
How do constraints distort float and the critical path?
A constraint changes the early dates, the late dates or both, so it changes total float:
- Late-date constraints (Finish On or Before, Start On or Before) shorten the backward pass. If logic cannot meet the date, the constrained activity and its predecessors show negative float. See total float and negative float explained.
- Start On or After can delay an activity's early dates and use up float downstream. On its own it does not create negative float.
- Start On, Finish On and Mandatory constraints pin the activity's late dates, so it tends to show zero or negative float even if the logic has room. A path can look critical because of the constraint rather than the work.
- Mandatory constraints also break the chain of logic: delays upstream do not flow through to successors, so the real driving path can be hidden behind the constrained activity.
In a logic-driven schedule, the critical path is the longest path to project completion, which P6 can display directly using the longest path option. Total float of zero or less is a common proxy, but constraints, multiple calendars and negative float can make the two differ. When constraints are present, check the longest path rather than relying on float alone.
Why does the DCMA 14-point assessment penalise hard constraints?
Check 5 of the DCMA 14-point assessment counts incomplete activities with hard constraints. The threshold is fewer than 5% of incomplete activities. Soft constraints are not counted. Hard constraints are treated as high risk because they stop the schedule from responding to delay, so the forecast dates no longer come from the logic.
The GAO Schedule Assessment Guide gives similar advice: hard constraints should be used only for genuinely fixed dates and each one should be justified. Many owners' specifications go further and restrict constraints to named contract milestones.
Constraints also weaken forensic delay analysis. Where a baseline or update carries hard constraints, it becomes hard to show whether a forecast date moved because of the work or because a constraint held it in place. Before a delay analysis relies on a schedule, its constraints need to be identified and their effect tested.
When is a constraint justified, and when should you use logic instead?
Justified uses of constraints
- Contract milestones: a Finish On or Before on a completion or sectional completion milestone where the date is fixed in the contract. It shows negative float when the programme is behind, which is the warning you want.
- External dependencies: a Start On or After on an activity that cannot begin before a known external date, such as a permit, an access date or a utility connection date outside the contractor's control.
- Seasonal windows: a Start On or After for offshore, marine or winter-restricted work where the window is fixed.
When to use logic instead
- Internal dependencies: if a task waits for other work in the project, link it with a relationship (with a justified lag if needed) rather than constraining it to a date.
- Resource limits: do not use date constraints to imitate resource availability. Use resource assignments, resource calendars and levelling.
- Contingency: do not hold schedule contingency with a constraint. Show it as a clearly labelled contingency activity on the path to the completion milestone.
A good rule: if the date is not imposed from outside the project and is not negotiable, model it with logic. This keeps the schedule responsive to change.
How do you audit constraints in a P6 schedule?
- Add the Primary Constraint, Primary Constraint Date, Secondary Constraint and Secondary Constraint Date columns to the Activities view.
- Filter for incomplete activities where Primary Constraint is not empty, and group by constraint type.
- Count the hard constraints against all incomplete activities. Fewer than 5% passes the DCMA check.
- For each constraint, compare the constraint date with the calculated early dates and total float. A large gap or negative float shows where logic and constraint disagree.
- Reschedule (F9) and open the schedule log, which lists constrained activities and activities scheduled out of logic sequence.
- Check each remaining constraint has a recorded reason, such as a contract clause or an external date, in a notebook topic or a user-defined field.
A schedule-checking tool or a standard P6 report can list constrained activities in bulk. As part of a project planning review, an independent reviewer such as Project Assure tests each constraint against its justification as well as counting it.
What are the best practices for managing P6 constraints?
- Keep hard constraints to fewer than 5% of incomplete activities (the DCMA threshold), and fewer still in practice.
- Record the justification for every constraint in the activity's notes or a user-defined field.
- Review constraints at every update and remove those that are no longer needed.
- Use Finish On or Before rather than Mandatory Finish on contract milestones, so negative float shows the slippage instead of hiding it.
- Avoid Mandatory Start and Mandatory Finish. Do not use them on working activities.
- Do not use constraints to model internal sequence, resources or contingency.
Constraints used sparingly, justified and reviewed, leave the logic in charge of the dates. That gives a schedule that passes DCMA review and holds up in delay analysis.
