The Risk Register: From 'Someone Mentioned That' to an Actual System
Someone on the client side mentions in passing that their data migration team is understaffed. You note it mentally. Two weeks later, the migration is the reason go-live slips by three weeks.
The risk was identified. It just wasn't managed.
This is one of the most common failure patterns in software implementation: risks get raised in meetings, land in nobody's tracker, and resurface later as problems. The PM knew about it. Everyone sort of knew about it. But without a formal record — an owner, a score, a response plan — it stays a concern instead of becoming a managed risk.
What the Risk Register Is
ProjektMind now includes a full Risk Register at the project level, built around PMI's standard probability-impact framework.
Each risk entry captures:
- Title and description — what the risk is and why it matters
- Category — Technical, Schedule, Resource, Scope, External, Financial, or Other
- Probability and Impact — rated Low, Medium, or High, which drives an automatic risk score (1–9)
- Response strategy — Avoid, Transfer, Mitigate, or Accept
- Risk owner — the person accountable for monitoring and responding
- Mitigation plan — what's being done to reduce likelihood or impact
- Contingency plan — what happens if the risk materializes
- Trigger conditions — early warning signs to watch for
- Status — Open, In Progress, Mitigated, Closed, or Accepted
- Dates — when it was raised, target resolution, and when it was resolved
Risks can be flagged as Hot Button items, which surfaces them in the Handoff Report when you're transitioning the project.
The Risk Matrix
The register includes a 3×3 probability-impact matrix view. Each cell shows how many risks sit at that intersection, and clicking a cell filters the list to just those risks.
Red cells (score 7–9) represent your high-severity open risks — the ones that need active management. Yellow cells (4–6) are medium severity. Green cells (1–3) are low severity, logged and monitored but not urgent.
The matrix gives you an immediate visual read on the risk profile of a project. A cluster of risks in the red zone tells you something different than a spread across yellow.
Risks Drive the Health Score
Open risks now feed directly into the project health indicator that appears across your dashboard and portfolio views.
A project with a high-severity open risk (score 7–9) shows as red — At Risk — even if all action items are on track and meetings are current. A medium-severity risk (4–6) tips the health to yellow. This is deliberate: a project that has no overdue tasks but carries an unmanaged high-probability, high-impact risk isn't actually on track.
The health reasons tooltip will surface the specific signal — "High-severity open risk" — so you know exactly what's driving the status.
Transcript Extraction
When you process a meeting transcript through ProjektMind's Transcript Processor, Sage now identifies and extracts risks directly into the Risk Register — not into project memory.
If someone on the call says "we're concerned the integration team won't be available during UAT," that comes through as a scoped, editable risk entry with a suggested category, probability, and impact — ready for you to review, adjust, and save. You're not retyping. You're reviewing.
Previously, risks mentioned in meetings ended up as memory entries with a "risk" category, which was better than nothing but not the same as a managed register entry with an owner and a response plan. That gap is now closed.
Sage Knows What's Open
Ask Sage about risks on a project and it will reference the open risk register — scores, owners, and response plans included. If you have three high-severity risks open going into go-live week, that context is in the conversation.
The Risk Register is available on all ProjektMind plans as part of the core project workspace.