Workarounds
Workarounds are unplanned responses to risks that were not previously identified or to risks for which no planned response was adequate. They are developed in the moment when a risk event occurs without a contingency plan.
Know it well enough for the exam? Questions on Workarounds are scenario-based, not definitional.
Practice it freeExplanation
While contingency plans are preplanned responses for identified risks, workarounds are improvised responses created when an unidentified risk materializes or when a planned response proves insufficient. Workarounds are by nature reactive, developed under time pressure when the risk event has already occurred.
For example, if a server crashes due to an unforeseen hardware defect (a risk that was never identified), the team might create a workaround by quickly provisioning a cloud server as a temporary replacement. This was not planned in advance but addresses the immediate problem.
Workarounds should be documented in the risk register after they are implemented, along with the risk they addressed. They are reviewed during Monitor Risks to determine if additional follow-up is needed. Frequent reliance on workarounds may indicate that the Identify Risks process needs improvement, as it suggests many risks are being missed during planning.
Key Points
- •Unplanned responses developed when unexpected risks materialize
- •Reactive by nature, created under time pressure
- •Documented in the risk register after implementation
- •Frequent workarounds may signal inadequate risk identification
Exam Tip
Workaround = unplanned response to an unidentified risk. Contingency plan = preplanned response to an identified risk. The exam often tests this distinction.
Frequently Asked Questions
Related Topics
Monitor Risks
Monitor Risks is the process of monitoring the implementation of agreed-upon risk response plans, tracking identified risks, identifying and analyzing new risks, and evaluating risk process effectiveness throughout the project.
Risk Triggers
Risk triggers (also called risk symptoms or warning signs) are events or conditions that indicate a risk is about to occur or has already occurred. They signal the need to activate a risk response.
Accept (Risk Strategy)
Accept is a risk response strategy where the project team acknowledges a risk but takes no proactive action to address it. Acceptance can be passive (do nothing) or active (establish a contingency reserve or plan).
Identify Risks
Identify Risks is the process of determining which risks may affect the project and documenting their characteristics. It is performed iteratively throughout the project.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Risk Register
The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.
Transfer (Risk Strategy)
Transfer is a threat response strategy that shifts the negative impact and ownership of a threat to a third party. The risk is not eliminated but the responsibility for managing it moves to another entity.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Power Interest Grid (Power/Influence Grid)
The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.
Critical Path Method (CPM)
The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Part of
Risk Management
Practice Workarounds
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.