1. Module Overview
26
API Endpoints
5
Proficiency Levels per Skill
Gap
Career Path Gap Analysis
Auto
Profiles from Appraisal Data

The Competency Management module (CMGM) gives organisations a structured, data-driven way to define what skills employees need, measure how they compare against those expectations, identify gaps, and plan meaningful development actions. It answers three fundamental talent questions at scale: What skills do we need? What skills do we have? and How do we close the gap?

Unlike standalone assessment tools that require managers to separately evaluate employees on skills, CMGM in GoodBooks is tightly integrated with the Performance Management module (PERM). When an appraisal cycle is finalised, CMGM automatically converts KRA evaluation scores into competency profiles using configurable mappings. Managers assess performance once — CMGM derives the skills picture automatically. This eliminates duplicate effort and ensures that competency data reflects real performance evidence rather than an extra round of subjective rating.

The module supports the full talent lifecycle: HR administrators build the skill catalog and behavioural anchor library, configure competency frameworks by job family, and map KRAs to skills. Employees view their own profiles, run self-assessments, and track career path readiness. Managers work with team gap matrices and drive development planning. Executives see organisation-wide heat maps, succession readiness by role, and capability trends across appraisal cycles.

Key Differentiator: CMGM bridges performance appraisal results into a concrete skills development view. One evaluation cycle — conducted through PERM — simultaneously updates performance scores and refreshes the entire competency profile layer. There is no separate competency assessment process to run.

Capabilities Matrix

Feature HR Admin Manager Employee Executive
Build & maintain skill catalog✔———
Write behavioural anchors✔———
Configure KRA → Skill mappings✔———
Create & manage competency frameworks✔———
Configure career paths✔———
Trigger / regenerate competency profiles✔———
View team competency matrix✔✔——
Create development plans for direct reports✔✔——
View own competency profile✔✔✔—
Run self-assessment——✔—
View own career path & gap——✔—
Create own development plan——✔—
Org-wide heat map & skill coverage✔——✔
Succession readiness by role✔——✔
Capability trend across cycles✔——✔
Generate org-wide gap report✔——✔
2. Stakeholder Roles

CMGM serves four distinct groups of users, each with a different lens on competency data. Understanding which role applies to you determines which screens you will use and which decisions you are accountable for.

🛠️ HR Administrator

  • Builds and maintains the skill catalog and behavioural anchor library
  • Maps KRAs to skills for each competency framework
  • Configures career paths for key job families
  • Triggers profile generation after appraisal cycles close
  • Generates org-wide gap reports for leadership review
  • Surfaces training needs from Critical and High gap patterns
  • Governs framework versions as business evolves

👔 Manager

  • Reviews competency profiles for all direct reports
  • Works with the team gap matrix to prioritise development
  • Creates and monitors skill development plans for each reportee
  • Uses gap analysis in context of appraisal conversations
  • Conducts periodic 1:1 dev plan progress reviews
  • Views career path readiness for succession discussions

🙋 Employee

  • Views their own competency profile (appraisal-derived)
  • Runs a self-assessment to record their own perspective
  • Sees the three-column gap view: Required, Derived, Self-Assessed
  • Tracks progress against chosen career path
  • Creates and updates personal skill development plans
  • Views available learning methods linked to each gap

📈 Executive

  • Views the org-wide competency heat map by department
  • Identifies skill clusters at risk (Critical gaps ≥ 30%)
  • Reviews succession readiness for key roles
  • Monitors workforce capability trends across appraisal cycles
  • Uses data to guide L&D investment and hiring priorities
3. Core Concepts

Before configuring or using CMGM, it helps to understand the terminology used throughout the module. The table below provides a plain-English definition for every key term, with a concrete example from a typical deployment.

