Resource Smoothing and Leveling Methods

Introduction

Project schedules describe when work is planned; resource plans determine whether that work can actually be performed. A schedule may be logically feasible yet operationally impossible when several activities require the same scarce people, equipment, facilities, or specialist suppliers at the same time. Resource smoothing and resource leveling are the principal methods used to reconcile precedence logic, delivery dates, and resource availability.

The distinction is fundamental. Resource smoothing adjusts activities within their available float while preserving the approved project completion date and critical path, where possible. Resource leveling resolves resource over-allocation even when this requires consuming float, changing the critical path, extending the project, or altering the delivery strategy. Smoothing is therefore primarily a schedule optimization technique; leveling is a constrained allocation and schedule-reconciliation technique.

These methods are not merely clerical exercises. They involve managerial judgments about priorities, safety, labor agreements, procurement, cost, quality, stakeholder commitments, and risk. At postgraduate level, the project manager must understand both the mechanics of moving activities and the governance implications of changing the baseline.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish resource smoothing from resource leveling.
2. Calculate total float and use it to identify smoothing opportunities.
3. Apply priority rules to resolve resource conflicts.
4. Evaluate activity splitting, resequencing, substitution, overtime, shift work, outsourcing, and schedule extension.
5. Assess the effects of resource decisions on cost, risk, quality, safety, and the critical path.
6. Recommend a defensible resource strategy for a complex project.

1. Resource Feasibility and Over-Allocation

A resource is over-allocated when the demand for a resource exceeds its available capacity during a period. If resource demand is represented by D_t and capacity by C_t, over-allocation occurs when:

Here, t denotes a time period, such as a day or week. Both demand and capacity must use the same unit—for example, electrician-hours per week. If three activities each require two electricians during the same week, demand is six electrician-equivalents. If only four are available, the excess is two electrician-equivalents.

Resource constraints may concern:

• Labor: project managers, engineers, trades, operators, or inspectors.
• Equipment: cranes, test rigs, vehicles, servers, or specialized tools.
• Facilities: laboratories, clean rooms, classrooms, or production lines.
• Materials: scarce components or controlled substances.
• Financial capacity: available cash or authorized expenditure.
• Organizational attention: decision makers, subject-matter experts, or approvers.

Not every apparent conflict is a true conflict. A calendar may show simultaneous work, but activities may use different skills, locations, shifts, or equipment. Conversely, two activities may appear to require one resource but actually compete for the same scarce specialist. Resource analysis must therefore use a realistic resource breakdown structure, calendars, productivity assumptions, and skill classifications.

2. Float, Criticality, and the Basis of Smoothing

For an activity with early start ES, early finish EF, late start LS, and late finish LF, total float is:

Total float is the amount of time an activity can be delayed without delaying the project completion date, subject to the schedule model and stated calendars. In a simple activity-on-node network, an activity with zero total float is critical. Activities with positive float are candidates for smoothing, although their float may be shared with other activities and may not be independently usable.

Free float is the delay possible without delaying the early start of any immediate successor. For an activity with duration d_i and successor set S_i, a common representation is:

The formula applies to a finish-to-start network with consistent calendars. More complex relationships, lags, constraints, and resource calendars require schedule-software calculations rather than blind application of the simple expression.

Smoothing uses this available time. It changes the timing of noncritical activities, normally without changing logical relationships, project duration, or the critical path. Because smoothing cannot create capacity, it is effective only when the resource peak can be reduced by using float.

Example: smoothing within float

Consider three activities using one survey team:

If B and C overlap in week 3 and require the same team, B can be moved from weeks 2–3 to weeks 1–2 only if that does not conflict with A, or C can be moved to week 4 if its two weeks of float and successor relationships permit the move. The chosen movement must be checked against predecessors, successors, calendars, and resource continuity. If the move does not delay project completion, it is smoothing. If no such movement is possible, leveling is required.

3. Resource Leveling

Resource leveling modifies the schedule to remove over-allocation when resource demand cannot be accommodated by the available capacity. It may involve delaying activities beyond their original float, changing sequence, splitting work, adding capacity, or extending the project.

Leveling can alter:

• the critical path;
• total project duration;
• milestone dates;
• cost and cash flow;
• resource productivity;
• risk exposure;
• contractual commitments.

A leveled schedule is not automatically superior. It is feasible with respect to the selected resource constraints, but it may be more expensive or slower. The project manager must compare alternatives using a transparent decision framework.

A useful objective is to minimize a combination of delay, cost, and instability. In conceptual form:

