Skip to main content
Training Needs Analysis

Needs Analysis

One cycle puts what each role has completed, what the regulator requires, what people searched for, and what their managers asked for on one board. A person records one decision per need, and the next cycle opens on what was decided.

What each role must learn next, and how sure you are.

  • Needs Cycles

    Set the scope, the window, and the evidence. The board fills from day one; the pulse and manager answers land as they arrive. Between cycles, a role change or an expiring certification raises a need on its own.

  • Eight Sources, One Board

    Completions, obligations, certifications, knowledge searches, catalog requests, the learner pulse, evaluations, and manager rankings — one row per role and skill, each cell showing who spoke and how many stand behind it.

  • Decisions, Recorded

    Five verbs, one decision per need, a reason each. Salalem AI may draft a rationale; a person records the decision, and every change is kept with who made it and when.

  • The Loop Closes

    A train decision becomes a program in the learner's existing journey. The manager who asked is told what was decided. Closing the cycle freezes a report for the board and files a chapter into the audit binder.

How a cycle runs

Five stages, from scope to a report you can file

  1. Scope

    Roles or departments, the window, and which of the eight sources to read.

  2. Intake

    Managers rank their team's needs; learners answer an anonymous pulse.

  3. Review

    The board takes its final reading. A person records one decision per need.

  4. Plan

    Train decisions become programs, stamped with the need they came from.

  5. Close

    A frozen report — PDF, spreadsheet, and a chapter in the audit binder.

The evidence

Eight sources the platform already holds

Nothing is entered for the analysis. Each source is a record the platform already keeps, read for one figure. None is a rating; none names a learner.

  1. 38%

    Requirement fulfilment

    Of the role's requirement met by a completed, passed activity.

  2. 61 days

    Compliance obligations

    Until the regulator's deadline. Inside ninety, with unmet training, it is always P1.

  3. 7

    Expiring certifications

    Certificates in the role lapsing inside the window.

  4. 12

    Knowledge searches

    Questions the role asked the knowledge base and found no answer to.

  5. 23

    Catalog requests

    People who asked for a course they could not enrol in.

  6. 31 of 48

    The learner pulse

    Answered anonymously. Shown per role only above the response floor.

  7. 2.9 / 5

    Course evaluations

    How far a completed course applied to the role, in aggregate.

  8. #1

    Manager and sponsor intake

    Where managers ranked it for their team — one signal of six, not the answer.

The board

What a priority is made of, and what it never is

One role, three needs, as the review screen shows them. The second row is the case the analysis exists to catch: requirements nearly all met, demand still high, and a decision that hands it to someone outside L&D.

  • A priority is arithmetic you can read

    Six signals, fixed weights, one rule above them: an obligation due inside ninety days with unmet training is P1. Every signal is one tap away with its source and headcount.

  • When the sources disagree, the board says so

    Ninety-two percent complete and forty-one people still asking is flagged, never blended into a middling score. It usually means a process or a tool is wearing a training request.

  • Nothing here rates a person

    Every figure is a completion, an obligation, a demand signal, or a count of people. The one proficiency figure it can show is your own HR system's rating, read-only and labelled as yours.

The five decisions — one per need, each with a reason

  • Train
  • Already covered
  • Defer
  • Knowledge fix
  • Not a training problem

Needs cycle

Retail banking, third quarter

In review · 6 roles
Role

Relationship manager48 people

  • Customer due diligence

    P1
    Requirements met
    38%
    Obligation due in
    61 days
    Asked for it
    23
    Sources agreeDecision Train

  • Complaint handling

    P2
    Requirements met
    92%
    Obligation due in
    None
    Asked for it
    41
    Sources disagreeDecision Not a training problem

  • Digital onboarding tools

    P3
    Requirements met
    64%
    Obligation due in
    None
    Asked for it
    9
    Sources agreeDecision Awaiting decision
Every figure is a completion, an obligation, or a count of people. No one was rated.

Bring One Requirement. Leave With Its Record.

Give us an hour and one real requirement — from your rulebook or from a role profile. You will see how it maps to people, deadlines, and evidence on Salalem.

Get a Demo
Get a Demo