TermPlain English DefinitionExample
Competency Framework
MCOMPETENCYFRAMEWORK
The overall structure that organises skills for a specific role family or department. A framework groups the KRA-to-skill mappings that apply to a set of employees. "Software Engineer Framework" covering 12 technical and behavioural skills; "Sales Representative Framework" covering 8 skills focused on communication and pipeline management.
Skill
MSKILL
A discrete, assessable capability — defined by a Code, Name, Category, and a maximum of 5 proficiency levels. Skills are shared across frameworks. SK-001 "SQL Proficiency" (Technical), SK-042 "Active Listening" (Behavioural), SK-018 "Budget Management" (Functional).
Proficiency Level A 1–5 numeric scale where 1 = Novice and 5 = Expert. Every skill uses the same 5-point scale for consistency across the organisation. A Level 3 in "Presentation Skills" means the employee can independently deliver presentations without supervision. A Level 5 means they design presentation frameworks for others.
Behavioural Anchor
MCOMPETENCYANCHOR
A plain-text description of what that proficiency level looks like in practice. Anchors make ratings consistent — every assessor and employee uses the same definition. Level 3 anchor for "Active Listening": "Consistently paraphrases what was heard, asks clarifying questions, and avoids interrupting — applied independently in all client interactions."
KRA → Skill Map
MCOMPETENCYKRAMAP
A configuration record that links a Key Result Area (from PERM appraisal) to a skill, setting the expected proficiency level an employee must reach when they perform well in that KRA. KRA "Client Communication" → Skill "Presentation Skills" at Expected Level 4, Mandatory = Yes.
Competency Profile
TEMPLOYEECOMPETENCYPROFILE
An employee's current derived skill levels — computed automatically from appraisal scores by the profile generation process. One profile snapshot per appraisal cycle is retained. After the FY2025-Q4 appraisal cycle closes, Sarah's profile shows: SQL Proficiency = 3, Presentation Skills = 4, Leadership = 2.
Gap Analysis The per-skill comparison of Required Level minus Actual Level. Positive = gap (underskilled); zero = met; negative = exceeds requirement. Required Level 4 for SQL − Actual Level 2 = Gap of 2 → Critical severity.
Gap Severity A 5-tier classification (Critical / High / Medium / Met / Exceeds) that determines urgency of development action and visibility in reports. Critical = mandatory skill with gap ≥ 2. Met = actual equals required. Exceeds = actual greater than required.
Career Path
MCAREERPATH
A documented progression route from one role to another, with a typical transition time (months) and a set of skill requirements the employee must reach before being considered ready. Junior Developer → Senior Developer, TypicalMonths = 24, requires SQL Proficiency at Level 4 and Code Review at Level 3.
Skill Development Plan
TSKILLDEVPLAN
A structured action record linking an employee to a specific skill they want to develop — including current level, target level, method (training, coaching, etc.), and target completion date. Employee ID 1042 plans to raise SQL Proficiency from Level 2 to Level 4 via Online Course + On-the-Job Assignment, by 31 December 2026.
Self-Assessment An employee's own rating of their proficiency against each skill. Stored separately from the appraisal-derived profile. Creates a three-way comparison: Required vs. Manager-Derived vs. Self-Assessed. Sarah rates herself at Level 4 in "Active Listening." Her appraisal-derived profile shows Level 2. This discrepancy becomes a talking point in her 1:1 with her manager.
5. Building the Skill Catalog — HR Admin Guide

The skill catalog is the foundation of CMGM. Every other configuration — frameworks, KRA mappings, career paths, development plans — references skills from this catalog. Investing time in a clean, well-anchored skill catalog is the highest-leverage action HR can take to make CMGM effective.

ⓘ Module Boundary — SkillManagement owns Skills
Skills (MSKILL) are defined and maintained in the SkillManagement module — a separate GB5 module from CMGM. CMGM reads the skill catalog but never writes to it. If you need to create new skills, add skill groups (MSKILLGROUP), configure skill domains (MSKILLDOMAIN), or manage skill proficiency levels (MSKILLLEVEL), do so in SkillManagement first, then return to CMGM to configure frameworks, behavioral anchors, and KRA-to-skill mappings.
1
Create Skill Categories

Before creating individual skills, define the categories that will organise them. Standard categories include Technical, Functional, Behavioural, and Leadership. Categories are used for filtering in gap reports and development plan views. Keep categories broad — four to six is typical for most organisations.

2
Create Skills

For each skill, enter a short Code (e.g. SK-001), a clear Name, its Category, and set MaxLevels to 5 for consistency. The skill code appears in reports and exports — use a systematic prefix per category (e.g. TK- for Technical, BH- for Behavioural). Avoid overlapping skill names: "Communication" and "Written Communication" are distinct; do not add both unless you intend to assess them separately.

3
Write Behavioural Anchors for Every Level

For each skill, write a plain-English description of what each proficiency level looks like in observable behaviour. Each anchor is stored against a specific SkillId and Level (1 through 5). Use concrete, behavioural language — describe what someone does, not what they know.

4
Review Anchors for Cross-Skill Consistency

Once anchors are written, read across Level 3 descriptions for all skills. Level 3 should represent independent competence in every skill — the baseline a fully effective employee in the role demonstrates without guidance. Level 1 should represent someone just starting to learn; Level 5 should represent a recognisable expert or thought leader. Adjust wording until the levels feel calibrated across skills.

Behavioural anchors are the most important investment in CMGM setup. Without them, levels are subjective — one manager's "Level 3" is another manager's "Level 2." With well-written anchors, a Level 3 means the same thing to every manager, every assessor, and every employee in the organisation. Time spent here pays dividends in every appraisal cycle.