where T is schedule delay, C is incremental cost, R is resource or delivery risk, S is schedule instability or disruption, and the w values are management-assigned weights. This is a decision model rather than a universal formula. The variables must be defined consistently, and the weights should be agreed through governance rather than selected arbitrarily.

4. Priority Rules for Conflicting Activities

When several activities compete for a limited resource, a priority rule determines which activity receives capacity first. No single rule is best for every project. The rule should reflect project strategy and stakeholder commitments.

A robust practice uses a hierarchy rather than a single rule. For example: first protect statutory and safety activities, then contractual milestones, then activities with least float, and finally optimize cost and continuity. The rule should be documented because changing it informally can create hidden favoritism and disputes.

5. Methods of Smoothing and Leveling

5.1 Activity shifting

Activity shifting moves an activity to a different time while preserving its duration and logical relationships. Within float, it is smoothing; beyond float, it is leveling. Shifting is attractive because it is easy to explain and usually has limited technical impact. It can, however, create a new resource peak elsewhere or cause trade crews to be mobilized and demobilized repeatedly.

5.2 Activity splitting

Splitting interrupts an activity and resumes it later. It is useful when work can be paused without substantial setup, quality, safety, or learning losses. For example, a report may be drafted, paused while a specialist is assigned elsewhere, and completed later.

Splitting is unsuitable when:

• continuity is required for curing, calibration, or testing;
• restart requires expensive setup;
• work-in-progress is vulnerable to damage;
• handoffs create quality defects;
• labor agreements restrict interruption;
• the activity contains hidden technical dependencies.

A split should be represented explicitly in the schedule, with non-working intervals and possible restart costs, rather than treated as an unrealistically flexible bar.

5.3 Resequencing and logic revision

Resequencing changes the order of activities while maintaining technical integrity. A finish-to-start relationship may become start-to-start, or two tasks may be performed in parallel after a design review. Resequencing is powerful but risky. It must be based on engineering, regulatory, and quality evidence—not simply on the visual appearance of a resource histogram.

Before changing logic, ask:

1. Is the proposed overlap technically permissible?
2. Does it increase rework or interface risk?
3. Are approvals, inspections, and hold points preserved?
4. Does the change transfer risk to another team or phase?
5. Has the baseline and change authority been identified?

5.4 Resource substitution

Substitution assigns an alternative resource with equivalent or acceptable capability. A senior engineer may be replaced by a qualified engineer for routine work, or a machine may be replaced by another with sufficient capacity.

Substitution requires competency verification. Apparent equivalence may be false because of differences in certification, productivity, software knowledge, language, safety authorization, or familiarity with the asset. A resource substitution decision should record the required competence, evidence of equivalence, supervision, and residual risk.

5.5 Overtime

Overtime increases labor capacity within existing calendar periods. It may be effective for short, urgent peaks, but it is rarely a sustainable solution. Fatigue can reduce productivity and increase incidents, errors, absenteeism, and turnover. Premium pay also changes the cost baseline.

The project manager should evaluate overtime using a net-benefit view: additional productive hours minus productivity loss, supervision requirements, premium wages, fatigue risk, and possible rework. Overtime must comply with labor law, collective agreements, health and safety requirements, and organizational policy.

5.6 Shift work and calendar expansion

Adding a second or third shift extends operating hours without necessarily increasing the number of workers in any one shift. It is suitable for facilities, equipment, or work fronts that can operate continuously. However, shift work requires handover controls, lighting, security, maintenance windows, supervision, welfare arrangements, and management of fatigue and circadian effects.

A nominal 24-hour operating calendar does not imply 24 hours of productive capacity. Setup, handover, maintenance, access restrictions, and reduced night productivity must be modeled explicitly.

5.7 Outsourcing and subcontracting

Outsourcing transfers part of the work to an external provider. It can rapidly add capacity or specialist capability, but it introduces procurement lead time, coordination costs, commercial exposure, confidentiality issues, and quality-control challenges.

The make-or-buy decision should consider total cost, not only the supplier quotation. Relevant factors include contract administration, onboarding, information transfer, inspection, interfaces, intellectual property, data protection, and supplier failure risk. Outsourcing should not be used to conceal an unapproved baseline change or evade labor and safety responsibilities.

5.8 Schedule extension

Schedule extension is the most direct leveling response when capacity is genuinely fixed and alternatives are unacceptable. It may protect quality and safety, but it can affect revenue, contractual damages, customer confidence, financing, and benefits realization.

An extension should be presented as a controlled decision: identify the constraint, quantify the delay, explain rejected alternatives, assess contractual entitlement, and obtain approval through change control. Extending the schedule is not failure when it is the safest and economically rational response; it is failure when it is hidden or unmanaged.

