Risks rarely stay inside one ART. This article shows you how a solution board brings several risk registers together, and how you filter, review and analyse them in one go.

One register per PI board, many per solution board

A PI board has exactly one risk register. A solution board can link as many registers as it needs, and shows all their risks together in one place. Open it from More › Risks Register.

	PI board	Solution board
Registers	One	Any number
Where they come from	Linked by the board owner	Every linked PI board's register is added automatically, plus any you link or create yourself
Workflow, matrix and fields	The register's own	Each risk keeps its own register's workflow, risk matrix and field layout

As soon as two or more registers are linked, the risk page switches to its multi-register mode: a Register Name column, a Risk Register filter, a status filter grouped per register, one board swimlane per register and a register picker in Analytics. With a single register the page works like a PI board's risk page, with the Linked Risk Registers chips and Link risk register on top.

PI board registers come in automatically

When you link a PI board to the solution board, the risk register attached to that PI board is linked to the solution board straight away. Kendis checks this again every time the solution board opens, so it stays in step with the PI boards.

Registers that came from a PI board carry a small PI badge on their chip. The badge shows once you have opened Link risk register on the page.
If a PI board leaves the solution and is linked again later, its register comes back with it, even if you had unlinked it before.
If several PI boards share the same register, it is linked only once.
If you unlink a PI board's register, Kendis remembers that and does not bring it back. Linking it again by hand cancels that.
When a PI board leaves the solution, its register is removed with it. A register you linked yourself stays.
Registers you linked yourself are listed first, then the ones that came from PI boards.

Link, create and unlink registers

The header shows Linked Risk Registers as coloured chips. The first two are shown; the rest sit behind a +N chip. Click Link risk register to open the Link Risk Registers popover:

Risk Registers lists every register in your company that is not already attached to one of this solution's PI boards. Tick one to link it.
PI Boards lists this solution's PI boards that have a register (Selecting a PI links the risk register already attached to that PI board.). Each row shows which register it brings in.
Search covers both sections. Changes are applied together when you press Link N Registers (or Apply Changes when you only removed ticks). Clearing an already-linked register unlinks it.
+ Create Risk Register creates a new register and links it to this solution board.

The Link Risk Registers popover. All three ARTs bring in Retail Platform Solution Risks, which therefore carries the PI badge.

Creating a register asks for a unique Prefix (letters and digits only), a Register Name, its WorkFlow and starting Status, the Risk Matrix, an optional Risk Connection to Jira or Azure DevOps and the custom field layout.

Creating a second register, Compliance & Security Risks (prefix CMP), from the solution board.

To unlink a register, click the × on its chip and confirm, or clear its tick in the popover and press Apply Changes, which unlinks it without a further question. The register and its risks are not deleted. Its risks do lose their connection to this solution board: the board is taken out of their linked solution boards, and their links to this board's capabilities are removed.

When no register is linked at all, the page shows No risk register linked yet with two buttons, + Create Risk Register and Link Existing Risk Register.

The list view

With two or more registers the table gets a Register Name column that shows each risk's register as a coloured pill, using the same colour as the register's chip in the header. Keys keep their register prefix (RPR-1, CMP-1…), so you can also tell them apart by key.

Risks from Retail Platform Solution Risks and Compliance & Security Risks in one list, with the Register Name column.

Switch between List and Board at the top. Expand the Linked Items cell of a row to see and add the capabilities it is linked to.

RPR-1 expanded: it is linked to Unified Checkout and Payments Platform Modernisation.

Filters