Example: Communication Skill — Behavioural Anchors

LevelLabelBehavioural Description
1 — Novice Follows instructions Communicates clearly only in familiar, scripted situations. Requires prompting and supervision to deliver messages appropriately. May struggle with audience adaptation or tone adjustment.
2 — Developing Applies with guidance Understands communication principles and applies them with coaching. Can prepare and deliver straightforward messages to familiar audiences. Occasionally needs feedback on tone, structure, or audience awareness.
3 — Competent Independent application Independently adapts communication style to audience and context. Delivers clear verbal and written messages without supervision. Manages difficult conversations professionally and escalates appropriately.
4 — Proficient Coaches others Coaches team members on communication effectiveness. Designs communication plans for complex stakeholder groups. Proactively identifies and resolves miscommunication risks before they escalate.
5 — Expert Thought leader Recognised as the communication authority within the organisation. Designs communication frameworks and standards used org-wide. Influences communication culture through example, coaching, and policy contribution.
6. KRA → Skill Mapping

The KRA-to-skill mapping is the bridge between the Performance Management module and CMGM. Each mapping record specifies: which KRA (from PERM) translates to which skill (from the CMGM catalog), at what expected proficiency level an employee should be when they perform well in that KRA, and whether the skill is mandatory for that role.

Mappings are stored in MCOMPETENCYKRAMAP and belong to a Competency Framework. When the profile generation engine runs, it reads every KRA the employee was evaluated on, looks up the matching framework mappings, converts the KRA scores to proficiency levels, and writes the employee's profile.

Example KRA → Skill Mapping Table

KRA (from PERM)Mapped SkillExpected LevelMandatoryImpact if Gap Found
Client CommunicationPresentation Skills Level 4 Yes Critical / High gap triggers immediate dev plan
Client CommunicationActive Listening Level 3 Yes Gap creates High priority development action
Technical DeliverySQL Proficiency Level 3 No Gap appears as Medium — recommended, not required
Technical DeliveryCode Review Level 3 Yes Gap creates High priority development action
Team LeadershipCoaching & Mentoring Level 4 Yes Critical gap if 2+ levels below — succession risk flag

IsMandatory: How It Affects Gap Severity

The IsMandatory flag on each mapping directly controls how gaps are classified. Mandatory skills are those the role cannot function without — the employee must demonstrate them regardless of other strengths. Optional skills are valuable but not blocking. The distinction shows up immediately in gap severity: a two-level gap on a mandatory skill is Critical (red); the same gap on an optional skill is only Medium (yellow).

Many-to-Many Relationships

One KRA can map to multiple skills — "Client Communication" maps to both Presentation Skills and Active Listening. One skill can appear in multiple KRAs — "Leadership" might be mapped from both "Team Management" and "Project Delivery" KRAs. When a skill appears in multiple KRA mappings, the profile engine takes the highest derived level from any single KRA to represent the employee's competency on that skill.

Setup tip: Start with your five most critical KRAs for each role family and map two to three skills each. This gives immediate value without overwhelming the setup process. Expand the mapping set iteratively as the organisation gains confidence with the tool.
7. Competency Framework Configuration

A Competency Framework (MCOMPETENCYFRAMEWORK) is a named grouping that brings together a set of KRA-to-skill mappings for a specific purpose. Frameworks exist so the organisation can have different competency expectations for different job families, departments, or levels — without needing to maintain separate skill catalogs.

When to Create Multiple Frameworks

Create one framework per job family or department that has meaningfully different KRA-to-skill requirements. An "Engineering Framework" emphasises technical skills; a "Sales Framework" emphasises commercial and relationship skills; a "Finance Framework" emphasises analytical and reporting skills. If all employees in your organisation share the same KRA structure and skill requirements, a single framework is sufficient to begin with.

Linking a Framework to an Appraisal Plan

Each framework is associated with one or more Appraisal Types or Plans in PERM. When an appraisal cycle runs using that plan, the system knows which framework's KRA-to-skill mappings to use when generating profiles for employees on that plan. This means engineers on the "FY2026 Engineering Appraisal Plan" automatically get their profiles generated using the Engineering Framework mappings.

Framework Lifecycle

Frameworks should be reviewed at the start of each appraisal year. When KRAs change in PERM (new KRAs added, old ones retired), update the corresponding framework mappings before the appraisal cycle opens. Framework version history is preserved — profiles generated in previous cycles retain the mappings that were active at that time, so historical gap data remains accurate.

8. Career Path Configuration (Optional but Powerful)

