I am in the process of reviewing a schedule wherein the activities have large float. The first problem I am seeing is that the float is increasing in the successor activities. For example, the first few activities have 187 days of float, the next series 222 days, the next series 262. All of these activities are FS relationships, all using a 5 day calendar, all have zero free float. The last activity in the chain (approximately 50 activities to the chain) ties to an overall milestone for Final Completion. There is only one constraint on the schedule which is the Final Completion with a finish on or before. There are minimal SS and FF relationships. There are no lags added in the series.I am baffled as to why the activities in the front end are not showing 262 days of float similar to the tail end activities. As you follow the trail backwards, the float decreases on the front end. Schedule uses retained logic and calculated using Finish Float. I tried Start Float and float values remain the same. What am I not seeing? Has anyone seen this before? Any suggestions?