19.3 Categorising and Allocating Resources

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.3 Categorising and Allocating Resources

Key Takeaways Explain This Topic AI

Resources are categorised as replenishable, such as people and equipment that become available again, or consumable, such as materials and funding that are used up.

Linear schedules allocate resources to a defined activity network, so the question is whether the right resource is free when the activity needs it.

Iterative schedules allocate a stable team capacity to a changing backlog, so the question is what the fixed capacity should work on next.

Resource histograms plot demand over time against available supply, making overallocation visible before it becomes a delivery failure.

Overallocation is a planning signal, not a personal performance issue — the plan is asking for more than the resource can supply.

Last updated: August 2026

Outcome 21c asks you to understand how resources are categorised and allocated to both linear and iterative life cycle schedules . The comparison is the examinable part: linear schedules allocate resources to a defined activity network, while iterative schedules allocate a stable team capacity to a changing backlog. Those are genuinely different planning problems.

From identification to allocation

Once resource need , availability , OBS , and RACI are understood, the project must allocate resources to scheduled activities and keep that allocation feasible over time. This section covers how resources are categorised and allocated in linear and iterative life cycle schedules, and the examinable distinction between resource smoothing and resource levelling (LO21c–d).

Weak answers use "smoothing" and "levelling" as synonyms. Strong answers state what is allowed to change , the effect on the end date and float , and when each technique is appropriate .

Categorising resources for allocation

Before loading a schedule, classify resources so the right constraints are applied.

• Category lens Examples Why categorise
• Type People, equipment, materials, facilities Different booking and lead-time behaviours
• Skill / grade Senior designer vs junior draughtsperson Prevent false fungibility

Internal vs external Employees vs contractors vs supplier plant Different acquisition routes and notice periods

Dedicated vs shared Full-time project team vs BAU experts on call Shared resources create multi-project conflict

Critical / scarce vs plentiful Named specialist, unique test cell vs general admin support Focus control on bottleneck resources

Consumable vs reusable Materials used up vs equipment reused Materials need replenishment; plant needs utilisation management

Cost behaviour Fixed period cost vs variable day rate Allocation choices affect budget profile

Bottleneck resources deserve explicit calendars and early conflict resolution. Allocating plentiful admin support in fine detail while ignoring a single certified tester is reverse prioritisation.

Allocating resources to the schedule

Resource allocation assigns named or pooled resources to activities with quantities and time periods (for example 1.0 FTE test analyst in weeks 12–14; crawler crane 40 hours in week 9; training room booked 3 days).

Allocation steps (practical)

Confirm activity list, durations, and logic (from schedule management).

Attach resource demands to activities (skills, plant, materials, rooms).

Apply calendars (working time, holidays, maintenance, BAU blackouts).

Check aggregate demand vs supply by period.

Resolve conflicts (smooth, level, add capacity, re-sequence, change scope).

Baseline only when the resource-loaded plan is credible .

Monitor actual use and re-allocate as forecasts change.

Allocation is not a one-off spreadsheet exercise. It is continuous control: actual progress, sick leave, supplier delays, and scope change all move the resource picture.

Allocation in linear life cycle schedules

In a linear (predictive/waterfall-style) life cycle, much of the scope and network is defined earlier. Resource allocation typically:

• Loads a fuller baseline schedule with resource demands across phases
• Seeks a stable profile for major packages before major delivery commitment
• Highlights peaks near design freezes, test phases, and cutover
• Integrates procurement lead times for materials and hired equipment on the same timeline
• Uses stage/gate reviews to confirm resource commitments for the next phase

• Linear allocation focus Example
• Early long-lead resources Book specialist plant or scarce consultants months ahead
• Phase-based peaks Design team ramps then hands to construction/build team
• Critical path resource risk Ensure critical activities are not staffed by overallocated people
• BAU windows Align training and cutover with operational calendars

Risk in linear plans: optimistic parallel activities that double-book the same people create a beautiful Gantt that cannot be staffed. Resource checking before baseline approval is part of integrated planning.

Allocation in iterative life cycle schedules

In iterative (and many agile or hybrid) approaches, detailed work is planned in timeboxes (sprints, increments) while a higher-level roadmap remains. Resource allocation typically:

Fixes a stable team capacity (velocity-style throughput) for the near term

Allocates people to backlog items selected for the iteration, not a 18-month task-level resource histogram for every story

• Re-plans allocation each iteration based on learning and remaining backlog
• Still manages shared specialists , environments, and BAU capacity as constraints across increments
• Maintains a release/roadmap resource view for scarce roles and external dependencies

• Iterative allocation focus Example
• Capacity-based planning Team of 6 with known capacity chooses sprint scope that fits
• Rolling wave detail Next 2–4 weeks resource-loaded in detail; later increments lighter
• Cross-team dependencies Shared security reviewer booked across squads
• Environment facilities Test environments reserved per increment

Important: iterative delivery does not remove resource management. It changes granularity and timing of detailed allocation. Roadmap-level resource risks (one performance tester for five squads) still need smoothing, levelling, or capacity decisions.

Hybrid note

Many projects combine linear stage structure with iterative build inside stages. Allocate stage-gate resources (assurance, procurement, training) on the linear backbone, and iteration capacity on the delivery teams.

Scenario A — linear vs iterative allocation failure modes

Linear failure: A construction fit-out baselines three parallel trade packages without checking that the same commissioning engineer is assigned 120% in week 22. Fix: re-sequence, extend duration, or add capacity before baseline.

Iterative failure: Five squads plan sprint demos the same week and all require the single UX researcher for validation. Fix: stagger sprint goals, increase UX capacity, or thin validation scope — capacity is the constraint, not story-point arithmetic alone.

Resource histograms and overallocation

A resource histogram (or load chart) shows demand per period for a resource or pool. Overallocation occurs when demand exceeds availability in a period.

• Signal Meaning
• Peak above availability line Infeasible load without action
• Sustained high utilisation Fatigue, quality, and leave risk
• Troughs next to peaks Opportunity to shift work using float
• Multiple projects on one person Portfolio-level conflict beyond one PM’s chart

When overallocation appears, two classic schedule techniques are smoothing and levelling . They are related but not the same .