Step 1. Creating Resource Loading Table: As already mentioned above, the histogram can be used to show the hours of resource requirements throughout the project life cycle.
Step 2. Determining Activity Late Finish Dates: The second step is the determination of activity late finish dates by using the slack times and modifying the resource loading table.
Step 3. Identifying Resource Overallocation: After modifying the resource loading table with late finish dates, we are ready to identify the resource overallocations. At that point, we know how many resources we need in each period during the project life cycle. So, the question is whether we can supply that much resource for this project. If the answer is ‘no’, then we have a resource overallocation problem which must be resolved to complete the project on time and in the budget limits.
Step 4. Leveling the Resource Loading Table: This step is the main step of the resource leveling procedure. At that step, in order to eliminate the overallocation determined in the previous step, the resource loading table is reorganized iteratively.