Performance Appraisal Module

A structured, KRA-driven appraisal engine covering the full cycle — from plan configuration to finalization, bell curve normalization, appeals, and PIP — with ESS self-service for employees at every stage.

Why Structured Appraisals Matter

When evaluations are unstructured — a single manager rating with no defined criteria — outcomes vary wildly across teams and business units. Employees in one department may be rated on completely different dimensions than peers doing equivalent work elsewhere, and there is no way to compare performance fairly at the organizational level. The PERM module replaces that with a KRA-based framework: every employee is measured against the same defined Key Result Areas, with explicit weights and measurable targets. The result is a process the employee can prepare for, the manager can defend, and HR can audit.

Fairness and transparency are the two qualities that determine whether an appraisal system is trusted by the workforce. Fairness comes from consistent criteria, calibrated rating scales, and bell-curve normalization when populations are large enough to support it. Transparency comes from giving employees visibility into their scores, a formal acknowledgement step, and a structured appeal path when they disagree. PERM is designed with both explicitly in mind: every configuration toggle in MPERMCONFIG maps directly to one of these two properties.

The third dimension is development. An appraisal that only produces a number is a missed opportunity. PERM connects weak KRA scores directly to PIP plans, and PIP plans to Training Need (TNA) requests, closing the loop between measurement and improvement. Managers who use the system well will find it becomes a coaching tool as much as a compliance exercise — one that generates evidence-based development conversations rather than annual surprises.

Capability Matrix

Stakeholder Roles

PERM serves four distinct stakeholder groups, each with a different relationship to the appraisal process. Understanding these roles is important when configuring the system — nearly every MPERMCONFIG toggle controls what each group can see or do.

Core Concepts

The PERM module uses a layered vocabulary that can be confusing at first. This glossary defines every key term in plain language, from the broadest concept down to individual scoring mechanics.

Setup Guide — HR Administrator

Setup Flow

Step 1 — Create a Rating Scale

The rating scale defines the grade bands that managers and employees will choose from when evaluating KRAs. Navigate to Performance → Configuration → Rating Scales → New Rating Scale.

For each grade band, specify: the label (e.g., "Excellent"), a display color (used in reports), and the minimum and maximum score percentage the band corresponds to. A typical 5-band scale looks like this:

You can create multiple rating scales (e.g., a 3-band scale for interns, a 5-band scale for permanent staff) and assign them at the Appraisal Type level.

Step 2 — Create KRA Categories and KRAs

KRAs are organized into categories for reporting and filtering purposes (e.g., "Operational", "Leadership", "Technical"). Navigate to Performance → Configuration → KRA Library.

For each KRA, define: the name, a brief description that helps evaluators understand what is being measured, the default weight (percentage), and the category it belongs to. Keep KRA names short and unambiguous — they will appear on the manager evaluation form and employee ESS view.

Step 3 — Create Measures under each KRA

Measures are the observable checkpoints within a KRA. Navigate to a KRA record and add Measures using the sub-form. For each Measure, decide whether it is Quantitative (a number target, e.g., "Maintain 98% uptime") or Qualitative (a behavioural descriptor, e.g., "Consistently meets deadlines without chasing").

Quantitative measures will prompt the manager to enter the employee's achieved value against the target during evaluation. Qualitative measures are rated directly on the rating scale. A KRA can have both types of measures.

Step 4 — Create an Appraisal Type

The Appraisal Type assembles the KRAs into a form template. Navigate to Performance → Configuration → Appraisal Types → New. Give the Type a name (e.g., "Standard Annual Review — Operations"), select the rating scale to use, and add KRAs from your library. Adjust the weights for this specific Type if they differ from the KRA defaults — just ensure the total remains 100%.

One Appraisal Type can be reused across many Plans. You would typically create a different Type for different employee populations (e.g., engineering vs. sales vs. support) if they have fundamentally different KRAs.

Step 5 — Configure MPERMCONFIG

Before creating a Plan, confirm the system-level settings in Performance → Configuration → Settings (MPERMCONFIG). These toggles control the visibility and self-service capabilities for the entire module. Review them with HR leadership before the first cycle. See the Configuration Reference section for a full description of each setting.

Step 6 — Create an Appraisal Plan

Navigate to Performance → Plans → New Plan. Link the Plan to an Appraisal Type, give it a name that identifies the period and population (e.g., "FY2026 Annual — All Staff"), and specify which employees or departments are included. The Plan holds the structural definition; the Cycle holds the live execution dates.

Step 7 — Open an Appraisal Cycle

Navigate to Performance → Cycles → New Cycle. Select the Plan, set the Evaluation Start Date and Evaluation End Date, and optionally set the Self-Assessment window (which typically runs before the manager evaluation window). Click Open Cycle to generate appraisal records for all employees in the Plan. From this point, the cycle is live.