6. A Practical Leveling Procedure

A disciplined procedure is more reliable than repeatedly dragging bars in scheduling software.

Step 1: Validate the model. Confirm activity logic, calendars, durations, constraints, resource assignments, skill categories, and availability. Remove duplicate assignments and incorrect calendars.

Step 2: Identify the constraint. Determine whether the conflict concerns a unique skill, total labor, equipment, facility, material, budget, or decision authority.

Step 3: Measure the overload. Compare demand and capacity by period. Record the magnitude, duration, and affected activities.

Step 4: Protect non-negotiables. Identify safety, regulatory, contractual, environmental, and quality constraints before applying cost or duration priorities.

Step 5: Apply smoothing. Move eligible activities within total or free float. Recalculate the schedule and resource profile after every material change.

Step 6: Apply priority rules. If overload remains, rank activities using documented criteria such as criticality, contractual importance, risk, value, and continuity.

Step 7: Evaluate alternatives. Compare splitting, resequencing, substitution, overtime, shifts, outsourcing, and extension. Include indirect effects.

Step 8: Recalculate the integrated plan. Check the critical path, float, milestones, cost, procurement, risk register, quality plan, and staffing assumptions.

Step 9: Obtain authorization. Changes affecting the baseline, contract, budget, safety, or scope require appropriate approval.

Step 10: Monitor actual performance. A leveled plan is a forecast, not a guarantee. Update actuals, remaining duration, resource availability, and productivity; then reforecast.

7. Worked Application

A software implementation has one integration architect available. Three activities require that architect:

The architect can support only one activity at a time. In the original schedule, B and C overlap in weeks 3–4, creating demand of one architect-equivalent plus one architect-equivalent against capacity of one.

First, apply smoothing. C has three weeks of float. If C is moved from weeks 3–4 to weeks 6–7, B can proceed in weeks 3–5 and the project completion date remains unchanged, assuming C’s successor permits completion in week 7. This is smoothing if the final milestone is not delayed.

Suppose, however, a regulatory review requires C to finish by week 5. C cannot be moved to weeks 6–7. The manager then evaluates alternatives:

• split C so that preparatory work occurs in week 3 and validation occurs in week 5;
• assign a qualified integration engineer to C under architect supervision;
• use overtime for a limited portion of B or C;
• outsource a defined validation package;
• extend the review milestone.

The choice should be based on competence, review independence, cost, fatigue, and regulatory acceptability. If substitution is approved and the engineer has demonstrated competence, the schedule may retain its dates. If not, a controlled milestone extension is preferable to an unsafe or noncompliant workaround.

The example illustrates that leveling is not simply a mathematical redistribution. The technically feasible option may not be the legally, ethically, or economically acceptable option.

8. Illustrative Case: Hospital Expansion Project

Background

A hospital expansion project includes structural construction, medical-gas installation, electrical commissioning, and infection-control inspections. The project has one specialist medical-gas commissioning team, shared with another hospital project. The approved completion date is fixed because the hospital has scheduled a staged opening.

Problem

The baseline schedule places medical-gas testing, electrical energization, and room certification in the same two-week period. Resource analysis shows that the commissioning team is required for both medical-gas testing and room certification. The team cannot work extended hours because testing requires controlled rest periods and independent verification.

Analysis

The project team first validates the logic and discovers that some room-certification activities were constrained by a date rather than by a true predecessor. Removing the artificial constraint allows four rooms to be certified earlier. This is a schedule-model correction, not resource leveling.

The remaining conflict involves six rooms. Applying the least-float rule would prioritize the rooms on the opening-critical path. However, safety and regulatory rules require that medical-gas testing be complete before room certification. The team therefore cannot simply overlap the activities.

Approach and solution

The team adopts four measures:

1. Smoothing: move non-opening-critical rooms into available float.
2. Sequencing: test opening-critical rooms first and release them to certification in batches.
3. Substitution: train and authorize a second internal specialist to conduct defined tests, with independent quality review.
4. Governance: update the risk register, inspection plan, resource calendar, and change log; obtain approval from the clinical engineering authority.

Overtime is rejected because fatigue could compromise testing reliability. Outsourcing is rejected because supplier mobilization would exceed the available time and create qualification risk.

Outcome

The opening date is retained, peak demand is reduced, and the schedule contains explicit batch handoffs rather than assumed continuous availability. The project incurs modest training cost but avoids a larger delay and preserves safety controls.

Learning points

The case demonstrates that the best leveling decision may combine several methods. It also shows why schedule logic, competence, quality assurance, and governance must be considered together. A resource histogram alone cannot determine an acceptable project plan.

