System Manual

The Modules

Kanso is made of modules that each own a part of the quality system, but they share one data model — so a record created in one place naturally connects to the others.

The Core Workhorses

These are the modules most people open every day. They cover the controlled documents, the improvement work, and the analysis that turns records into insight.

DocumentsControlled document management — the procedures, work instructions, and records that make up the quality system.
ProjectsDMAIC improvement projects, each carrying its own per-project toolkit of Lean Six Sigma tools.
AnalyticsDatasets and dashboards, with SQL, Python, and R, a Data Lab for exploration, and a wide range of chart types.

Documents holds the version-controlled heart of the system. Projects is where improvement happens, with the right tools attached to each effort instead of scattered across the navigation. Analytics is the engine that reads across all of it.

Compliance and Risk

These modules keep the system honest against ISO 9001 and against the risks the organization is carrying.

  • Registers — configurable registers including a risk register and an incidents register, for logging and tracking what needs watching.
  • Audits & Clause Evidence — audit management and per-clause evidence, so the system's readiness against ISO 9001 clauses is visible and defensible.
  • Process Atlas & Process Maps — an auto-generated inventory of your processes alongside editable maps you can shape and keep current.

Intelligence and Guidance

Beyond the records, Kanso helps people learn the system and catches problems before they drift too far.

WatchtowerA monitoring agent that watches records and flags issues that need attention.
Training & GuidesIn-app guided walkthroughs and learning, tied to competency records.
Kanso UniversityIn-app product learning that helps people get fluent with the platform.
AI copilotWorkspace-grounded assistance for drafting, explaining, and analysis across modules.

Connectors and Notifications

Two modules keep Kanso in touch with the rest of the business and with the people using it.

  • Connectors — integrations with Microsoft Dynamics 365 Business Central and Dynamics, to bring operational data into the platform.
  • Notifications — the inbox and alerts that tell people when something needs their attention: an approval to give, a review coming due, a flag raised.

Why One Data Model Matters

The modules are not separate apps that happen to share a login. They share one data model, so records connect instead of sitting in isolation. That connectivity is where much of Kanso's value comes from.

  • An incident logged in Registers can become a controlled report in Documents.
  • A gap surfaced during an audit can become an audit finding tied to its clause.
  • A dataset built in Analytics can feed a dashboard that leadership reads live.
Tip:Because everything is linked, you rarely re-enter the same information twice. A record follows the thread from where it started to wherever it needs to go next.

◳ Screenshot

Kanso's modules arranged around a shared data model, with records flowing between compliance, improvement, and analytics.