Skip to main content
Kalonesis
Request a demo

Kalonesis for HR and L&D

Evidence of development, instead of a record of attendance

You are asked every year what the training budget produced, and the honest answer is that nobody knows. Completion rates say who sat through something. They do not say who can now do the thing.

01

The problem

Development is measured with the artefacts that are easy to collect: enrolments, completions, hours, satisfaction scores. The moments where people actually learn — the interview, the meeting, the tutoring session, the week after the course — produce nothing at all. So the record of a workforce’s capability is assembled from self-assessment and memory, and everyone involved knows it.

02

What changes

  • A development record that begins at the selection interview, not at the first enrolment
  • Evidence of what someone demonstrated, in the moment they demonstrated it
  • Gaps that surface in the week they appear rather than at the annual review
  • A basis for judging whether a programme was worth repeating
  • An answer for the works council, ready before the question
03

What you would use

Capture unit

Present in the declared moments

Interviews, meetings, tutoring, seminars — the list your organisation declares, and nothing outside it.

Cloud platform

Moments turned into evidence

What was demonstrated, what was difficult, what changed since last time — each with a confidence value and a pointer back to the moment.

Learning Twin

A record that keeps itself current

Knowledge, objectives, context and trajectory per person, from the selection interview onwards, updated without anyone entering anything.

Recording controls

The part your works council reads

Notice, consent, retention, permissions and an audit trail — plus a clear statement of what the employer must complete before any of it runs.

04

What it looks like in a week

Nothing here adds a meeting or a form.

  • A new joiner’s record starts at their selection interview instead of their first course
  • A tutor sees what the previous sessions changed before the next one begins
  • A manager is shown a gap against the requirements of the role, with the evidence attached
  • A seminar is evaluated on what participants could do a week later
  • A person asks what is held about them, and is shown it
Required human stepDiagram of a governed path, left to right: Moment → Capture → Evidence → Review → Step → Outcome. The review step is marked as a required human step: nothing derived from a captured moment reaches a decision about a person without someone who can see the evidence and disagree with it. A band above indicates that the whole path operates within the policy, permissions and retention the organisation sets.Policy, permissions and retentionMomentDeclaredCaptureThe unitEvidenceWith confidenceReviewA personStepProposedOutcomeRecordedRequired human step
05

Built to survive the works council meeting

Recording people at work is regulated, and in Italy any tool from which remote monitoring could arise — software included — requires a union agreement or authorisation from the labour inspectorate before it is switched on. That obligation is the employer’s and we do not pretend otherwise. What we provide is the thing that makes the conversation possible: a declared list of moments, notice to everyone present, retention you set, permissions you control, and a full public statement of what is recorded and what never is.

06

Alongside your existing stack

The record is designed to be read by the learning platform, HR system, identity provider and collaboration tools you already run. Kalonesis produces the evidence they cannot; it does not ask you to migrate anything.

The other solutions

Start with one role family and one moment

A defined population, one declared moment, and a question you actually want answered is the fastest way to find out whether this works for you.