9. Technology, Software, and AI-Enabled Planning

Modern project-management systems can generate resource histograms, identify over-allocation, calculate float, and test alternative calendars. Optimization tools may use constraint programming, simulation, or heuristic search to find feasible schedules. These tools are valuable when projects contain thousands of activities and multiple resource types.

However, automated leveling depends on the quality of the model. A system may produce a mathematically feasible schedule that violates labor rules, ignores setup time, assigns unqualified staff, or creates unsafe handoffs. AI-assisted scheduling should therefore be treated as decision support. The project manager remains accountable for:

• validating data and assumptions;
• explaining priority rules;
• testing sensitivity to uncertain durations and availability;
• preserving audit trails;
• protecting personal and commercial data;
• ensuring human review of safety and compliance decisions.

A useful contemporary practice is scenario analysis. The team can compare a baseline, a minimum-cost plan, a minimum-duration plan, and a risk-minimizing plan. The comparison should show trade-offs rather than present a single algorithmic answer as objective truth.

10. Challenges, Limitations, and Governance

Resource smoothing and leveling have several limitations. Duration estimates may be uncertain; productivity may decline under congestion; resources may not be perfectly interchangeable; and schedule relationships may represent assumptions rather than physical laws. Float can also be misleading when activities share a common downstream constraint.

Important governance issues include:

• Baseline control: changes to dates, cost, scope, or resources should be traceable.
• Transparency: priority rules should not unfairly favor influential stakeholders.
• Health and safety: overtime and shift work must not create unacceptable fatigue exposure.
• Labor and equality: allocation decisions should comply with employment law and agreements.
• Procurement integrity: outsourcing must use fair, authorized commercial processes.
• Quality independence: resource pressure must not eliminate required inspection or review.
• Data protection: workforce data and supplier information must be handled lawfully.

Resource decisions also have ethical dimensions. A project should not meet a public milestone by transferring unreasonable risk to workers, subcontractors, patients, communities, or future operators.

Best-Practice Checklist

Before approving a smoothed or leveled schedule, confirm that:

1. Resource demand and capacity use consistent units and calendars.
2. Skills, certifications, locations, and shift restrictions are modeled.
3. Float has been calculated from validated logic.
4. The method distinguishes smoothing from leveling.
5. Priority rules are documented and defensible.
6. Splits and handoffs include setup, restart, and quality effects.
7. Overtime and shift work address fatigue and legal requirements.
8. Substituted or outsourced resources are demonstrably competent.
9. Critical path, cost, risk, and contractual effects have been recalculated.
10. Approved changes are recorded and actual performance is monitored.

Chapter Summary

Resource smoothing adjusts activities within available float to reduce resource peaks while preserving the planned completion date whenever possible. Resource leveling addresses remaining over-allocation and may consume float, change the critical path, increase cost, or extend the schedule. Float calculations support smoothing, but their validity depends on sound logic, calendars, relationships, and constraints.

Priority rules—such as least float, earliest late finish, risk, contractual importance, and value—provide a disciplined basis for resolving conflicts. Practical methods include shifting, splitting, resequencing, substitution, overtime, shift work, outsourcing, and schedule extension. Each method creates trade-offs involving productivity, quality, safety, cost, risk, and governance. Effective resource management therefore combines quantitative schedule analysis with professional judgment, transparent decision rules, and formal change control.

Key Terms

Resource smoothing: Adjusting activities within available float to reduce resource fluctuations without normally changing the project completion date.

Resource leveling: Resolving resource over-allocation, potentially by changing dates, sequence, resources, or project duration.

Resource over-allocation: A condition in which resource demand exceeds available capacity.

Total float: Time an activity can be delayed without delaying project completion, subject to the schedule model.

Free float: Time an activity can be delayed without delaying the early start of an immediate successor.

Critical path: The longest logical path through the schedule, normally determining the earliest project completion.

Resource calendar: A representation of when a resource is available, including working time, holidays, shifts, and restrictions.

Priority rule: A documented criterion for deciding which competing activity receives scarce capacity first.

Activity splitting: Interrupting an activity and resuming it later.

Resequencing: Changing the order or logical relationships among activities.

Resource substitution: Replacing an assigned resource with another acceptable resource.

Overtime: Work performed beyond normal working hours, usually with premium cost or fatigue implications.

Shift work: Operating multiple work periods within a day to extend productive availability.

Outsourcing: Assigning defined work to an external organization.

Schedule extension: Increasing the planned project duration to accommodate constraints.