Career paths (MCAREERPATH) document the progression routes from one role to another within the organisation. They are optional — CMGM provides full gap analysis and development planning without them — but career paths add a powerful dimension: they let employees see exactly what skills they need to develop to reach their next role, and let HR and executives assess succession readiness objectively.

What a Career Path Contains

FieldDescriptionExample
CurrentRoleThe starting role in this progression stepJunior Developer
TargetRoleThe next role in the progressionSenior Developer
TypicalMonthsExpected time to make the transition in months24
FrameworkIdThe competency framework whose skills apply to this pathEngineering Framework
CareerPathRequirements
MCAREERPATHREQUIREMENT
Per-skill minimum level and mandatory flag for this pathSQL Proficiency MinLevel=4, IsMandatory=Yes

Creating a Career Path — Step by Step

1
Define the role pair

Identify the CurrentRole and TargetRole. Career paths can be linear (Dev → Senior Dev → Tech Lead → Engineering Manager) or lateral (Developer → Business Analyst). Create one path record per step in the progression — a four-role track requires three path records.

2
Set TypicalMonths

This is the expected transition time under normal conditions. It is informational — used to show employees how far they are from readiness by time as well as by skills. If the organisation has no firm expectation, use a range midpoint or industry benchmark.

3
Link to a Competency Framework

Associate the career path with the framework that contains the relevant skills. This determines which skill pool the requirements are drawn from.

4
Add Career Path Requirements

For each skill the target role demands, add a requirement record specifying the MinLevel the employee must reach and whether it is mandatory. These requirements become the comparison baseline for employee career readiness scoring.

Employee Career Readiness

The system calculates a percentage readiness score for each employee against each career path they have selected. The calculation compares the employee's current proficiency levels (from their latest competency profile) against the path's CareerPathRequirements. A mandatory skill not yet at MinLevel reduces readiness significantly; an optional skill gap reduces it moderately; skills already at or above MinLevel count as satisfied.

Example Scenario

Sarah is a Senior Analyst aiming to become a Data Science Manager. Her career path shows she needs SQL Proficiency at Level 4 (currently at Level 2 — a Critical gap), Statistical Modelling at Level 3 (currently at Level 3 — Met), and Leadership at Level 3 (currently at Level 2 — High gap). These two open gaps become her priority development areas, surfaced automatically in her ESS career path view and suggested as candidates for her next development plan cycle.

9. Generating Competency Profiles

Competency profile generation is the process that converts PERM appraisal scores into the skill-level data stored in TEMPLOYEECOMPETENCYPROFILE. It runs automatically when an appraisal cycle is Finalised in PERM, and can also be triggered manually by HR administrators.

What Happens During Generation

1
Read KRA Evaluation Scores

The engine reads the finalised KRA scores for every employee covered by the appraisal cycle from TAPPRAISALEVAL. Only finalised cycles are used — in-progress appraisals do not contribute to profile data.

2
Identify the Matching Framework

Using the appraisal plan associated with this cycle, the engine looks up the linked Competency Framework and retrieves all KRA-to-skill mappings (MCOMPETENCYKRAMAP) for that framework.

3
Convert Scores to Proficiency Levels

Each KRA score (on a 1–5 scale) is converted to a proficiency level using a linear mapping. The conversion is applied per mapped skill, taking the highest derived level if a skill appears in multiple KRA mappings for that employee.

4
Write the Competency Profile

One TEMPLOYEECOMPETENCYPROFILE record is written per employee per skill per cycle. The record includes the derived proficiency level, the source KRA, the appraisal cycle reference, and the generation timestamp. Existing profile records for the same cycle are updated; prior cycle records are preserved as history.

5
Calculate Gap per Skill

The engine calculates the gap (Required Level from MCOMPETENCYKRAMAP minus the derived level) for every skill in the employee's profile and determines the gap severity. These gap values are stored alongside the profile and immediately available for reporting.

Manual Trigger

HR administrators can re-trigger profile generation at any time from the CMGM Admin screen — for example, after updating KRA-to-skill mappings to apply revised expectations to an already-finalised cycle, or after correcting a data issue. Re-generation overwrites the profile records for the selected cycle but does not affect other cycles.

Profile History

Each appraisal cycle creates a distinct set of profile snapshots. Employees and managers can view how skill levels have changed across cycles — showing growth trajectory over time. Gap trends across cycles are visible in the executive capability trend view.

Important: Profile generation only runs for employees who have a completed appraisal evaluation in the cycle AND whose appraisal plan is linked to a Competency Framework. Employees evaluated under an unlinked plan will not have profiles generated — verify framework linkage before closing each appraisal cycle.
10. Understanding the Gap Analysis

