Trust

An AI wrote my course. Who is responsible?

A person at your company. By design, and without exception.

Book a live build

Everyone in this market ships drafts.

Draft courses. Preliminary content. A co-author. An efficiency booster. That wording is doing a job: it moves responsibility for the output onto you, quietly, in the marketing copy.

We say it plainly instead. The output is yours. A named person on your side approves it. The system is built so that approval cannot be skipped on the way to a learner.

Draft coursesPreliminary contentA co-authorAn efficiency booster

Ours: The output is yours, and a named person approves it.

You will never have to defend training nobody read.

Every section is scoped by a person before it is built, and approved by a person after. When a regulator asks who signed off on module four, you have a name and a date.

  • 01
    You review a proposal, never a finished factNothing the system generates counts as correct until someone on your team says it is.
  • 02
    Checked by the product, decided by a personAn internal reviewer checks every screen against your sources and pins what it finds. A person on your team decides what ships, findings and all. The decision is theirs, and it is recorded.
  • 03
    Nothing deploys automaticallyThere is no path from generated to in front of a learner that skips a person.
  • 04
    You can show who approved whatAn approval is attached to the person who gave it, with the date.
A reviewer approving a course screen by screen in Re-skillEnlarge

The review panel. The product pins what it finds to the screen it refers to. A person decides, and the approval carries their name and the date.

We would rather be generic than confidently wrong.

Generating without knowledge of your organisation produces generic but correct output. Generating against low-confidence assumptions produces confidently wrong output. So we only use what we are confident about. Everything else is shown to you as a suggestion to confirm or override, never silently baked into what a learner sees.

Example

Suggestion. Not yet true.

"Your field staff are called technicians, not engineers."

ConfirmEditRemove

Confirmed. Used in every course.

"Field staff are technicians. Escalations go to the O&M lead."

Confirmed by a named person on your team, with the date.

What we do not do

We do not set your targetsTraining is built to the objectives you give us. We never invent them for you.
We do not write to your systemsConnections to your sources are read-only. Nothing we generate is written back.
We do not replace your LMSWe export SCORM and xAPI into the system you already own. Keep it.
We do not claim causationReporting is honest about what it can and cannot attribute to training.

Bring one policy document. We will show you who signs off on what.

Thirty minutes, your material, your language, into the LMS you already run. You leave with a module your reviewers can approve, and a name against every screen.

Thirty minutes, your material, your language, a module your reviewers can approve.

Book a live build