Running an Appraisal Cycle

When to Open a Cycle

Open the cycle at least one to two weeks before the evaluation window begins. Employees need time to complete self-assessments before managers start their evaluations; managers need the full window to review evidence and write meaningful comments. A typical calendar looks like this:

Auto-generating vs. Manual Appraisal Records

When a cycle is opened, the system auto-generates an appraisal record for every active employee within the Plan's scope. If an employee joined during the cycle period or was missed due to a data issue, HR can manually add an individual appraisal record from the Cycle detail view without re-opening the entire cycle.

Monitoring Completion

Navigate to Performance → Cycles → [Cycle Name] → Completion Dashboard. This shows a real-time breakdown of: employees who have completed self-assessment, managers who have submitted evaluations, outstanding records, and overall cycle completion percentage. HR can filter by department and drill into individual records.

Handling Late Submissions

If a manager has not submitted by the evaluation end date, HR has two options. First, send a reminder notification from the Cycle dashboard — this triggers a system notification and ESS pending-task prompt. Second, if the manager is unavailable (e.g., on leave), HR can submit the evaluation on behalf of the manager by using the HR Override function. All override actions are audit-logged.

Finalizing the Cycle

Finalization should only be triggered once all manager evaluations are submitted. The system will warn (but not block) if outstanding records exist at finalization time. Once finalized, the following cascade occurs:

1. All appraisal records are locked — no further edits by managers or HR.
2. FinalScore is stamped on each record — this is the bell-curve-adjusted score if bell curve was applied, otherwise the CalculatedScore.
3. IsFinalized flag is set to 1 on the cycle record.
4. Score visibility is activated for employees if ScoreVisibilityOnFinalize = 1.
5. Notifications sent via SignalR hub (/hubs/perm) and ESS pending-task bucket.
6. Auto-PIP triggered for any employee whose FinalScore falls below AutoPIPThreshold (if configured).
7. Acknowledgement tasks appear in ESS for all employees in the cycle.

Post-Finalization Reports

After finalization, HR can generate the following reports from the Cycle detail view: Score Distribution Report (bell curve chart), Appraisal Summary by Department, KRA Weakness Analysis (which KRAs had the lowest average scores), and Top/Bottom Performer List. These reports are available for export to Excel or PDF.

Self-Assessment — Employee Guide

What Self-Assessment Is

Self-assessment is your opportunity to rate your own performance on each KRA before your manager submits their evaluation. It is not a negotiation — your self-assessment score does not directly change your appraisal outcome. Rather, it gives your manager context: how you perceive your own performance, where you feel you exceeded expectations, and where you acknowledge development opportunities. Managers who see a self-assessment tend to write more specific, evidence-based evaluations because the conversation has already started.

How to Access Self-Assessment

Log in to the ESS portal. On your dashboard under My Pending Tasks, you will see a task titled "Complete Self-Assessment — [Cycle Name]". Click it to open the self-assessment form. If you do not see this task, confirm with HR that self-assessment is enabled for your cycle (AllowSelfAssessment = 1 in MPERMCONFIG).

Rating Your KRAs

The self-assessment form lists each KRA in the cycle. For each one, select the grade band that best describes your performance during the evaluation period. Use the same rating scale as your manager will use — refer to the grade descriptions in the form for guidance. For quantitative measures, enter your actual achieved value alongside the target — this is factual and easy to verify.

You can save your progress as a draft and return to it before the self-assessment deadline. Once you click Submit Self-Assessment, your ratings are locked and sent to your manager. Check the task deadline in the pending task — once the self-assessment window closes, submissions are no longer possible.

After Submission

Your self-assessment is visible to your assigned manager and to HR. It is not visible to your peers or skip-level manager unless peer or skip-level evaluation is enabled for your cycle. Your self-assessment score is stored separately from your manager's evaluation — both are displayed in the final score view if ScoreVisibilityOnFinalize is enabled.

Viewing Your Score

After the cycle is finalized, return to the ESS portal. If score visibility is enabled, your My Appraisal view will show your FinalScore, a KRA-level breakdown with self vs. manager comparison, and your grade band. If visibility is not enabled, you will see the acknowledgement prompt but not the numeric score.

Manager Evaluation Guide

Accessing Your Pending Evaluations

When the manager evaluation window opens, a pending task — "Complete Appraisal Evaluations — [Cycle Name]" — appears in your ESS dashboard. Click it to see a list of all your direct reports included in the current cycle. The list shows each employee's name, self-assessment status (Submitted / Pending), and your evaluation status (Not Started / Draft / Submitted).

