HiBob

The review cycle itself: configurable templates and rating scales, self, manager and 360° input, calibration across teams, and whether each rating can be traced back to criteria fixed before the cycle began.

0 — No structured reviews; at most a free-text form with no cycle, no scale and no record of who wrote what.

3 — Fixed review templates with self and manager input, but no configurable criteria, no calibration and no statement of what the employee sees.

5 — Configurable cycles, questions and rating scales, self, manager and peer input, employee sign-off or acknowledgement, and the review history kept per employee.

8 — 360° feedback with configurable reviewer selection, calibration views across teams with rating distributions, review criteria per role or level, reminders and deadlines per cycle, and a documented rule for what the employee, the manager and HR can each see.

10 — Reviews are an auditable process: criteria and competency models versioned and fixed before the cycle, every rating change during calibration attributed and reasoned, bias checks or distribution analysis described, and the full review history exportable per employee.

The work between review cycles: individual and team goals or OKRs with alignment, progress check-ins, 1:1 meetings with shared agendas, and feedback and recognition — judged on whether the year-end review can draw on it rather than starting from memory.

0 — No goals or feedback features; objectives live in documents outside the product.

3 — Individual goals with a progress percentage, and praise or feedback as an unstructured feed, with no link to the review cycle.

5 — Goals or OKRs at company, team and individual level with alignment, regular check-ins, 1:1 agendas shared between manager and employee, and requested feedback that can be pulled into the next review.

8 — OKR or goal cascading with dependencies and confidence tracking, goal changes logged with history, 1:1 notes with private and shared parts stated, feedback requests to named colleagues, and integrations into Microsoft Teams or Slack for check-ins.

10 — Continuous performance management that feeds the record: goal history, check-ins, 1:1 outcomes and feedback visible in the review with their dates, configurable whether goal attainment affects ratings, and reporting on goal progress across the organisation.

Growing people rather than only rating them: learning paths or course delivery, a skills or competency framework, career paths and development plans, and talent reviews and succession planning for key roles.

0 — No development features; the product rates people but says nothing about developing them.

3 — A development-plan text field or a link to an external course catalogue, with no skills model and no succession view.

5 — Development plans linked to review outcomes, a configurable competency or skills framework, assigned learning content or integration with a named LMS, and career paths per role.

8 — Skills profiles per employee with gaps against role requirements, learning paths with completion tracking and mandatory training, talent reviews (such as a nine-box) with succession plans per key role, and internal mobility shown against open positions.

10 — Development is planned and measured: skills data maintained and versioned, learning outcomes linked to skills and reviews, succession coverage and risk reported per role, SCORM or xAPI content supported or a named LMS integrated both ways, and certificates and training records exportable.

What the employer can put in a works agreement: visibility and access rules per role, anonymity thresholds for surveys and upward feedback, retention and deletion of review data, access logging, and disclosure and control of every AI feature that summarises, scores or suggests ratings.

0 — Nothing stated about who sees which review data, how long it is kept, or what the AI features process; "anonymous" feedback with no threshold.

3 — Role-based access mentioned in general terms and an assurance of confidentiality, but no anonymity threshold, no retention setting and AI features described only as benefits.

5 — Visibility rules per role documented, a configurable minimum group size for anonymous results, retention or deletion of review data configurable, and each AI feature named with its inputs and an option to disable it.

8 — Field-level permissions and private versus shared notes stated, access to review data logged, retention per data type, AI features off by default or switchable per module with the model provider named, and documentation or templates aimed at works councils or a works agreement.

10 — The vendor publishes what a works agreement needs: a complete list of the data each module processes and who sees it, audit logs exportable, deletion runs reportable, AI features never rating or ranking employees without a human action, the EU AI Act position stated, and EU processing for the AI features.

How the tool fits next to the system of record and what leaves with the customer: employee and org-chart sync from the HR system, SSO and SCIM, collaboration-tool integrations, an API, and export of the full review, goal and feedback history.

0 — No HR-system integration and no export; employees and managers are maintained by hand and the history stays in the product.

3 — A CSV import of employees and a PDF export of single reviews, with no named HR-system integration and no API.

5 — Maintained sync with at least one HR system common in DACH (e.g. Personio, SAP SuccessFactors, HRworks), SSO, a documented API, and an export of review and goal data in a structured format.

8 — Several named HRIS integrations including org-chart and manager relations, SCIM provisioning, Microsoft Teams or Slack integration, webhooks, an API with published limits, and a bulk export of the complete review, goal and feedback history.

10 — Portability is designed in: a versioned API with a deprecation policy, a documented full export (structured data plus attachments) available at contract end, deletion that propagates to synced systems, and the vendor maintaining the German HRIS integrations itself.

Where performance, feedback and survey data lives, who the contracting entity is, and who the subprocessors are — including the AI providers that summarise reviews and feedback. Independently sourced by the sovereignty pipeline. Weighted with the employment relationship in mind: these are judgements about people who did not choose the vendor.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and AI processing of unclear location.

3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent, or AI features run outside the EU without saying so.

5 — EU hosting as standard and an EU contracting entity, but parts of the chain — AI summaries, email, analytics or support — are non-EU without an explained safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published including AI providers, and a DPA that covers employee performance data as the customer's processing.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and the AI features run within the EU on providers the customer can see.

Whether a buyer can compute the real annual cost from public pages alone: the pricing basis (per employee, per active user, per module), which of reviews, goals, engagement surveys and learning sit in which tier, add-ons for AI or analytics, and the minimum term.

0 — No public prices at all; every module is a sales conversation.

3 — A starting price exists, but the pricing basis or which modules it covers is unstated — the invoice is unknowable.

5 — Module or tier prices public with the pricing basis given, but at least one commonly needed piece (engagement surveys, learning, AI features, HRIS integration) is unpriced.

8 — Every module or tier priced publicly with its basis, add-on prices listed, minimum headcount, minimum term and VAT treatment given.

10 — Complete price computability: the annual invoice derivable for a given headcount and module mix, with every add-on, implementation fee and overage published.