ACRP-PM common mistakes
ACRP-PM · Understand the traps and how to avoid them.
Answering clinical-operations questions from trial-execution instinct (e.g., 'just escalate to the PI immediately') instead of applying the standard PM process sequence of identify, document, assess, plan response, then escalate.
Candidates come from coordinator, monitor, or CRA backgrounds where escalation is the reflex, and they never map the question to a PM process framework before choosing an answer.
What to do instead
Before choosing, classify the question by process group (initiating/planning/executing/monitoring/controlling/closing) and ask which PM artifact or step logically precedes the others; prefer answers that document and assess before acting.
Selecting the most comprehensive-sounding answer (e.g., 'create a full risk register and re-baseline the schedule') when the question asks for the next or first action.
Exam stems are often long and stress-laden, pushing candidates toward the biggest-sounding remedy rather than the smallest correct next step.
What to do instead
Underline the qualifier in the stem (first, next, best, primary) and eliminate any option that jumps ahead of the immediate step, even if it is a valid later action.
Building a study timeline by listing activities without sequencing dependencies, milestones, or resource calendars, then treating the resulting date list as a schedule.
Site-startup and enrollment dates feel intuitive to operational staff, so dependencies (IRB approval before site activation, protocol finalization before database build) get assumed rather than modeled.
What to do instead
Practice constructing a small network diagram with predecessors and durations for a startup-to-first-patient-in path, and identify the critical path before answering schedule questions.
Accepting a sponsor- or executive-imposed enrollment target as the plan baseline without testing it against site capacity, screen-failure rate, and startup lag.
Candidates confuse an approved target with a validated estimate and skip feasibility arithmetic under time pressure.
What to do instead
Rehearse back-of-envelope enrollment math (sites x activation date x monthly accrual x screen-fail adjustment) and, when an option offers to validate feasibility before committing, prefer it over accepting the target.
Treating budget questions as pure arithmetic and ignoring scope-change control, so cost overruns are answered with 'find more money' rather than change control or scope reconciliation.
Candidates separate cost from scope in their heads even though the exam tests integrated change control and earned-value-style thinking.
What to do instead
For any budget question, first ask whether a scope change occurred and whether it went through change control; answers that route through a documented change request usually beat answers that absorb or reallocate cost.
Choosing to manage an underperforming vendor by informal conversation or by immediately terminating, skipping contract terms, performance metrics, and a documented corrective-action path.
Relationship instincts and frustration drive the choice; candidates rarely review the contract-administration options in the answer set.
What to do instead
Memorize the vendor-management ladder (measure against agreed metrics, document, issue formal notice per contract, corrective action plan, escalate, then consider termination) and pick the earliest rung that fits.
Handling a risk question by proposing a contingency (extra budget, backup vendor) when the correct answer is to avoid, transfer, mitigate, or accept the risk as a planned response.
Candidates conflate contingency reserves with risk response strategies and default to 'have a backup' for every threat.
What to do instead
Sort each risk option into the standard response categories and reject options that merely add slack without addressing the risk's probability or impact; identify which category the stem's risk actually calls for.
Answering quality questions by adding more monitoring visits or more source-data verification rather than addressing root cause through CAPA and process change.
Monitoring is the most familiar quality tool to clinical staff, so it crowds out corrective-and-preventive-action reasoning.
What to do instead
When a stem describes a recurring or systemic deviation, prefer options that investigate root cause and implement a preventive change over options that increase inspection frequency.
Choosing to communicate bad news upward only after the problem is fully resolved, or choosing to inform the whole study team before informing the accountable stakeholder.
Candidates fear premature escalation and default to either silence or broad broadcast, ignoring stakeholder analysis and communication planning.
What to do instead
Identify the accountable decision-maker in the stem and the communication plan's escalation thresholds; prefer timely, targeted communication to the responsible party over delayed or scattershot messaging.
Resolving team-conflict questions by picking the option that preserves harmony (avoid the conflict, reassign the person, smooth it over) instead of addressing the issue directly with those involved.
Clinical teams prize consensus, and candidates import a conflict-avoidant workplace norm into situational-judgment items.
What to do instead
Recall that collaboration and direct, private confrontation of the issue is the preferred conflict mode in PM frameworks; eliminate accommodation, avoidance, and forcing options unless the stem shows a genuine emergency requiring command decisions.