Personio

Personio exposes five entity types through its API: employees, attendances, absences, absence balances, and projects. This integration covers the three entity types that yield individually attributable performance indicators: attendances for workforce presence, absences for leave behaviour, and absence balances for entitlement consumption. Employees as an entity anchor all attribution, since every attendance and absence record resolves to an email via the employee identifier. The recruiting API was excluded because the v1 endpoint does not expose a candidate pipeline, only open positions. Five KPIs were retained, selected against three criteria: ability to attribute each record to a named employee, resistance to gaming, and balance between leading and lagging indicators.

Workforce presence: reading Attendance Hours and Project Hours together

Attendance Hours measures the total confirmed working time an employee logs in the period. Project Hours measures the subset of that time allocated to a named project. Both are leading indicators: they reflect current effort rather than outcomes already produced. Taken in isolation, Attendance Hours answers only whether an employee is present and logging time. The pairing with Project Hours answers a more diagnostic question: of the time logged, how much is directed toward structured, trackable work versus unallocated activity. A high Attendance Hours count combined with a low Project Hours count may indicate that the employee is present but not engaged in defined deliverables — a signal relevant to capacity planning and role clarity rather than to individual underperformance.

Project Hours carries a data-reliability caveat that Attendance Hours does not: it depends on the team using Personio's project module consistently. In organizations that do not assign projects at the attendance level, this KPI will systematically read zero and carry no analytical value. The KPI is therefore conditional on usage discipline, a dependency that the scope section addresses directly.

Absence behaviour: three indicators for a layered diagnostic

Absenteeism Rate expresses absence days as a proportion of available working days. Absence Days by Type decomposes that total into its constituent categories — sick leave, annual leave, and other approved absence types. Leave Consumption Rate measures what fraction of the annual entitlement has been used relative to the point in the leave cycle. These three indicators address distinct management questions that a single absence count cannot resolve.

Absenteeism Rate reveals whether an employee's absence pattern is drifting above the baseline for the team or organisation. Because it is a rate rather than an absolute count, it remains comparable across employees with different scheduled hours and contract types. The indicator's diagnostic power increases when read alongside Absence Days by Type: a rising Absenteeism Rate composed primarily of sick leave days points in a different direction from the same rate driven by approved annual leave. The first may signal a wellbeing or engagement issue; the second reflects normal entitlement usage and warrants no intervention.

Leave Consumption Rate introduces a dimension that neither of the other two indicators covers: the trajectory of entitlement usage over the leave cycle. An employee consuming a very low share of their entitlement by mid-year is not flagging a performance issue but a welfare and financial-liability one. Research on occupational burnout consistently identifies accumulated untaken leave as a precursor to abrupt, high-duration sick leave episodes. HR managers who intervene early — encouraging leave usage before the year-end peak — reduce both the financial accrual risk and the human cost. This KPI is the only one in the integration that functions as a welfare signal rather than a performance signal.

Scope and limits of the integration

Personio's API covers the administrative layer of HR: who is employed, when they are present, and when they are absent. It does not expose performance management, learning activity, compensation benchmarking, or any indicator of work quality. An employee with high Attendance Hours may be producing high-value output or running in place; the API data does not distinguish between the two. Headcount and turnover metrics, while available in the data, were excluded from this integration because they cannot be attributed to an individual contributor — they are organisational health metrics, not individual performance indicators.

The accuracy of every KPI in this integration depends on how rigorously employees and managers log attendance and absences in Personio. Unrecorded attendance periods, absences submitted but not approved in the system, and project assignments omitted at entry time all introduce systematic under-counting. In organisations where Personio is used primarily for payroll and leave approval rather than as a day-to-day HR tool, the data completeness will be structurally lower and these indicators will reflect only partial workforce activity.