Projects · Governance
Route /project/risks Flag risksEnabled

Risks

Project risks on live projects — register and RAG, not a side RAID spreadsheet as source.

Scroll to Flowcharts. Scenario: Log a project risk.

Uncertain downside

Risks on the project file

Risks live on Project. They are not a workbook beside Tracopus and not Work Graph comments as the register.

Projects → Risks Route /project/risks Org flag risksEnabled Manager · Project Manager · Executive · Admin

The job of this console

Log, own, mitigate, close. Escalate on governance when RAG is red.

Seat at the table

PMs, executives, admins. Contributors may raise; authors typically PMs.

The working rhythm

Filter project, add or update, review in governance, close when residual is accepted.

Moments that bring you here

Kickoff RAID. Vendor delay. Staffing hole. Before a customer steering.

ⓘ
On Project
Issues, lessons, and RCA are siblings. AI agents only summarize masked sources.

Flowcharts

1 — Log and own a risk

Add a risk on the project, assign owner, review RAG.

flowchart TD
  A[Open Risks] --> B[Pick project]
  B --> C[Add risk]
  C --> D[Owner + mitigation]
  D --> E[Governance / exec pack]
            
  1. 1
    OpenProjects → Risks.
  2. 2
    ProjectCanonical Project.
  3. 3
    LogOwner and mitigation.
  4. 4
    ReviewGovernance.

Overview

Risks hang off Project. Issues are realized. Lessons and RCA come after. Analytics risk intelligence charts the same family.

How to use

1. Project required
No orphan corporate risk without a home if the model is project-scoped.
2. Owner is Employee
Not a free-text nickname as the only owner.
3. Close with evidence
Do not leave residual red forever.