Hello, How can we help?

What this does

Identify, assess, and track risks within a project. Each risk can have mitigation actions linked to tasks, so risk management becomes part of your project workflow rather than a separate activity.

Current access and functionality

• Verified against the current impact-web, impact-client, and impact-marketplace code on 2026-05-07.
• In impact-web, users must be signed in and working in an active workspace. Navigation and write actions are role-, permission-, and entitlement-aware; unavailable modules are hidden or disabled instead of being universally visible.
• Project creation and management are available to company admins, owners, project coordinators, and project managers according to the permission matrix. Project members may only see assigned or permitted project content.

Before you start

• You must have an existing project.
• You must be the project manager or have edit permissions on the project.

Steps

Adding a risk

1. Open the project and go to the Risks tab.
2. Click Add Risk.
3. Fill in the risk details:
   • Name — a short label for the risk (e.g., "Key developer unavailable").
   • Description — detailed explanation of the risk and its potential impact.
   • Likelihood — how likely the risk is to occur.
   • Impact — how severe the consequences would be if it occurs.
4. Add any Notes for additional context.
5. Click Save.

Adding mitigation actions

1. Open a risk and go to the Mitigations section.
2. Click Add Mitigation.
3. Enter the mitigation details:
   • Title — what action will reduce or eliminate the risk.
   • Description — how the mitigation will be carried out.
   • Mitigation Type — the category of response (e.g., avoid, transfer, mitigate, accept).
   • Assigned To — the team member responsible for this mitigation.
4. Optionally link the mitigation to a Task — this creates a direct connection between your risk register and your project tasks.
5. Click Save.

Resolving a risk

1. Once all mitigations are in place and the risk is no longer active, mark the risk as Mitigated.
2. The resolution timestamp and the person who resolved it are recorded.

Tips

• Review risks regularly during project meetings. Risks that were low likelihood at the start may increase as the project progresses.
• Link mitigations to actual tasks so they show up in your task list and get tracked like any other work item.
• Use Likelihood x Impact to prioritise which risks need attention first.
• Keep the risk register updated — outdated risk registers give a false sense of security.

Common issues

• Issue: Risk is mitigated but still shows as active — Fix: Make sure you explicitly marked the risk as mitigated using the resolve/mitigate action, not just completing the linked tasks.
• Issue: Cannot add mitigations — Fix: Check your project permissions. Only project managers and users with edit access can manage risks.

Related

• How to create a project
• How to create and assign tasks