Schedule Levels are used to identify the level of detail shown on the schedule scale. The higher a schedule level, the higher a level of view it implies (the less details it contains, while being focused on the major options). Details to be included at every schedule level are not regulated by some rule, but usually this works in such a way:
- Level 1: it summarizes the overall scope of a project for the customer and management in terms of the major milestones, project phases, and project start time and due date;
- Level 2: a schedule begins to breakdown into more details. It gets decomposed into tasks and deliverables that form up each one of phases previously summarized on the level 1;
- Level 3: this one is supposed to give a full use to the critical path method (CPM). It includes a sufficient level of details making it possible to derive an accurate project duration estimate;
- Level 4: a work package level where activities and tasks of every individual or working unit are scheduled in the most detailed and specific terms. The lower possible level where decomposing a schedule further doesn’t make any sense;
Depending on the schedule use, type of software, time pattern adopted, specifics of a workflow, and other essential aspects, these parameters may have their own limitations or specifications. The use of these parameters is simple – by giving a value to each of them, a person can address to a specific point on the schedule (to a specific date & time), and once it is reached, can learn if something is recorded already (scheduled) on that date.