Use tense and certainty to choose the document
“The supplier may miss the delivery date.”
“The supplier missed yesterday’s delivery date.”
“We expect legal approval by 15 September.”
May, might, could: risk. Has, is, did: issue. Believe, expect, presume: assumption. Then assess impact, assign ownership and take the appropriate action.
Risk register: manage uncertain threats and opportunities
A risk register records identified uncertainties and how the team intends to monitor or respond. A useful risk statement separates cause, uncertain event and effect: Because the component is single-sourced, the supplier may miss the shipment date, causing integration testing to start late.
Do not merely add a risk and wait. Analyse it proportionately, agree a response, fund or schedule actions when needed, and review triggers and residual exposure.
Issue log: drive ownership and resolution of a current problem
Once a condition exists, the team needs resolution rather than probability analysis. Record the problem, effect, priority, owner, actions, due date, status and required escalation or decision.
Security testing cannot begin because the approved environment is unavailable.
Owner: Infrastructure lead
Target: Restore by Wednesday
Action: Reallocate capacity and validate access
Escalation: Sponsor decision if delay exceeds two days
The issue log supports visibility; it does not solve the issue by itself. The project manager facilitates analysis, involves the right people, implements corrective action and communicates effects according to governance.
Assumption log: make planning beliefs testable
Teams plan with incomplete information. An assumption is treated as true for planning, even though it has not been fully proven. A constraint limits available options. Record both, identify who will validate them, and revisit them as information changes.
Subject-matter experts will provide 10 hours per week.
Validate: Resource manager confirmation by 20 August.
If false: Requirements workshops and schedule may slip.
The regulatory filing date is fixed.
Effect: Scope, resources or sequence must adapt around the deadline.
Review: Confirm any permitted staging or exception process.
An unvalidated assumption can generate a risk. If the assumption proves false and causes a present obstacle, that condition becomes an issue requiring action.
The records form a decision chain
Vendor approval is expected Friday.
Approval may be late, delaying procurement.
No approval by Thursday noon.
Friday arrives without approval.
Keep traceability without duplicating noise. The assumption remains useful history, the risk records planned exposure and response, and the issue log manages the actual condition. Update stakeholders and related plans when the change affects commitments.
Worked scenario: critical engineer may leave
Situation: A team hears that its only integration engineer is interviewing externally. The engineer has not resigned.
Record and assess the risk
Capture the uncertainty, schedule impact, owner, indicators and response options.
Reduce exposure
Cross-train another engineer, improve documentation and remove knowledge concentration.
Open and resolve the issue
Activate transition actions, update forecasts and escalate resource decisions as required.
Do not wait passively or replace the employee based on a rumor. Assess the uncertain event, act on an approved response, communicate appropriately, and treat the resignation as an issue only if it occurs.
Agile and hybrid teams still manage risks, issues and assumptions
The format may be lightweight: risks can appear on a risk board or backlog, issues may be impediments, and assumptions may be captured in discovery notes or an assumption map. The management need remains—visibility, ownership, validation, response and escalation.
Use retrospectives, reviews, daily collaboration and backlog refinement to surface changing exposure. Do not force documentation for its own sake, but do not hide significant uncertainty because the delivery method is adaptive.
Practice checks with explanations
A permit might arrive two weeks late. Where should it be recorded first?
Best answer: the risk register. It is an uncertain future event; analyse impact, assign an owner and plan a response.
The permit deadline passed and work is blocked. What now?
Best answer: manage it as an issue, implement corrective or workaround actions and communicate schedule effects. Update the original risk status for traceability.
The plan expects customer data by Monday but confirmation is pending. What is this?
Best answer: an assumption. Record its basis, owner, validation date and consequence if false; identify a related risk if the effect warrants it.
Common PMP scenario mistakes
- Calling a current blocker a risk because it was once uncertain.
- Recording a risk without an owner, response or review.
- Using the issue log as a substitute for corrective action.
- Leaving assumptions hidden in the schedule or estimate.
- Escalating every uncertainty before analysing it with the team.
- Closing the risk record without preserving traceability when it becomes an issue.
- Assuming agile delivery eliminates project risks or governance.
Frequently asked questions
What is the difference between a risk and an issue in PMP scenarios?
A risk is an uncertain event or condition that may affect objectives in the future. An issue has already occurred or currently exists and requires action, ownership and resolution.
What belongs in a risk register?
Useful fields include the risk statement, category, cause, probability, impact, owner, response, trigger, status and review date. The exact format should fit the project and governance needs.
What belongs in an issue log?
An issue log commonly records the current problem, discovery date, impact, priority, owner, target resolution, actions, status and escalation or decision history.
What is an assumption log used for?
It records assumptions and constraints, their basis, owner, validation method or date, status and the effect if an assumption proves false. It keeps planning beliefs visible and reviewable.
Does every risk become an issue?
No. A risk may never occur, may be avoided, or may be reduced. When the uncertain event occurs, manage the present condition as an issue while preserving relevant risk history and response information.
Official PMI references
Confirm the active credential and preparation guidance on the official PMP certification page, PMP exam-preparation page, and PMI standards catalog. ITCertPath explanations are independent study resources and do not reproduce confidential exam questions.