The gap analysis view is the primary operational output of CMGM. It translates the raw proficiency data into an actionable picture — who has which skill gaps, how severe they are, and where to focus development energy. Understanding how to read and act on this view is the core skill for both HR administrators and managers.

Gap Severity Guide

SeverityConditionColourRecommended Action
Critical Mandatory skill, gap ≥ 2 levels (Actual is 2 or more below Required) Red Immediate development plan. Consider temporary support or supervision adjustment. Flag in succession review.
High Mandatory skill, gap = 1 level Orange Development plan this cycle. Include in next 1:1 discussion. Set a target completion date.
Medium Optional skill, gap ≥ 1 level Yellow Recommended development plan. Good candidate for self-directed learning or mentoring.
Met Actual level equals Required level Green No immediate action. Acknowledge in performance conversation. Maintain through practice.
Exceeds Actual level is above Required level Blue Recognise the strength. Consider stretch assignments, internal mentorship, or accelerated career path progression.

How to Read the Gap Matrix

The gap matrix presents rows (employees or the current employee) against columns (skills). Each cell shows the gap severity using the colour coding above. Reading across a row shows one employee's overall competency health. Reading down a column shows how a specific skill is distributed across the team or organisation.

Team Gap View (Manager)

A manager's team gap matrix shows all direct reports on the left axis and all skills from the active framework across the top. Critical cells (red) demand immediate attention. A column that is mostly red indicates a systemic gap — the team lacks a skill broadly, which may indicate a need for group training rather than individual development plans.

Org Heat Map (Executive)

The executive heat map aggregates gap severity by department and skill. A red cell at the intersection of "Engineering" and "Code Review" means that a significant proportion of the Engineering department has a Critical or High gap in Code Review. This view guides L&D budget prioritisation and identifies potential organisational risk areas.

Available Filters

Both team and org views support filtering by gap severity (show only Critical, show Critical and High), by skill category (show only Technical skills), by competency framework, and by department or team. Use severity filters when conducting triage; use category filters when planning a specific L&D initiative (e.g. "all Behavioural skill gaps across the sales team").

11. Skill Development Plans

A Skill Development Plan (TSKILLDEVPLAN) is the action layer of CMGM — it turns the gap identification into a concrete commitment with an owner, a method, and a deadline. Development plans can be created by employees for themselves or by managers for their direct reports. Both views are available from the CMGM and ESS screens respectively.

Creating a Development Plan

FieldDescription
EmployeeThe employee this plan is for. Pre-filled when created from the employee's own profile.
SkillThe specific skill from the catalog being developed. Selected from the gap view or manually chosen.
Current LevelAuto-populated from the employee's latest competency profile. Can be manually adjusted if needed.
Target LevelThe level the employee should reach by the completion date. Should match or exceed the Required Level for the skill.
PriorityHigh / Medium / Low — drives sort order in the manager's dev plan dashboard.
Development MethodHow the employee will build this skill (see methods below).
Target Completion DateThe date by which the target level should be achieved.
NotesFree-text field for additional context, resources, or agreed actions from a 1:1 discussion.

Development Methods

Classroom Training

Instructor-led programme, internal or external

Online Course

Self-paced digital learning platform

Coaching

One-on-one sessions with an internal or external coach

Mentoring

Structured relationship with a senior practitioner

Self-Study

Books, articles, and self-directed research

On-the-Job Assignment

Deliberate task assignment to practise the skill

Stretch Project

Voluntary project beyond current role scope

Integration with L&D and Gap Auto-Suggest

When a Critical or High gap is detected during profile generation, the system can automatically surface a suggestion to create a development plan for that skill. Employees see this as a prompt in their ESS dashboard; managers see it as a pending action in their team view. Clicking through pre-populates the plan form with the skill, current level, and required target level already filled in.

If your organisation uses a Training Management module, development plans can be linked to specific training programmes. When the linked training is completed, the completion date and outcome can flow back to update the plan status automatically.

Progress Tracking

Each development plan progresses through status stages: Draft → In Progress → Completed or Cancelled. Managers and employees review plan status together during periodic 1:1 meetings. The manager's team dev plan dashboard shows a summary count of plans by status per employee, making it easy to spot who is on track and who may need additional support.

12. Employee Self-Assessment (ESS)

The self-assessment feature lets employees record their own view of their proficiency against each skill in their competency framework. It is an entirely separate data set from the appraisal-derived profile — the two are stored independently and shown side by side, not averaged together. This distinction is deliberate and important.

Why Self-Assessment Matters

