Use case · Risk management

From gut feeling to a risk value in euros - and a measure on the board

Risks arise on the work package, get priced as probability times impact, are handled as cards and decided in the steering committee - one loop on one data foundation, not a second register.

A risk's journey

Identify
Assess
Treat
Decide
Monitor

Risks are captured where they surface - on the work package, no context switch; the AI proposes from project data.

Why risk management fails today

Rarely at spotting risks - mostly on the way from register to effect.

The register lives next to the project

Assessment happens in one tool, work in another. Between risk and countermeasure lies a media break - and that's where it fizzles out.

Assessment without a currency

“High”, “medium”, “red”: without a euro amount, every risk stays negotiable. The budget reserve is guessed instead of computed.

The committee decides - documented nowhere

The top risk gets discussed, a decision is made, the minutes go into a folder. Three weeks later nobody knows who owns the condition.

Assessed once, never touched again

Without a review cadence every assessment ages. That a risk got sharper only shows once it materialises.

One risk, five stations - from work package to cockpit

This is how WORKSPACE.PM walks the risk “data-privacy sign-off delayed” through a CRM rollout: price it, treat it, decide it, monitor it - without a second register.

1Identify

Risks arise where they surface

Every work package can carry its own risk tab - capture happens without a context switch, right in the container. And the AI thinks along: from project and container data it proposes risks with probability and impact, and up to ten from the briefing PDF at project creation. You review and adopt one by one - nothing enters the register unasked.

WP 3.2 - Data migrationRisk tab on the work package

Risk: data-privacy sign-off for customer data delayed

AI proposal from project data - adopt one by one
2Assess & reserve

“High” becomes an amount in euros

Probability times impact yields the gross risk value - shown transparently as a formula; the effect of measures lowers it to the net value. Across all open risks, the Monte Carlo simulation runs 10,000 iterations, and you adopt the reserve at your chosen percentile - P80 by default - as a cost position on the work package.

Probability 40 %×Impact €120k=gross €48k
after measures:net €18k
Reserve (P80) adopted as a cost position on the work package

The formula is visible on the risk - assessment happens in amounts, not colours.

3Treat

Measures are cards - not declarations of intent

You pick the response strategy modelled on PMI - avoid, mitigate, transfer, accept - and record owner, reduction value, cost and deadline per measure. One click turns the risk into a Kanban card with dual affiliation: it knows project and risk, the owner actively commits, and the done-state is visible on the risk.

Card: bring the privacy review forwardcommitted
Project: CRM rolloutRisk: privacy sign-off

Strategy: mitigate · reduction recorded · deadline set

DoneThe done-state is visible on the risk - net instead of gross.
Done with:Tasks & board
4Decide & escalate

The top risk goes to the steering committee - with consequences

Raise the risk's scope to programme or portfolio level and it appears in the cockpit's list of escalated risks. In the steering committee, the decision is marked right in the minutes and released with conditions - and the follow-up task is the same card that knows meeting and risk at once. Nothing fizzles out in a folder.

Scope: portfolio - appears as an escalated risk in the cockpit
Decision in the minutes: additional privacy review loopreleased with conditions
Follow-up task - knows meeting AND risk

Decision register per series and project-wide - nothing fizzles out in a folder.

5Monitor

Visible from the one-pager to the portfolio cockpit

The project one-pager shows the top risks with schedule, cost and performance impact, and the health score deducts points for critical risks. Early-warning indicators watch register metrics against thresholds and flag “breached” as a badge; reviews run on fixed cycles from 30 to 365 days with a documented sign-off. Overdue reviews and escalated risks appear in the PMO cockpit.

Project one-pager (excerpt)

Top risks: 7 open · 2 critical (S/C/P)

Health score: 68 - deduction for critical risks

PMO cockpit (excerpt)

Early-warning indicator: net exposureBreached
Reviews overdue1
Escalated risks2

And the good surprises? Opportunities have the same home: their own assessment, enhancing measures and gross/net logic - in the same system, deliberately leaner.

One loop, seven modules - one data foundation

In WORKSPACE.PM, risk management is not an extra register but the platform working in concert: the risk travels through the modules, the data stays the same.

One data foundation - from risk to card to cockpit

Risk events can trigger workflows, the register is open to AI and API - and every measure stays the same card, wherever you look from.

And who maintains the register?

Risk management only helps if it doesn't feel like a second job.

The AI proposes - you decide

From project and container data the AI identifies risk candidates with an assessment proposal and drafts preventive and corrective measures. Everything stays a draft until you adopt it item by item.

It keeps itself current

Review cycles with documented sign-off and full history, early-warning badges on threshold breaches - and workflows react to risk events, for instance with a notification when an indicator is breached.

Accountability stays personal

Every risk has an owner, every measure a responsible person with a deadline - and on the board, the commitment is actively given instead of silently assumed.

Frequently asked questions about risk management

What PMOs and project managers want to know before switching.

No. Many teams start with the top risks of their running projects and let the AI add candidates. For larger inventories the REST API is available - from then on, the register grows with every project by itself.

Capture is modelled on the PMI standard: probability and impact with schedule, cost and performance dimensions, plus the four response strategies avoid, mitigate, transfer and accept. Assessment happens in a 5×5 matrix with a gross/net toggle.

It runs 10,000 iterations on three-point estimates (PERT) and delivers cost exposure as P50, P80 and P90 percentiles. Costs are simulated fully; for schedules it provides an approximation without network-plan weighting - which the system states honestly.

You set the status to “materialised” and turn the risk into a Kanban card in the same step - the risk owner becomes the assignee, and the card knows its risk. A workflow can also react to the event, for instance with a notification or another task.

Yes. Opportunities have their own system with assessment, enhancing measures and gross/net logic - deliberately leaner than the risk module, for instance with a 4×4 matrix and without Monte Carlo simulation.

Turn risks into numbers, cards and decisions

Start for free: capture the top risks, price them in euros, put measures on the board - and in 30 days you'll know whether it fits.