Mark,
If activities go out of sequence, you should correct the logic before advancing the data date. That way the critical path will be clean and obvious.
I agree.
If you have a delay claim that is not on the critical path, and if you have advanced the data date before correcting logic, dates, durations and lags, you probably will not get your claim approved.
I agree.
You can always go back in time to find out where the critical path was ...
I do not agree, you cannot go back in time and change logic after the fact in the hope it will be accepted, the logic must have been corrected on due time, otherwise it will be considered self-serving.
but you will need to use the Longest Path Approximator to do that.
I agree that it can be of some help, especially when analyzing intermediate contract milestones. The problem is that it is not necessary valid for resource leveled schedules, it can miss the resource dependencies and therefore get lost. As an initial check up try finding longest path for a four activities schedule, no activity linked with logic links to any other, all using a single resource for which only one is available and then find longest path to last activity without any manual intervention.
Makunda,
At home, usually they never understand these technical things unless you can go to a lower technical level which is not always possible, that is why at times (too many) it ends up in court, using forensic methodology for after the facts that exponentially complicate things.
Keep trying to solve issues early, do not wait for too late in the hope it will be better, it will not, no matter on which side you are. At least keep valid and on record your assumptions at the different stages of the job.
Best regards,
Rafael