The most valuable insight from self-assessment is not the number itself — it is the gap between what the employee believes and what the appraisal evidence shows. When an employee rates themselves at Level 4 on "Stakeholder Management" and their appraisal-derived profile shows Level 2, that discrepancy becomes a powerful, specific topic for a development conversation. It opens the door to understanding: does the employee have blind spots? Did the KRA scores unfairly represent their stakeholder work? Was the appraisal calibration off? These conversations are far more productive than generic performance feedback.

How to Complete a Self-Assessment

1
Navigate to ESS My Competency Profile

In the Employee Self-Service portal, open the "My Competency Profile" section and activate the "Self-Rate" toggle. The skill list for your current framework is displayed with behavioural anchor descriptions visible for each level.

2
Read Behavioural Anchors Before Rating

Before selecting a level, read the anchor description for each level of that skill. Find the level whose description most accurately reflects your day-to-day behaviour — not where you aspire to be, but where you genuinely are today. Honest self-rating produces better development conversations than aspirational rating.

3
Rate Each Skill and Submit

Set a level for each skill in the list. All skills must be rated before submitting. Once submitted, the self-assessment is saved and visible to you and your direct manager.

The Three-Column View

Once both the appraisal-derived profile and a self-assessment exist, the gap view shows three columns for each skill:

ColumnData SourceMeaning
Required Level MCOMPETENCYKRAMAP — set by HR when configuring the framework What the role demands — fixed by the framework configuration
Manager-Derived Level TEMPLOYEECOMPETENCYPROFILE — auto-generated from appraisal What the appraisal evidence says about the employee's proficiency
Self-Assessed Level Self-assessment input by employee via ESS What the employee believes their proficiency to be
Privacy: Self-assessment data is visible to the employee and their direct manager only. It does not appear in org-wide gap reports or executive heat maps, which are based exclusively on appraisal-derived profiles. Employees can self-assess without concern that their candid self-ratings will be aggregated into org-level metrics.
13. Team & Org Views for Managers and Executives

Manager View — Team Competency Matrix

The manager's primary view in CMGM is the Team Competency Matrix. This screen places all direct reports on the vertical axis and all skills from the active competency framework on the horizontal axis. Each cell displays the gap severity for that employee-skill combination using the five-tier colour code (Critical / High / Medium / Met / Exceeds).

Reading the Matrix Strategically

Scan rows first — an employee with a mostly-red row has broad, deep skill gaps and likely needs a structured development conversation and a comprehensive plan. Scan columns next — a skill column that is predominantly red or orange across many employees indicates a team-level gap, which is better addressed by a group training initiative than individual plans. The matrix makes both patterns visible at once.

The Team Competency Matrix also shows development plan status for each employee-skill combination — a small icon indicates whether a plan is Pending, In Progress, or Completed for that gap. This lets managers quickly identify which Critical gaps have no plan yet (highest risk).

Available Filters for Managers

Filter the matrix by skill category to focus on a single domain (e.g. see only Behavioural skills), by gap severity to see only actionable items, or by competency framework if an employee is covered by multiple frameworks. Filters persist within the session for efficient review.

Executive View — Org Heat Map and Succession Readiness

Organisation-Wide Heat Map

The executive heat map aggregates gap severity by department (or cost centre / organisational unit, depending on HR configuration) and by skill. Each cell shows the percentage of employees in that department-skill intersection who have a Critical or High gap. Cells with high percentages appear in deeper red; cells with low or no gaps appear in green. This instantly shows which departments have significant capability risks and which skills are most broadly lacking across the organisation.

Succession Readiness by Role

For each key role that has a career path configured, the succession readiness report shows how many employees with that role as their target path are at three readiness states: Ready (all mandatory CareerPathRequirements met), Gap (one to two mandatory skills below MinLevel), and Not Ready (three or more mandatory skills below MinLevel). Executives can drill into each readiness group to see the specific employees and their outstanding requirements.

Capability Trend

The capability trend view shows the average proficiency level per skill across the organisation, plotted across successive appraisal cycles. A rising trend in a skill indicates that development investment is working. A flat or declining trend despite development plans suggests the plans are not effective and warrants review. This view is most useful after at least three appraisal cycles of data have been accumulated.

Critical Skill Risk Indicator

CMGM flags any skill where 30% or more of the assessed employee population has a Critical or High gap. These skills appear in a dedicated "Critical Skill Risk" list in the executive dashboard, ordered by percentage of employees at risk. This view is specifically designed to surface systemic capability risks that require strategic response — such as a new hiring initiative, an external training programme, or a framework adjustment that re-classifies the skill as optional.

14. Integration Map

CMGM is not a standalone module. It sits at the intersection of several GoodBooks modules and derives maximum value when connected to them. The integrations below are either automatic (happen without configuration once both modules are active) or configured (require a one-time linkage setup by HR).

