One plan for performance, at every stage.

Different functions want different frameworks. Lose one and it does not disappear — it reappears as a spreadsheet somebody in HR reconciles by hand every quarter.

One reviewer field, three actual reviewers. Bundled modules model the straight-line case well. It is the exceptions — skip-levels, appeals, blue-collar cycles — that come back to the HRBP as email.

Check-ins happen in chat and disappear. By March nobody can evidence what changed, so ratings get argued from memory and the HRBP is left refereeing. One row here is worth a second look: who your appraisal emails come from. A suite that sends every notification centrally from its own cloud means reminders about your people's appraisals arrive from an outside domain — which is what spam filters act on, and a poor look besides. We send through your own domain: your IT team sets up one no-reply address, and your managers get mail from your company rather than from a vendor.

The rating is published and then nothing happens. Development plans sit in documents on a shared drive and HR has nothing to review at the next cycle.

This is the module most often missing entirely. In most SME and mid-market organisations the increment cycle still runs on a spreadsheet emailed between HR, department heads and finance, and the HRMS only receives the final number. Full compensation planning — budgets, merit matrix, variable pay computation, approval versions — is rare below enterprise HCM, and a suite built around payroll will show you a salary revision screen and call it compensation management. Ask any vendor to run a live increment cycle with a budget limit and a merit matrix in front of you. If you get a salary master instead, you have your answer. Our position: rather than ship a shallow version, we integrate both Skills2Talent and aim performance (PRO) with a specialist compensation platform that does this properly — those are the rows marked Via integration. We are also evaluating building the compensation cycle natively into aim performance (PRO).

This is the category where what you run today is weakest. It was built before any of this existed. Four of these six rows are the actual argument for upgrading rather than staying put.

One dashboard for everyone. The CHRO scrolls past completion counts, line managers hunt for their two charts, and HRBPs export to a spreadsheet to rebuild the view they needed.

A PMS tied to one HRMS makes every future HRMS decision a performance decision too. The question to ask is what leaves with you, in what format, if you change suite again in three years.

Support is where a bundled module quietly costs you the most. In a suite, the same support team covers payroll, leave, attendance, recruitment and performance, and it rotates — so the person answering your appraisal question this cycle was on payroll last quarter and has never seen your configuration. Performance is also the module with the sharpest load spike: nothing for ten months, then every manager at once in the last week of the cycle. Ask any vendor two questions. Is the person answering a performance query a performance specialist, or on rotation? And can a manager reach a human by phone during cycle-close week, or only raise a ticket and wait?

Appraisal data sits with whoever bundled it. When legal asks who governs the AI scoring your people, somebody has to have an answer and a certificate to go with it.