User Manual

Registers & Incidents

Kanso's registers share one consistent interface, so a risk register and an incidents register feel the same. Raise an incident, score it on unambiguous scales, and turn it into a controlled document in a click.

Configuration-driven registers

Kanso's registers are configuration-driven. A risk register, an incidents register, and similar ISO registers are all defined from configuration and share one consistent interface, so learning one register means you already know how to use the others. The columns and fields differ by purpose, but the way you add, edit, and read entries stays the same everywhere.

◳ Screenshot

A configuration-driven register — the same interface serves risk, incidents, and other ISO registers.

Labeled 1–5 scales

Registers use labeled scales rather than bare numbers. Each level from 1 to 5 carries a meaning, so severity and likelihood are unambiguous — everyone reading the register knows what a given score represents instead of guessing what "a 4" means.

Scale range	Each field uses a 1–5 scale
Labeled levels	Every level has a written meaning
Typical use	Severity and likelihood on risks and incidents

Tip:Because each level is labeled, two people scoring the same incident are far more likely to land on the same number — that consistency is what makes the register trustworthy over time.

Raise an incident

When something goes wrong, you record it in the incidents register. Scoring it on the labeled severity and likelihood scales places it clearly, and from there Kanso can carry it into the controlled-document process.

•
Add the incident
Create an entry in the incidents register and describe what happened.
•
Score severity and likelihood
Use the labeled 1–5 scales so the incident's rating is unambiguous.
•
Convert to an incident report
With one click, turn the incident into a controlled incident-report document.

Turn an incident into a controlled report

One click turns an incident into a controlled incident-report document. Kanso files it under an "Incident Reports" folder, and from that point it follows the normal document approval chain — the same review and approval flow as any other controlled document. You get a proper, auditable record without stepping outside the register.

Read the incident detail view

Each incident has a detail view that puts the important context in one place, so you can understand where it sits and how it has moved.

A risk matrix that plots the incident from its severity and likelihood.
A timeline showing how the incident has progressed.
Its current status.

← PreviousDashboards & Datasets Next →Clause Evidence & Audit Readiness