ARE 5.0: PjM common mistakes
ARE 5.0: PjM · Understand the traps and how to avoid them.
Treating the project budget as a single lump sum and answering cost questions without separating labor, consultants, reimbursables, and contingency.
Candidates study the budget as one number and never practice breaking a fee into its component cost categories, so they cannot reason about which line item a scenario is actually testing.
What to do instead
Before answering any cost question, write the fee structure out: labor by phase and staff level, consultant fees, reimbursable expenses, and contingency. Practice converting a total fee into a bottom-up labor budget using hours times billing rate, and identify which category absorbs a given change.
Confusing the billing rate multiplier with the break-even multiplier and using them interchangeably in staffing calculations.
Both are called multipliers and both relate hours to fees, so candidates memorize one formula and apply it to every problem without checking whether overhead and profit are included.
What to do instead
Drill the distinction explicitly: the break-even multiplier covers direct labor plus overhead, while the billing multiplier adds profit on top. Work practice problems that require computing direct labor cost from hours, then applying each multiplier separately and labeling the result.
Assuming a project can be compressed by adding staff at any point, without checking phase, task interdependence, or the point of diminishing returns.
Candidates apply general 'crash the schedule' logic from other exams and ignore that design work is sequential and that adding people late increases coordination cost rather than reducing duration.
What to do instead
For any schedule-compression scenario, first identify whether the task is on the critical path and whether it can be parallelized. Recall that adding staff helps most early in a phase with divisible work and least during final coordination; select the answer that reflects resequencing or fast-tracking before adding headcount.
Building a work plan that lists phases but omits the deliverable, the responsible party, and the review or approval gate for each task.
Candidates confuse a phase list with a work plan and answer planning questions at too coarse a level, missing the accountability and milestone structure the exam is probing.
What to do instead
Practice drafting work plans in a table with columns for task, deliverable, responsible staff, hours, duration, predecessor, and sign-off. When a question describes a planning gap, look first for the missing responsibility assignment or missing milestone rather than the missing activity name.
Treating the critical path as fixed and failing to update it after a scope change or a delay in a non-critical activity.
Candidates learn the critical path as a single correct answer on a diagram and do not rehearse the idea that float consumption can shift the critical path mid-project.
What to do instead
For every schedule scenario, recompute total float on the affected chain before choosing. Practice problems where a delayed non-critical task consumes its float and becomes critical, and where a scope addition creates a new longest path.
Delegating a task to the first available person rather than matching the task to the required skill level and license.
Candidates optimize for availability because it is the most visible constraint in a staffing scenario, overlooking competence, licensure, and supervision requirements that drive the correct answer.
What to do instead
When assigning work, screen candidates in order: required license or certification, required technical skill, availability, then cost. Practice identifying tasks that legally or contractually cannot be delegated to unlicensed staff regardless of workload.
Managing team performance only through corrective feedback and skipping the goal-setting and expectation-setting step.
Candidates associate team management with resolving conflict and miss that most exam scenarios test prevention: clear roles, defined expectations, and regular check-ins.
What to do instead
For any team performance scenario, ask whether expectations were documented and communicated before diagnosing the individual. Choose answers that establish clear roles, measurable expectations, and scheduled feedback over answers that escalate or discipline.
Addressing a conflict between team members by escalating to the client or principal before attempting direct resolution.
Candidates read escalation as decisive and professional, but the exam generally rewards resolving issues at the lowest effective level and preserving the client relationship.
What to do instead
Rank response options by level of escalation and prefer the lowest level that can resolve the issue: direct conversation, then project manager facilitation, then firm leadership, then client involvement only when the issue affects client scope, cost, or schedule.
Treating risk management as a one-time list created at kickoff rather than a monitored register with owners, triggers, and responses.
Candidates memorize risk categories and stop there, so they cannot distinguish a risk from an issue or explain what happens after identification.
What to do instead
Practice building a risk register with columns for risk, probability, impact, owner, trigger, response strategy, and review date. Drill the distinction between a risk (future, uncertain) and an issue (current, certain) and choose responses that assign an owner and a monitoring trigger.
Choosing to avoid or transfer a risk when mitigation or acceptance is the appropriate response for a risk the firm controls.
Candidates match response strategies to keywords rather than to who controls the risk and whether the exposure is worth the cost of the response.
What to do instead
For each risk, first ask who controls it and whether the response cost is proportionate to the exposure. Avoid when the activity can be eliminated, transfer when another party is better positioned to bear it, mitigate when the firm controls the likelihood or impact, and accept when the exposure is small or the cost of response exceeds the loss.