Editing Float

it all depends on the level of detail in your schedule. can you tie this to punchlist, commissioning or testing or something other than the proect finish milestone.

Another thing to do it to add an additionla predecessor whch is later in time. 

Hi Mohamed

This happens when you use SS logic with Lead Lags and no end successor.

As Zoltan says make sure every task has an end successor even if it down to Project Completion.

Best regards

Mike Testro

Agreeing with Zoltan.

To reduce float, assign a later predecessor and/or an earlier successor.  No need to be more specific, since whoever wrote the specification doesn't really CARE about your sequential plan to accomplish the work.  I suppose he'll get what he's after.

Mike's advice to avoid dangling finishes is definitely good, though I would not expect that to contribute to the problem of excessive float in a baseline project schedule (assuming no progress).

Finally, the small negative float (-1d) could have several causes, but I would first look for a small clock-time mismatch at the project completion milestone (e.g. finishing at end of day when the project must finish by constraint is set to beginning of day.) Alternately, there could be a late constraint somewhere that you don't know about.