DELIVERY RISK
Explain a project risk before it becomes an unexplained delay
Record severity, impact, mitigation, an owner and a follow-up date. Keep important delivery warnings visible in the project assessment.
Put uncertainty into words the team can act on
A warning such as “the launch may slip” is hard to manage without a reason or a next step. Tsumira lets a project team create a specific risk record: what could happen, how serious it would be and what someone will do about it. The risk stays with the delivery project so the next progress conversation has evidence rather than a recollection of an earlier concern.
Describe the risk and a practical response
Each risk has a title and a severity of low, medium, high or critical. Add an estimated probability, an impact description and mitigation when these are useful. Probability is the team’s entered assessment, not an AI forecast. A named owner and optional due date make the response concrete: who will check the issue, and when the team expects an answer.
- Four severity levels
- Optional probability and impact
- Mitigation, owner and follow-up date
Keep serious warnings visible
Open high and critical risks contribute to the project health calculation. Critical risk takes precedence over a reassuring manual assessment; a team cannot simply repaint a known deterministic warning green. Health also considers blocked and overdue work. The result shows the reason for attention, helping the project lead distinguish an urgent exposure from a general feeling that the project is uncomfortable.
- High and critical risk signals
- Reasons alongside the health assessment
- Manual assessment does not erase objective warnings
Resolve the issue without erasing its existence
An authorized project colleague can mark the risk resolved, recording the resolution time. The update checks the current revision, protecting a newer change from an outdated request. Resolve a risk when the exposure has genuinely been dealt with, and use the project conversation or update to explain the outcome. A risk record supports a delivery decision; it is not an insurance, safety or regulatory certification.
- Explicit resolved state and timestamp
- Current-revision checks
- Project context for explaining the outcome
A concrete workflow
Name the exposure
Write the specific event that could affect delivery and its likely consequence.
Choose the response
Set severity, explain mitigation and name the colleague responsible for following it up.
Review project impact
Discuss the risk with the project’s blocked work, dates and health reason rather than considering it in isolation.
Close it deliberately
Record resolution when the exposure has been addressed and communicate any remaining effect on the delivery plan.
An illustrative working example
Example: materials may arrive too late
A technical team learns that a required component may miss the installation date. The project lead records a high risk, explains the customer impact and assigns a colleague to check a substitute by Thursday. The risk contributes to the project warning while the answer is pending. Once the alternative is confirmed, the colleague records resolution and the next project update explains the revised preparation steps.
Questions about this topic
Is probability calculated automatically?
No. The supported probability field records an assessment entered for the risk. It should not be presented as a statistical prediction.
Can a manual green assessment hide a critical risk?
The project health calculation gives objective delivery warnings priority. A critical open risk remains a reason for an off-track assessment.
Who can resolve a risk?
Resolution follows the project write authority and the relevant operation permissions. Seeing the project does not automatically permit changing its risks.
Does a risk register replace formal compliance review?
No. It organizes project delivery concerns. Specialized safety, legal or regulated risk decisions still need the appropriate professional process.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Jira (OAuth)
Workflow concept: Review a blocking issue before describing its delivery risk and mitigation.
Microsoft Excel
Workflow concept: Prepare a risk assessment with explicit severity, owner and follow-up date.
Slack
Workflow concept: Review a reported concern before making it a project risk record.