Resource histogram: A time-based display of resource demand.

Resource constraint: A limitation on the amount, timing, skill, or availability of a resource.

Baseline: The formally approved version of the project plan used for performance comparison.

Review Questions

Short Answer Questions

1. What is the principal difference between resource smoothing and resource leveling?
2. Define total float and explain its relevance to smoothing.
3. Why can activity splitting reduce, rather than improve, project performance?
4. Identify two risks associated with overtime.
5. Why must a substitution decision verify competence rather than availability alone?

Long Answer Questions

1. Explain how a project manager should develop and apply priority rules when several activities compete for one specialist resource.
2. Compare activity shifting, resequencing, substitution, overtime, shift work, outsourcing, and schedule extension as leveling methods.
3. Discuss how resource leveling can change the critical path and project risk profile.
4. Explain the governance controls required when a leveled schedule changes an approved milestone.
5. Evaluate the appropriate role of scheduling software and AI in resource-constrained project planning.

Analytical / Application Questions

1. A specialist is required by two activities in the same week. One activity has two weeks of float and the other is critical. Develop a smoothing response and identify the checks required before implementing it.
2. A construction project cannot meet a fixed opening date because a certified testing team is over-allocated. Compare substitution, outsourcing, overtime, and schedule extension, then recommend a strategy using safety, cost, and compliance criteria.
3. A project team proposes splitting a highly technical commissioning activity into three non-consecutive periods. Analyze the potential productivity, quality, safety, and schedule consequences and state the evidence required before approval.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes resource smoothing from resource leveling?

A. Smoothing changes scope, whereas leveling changes quality.

B. Smoothing uses available float, whereas leveling may consume float or extend the project.

C. Smoothing always adds staff, whereas leveling always removes staff.

D. Smoothing applies only to equipment, whereas leveling applies only to labor.

Correct Answer: B. Smoothing uses available float, whereas leveling may consume float or extend the project.

Question 2

For a finish-to-start activity with ES = 4, EF = 9, LS = 7, and LF = 12, what is its total float in time units?

A. 2

B. 3

C. 4

D. 5

Correct Answer: B. 3

Question 3

What is the primary purpose of a resource priority rule?

A. To determine which competing activity receives scarce capacity first

B. To eliminate all project risks

C. To guarantee that every activity starts on its early-start date

D. To replace the need for schedule logic

Correct Answer: A. To determine which competing activity receives scarce capacity first

Question 4

Which situation is most suitable for activity splitting?

A. A curing process that requires uninterrupted continuity

B. A task whose restart requires extensive recalibration

C. A work package that can be paused without material setup or quality loss

D. A safety inspection that must be independent and continuous

Correct Answer: C. A work package that can be paused without material setup or quality loss

Question 5

What is a major risk of using overtime as a long-term leveling solution?

A. It necessarily reduces the authorized budget

B. It can increase fatigue, errors, incidents, and turnover

C. It always eliminates the critical path

D. It prevents any use of subcontractors

Correct Answer: B. It can increase fatigue, errors, incidents, and turnover

Question 6

Which action is resource smoothing rather than resource leveling?

A. Delaying a noncritical activity within its available float without delaying completion

B. Adding a night shift after all float has been consumed

C. Outsourcing critical work after a milestone is missed

D. Extending the project completion date because capacity is fixed

Correct Answer: A. Delaying a noncritical activity within its available float without delaying completion

Question 7

Why is resource substitution not based solely on whether another person is free?

A. Available people cannot be assigned to schedules

B. The replacement must have acceptable competence, authorization, and capability

C. Substitution always requires a new project charter

D. Only equipment can be substituted

Correct Answer: B. The replacement must have acceptable competence, authorization, and capability

Question 8

Which issue should be checked before resequencing activities?

A. Whether the proposed overlap is technically and regulatorily permissible

B. Whether the Gantt chart uses the preferred color scheme

C. Whether every activity has zero float

D. Whether outsourcing has already been approved

Correct Answer: A. Whether the proposed overlap is technically and regulatorily permissible

Question 9

A resource requires 6 units of capacity in a week, but only 4 units are available. What is the over-allocation?

A. 1 unit

B. 2 units

C. 4 units

D. 10 units

Correct Answer: B. 2 units

Question 10

Which statement about AI-enabled resource leveling is most accurate?

A. An algorithm makes governance approval unnecessary

B. AI can replace validation of safety and competence assumptions

C. AI is useful for scenario analysis but remains dependent on model quality and human review

D. AI guarantees the globally optimal schedule in every project

Correct Answer: C. AI is useful for scenario analysis but remains dependent on model quality and human review