PMI-RMP exam content outline: domains, tasks and weights

The PMI-RMP Examination Content Outline organizes the exam into five domains: Risk Strategy and Planning, Risk Identification, Risk Analysis, Risk Response, and Monitor and Close Risks. Risk Identification and Risk Analysis carry the largest individual weights at 23% each, followed by Risk Strategy and Planning at 22%, Monitor and Close Risks at 19%, and Risk Response at 13%.

The outline is more than a list of topics. PMI structures each domain around tasks representing responsibilities performed by project risk management professionals, with enablers illustrating activities associated with those tasks. This makes the ECO a useful blueprint for understanding both what the exam covers and the type of professional judgement candidates may need to apply.

The PMI-RMP blueprint uses three levels: domains, tasks, and enablers. Domains represent major areas of project risk management practice. Tasks describe responsibilities performed within those domains, while enablers provide examples of activities that support each task.

PMI states that every examination includes the tasks associated with each domain while maintaining the published percentage distribution at the domain level. Enablers should therefore be treated as illustrations of task scope rather than a finite list of items to memorize.

• Domain — a high-level knowledge area essential to project risk management practice.
• Task — a responsibility performed by the project risk management professional.
• Enabler — an illustrative activity demonstrating what a task can involve.
• Domain percentages determine the relative distribution of exam content.

The domain percentages indicate how PMI distributes examination content across the five areas. The percentages can help guide study allocation, but a lower percentage should not be interpreted as permission to ignore a domain. Risk-management decisions frequently connect activities across multiple domains.

Risk Strategy and Planning establishes the environment in which project risk management will operate. It covers the information, organizational context, stakeholder expectations, thresholds, processes, roles, and communication structures needed before and during risk-management activities.

Candidates should understand how risk appetite and thresholds influence project decisions and how organizational factors, stakeholders, methodology, assumptions, and project objectives affect the risk-management approach.

• Perform a preliminary document analysis.
• Assess the project environment for threats and opportunities.
• Confirm risk thresholds based on risk appetites.
• Establish the risk management strategy.
• Document the risk management plan.
• Plan and lead risk management activities with stakeholders.

Risk Identification focuses on discovering and documenting uncertainty that may affect project objectives. The domain covers formal identification activities as well as examination of assumptions, constraints, triggers, thresholds, causes, consequences, and risk ownership.

A candidate should be able to distinguish threats from opportunities, recognize how assumptions and constraints can create risk exposure, and understand how identified information is converted into usable risk-register data.

• Conduct risk identification exercises.
• Examine assumption and constraint analyses.
• Document risk triggers and thresholds based on project context and environment.
• Develop the risk register.

Risk Analysis is tied with Risk Identification as the highest-weight PMI-RMP domain. It evaluates the ability to assess identified risks, prioritize them, analyze their potential effect on project objectives, and determine how uncertainty should influence decisions.

The domain includes both qualitative and quantitative analysis. Candidates should understand probability and impact assessment, risk matrices, prioritization, forecasting, sensitivity analysis, and quantitative techniques in the context of project risk decisions rather than as isolated formulas.

• Perform qualitative risk analysis.
• Perform quantitative risk analysis.
• Identify threats and opportunities through analysis of project risk complexity and objectives.
• Interpret risk information in relation to schedule, cost, scope, resources, quality, stakeholders, and strategic objectives.

Risk Response is the smallest domain by percentage, but it remains a core part of the project risk lifecycle. It focuses on selecting appropriate response strategies and turning those strategies into owned, executable actions.

Candidates need to evaluate whether a response fits the characteristics of the risk, determine appropriate actions and owners, assess effectiveness, and recognize residual or secondary risks that may arise when responses are implemented.

• Plan risk responses.
• Determine appropriate risk response strategies.
• Define risk response actions and assign owners.
• Assess the expected effectiveness of response actions.
• Implement risk response and contingency plans.
• Evaluate residual and secondary risks created through implementation.

Monitor and Close Risks focuses on what happens after risks and responses have been identified and planned. It covers performance information, changing risk exposure, residual and secondary risks, project-document updates, communication, and closure of risks that are no longer relevant.

This domain requires candidates to think dynamically. Risk management does not stop after the register or response plan is created; new information must be evaluated and existing risk information may need to be updated throughout the project.

• Gather and analyze performance data.
• Monitor residual and secondary risks.
• Provide information needed to update relevant project documents.
• Monitor project risk levels.
• Communicate changing risk information to relevant stakeholders.
• Close expired risks and capture relevant information.

The five PMI-RMP domains should not be interpreted as belonging to a single project delivery approach. PMI states that predictive, agile, and hybrid approaches can appear throughout the five domains rather than being isolated into a separate methodology section.

For preparation, this means candidates should be comfortable applying risk-management reasoning in different project environments. The core decision may still involve identification, analysis, response, or monitoring, but the surrounding context and way information is gathered or acted upon can differ.

• Do not study agile risk management as if it were a separate sixth domain.
• Expect the project environment to influence how risk activities are performed.
• Focus on the purpose of the risk-management action rather than memorizing one delivery approach.

The ECO works best as a preparation map rather than a checklist of definitions. Start by understanding what each domain is responsible for, then work downward into tasks and the concepts or techniques required to perform them. Practice questions can then be mapped back to the relevant domain and task.

This approach makes incorrect answers more useful. Instead of recording only that a question was missed, identify whether the problem came from misunderstanding the project context, identifying the wrong stage of the risk lifecycle, applying an analysis technique incorrectly, or selecting an inappropriate response.

Domain weight is an important planning signal, but it should not be used mechanically. Risk Identification and Risk Analysis deserve substantial preparation because they each represent 23% of the examination, yet weaknesses in a smaller domain can still affect overall performance and can also undermine reasoning in connected scenarios.

Practice exams become more informative when results are reviewed against the ECO. An overall percentage may show general performance, but domain-level patterns explain where preparation needs to change. Repeated Risk Analysis misses, for example, call for a different response than recurring mistakes involving residual risks or risk closure.

A useful review process combines domain classification with the reason an answer was missed. This helps distinguish a concept gap from a scenario-reading problem, an analytical mistake, or an inappropriate response-selection decision.

• Tag each missed question by PMI-RMP domain.
• Identify the task or decision being tested where possible.
• Record why the selected option was weaker than the preferred response.
• Separate conceptual errors from scenario-interpretation errors.
• Use targeted review before adding another full mock exam.
• Retest with unfamiliar scenarios to confirm improvement.

The ECO can be misused when candidates treat it as a vocabulary list or assume percentages alone provide a complete study plan. Its purpose is to describe the responsibilities and activities represented on the exam. Effective preparation therefore requires understanding relationships between domains, tasks, techniques, and project situations.

• Studying domain percentages without studying the tasks underneath them.
• Ignoring Risk Response because it has the lowest percentage.
• Treating qualitative and quantitative analysis as isolated calculations.
• Assuming predictive, agile, and hybrid approaches belong to separate exam sections.
• Memorizing enablers without understanding the responsibility represented by the task.
• Using overall practice scores without checking domain-level weaknesses.

Use the PMI-RMP Examination Content Outline as the structural source of truth for what the exam evaluates. From there, combine the official tasks with reference materials, scenario-based study, and domain-level practice analysis.

If you are still determining whether you qualify for the credential, review the PMI-RMP eligibility requirements first. If your preparation structure is already established, move to the PMI-RMP practice-exam guide and use the five-domain blueprint to interpret your results.