Risk, Quality, and Issue Management
The core idea
Risk management is proactive; issue management is reactive. Know the risk process: identify, analyze (qualitative and quantitative), plan responses, implement, and monitor. Distinguish risk (uncertain future event) from issue (a realized problem requiring action now). Understand response strategies: avoid, mitigate, transfer, accept (and escalate for threats), each with cost/benefit tradeoffs.
Concepts to master
A risk register captures description, probability, impact, owner, response, and trigger. Quality management in trials spans quality planning (defining standards, e.g., ICH E6 GCP), quality assurance (process-level, planned, often audit), and quality control (product-level, checking outputs, e.g., source data verification). Know root cause analysis tools (5 Whys, fishbone) and corrective and preventive action (CAPA): correction fixes the instance; corrective action addresses cause; preventive action stops recurrence elsewhere. Understand the quality tolerance limits and risk-based monitoring concepts that emphasize critical data and processes.
Traps
Common distractors: labeling a known problem a "risk"; choosing "accept" when a low-cost mitigation exists; and confusing QA with QC. Another trap is applying a correction and calling it a CAPA-questions often test whether you addressed the root cause and prevented recurrence. Also watch for "transfer" being misread as eliminating risk (insurance and vendors transfer financial/operational impact, not accountability).
Rule of thumb
If it has already happened, it is an issue-log and act. If it might happen, it is a risk-score and plan a response with an owner.
Worked example
Repeated temperature excursions in a shipment are an issue. Isolating affected product is a correction; investigating the shipping validation and updating the process to prevent recurrence is the corrective action; applying the same fix to other sites is preventive action.