KnowGauge
Assessment studio
Public beta soon
Grounded in your sources

Build reliable multiple-choice tests from your own documents

KnowGauge turns an organisation’s own documents into multiple-choice assessments. It is AI-powered, but deliberately bounded: every question, answer and explanation is derived from the documentation you provide, every wrong answer is verified, and a reviewer approves the test before anyone takes it.

Retrieve passages Write questions Verify answers You review
The public beta opens soon

How it works

From a folder of documents to a published test in five steps.

01

Organise and upload

Arrange your material in a topic tree and upload the PDFs that define what people should know.

02

Index

Documents are split into passages and indexed, so the relevant parts can be retrieved for each test.

03

Generate

A language model writes questions, answers and explanations using only the retrieved passages.

04

Verify

A separate verification step checks every wrong answer and flags options that could also be correct.

05

Review and publish

A reviewer accepts fixes, regenerates or edits questions, then publishes the test, which freezes it.

Principles

What you can rely on in every test KnowGauge produces.

Grounded in your documentation

Questions are drawn only from the documents in your library, not from the open internet or a model’s general knowledge. Each question keeps a reference to the passages it was written from.

Verified before review

Plausible but wrong answers are the hardest part of a good test. An independent check flags ambiguous options and suggests a clearer alternative.

People stay in control

Nothing is final until a reviewer approves it. Every change is versioned with its author and reason, and published tests can no longer be altered.

Where it fits

  • Employee onboarding and policy training
  • Compliance and regulatory knowledge checks
  • Technical and product knowledge assessments
  • Certification and exam preparation

Your content stays the source of truth

The language model is used as a writing and checking tool, within the boundaries of your documentation. When your documents change, re-ingest them and generate a new test: the questions follow the material, not the other way round.