⚠ Clarification — "Competency" means different things in different modules
Two separate "Competency" concepts exist in GB5, with different ownership and purpose:
ConceptTableOwner ModuleMeaning
TMS CompetencyMCOMPETENCYTMS (Training Mgmt)A training-level competency: what a learning programme develops. Has Type (Functional/Behavioural/Technical) and MaxLevelNo. Used in MPROGCOMPETENCYMAP to tag programmes with the competencies they build.
CMGM SkillMSKILLSkillManagementA granular, assessable work capability with a structured 1–5 proficiency scale (MSKILLLEVEL) and behavioural anchors (MCOMPETENCYANCHOR). This is the unit CMGM measures employees against.
CMGM FrameworkMCOMPETENCYFRAMEWORKCMGMAn organizational structure grouping KRA→Skill mappings for a role family. Not a competency itself — it is a container that defines which skills matter for a given job family and at what level.

Future integration: When a CMGM gap identifies SkillId=X as Critical, the intended flow searches TMS for programmes where MPROGCOMPETENCYMAP is tagged to the same skill — surfacing relevant training options automatically. This cross-module linkage is planned but not yet implemented.

📊
PERM

Appraisal KRA scores automatically generate competency profiles when an appraisal cycle is Finalised. This is the primary data source for all competency profiles. No additional configuration required once the framework is linked to an appraisal plan.

🎓
L&D / Training Management

Critical and High gaps can auto-trigger training need records in the Training Management module. When a training programme is completed, the outcome flows back to update the development plan status and — on the next profile generation — refreshes the competency level if the KRA score improves.

💬
FBCK (Feedback)

360-degree feedback signals collected through the FBCK module can surface alongside competency gap data to inform development plan recommendations. Feedback patterns around a specific skill corroborate or challenge the appraisal-derived proficiency level.

🖥️
ESS Portal

Employees access their competency profile, self-assessment form, development plan list, and career path readiness view from the ESS portal's "My Development" section. All CMGM employee-facing features are surfaced through ESS without requiring access to the HR admin module.

🛤️
Career Path Module

Gap-to-path analysis for succession planning and individual career development. Employees select a target role, the system calculates readiness against CareerPathRequirements, and surfaces the specific skills to develop. HR and executives see succession readiness aggregated across the organisation.

15. Implementation Checklist

Use this checklist to track progress through the CMGM setup and go-live process. Items are ordered for a first-time implementation starting from a clean state. Items marked Optional can be deferred to a later phase without blocking core gap analysis functionality.

