System Manual
The Modules
Kanso is made of modules, each covering one part of the quality system. They share one data model, so a record created in one module can link to records in the others.
The Modules You Open Every Day
Most people spend their time in these three: controlled documents, improvement projects and analysis.
| Documents | Controlled document management: the procedures, work instructions and records that make up the quality system. |
| Projects | DMAIC improvement projects, each with its own set of Lean Six Sigma tools. |
| Analytics | Datasets and dashboards, with SQL, Python, and R, a Data Lab for exploration, and a wide range of chart types. |
Documents holds the controlled, versioned record. Projects is where improvement work is run, with the tools attached to each project. Analytics reads across both.
Compliance and Risk
These modules track the system against ISO 9001 and against the risks the organization carries.
- Registers: configurable registers, including a risk register and an incidents register.
- Audits & Clause Evidence: audit management and per-clause evidence, so you can see how ready each ISO 9001 clause is and what supports it.
- Process Atlas & Process Maps: an inventory of your processes that Kanso builds for you, and maps you can edit and keep current.
Monitoring and Guidance
Kanso also watches the records for things that are slipping, and helps people learn the system.
| Watchtower | A monitoring agent that watches records and flags issues that need attention. |
| Training & Guides | In-app guided walkthroughs and learning, tied to competency records. |
| Kanso University | The in-app manual for learning Kanso itself. |
| AI copilot | Help with drafting, explaining and analysis, based on your workspace's own records. |
Connectors and Notifications
Two modules connect Kanso to your other systems and to the people using it.
- Connectors: integrations with Microsoft Dynamics 365 Business Central and Dynamics that bring operational data into Kanso.
- Notifications: the inbox and alerts that tell people when something needs them, such as an approval to give or a review coming due.
Why One Data Model Matters
The modules share one data model, and any record can link to any other with a named relation: caused by, addresses, verifies, evidence for, mitigates, supersedes or relates to. That is how a nonconformity leads to its CAPA, and a clause to its evidence.
- An incident logged in Registers can become a controlled report in Documents.
- A gap found 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.