There shouldn’t be conflicts between concurrent activities.
Realistic resource loading should be done to support the planned construction operation.
Make sure that subcontractors and suppliers meet the planned construction schedule.
The schedule early dates should be realistic, reasonable and achievable.
Standard company activity codes and ID structure should be used.
All contractual milestones must be met in schedule.
Make sure the correctness of Project Calendars.
Compare resource loading with duration to determine if both are logical, reasonable and mutually supportable.
All activities relationships should be complete & valid.
Schedule should cover the complete project scope.
Schedule should be detailed enough as per the type of schedule. In case it is a working schedule, it should be detailed enough to be make it useful during the execution of project.
The critical path should be reasonable. Make sure the activities are correctly linked to get the correct critical path(s) : e.g. make sure that every activity has FS (Finish-to-Start)/FF (Finish-to-Finish) link with other activity or milestone in P3.
Level 3 activities should be coded for : a) WBS, b) OBS, c) Workcode, d) Project Stage (EPC), e) Discipline, f) Responsibility
Eliminate all dangles
Avoid use of lags ,especially long duration lags
Roll ups from Level 3 to Level 2 must be "many to one " with no splitting of Level 3 activities into individual level 2's
Use Constraints only for milestones. Avoid them as much as possible
