Karka for organisations

Let’s scope your Karka pilot.

Tell us what your organisation needs to assign, track and prove. We’ll reply within one business day with a practical pilot recommendation — not a generic sales presentation.

Specimen recordCycle 1 · one team
Information Security 2026Mandatory course · pass mark 70% · due 31 Mar82%
Code of Conduct, v4Policy acknowledgement · append-only, cannot be edited after14 Mar
Next cycle opens automaticallyOnly for people still employed and still in scopeMar 2027
The certificate opens for an auditor with no account and nothing to ask us for.

An illustration of what one pilot cycle leaves behind — not a customer record.

Pilot enquiry

You


What you need

Workforce size

How your people already sign in.

If people are already assigned training somewhere.


The point of the pilot

The evidence someone will ask you for — an auditor, a regulator, a board.

A quarter, a month, or the audit date you are working back from.

One business day. A person, not a sequence.

How a pilot gets scoped

  1. A short fit call

    Thirty minutes on what people have to be trained on, and what evidence someone will ask you for afterwards.

  2. Pick one of everything

    One team, one mandatory course or policy, one compliance cycle. Small enough to run properly, real enough to judge.

  3. Confirm identity, reporting and security

    How your people sign in, who sees which report, and what our answers are to the questions your security review will ask.

  4. Agree what would count as a pass

    Written down before the pilot starts, so at the end there is a result rather than an argument.