Study guide
19.4 Resource Smoothing and Resource Levelling
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
19.4 Resource Smoothing and Resource Levelling
Key Takeaways Explain This Topic AI
Resource smoothing keeps the completion date fixed and adjusts work within available float to even out resource demand.
Resource levelling treats the resource limit as the hard constraint and accepts that the completion date may move.
Smoothing is the right technique when the end date is contractually fixed and non-critical activities have float to absorb the peak.
Levelling is the right technique when a genuinely finite resource cannot be increased and no float remains to exploit.
Both are planning techniques, not excuses: whichever is used, the resulting change to dates or float must be reported and, if it breaches a baseline, controlled.
Last updated: August 2026
Outcome 21d is a single line — know the differences between resource smoothing and resource levelling — and it is one of the most reliably examined distinctions on the whole paper. Get the two directions the right way round and the marks follow; reverse them and every scenario answer built on them fails.
Resource smoothing vs resource levelling (high-yield distinction)
Both techniques address uneven or excessive resource demand. The critical differences are what may change and whether the project end date is protected .
Comparison table
Dimension Resource smoothing Resource levelling
Primary aim Flatten peaks and troughs to a more even, efficient use of resources Remove overallocation / make the schedule resource-feasible
End date Preserved — completion date stays the same May move later (or other hard constraints may be broken and then renegotiated)
Float / slack Uses available float only; activities delay only within float May consume all float and then extend durations or delay activities beyond previous float
What changes Timing of non-critical activities within float; sometimes minor redistribution of work Activity starts/finishes, sequencing, durations, or resource assignments as needed for feasibility
What does not change (normally) Project end date; critical path length in total (critical activities not delayed for smoothing alone) Nothing is sacred if the plan was infeasible — dates can slip
Typical trigger Peaks exist but float is available and the deadline is fixed Demand still exceeds supply after float is used, or no useful float exists on the overloaded path
If overload remains Smoothing cannot fix it without other actions (extra resource, overtime, scope change) Levelling continues until load fits availability, often by delaying work
Exam memory hook Smooth within float; protect the end date Level to fit resources; end date may slip
UK spelling on the PMQ: expect levelling (double l). The concept matches "resource leveling" in some international texts.
Resource smoothing — deeper view
Resource smoothing reschedules work to reduce peaks while staying inside existing float so the imposed or baselined end date does not move . Non-critical activities may start later (or be paced differently) where total float allows. Critical activities are not delayed solely to smooth, because that would push the end date.
Use smoothing when:
- The deadline is fixed (contractual end date, regulatory date, market window)
- Histogram peaks are caused largely by discretionary parallel work on paths that have float
- Availability is roughly adequate in total but poorly timed
- You want more stable utilisation (cost, morale, plant hire efficiency) without renegotiating time
Limits of smoothing: if overallocation sits on the critical path , or total demand in a period still exceeds supply after all float is used, smoothing cannot solve the problem alone. You then need more resource, overtime, method change, scope cut, or levelling that accepts date movement.
Resource levelling — deeper view
Resource levelling prioritises resource feasibility . Activities are delayed, stretched, or re-sequenced so that demand does not exceed availability. If that requires delaying critical work, the project end date moves (unless compensated by other approved changes such as adding resources — which is a capacity decision, not pure levelling).
Use levelling when:
- Named resources or plant are hard-constrained and cannot be exceeded
- Smoothing within float is insufficient
- A realistic plan is more valuable than an optimistic date nobody can staff
- Sponsors will accept a later date (or must be shown the true trade-off)
After levelling: re-check critical path, cost (delay costs, extended hire), risk, and benefits timing. Levelling is a re-planning act that may need governance approval if baselines change.
Side-by-side worked numbers (conceptual)
A specialist is available 5 days/week . Week 10 demand is 8 days across Activity A (critical, 5 days) and Activity B (3 days float available on B’s path).
Smoothing: move or pace Activity B within its float so week 10 demand becomes 5 days; end date unchanged if B still finishes inside float.
If Activity B had no float and both must use the specialist, smoothing fails . Levelling delays B (or part of A if re-planned), and the end date may slip unless another specialist is added.
Other responses often used with smoothing/levelling
Smoothing and levelling are schedule-logic responses. Exam scenarios may also require capacity responses. Distinguish them clearly:
- Response End date impact Notes
- Smoothing None (uses float) Timing only within slack
- Levelling Often later Feasibility by delaying work
- Add resources / overtime Often protects or recovers dates Cost and quality/fatigue risk
- Fast-track / re-sequence May shorten or rebalance Different technique; more interface risk
- Reduce scope May protect dates Benefits/change control implications
- Change method Variable E.g., prefabrication reducing site labour peak
Do not call "hire two more testers" smoothing . Hiring is a resource acquisition decision. Smoothing and levelling rearrange when existing constrained resources do work (levelling may also stretch durations).
- Scenarios for the distinction
- Scenario B — smoothing succeeds
A software project must hit a fixed regulatory submission date. The test environment is overloaded in week 14 because three non-critical documentation and training-prep tasks were planned in parallel with critical test execution. The project manager smooths : shifts documentation tasks into weeks 12–13 and 15 where float exists, keeps critical testing in week 14, and holds the submission date . Histogram peaks fall; end date unchanged.
Scenario C — levelling required
The same project discovers the only performance tester is required full time on the critical test path and on a critical defect-fix path in the same week, with zero float on both. Smoothing cannot move either without breaking the end date logic. Options: level (accept slip on one path and thus likely the end date), add a second performance tester (cost), or descope performance scenarios (quality/risk). Presenting only "we will smooth" would be incorrect because no float remains.
Scenario D — iterative capacity levelling
An agile programme’s roadmap promised three features in Release 2, but the single data-migration specialist is already fully allocated to Release 1 hypercare. The release train levels feature capacity: one feature moves to Release 3 (date of that feature slips), rather than pretending all three can be staffed. Iteration smoothing inside a sprint (reordering backlog items within sprint capacity) is the short-horizon cousin of the same idea — still limited by true capacity.
Scenario E — plant resource
A site has one mobile crane. Two lifts were scheduled the same morning. Smoothing moves the non-critical lift to the afternoon if the day still finishes inside float for that activity’s path. If both lifts sit on the critical path for a possession window that ends at noon, levelling (or adding a second crane) is required; wishful double-booking is not a plan.
Choosing the technique in exam answers
Use this decision pattern:
State the overallocation (which resource, which period).
Check float on the overloaded activities and whether the end date is fixed .
If peaks can be moved within float and the end date must hold → resource smoothing .
If demand still exceeds supply or critical work is overloaded → resource levelling and/or extra capacity / scope / method change; declare end-date impact .
Link to governance : baseline changes, sponsor options, cost and benefits effects.
Mention life cycle : linear full-network histograms vs iterative capacity and rolling-wave allocation.
- Memory contrast (one line each)
- Smoothing: "Use the slack; keep the deadline."
- Levelling: "Fit the people/plant; the deadline may move."
- Integrated control reminders
Resource allocation sits inside the integrated project management plan:
Schedule feasibility depends on resource-loaded reality, not logic alone.
Cost baselines change if overtime, extra hire, or delay costs appear.
Risk rises when utilisation is permanently near 100% (no contingency capacity).
RACI Responsible parties must match the allocation — a Responsible person at 150% is a fiction.
Reviews and assurance should test whether reported status assumes unavailable resources.
Mastering the smoothing vs levelling distinction, and applying it in linear and iterative contexts, is high-yield for APM PMQ resource management questions and long-response scenarios.