HKSM

Preplanned, condition-based risk responses that are executed only when defined triggers occur. They specify thresholds, actions, owners, and reserves to address threats or opportunities if needed.

Key Points

• Predefined actions activated by clear triggers or thresholds tied to risk indicators.
• Used when it is inefficient to implement a response unless the risk condition actually occurs.
• Applicable to both threats (e.g., activate a workaround) and opportunities (e.g., scale up to capture upside).
• Often documented as contingency plans with associated reserves and, if needed, fallback plans.
• Require assigned owners, lead-time considerations, and integration with monitoring and escalation paths.
• Reviewed and adjusted as risk exposure, assumptions, or project context change.

Purpose of Analysis

To decide when and how to act only if specific risk conditions arise, balancing preparedness with efficient use of resources. This analysis aligns triggers, actions, and reserves with the project's risk appetite and ensures timely, consistent responses.

Method Steps

• Identify risks suitable for condition-based responses (uncertain occurrence, measurable precursors).
• Define objective triggers and thresholds (metrics, dates, events) that signal activation.
• Design the contingent action: scope, steps, lead time, resources, and fallback if the action is ineffective.
• Estimate cost and schedule impacts; size and earmark contingency reserves as needed.
• Assign response owners and clarify decision rights and escalation rules.
• Integrate triggers into monitoring and reporting (dashboards, control charts, milestone checks).
• Validate feasibility with what-if analysis or simulations; obtain approvals and document in the risk register and response plans.

Inputs Needed

• Risk register and risk report (identified risks, assessments, and priorities).
• Risk appetite, thresholds, and stakeholder risk attitudes.
• Project scope, schedule, and cost baselines; resource plans.
• Assumptions log and constraints that may influence triggers or actions.
• Performance data and predictive indicators relevant to the risk.
• Reserve policies and change control procedures.
• Lessons learned and historical data on similar risks and triggers.

Outputs Produced

• Documented contingency plans and, if needed, fallback plans with activation criteria.
• Defined triggers, thresholds, monitoring approach, and response owners in the risk register.
• Reserve requirements and updates to cost/schedule forecasts and plans.
• Change requests if baselines, contracts, or governance elements must be updated.
• Updates to communications and stakeholder engagement plans regarding trigger handling.

Interpretation Tips

• Use measurable, objective triggers to avoid ambiguity and delay.
• Ensure triggers provide enough lead time for the action to be effective.
• Link each trigger to a single point of accountability for activation decisions.
• Right-size reserves to the exposure; avoid over-buffering many low-value contingencies.
• Test plans through scenarios to confirm feasibility and supply chain or vendor readiness.
• Revisit triggers after major changes; emerging risks may require new or revised conditions.

Example

A supplier delay risk is identified for a critical component. Trigger: no confirmed shipment date by 10 business days before the needed date. Contingent action: place an expedited order with a prequalified alternate supplier, using a reserved budget for the price premium and rush shipping. Fallback: re-sequence work to consume available float if the alternate cannot deliver on time.

Pitfalls

• Vague triggers that rely on subjective judgment or informal signals.
• No reserved funds or capacity, making the contingent action infeasible when needed.
• Ignoring lead times, resulting in too-late activation and limited effectiveness.
• Overcomplicating with excessive contingencies that burden monitoring and governance.
• Unassigned ownership or unclear authority to activate plans.
• Failure to align with contracts, compliance, or procurement constraints.

PMP Example Question

A project team defines an action to rent additional equipment only if throughput drops below 70% for two consecutive days, as shown on the dashboard. What is this approach best described as?

1. Contingent response strategy.
2. Mitigation plan applied immediately.
3. Workaround implemented after an issue occurs.
4. Risk transfer to a third party.

Correct Answer: A — Contingent response strategy

Explanation: The action is preplanned and activated by a defined trigger (throughput below 70% for two days). It is not immediate mitigation, a reactive workaround, or a transfer of risk.