Nick, here are the obvious result of violated late (i.e. SNLT/FNLT) constraints: 1. In the indicators column, the constraint itself will be indicated by a calendar icon with a red dot. This exists whether or not the constraint is violated. 2. The constrained task and at least some of its predecessors will have Total Slack < 0, and they will be shown as “Critical.” 3. If the schedule option, “Tasks will always honor their constraint dates” is checked (i.e. the default option), then the scheduling conflict will be allowed, and no other alerts will be shown. If the box is un-checked, then the task will obey its predecessor logic and violate the constraint. The indicators column will then show a yellow-triangle-exclamation alert together with the calendar icon mentioned earlier.