This button allows you to check the technical quality of a schedule.
It is used before finalizing and saving the baseline schedule.
When you click on the button, the following window is displayed; allowing you to select the fields to check.
After verification, the Check Schedule display will appear with a Verification Code field that will allow you to check for technical schedule errors or potential errors that you need to check.
In principle, to have technical schedule conformity, it is necessary;
- Having predecessors everywhere except the first activity, milestones may not have predecessors since there is a constrain for the start date. No predecessor link should be applied to summary tasks.
- Having successors everywhere except for the last activity. To have a good calculation of the network (mathematical model) all the tasks must be linked. We also check that links type are FS (Finish to Start) relation which is ideal to have a mathematical sound schedule. No successors link should be applied to summary tasks.
- The activities must be calculated automatically (always to have technical compliance and a good calculation of the network) so we check the task mode of each task is at auto-schedule.
- Have constraints only on milestones (events) and that they are justified.
- Have a single resource for each task ( to have a good level of detail and facilitates monitoring/updating and future analysis of the schedule). Also, have at least one resource assign to each task.
- No estimated duration, it is necessary before saving the baseline schedule that all durations are confirmed.
- Checking that only mandatory calendars are assigned to tasks (for example; a weather calendar assigned to outdoor tasks which may be weather dependent)
- Lags on predecessor and successor links should not be longer than the duration of the task to have proper monitoring and to be a logical link.
- All tasks should have a fixed duration, except if you are using work type resources.
- Verify if the leveling delay field has been applied and check its validity. Usually, on a baseline schedule, every leveling delay should be justified (you may write the justification in the Note field), or if you are using work type resources and whish to let Project level your resources and resolve conflicts or over allocations of those resources.