Evaluating a Direct Report

Click on an employee's name to open their evaluation form. The form displays each KRA with its weight and the list of Measures beneath it. For each KRA:

• Select a grade from the rating scale dropdown (e.g., Excellent / Good / Average).
• For quantitative measures, enter the employee's actual achieved value — do not leave this blank, as it drives the calculated score for that measure.
• For qualitative measures, select the grade and optionally add a brief comment as evidence.
• Add a KRA-level comment if the rating needs context (e.g., "Performance improved significantly in Q3 after training").

After all KRAs, add an overall comment. This appears in the employee's appraisal record and is visible to HR. It should summarize the employee's year, highlight standout contributions, and flag any development priorities.

Viewing Self-Assessment as Context

If the employee submitted a self-assessment, you will see their self-rated grade for each KRA alongside your rating selector. Where there is a significant gap between self and manager rating, add a comment explaining the discrepancy — this is important if the employee later files an appeal.

Saving and Submitting

You can save your evaluation as a draft at any time — progress is preserved between sessions. Click Save Draft after each session. When all KRAs are rated and you are ready to submit, click Submit Evaluation. Once submitted, your evaluation moves to Submitted status. You can request HR to un-submit for corrections if needed before the cycle is finalized.

Best Practices for Evaluation Quality

Bell Curve Distribution

When to Use Bell Curve

Enable bell curve (BellCurveEnabled = 1 in MPERMCONFIG) when all of the following are true: your cycle population is 20 or more employees, your organization needs cross-department comparability, and HR leadership has agreed on target distribution percentages. Do not apply bell curve to small teams, specialist roles with genuinely homogeneous high performance, or situations where the workforce genuinely does cluster at the high end due to recruitment quality.

How It Works

Once all managers have submitted evaluations, HR navigates to Performance → Cycles → [Cycle Name] → Bell Curve Analysis. The system shows the current CalculatedScore distribution versus the target distribution. HR reviews where actual scores deviate from targets and can make band adjustments — moving employees between bands — before finalizing.

Target Distribution Example

Target distributions are organization-defined. The example above (10/25/40/20/5) is a common starting point; HR should adjust based on the organization's context and talent philosophy. The percentages are stored as configuration on the bell curve definition, not hardcoded.

HR Workflow: Reviewing and Adjusting

The Bell Curve Analysis screen shows each employee as a data point with their CalculatedScore and their current band. HR can drag employees between bands (or use the band assignment form) where the distribution deviates from target. All adjustments are recorded in the audit log with the HR user's ID and timestamp. When the distribution is satisfactory, HR confirms the bell curve — at this point, each employee's FinalScore band is set, and the cycle is ready for finalization.

Bell Curve and Individual Fairness

Bell curve adjustments modify the band an employee lands in; they do not change the underlying CalculatedScore that remains on record. Employees can appeal a bell curve downgrade through the standard appeal process after finalization. HR should document the rationale for any specific adjustments in the bell curve notes field — this documentation will be important if an appeal is submitted.

Score Visibility & Acknowledgement

The ScoreVisibilityOnFinalize Toggle

MPERMCONFIG.ScoreVisibilityOnFinalize (0 or 1) is the single switch that controls whether employees can see their numeric appraisal score in the ESS portal after finalization. This is a deliberate organizational policy choice. Most organizations set it to 1; some prefer to share scores only in the manager-employee review conversation rather than having employees see numbers in isolation.

Acknowledgement

Acknowledgement is the formal step where an employee confirms they have seen and received their appraisal outcome. It is not an endorsement — the employee is not agreeing that the score is correct, only confirming they have been informed. Navigate to the My Appraisal page in ESS and click Acknowledge. The system stamps IsAcknowledged = 1 and records the timestamp on the appraisal record.

HR can monitor acknowledgement status from the Cycle dashboard — it shows a count of acknowledged vs. pending acknowledgements per department. Some organizations require 100% acknowledgement before reporting to the board. The appeal window runs independently of acknowledgement; an employee can acknowledge and still file an appeal.

Appeal Workflow

When an Employee Can Appeal

An appeal can be submitted after finalization and within the appeal window defined by MPERMCONFIG.AppealWindowDays (default: 7 calendar days from finalization date). Once the window closes, the system will not accept new appeal submissions for that cycle.

The employee must specify: which KRA(s) they are contesting, their reason for the appeal, and any supporting evidence (comments, metrics, references to documented work). Vague appeals ("I deserved a higher score") without specific KRA references will be harder to resolve fairly.

Appeal State Machine