Filter	What it does
Risk Level	High, Medium, Low … (the union of every linked register's matrix levels) plus Not Set.
Status	Grouped by register. Each register lists its own workflow's statuses with a risk count, because statuses follow each register's own workflow. A status with the same name in two registers is filtered separately.
Risk Register	Shown with two or more registers. Keeps only the risks of the selected registers; on the board it also hides the other registers' swimlanes.
Responsible	Any user, plus Unassigned.
More Filters	Program Board, Solution Board, Collection, the Azure DevOps Area Path / Iteration Path (only with an Azure-connected register) and the custom fields of all linked registers.

Press Update Filter to apply.

The Status filter, grouped per register with counts.

Create or edit a risk

Click + Add Risk (or the + on a register's swimlane in the board view, which preselects that register).
With several registers linked, choose the register in Select Risk Register, just above Status. The form then switches to that register's workflow, matrix, layout and fields. Title, description, mitigation, responsible, dates, links and watchers are kept; status, probability and impact reset to the new register's defaults.
Set Probability and Impact; the Risk Level follows from the register's matrix.
Describe the risk and the Mitigation Actions, set the Responsible, Raised On, Target Resolution Date and Status.
Linked Program Boards and Linked Solution Boards decide where else the risk is shown. Tick Notify Watchers to send an update on save.

Choosing the register for a new risk.

An existing risk, RPR-1, with probability, impact, mitigation and dates.

The board view: one swimlane per register

In Board view each linked register gets its own swimlane (colour dot, name and a + to add a risk to that register). The columns are the statuses of all linked registers together; statuses with the same name share a column, so registers on the same workflow line up, and a register with its own statuses adds its own columns.

A risk can only be dragged within its own register's lane, and only to a status that is part of its register's workflow.
The summary above the board counts risks per level and per status across all registers.
Use the sort button (Manual order, Severity, Target Resolution Date, Raised Date), minimise empty columns, or Present for a full-screen ROAM view.

The board view with one swimlane per register: the CMP risks sit in Open, the RPR risks are spread over the ROAM columns.

Analytics across registers

Analytics opens charts for all risks of the linked registers. The filters of the list are not carried over; Analytics has its own filter bar. With several registers a Risk registers panel lets you pick which ones to include (all are selected at first; at least one always stays selected). Every chart is built per register and then combined:

Chart	How registers are combined
Risk Matrix	One probability × impact grid per matrix shape. Registers with the same matrix share a grid; a different matrix gets its own grid, captioned with the register names.
Risk Level	Counts summed by level name.
Risks By Status	Each register's statuses are listed as they are, so registers with different workflows each show their own slices and bars.
Selected risk levels risks by responsible / Responsible wise risk levels	Counts summed per person.

Lists you open from a chart add a Register Name column when they span more than one register.

Analytics with both registers selected (2 of 2).

Risk Level and Risks By Status across the two registers.

Link risks to capabilities

From a risk's Linked Items (or Link a new item on an expanded row) choose the solution board, tick the capabilities the risk affects and Save. The risk then appears on the Risks tab of each capability popup.

Linking RPR-1 to capabilities of the solution.

The Risks (ROAM) tab

ROAM stands for Resolved, Owned, Accepted, Mitigated. The Risks (ROAM) tab of the analytics area is a compact read-only register: ROAM state, key, level, register, owner, the ARTs affected and raised → target dates, with chips to filter by status. See Analytics: Risks (ROAM) for the details.

The Risks (ROAM) tab.

Frequently asked questions

Why did a register appear on my solution board that I never linked?

It belongs to one of the solution's PI boards. Every linked PI board brings its register in automatically. Unlink it with the × on its chip if you don't want it; Kendis will not add it again.

Can a PI board have more than one register?

No. A PI board has one register; only solution boards can combine several.

Why don't I see the Register Name column or the Risk Register filter?

They appear only when two or more registers are linked to the solution board.

Why can't I drag a risk into another swimlane?

Each swimlane is a register. A risk belongs to its register and can only move between that register's statuses.

Two registers use different workflows. How is that shown?

Each keeps its own statuses: the status filter is grouped per register, the board adds a column for each distinct status name, and the Risks By Status chart shows every register's statuses separately.

Does unlinking a register delete its risks?

No. Only the link to this solution board is removed.

Can one risk sit on several solution boards?

Yes, add every board under Linked Solution Boards on the risk.

Risks and risk registers