Task Prioritization and Workload Impact Assessment

Methods for prioritizing design and project management tasks based on urgency, criticality, dependencies, and resource constraints, and techniques for assessing how workload changes impact project schedules and team capacity.

ARE · Project Management

Overview

Not every task on a project deserves equal attention. Some tasks sit on the critical path and will delay the entire project if they slip. Others have float and can absorb a few days of delay without consequence. Some require specific expertise that's only available during certain windows. Others are level-of-effort activities that run continuously but don't drive milestones.

The PjM exam tests your ability to distinguish between these categories and make scheduling decisions based on that distinction. You need to evaluate how adding, removing, or shifting tasks affects the total schedule. You need to assess whether a team can absorb additional workload without degrading quality or blowing deadlines.

This matters because architecture firms constantly face competing demands. A new project lands while three existing ones are in active production. A client accelerates a deadline on one project, and the team working on it is also assigned to two others. The project manager who can quickly assess which tasks are critical, which can flex, and what the workload impact will be is the one who keeps projects on track.

At its core, this topic connects two related skills: knowing what to prioritize (based on schedule logic, dependencies, and criticality) and knowing what happens when you shift resources around (workload impact assessment).

Essential

Scheduling isn't just about listing tasks and assigning dates. The real skill is knowing which tasks matter most at any given moment and understanding what happens when workload shifts. This section breaks down the frameworks and methods you need for the exam. ## The Critical Path as a Prioritization Tool The critical path method (CPM) gives you an objective basis for task prioritization. Tasks on the critical path have zero total float, meaning any delay to these tasks delays the entire project by the same amount. Tasks off the critical path have positive float, meaning they can slip by some amount without affecting the project completion date. This creates a natural prioritization hierarchy: 1. Critical path activities (zero float): Highest priority. Any slippage here is a direct schedule delay. 2. Near-critical activities (low float, typically less than 10 working days): High priority.

Professional

Consider a 15-person architecture firm running four projects simultaneously. Project A is in construction documents with a permit submission deadline in 6 weeks. Project B just kicked off schematic design. Project C is in design development with a client presentation in 3 weeks. Project D is in construction administration. The firm's principal asks the project manager to assess whether the firm can take on a fifth project starting next month. This is a pure workload impact assessment problem, and it's the kind of scenario that shows up on the PjM exam. ## Step-by-Step Workload Assessment The project manager starts by mapping current resource allocation.

TLDR

Critical path activities (zero float) get highest priority; any delay here delays the whole project
Near-critical activities (low float) deserve almost as much attention; they can become critical with minor slippage
Four schedule logic types: Finish-to-Start (most common), Start-to-Start, Finish-to-Finish, Start-to-Finish (rare)
Hard constraints (fixed dates like board meetings) override scheduling logic and create non-negotiable priorities
Resource loading converts an abstract schedule into a staffed plan; utilization rate tracks billable vs. non-billable time
Workload impact assessment follows five steps: identify affected activities, calculate float consumption, check resource conflicts, assess quality implications, consider cross-project ripple effects
Level-of-effort (LOE) activities consume resources but don't drive the schedule; account for them in capacity planning
Pareto Principle: roughly 80% of schedule risk concentrates in about 20% of work packages
Rolling wave planning: detail the next 4-6 weeks at the task level, keep everything beyond that at the work-package level
Overload signals: consistent overtime, rising quality review comments, missed internal deadlines, utilization above 85%

ELI5

You know when you have homework in three subjects due on different days, and you have to figure out which one to do first? That's task prioritization. The math homework due tomorrow goes first, obviously. The science project due Friday can wait until Wednesday. The history reading due next week is the lowest priority right now. You're ranking tasks based on when they're due and how long they take. Now add a twist: your friend asks you to help them study for a test tonight. Can you do that AND finish your math homework? That depends on how much math you have left and how long the study session will take. Figuring out whether you can handle the extra work without messing up your existing commitments? That's workload impact assessment. In architecture, project managers do this with much bigger task lists.

AREProject Management

Task Prioritization and Workload Impact Assessment

2 min read211 words

Why Task Prioritization Drives Schedule Success

Want to track your progress and access more study tools?

Create a free account