• Pending — Submitted by employee, awaiting HR acknowledgement.
• Under Review — HR has picked up the appeal and is reviewing evidence. HR can request additional information from the employee at this stage.
• Resolved — HR has recorded a decision. The resolution note is visible to the employee in ESS. If the appeal results in a score change, HR triggers a re-finalization for that specific record.
• Withdrawn — The employee decided to withdraw the appeal (e.g., after a conversation with their manager). No score change occurs.

Score Adjustments Following an Appeal

If HR determines the appeal is valid and a score adjustment is warranted, the process is: (1) HR updates the affected KRA evaluation with the corrected score, (2) the system recalculates CalculatedScore, (3) HR triggers a targeted re-finalization for that employee's record, (4) the updated FinalScore is stamped, and (5) the employee receives an ESS notification. The appeal record is updated with the resolution and the score change is noted.

HR Side: Reviewing an Appeal

Navigate to Performance → Appeals to see all open appeals across all cycles. For each appeal, HR can view the employee's stated reason and evidence, the manager's original evaluation comments, the KRA score history, and any uploaded documents. HR records a formal response in the Resolution Notes field — this text is visible to the employee once the appeal is resolved.

Performance Improvement Plan (PIP)

PIP Triggers

What a PIP Contains

A PIP record (TPIPPLAN) documents the improvement agreement and tracks progress. It includes:

• Improvement Targets — specific, measurable goals per KRA where the employee is underperforming
• Support Measures — training, mentoring, resources, or workload adjustments that will be provided
• Review Dates — typically 30-day, 60-day, and 90-day check-in milestones
• Assigned HR Owner — the HR team member responsible for facilitating the process
• Manager — the direct manager responsible for day-to-day support and observation
• Start and End Date — the formal duration of the improvement plan

Periodic Reviews (Check-ins)

At each review date, the manager records a check-in note against the PIP: progress observations against each improvement target, a qualitative rating (On Track / Needs Attention / Off Track), and any adjustments to the support measures. Check-in records are appended to the PIP record and are visible to the employee, the manager, and HR.

Outcomes

At the end of the PIP period, HR marks the plan with one of three outcomes:

• Completed — Improvement Demonstrated: The employee met the improvement targets. The PIP is closed; a summary note is added. In the next appraisal cycle, the employee starts fresh.
• Extended: Partial improvement was demonstrated. HR and the manager agree to extend the PIP for a further defined period with revised targets.
• Escalated: No meaningful improvement was demonstrated. The PIP is marked Escalated and handed to HR for further action in accordance with employment policy.

PIP and Training Needs

When a PIP is created, HR can link it to a Training Need request (TTNAREQUEST). This connects the identified skill gap to the organization's TNA module, ensuring the required training is sourced and scheduled — closing the loop between performance measurement and development investment.

Analytics & Dashboard

The PERM analytics views are available to HR Administrators and Executives. They provide both cycle-level operational metrics and multi-cycle trend data for strategic workforce analysis.

Cycle-Level Metrics

Multi-Cycle Trend Analysis

Navigate to Performance → Analytics → Trends to view an employee's score trajectory across multiple cycles. A consistently improving trajectory identifies high-potential employees. A declining trajectory that precedes a PIP creates an evidence-based record. Trend charts are available at employee, department, and organization level.

KRA Weakness Analysis

This report aggregates KRA scores across all employees in a cycle and identifies which KRAs had the lowest average scores. This is a leading indicator for organization-wide capability gaps — if "Digital Proficiency" consistently scores low, that is a signal for a systemic training intervention, not just individual PIPs.

Top and Bottom Performer Identification

The cycle summary view surfaces the top-decile performers (candidates for fast-track, retention focus, or recognition programs) and the bottom-decile performers (candidates for PIP or support). These lists are filtered by the HR user's access scope — cross-department data requires HR Administrator or Executive access.

Executive Dashboard

Executives see an org-wide summary dashboard with: overall completion rate, score distribution chart across the full population, average score by business unit, and a count of active PIPs. The dashboard is read-only — executives cannot drill into individual employee records. Data refreshes in real time via the SignalR hub at /hubs/perm.

Integration Map

PERM does not operate in isolation — it exchanges data with four other GB5 modules, forming the Performance Management Platform (PERM + OKR + FBCK + CMGM) and connecting to the ESS portal and TNA workflow.

Configuration Reference (MPERMCONFIG)

All PERM system settings are stored in MPERMCONFIG, one row per client. Navigate to Performance → Configuration → System Settings to review and update these values. Changes take effect immediately — no server restart is required. Confirm these settings with HR leadership before opening the first cycle.

Implementation Checklist

Use this checklist when configuring PERM for the first time or for a new business unit. Work through it in order — each item depends on the preceding ones being complete.

Frequently Asked Questions