Risks and Issues
A project that does not record its risks will surprise management when they occur. The Risks and Issues tab distinguishes between what might happen and what has already happened.
Location: 360 View ← Risks and Issues
| Risk | Issue | |
|---|---|---|
| Timing | Future | Existing now |
| Question | What if? | What happened? |
| Goal | Avoid or mitigate | Resolve and close |
Shared Fields
| Field | Description |
|---|---|
| Name and Description | The event and its impact |
| Type | Technical or administrative (or your organization's types) |
| Open Date | When it was recorded |
| Impact | The potential or actual extent of harm |
| Importance / Urgency / Severity | Used to prioritize the response |
| Response Strategy | Accept, avoid, mitigate, transfer, and so on |
Risk Statuses
- Open
- In Progress
- Resolved
Issue Statuses
- Open
- In Progress
- Resolved
(Status labels may appear as configured by your organization.)
How to Manage Risks
- Record risks at the start of the project, not during a crisis.
- Assign an owner to every high risk.
- Review high risks weekly alongside the schedule.
- If a risk occurs, close it and create an issue linked to the actual event.
How to Manage Issues
- Record the issue on the day it appears, including its impact.
- Determine whether it stops the work or can be worked around.
- Link it to a change request if the solution requires changes to scope, cost, or time.
- Do not leave an “In Progress” issue without a review date.
Best Practices
A risk without an owner is not a managed risk
If no responsible person is named in the weekly review, the response will not move forward.
Hiding issues to protect the project's “image”
An unrecorded issue reaches management late and with greater impact. This register is for protection, not personal blame.
Related Sections
- Scope — change requests arising from issues
- Management Center — assumptions that may become risks
- Project Actions — pausing the project if an issue blocks work