ItemOwnerNotes
Skill categories definedHR Admin Typically 4–6 categories: Technical, Functional, Behavioural, Leadership. Agree with business before creating.
Core skill catalog created (start with 10–20 critical skills)HR Admin Do not try to catalog every skill at once. Start with the skills most relevant to your highest-priority job families.
Behavioural anchors written for each skill (all 5 levels)HR Admin + Subject Matter Experts Involve department heads for technical skills. HR writes first drafts; SMEs validate. Budget 30–45 min per skill.
Competency Framework(s) createdHR Admin One framework per distinct job family. Link each framework to the corresponding Appraisal Plan in PERM.
KRA → Skill mappings configured (minimum: top 5 KRAs per framework)HR Admin Start with mandatory skills only. Mark IsMandatory appropriately — this directly drives Critical/High gap classification.
At least one Appraisal Cycle completed in PERMHR Admin / PERM Admin Profile generation requires finalised appraisal data. Coordinate CMGM setup with the PERM cycle calendar.
Profile generation triggered and reviewed for sample employeesHR Admin Run generation, then spot-check 5–10 employee profiles against expected results. Verify level conversions look correct.
Gap analysis reviewed with HR leadershipHR Admin + CHRO Present the initial gap heat map to leadership before rolling out to managers. Align on messaging around Critical gaps.
Career paths configured for key job families OptionalHR Admin + Talent Team Prioritise the 3–5 job families where succession planning is most critical. Can be added incrementally after initial rollout.
Manager training on gap analysis and development plan creationHR / L&D 90-minute session recommended. Cover: how to read the matrix, gap severity definitions, how to create a dev plan, and the 1:1 review cycle.
Employee orientation on self-assessment and career path viewHR / L&D 30-minute session or written guide. Explain the purpose of self-assessment, how behavioural anchors work, and where to find career path readiness.
16. Frequently Asked Questions
1. Do we need to separately assess employees' skills — or does CMGM use appraisal data?
No separate skills assessment is needed. CMGM derives competency profiles automatically from the KRA evaluation scores in each PERM appraisal cycle. When an appraisal cycle is Finalised, the profile generation engine reads each employee's KRA scores, applies the KRA-to-skill mappings configured for their framework, and produces an updated competency profile. Managers evaluate performance once — CMGM converts that evaluation into skill-level data automatically. The only prerequisite is that HR has configured the KRA-to-skill mappings before the appraisal cycle closes.
2. Can skill levels be manually overridden outside of an appraisal cycle?
Yes, HR administrators can manually set or adjust a proficiency level for a specific employee-skill combination from the Competency Profile admin screen. Manual overrides are recorded with a timestamp and the override reason, and are visually distinguished from appraisal-derived levels in reports. This mechanism is intended for edge cases — for example, when an employee earned a professional certification that demonstrates Level 5 proficiency but no relevant KRA was evaluated in the current cycle. Routine use of manual overrides undermines the integrity of the automated process and should be governed by a formal exception policy.
3. What happens if a KRA doesn't map to any skill in the framework?
KRAs without skill mappings are evaluated and scored in PERM as normal — the appraisal process is unaffected. However, those KRA scores are not used in competency profile generation. The employee still gets a performance score for the unmapped KRA, but it does not contribute to their competency profile. This is a valid design choice for KRAs that measure outcomes (e.g. "Revenue Target Achievement") rather than skills. If you want a KRA to contribute to competency data, add at least one KRA-to-skill mapping for it in the active framework.
4. How often should behavioural anchors be reviewed?
Behavioural anchors should be reviewed annually at minimum — ideally at the start of each appraisal year before the cycle opens. Reviews should check whether the language still accurately reflects what the organisation expects at each level, particularly if the role has evolved, new technology has been adopted, or business priorities have shifted. Anchors for rapidly changing technical skills (e.g. a skill in a technology that has undergone a major update) may need more frequent review. Avoid changing anchors mid-cycle, as this creates inconsistency in how assessors use them during an active appraisal.
5. Can an employee have multiple career paths?
Yes. An employee can select multiple target roles from the available career paths in their ESS profile. The system will show a readiness score and gap breakdown for each selected path separately. This is useful when an employee is genuinely uncertain about their direction — seeing the gap profiles side by side helps them understand which path they are closer to achieving and may influence their development plan priorities. In practice, most employees focus on one active path at a time and use the multi-path view for exploration.
6. What is the difference between CMGM and the L&D Skill Management module?
CMGM (Competency Management) focuses on defining skill expectations by role, measuring employees against those expectations through appraisal-derived profiles, identifying gaps, and planning individual development. The L&D / Training Management module focuses on the catalogue of training programmes, scheduling, attendance tracking, and certification management. The two modules are complementary: CMGM identifies which skills each employee needs to develop (the demand side); L&D provides the mechanisms to develop them (the supply side). A Critical gap in CMGM can trigger a training need in L&D, and completion of a training programme in L&D can be linked to a development plan in CMGM.
7. Can we generate profiles before an appraisal cycle is complete?
No. The profile generation engine only processes Finalised appraisal cycles. An in-progress or submitted (but not finalised) cycle does not contribute to profile data. This is intentional — using partial evaluation data would produce misleading competency profiles. The recommended approach is to coordinate the CMGM profile generation trigger with the PERM cycle calendar so that profiles are refreshed promptly after each cycle closes.
8. What if a new skill is added mid-year — does it affect existing profiles?
Adding a new skill to the catalog and adding KRA-to-skill mapping records for it does not automatically update existing competency profiles. The new mappings take effect the next time profiles are generated — which requires a finalised appraisal cycle with KRA data that covers the newly mapped KRA. Existing profile records for prior cycles are unchanged. If you need to apply a new skill's required level to gap reporting immediately (before the next cycle), HR can use the manual override mechanism to set initial proficiency levels for the new skill across the affected employee population while awaiting the next natural generation event.
9. How do we handle employees whose role has no configured career path?
An employee whose role has no career path in CMGM still gets a full competency profile and gap analysis — the career path view simply shows "No career path configured for your current role." HR can add career paths incrementally without affecting the core competency and gap analysis features. For employees in roles without a path, the development planning process is still fully available — managers and employees create dev plans based on the current-role gap analysis rather than a career path target. The career path readiness view is an enhancement; the core loop of profile → gap → dev plan works independently.
10. Can employees see the full gap matrix across all colleagues?
No. Employees can only see their own competency profile and gap data. They cannot see the profiles of their colleagues, peers, or even their manager. The team gap matrix is visible to managers for their direct reports only, and the org heat map is visible to HR administrators and executives. This ensures that competency data — which is derived from performance evaluation scores — remains appropriately confidential and is only visible to those with a legitimate management or organisational oversight need. Self-assessment data is additionally restricted to the employee and their direct manager only.