Project Managementoperational
Project & Task Risks
How are project risks recorded, scored, and mitigated?
Every project carries its own risk register: named risks with details and a mitigation plan. Risks then attach to specific tasks and are scored by probability and impact, producing a level that pulls a suggested mitigation text from configured values.
Referenced across3 other parts of continON
How it works
The project risk register is a list of records — each risk has a name, details, and a mitigation plan — maintained on the project screen with the usual create, update, and delete controls under project permissions.
Risks become operational when attached to tasks. A task risk links a register risk to a specific task and scores it with probability and impact values that resolve to a risk level; the level looks up a suggested mitigation plan text from configured lookup values, which can be edited per task risk. The register also tracks which risks are not yet assigned to a given task.
At the top, the project record carries an overall risk level, and the project screen lists risks at both scopes — the register and the per-task assignments — so review happens where the plan lives.
What the register holds
4 on the record- Per-project risk register
- Risks are records owned by the project, each with a name, details, and a mitigation plan.
- Probability × impact scoring
- Task risks carry probability and impact values that resolve to a risk level per task.
- Level-driven mitigation text
- Each risk level maps to a suggested mitigation plan pulled from configured lookup values and editable on the task risk.
- Overall project risk level
- The project record itself carries an overall risk level field visible from the register.
What this touches
- Task Management
Risks attach to individual task records, where the probability and impact scoring lives. - System Administration
Risk levels and suggested mitigation texts come from configurable lookup values. - Identity & Access
Risk create, update, and delete actions sit under the project permission resource granted by position.
See project & task risks running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.