Skip to main content

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

RiskIssue
TimingFutureExisting now
QuestionWhat if?What happened?
GoalAvoid or mitigateResolve and close

Shared Fields​

FieldDescription
Name and DescriptionThe event and its impact
TypeTechnical or administrative (or your organization's types)
Open DateWhen it was recorded
ImpactThe potential or actual extent of harm
Importance / Urgency / SeverityUsed to prioritize the response
Response StrategyAccept, 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​

  1. Record risks at the start of the project, not during a crisis.
  2. Assign an owner to every high risk.
  3. Review high risks weekly alongside the schedule.
  4. If a risk occurs, close it and create an issue linked to the actual event.

How to Manage Issues​

  1. Record the issue on the day it appears, including its impact.
  2. Determine whether it stops the work or can be worked around.
  3. Link it to a change request if the solution requires changes to scope, cost, or time.
  4. 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.