Resource levelling
A schedule computed with the critical path method assumes unlimited resources. In reality the site has a fixed number of carpenters, one tower crane or two concrete pumps. If several activities that need the same resource are scheduled at the same time, the resource histogram shows peaks above what is available, and the plan is not achievable. Resource management adjusts the schedule to match resources.
Resource smoothing moves non-critical activities within their float to flatten peaks and valleys, without changing the project finish. It gives steadier labour demand, which reduces hiring and idle time. Resource levelling goes further: when resources are strictly limited, it delays activities, even critical ones, until resources are free, so the project may take longer. The order in which competing activities get resources follows priority rules, such as least total float first, shortest duration first, or most successors first. Software automates this but planners must check the result, because levelling can create a new critical path driven by resources rather than logic.
Resource loading is the first step: assign resources and quantities to each activity. Productivity rates from past jobs make durations realistic. Histograms and cumulative resource curves show the plan. A smooth labour curve, rising to a plateau and tapering off, is a sign of a well-planned project; jagged peaks are a warning.
Level the key scarce resources only, such as cranes and specialist crews; levelling everything at once makes the schedule hard to follow.
Resource demand on a day = Σ resource of activities active that daySmoothing: shift within float; finish unchangedLevelling: delay until resource available; finish may extendSum of squares of daily demand: lower = smoother
Accepting a software-levelled schedule without checking that the new critical path makes practical sense.
Problem. Two activities each need 6 workers: X (days 1–4, float 0) and Y (days 1–3, float 4). Only 8 workers are available. Level the plan.
- Demand on days 1–3 = 12 workers, above the limit of 8.
- X is critical, so keep it on days 1–4.
- Delay Y by 4 days to days 5–7, using its float.
- Demand is now 6 on days 1–7; the project finish is unchanged.
Answer. Shift Y to days 5–7; peak falls from 12 to 6 workers
Quick quiz
1What is resource smoothing?
Moving non-critical activities within float to flatten demand without changing the finish.
2Can levelling extend the project?
Yes, if resources are strictly limited.
3Name one priority rule.
Least total float first (others: shortest duration, most successors).
- IS 15883 (series) (India): Guidelines for construction project management, one part per knowledge area.
Clauses and documents to read
- IS 15883 (Part 2):2013 (time management)
Cited by number and clause only. We do not reproduce clause text, tables or figures (BIS Act 2016, s.10(5) and s.11). Check the current edition and amendments before use.
References and further reading
Standard texts, listed in no order of merit. We do not copy text, figures, tables or solved problems from any book; our explanations and examples are original.
- B. C. Punmia, K. K. Khandelwal, Project Planning and Control with PERT and CPM, Laxmi Publications, latest edition.
- J. W. Hinze, Construction Planning and Scheduling, Pearson, latest edition.
Free and official sources
Found an error? Write to indiacongroupofengineers [at] gmail [dot] com. For corrections and feedback. We never ask for payment or personal details.