Skip to main content
Roles and requirements

Role Readiness

Map roles, import your organization's framework, and inspect requirements met, unmet, or not connected to learning. Use this view independently or as evidence in TNA. Your framework adds a requirements lens; it is not a prerequisite for every capability in Salalem.

See what each role requires, and what is still outstanding.

  • Org Mapping

    Your structure as Salalem reads it: departments, roles, and reporting lines. Every assignment rule and readiness view is drawn from this one map, so an org change lands everywhere at once.

  • Competencies

    Import the role and competency framework your organization owns. Salalem AI can structure your existing document into a reviewable draft; your experts correct and approve it before applying the model.

  • Connected learning

    Review program proposals against your role requirements and connected learning. Choose catalog content, prepare new content, curate a source, connect an external activity, or request content from Salalem. Your team reviews the draft before publishing.

  • Governance

    A proposal arrives as a draft with its reasoning attached. Authorized training administrators review, edit, or reject it and control publication. A direct-manager relationship alone does not grant that authority.

The readiness view

Which role requirements are met, and what remains

Readiness reads one question per role: are its requirements fulfilled? Each requirement is met by an activity someone completed and passed, so the view is drawn from evidence the platform already holds rather than from an opinion someone entered.

  • Fulfilled or not fulfilled — never a rating

    A requirement is met, unmet, or not yet connected to any activity. Salalem does not score how good someone is at a skill, and it does not turn completions into a proficiency level. The framework and its levels stay your HR system's.

  • Drawn from the same org map as everything else

    The roles here are the roles in your structure, so moving a person or renaming a department moves this view with it. No second hierarchy to maintain for reporting.

  • Unmet requirements feed ongoing needs

    With TNA, an unmet requirement connected to learning creates an ongoing need without a formal cycle. Your team reviews the evidence and chooses the response. Later completions update that same need; decisions and earlier reviews remain. An unconnected requirement stays a setup task, not a failed training result.

  • The framework arrives from your HR system

    Upload it, sync it, or have Salalem AI structure the document you already wrote — then your experts correct it. Salalem executes against a framework you own; it does not author your job architecture.

Fictional example
Requirements fulfilled78%
Relationship manager72%
Branch teller85%
Follow role evidence into Training Needs Analysis

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.

Book a demo