docs/hr.md

# hr

The HR system, shaped like an HRMS with a payroll module, covering all three employing entities: employment terms, contract documents, pay and its history, payroll runs and payslips, India's daily attendance register, leave, the April performance reviews, expense claims and separations. Every row is about an employee in core; times are on the employee's office clock.

| Table | Rows | What it holds |
|---|---:|---|
| [attendance](#attendance) | 150,277 | India's attendance register (PTPL only): one row per employee per calendar day, from the later of their first day and 1 October 2023 to their last day, with the day's status and punches. Employees in Rotterdam and the US have no rows. |
| [compensation](#compensation) | 287 | One row per employee: their pay as it stands on their last day or at the end of the period. Its history is compensation_versions. |
| [compensation_versions](#compensation_versions) | 884 | Every version of each person's pay from the later of their hire and 1 April 2019. Pay changes only on an offer, on 1 April (the appraisal increment, a promotion) and in India's April 2026 restructure. |
| [contract](#contract) | 1,313 | One row per employment document issued from April 2019: offer letters and contracts, appointment and confirmation letters, each April's increment letter, promotion letters and fixed-term renewals. |
| [employment](#employment) | 287 | One row per employment: the entity a person is employed by, from when to when, on what terms. Each employee has one employment. |
| [expense_claim](#expense_claim) | 3,433 | One row per expense claim an employee filed, with its outcome. Who approves depends on the claim's total and the expense policy version in force. |
| [expense_line](#expense_line) | 8,901 | One row per line of an expense claim: one expense, its day, category and merchant. |
| [leave_request](#leave_request) | 5,388 | One row per leave request: what was asked for, which days, and what was decided. Requests made before October 2023 for leave inside the period are included, and leave asked for near the end may start after it. Each entity keeps its own leave types; India's policy changed on 1 January 2025. |
| [payroll_run](#payroll_run) | 143 | One row per payroll run: PTPL and PEBV monthly, PINC twice a month, and PTPL's off-cycle final settlements for leavers. |
| [payslip](#payslip) | 5,489 | One row per payslip: one employee's pay in one run. Gross is the sum of its earning lines, deductions the sum of its deduction lines, and net is gross less deductions. |
| [payslip_line](#payslip_line) | 56,402 | One row per line of a payslip: an earning, a deduction or a contribution the employer pays on top, worked out from the payroll law in force on the pay date. |
| [performance_review](#performance_review) | 398 | One row per employee per April review cycle in the period (reviews written in March 2024, 2025 and 2026), for everyone who joined by 31 December before and was employed on 31 March. |
| [separation](#separation) | 114 | One row per employee who left during the period or was serving notice at its end, whose last day may then fall after it. |

## attendance

India's attendance register (PTPL only): one row per employee per calendar day, from the later of their first day and 1 October 2023 to their last day, with the day's status and punches. Employees in Rotterdam and the US have no rows.

150,277 rows; key `attendance_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `attendance_id` | integer, key | 0.0% | 1 to 150277 | The row's key, in date order. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 287 | The employee. |
| `date` | timestamp, local wall clock, no zone | 0.0% | 2023-10-01 00:00:00 to 2026-09-30 00:00:00 | The day. |
| `status` | text | 0.0% | `weekly_off`, `holiday`, `present` | The day's status: present, wfh (worked from home), on_duty (worked away from the office: customer visits, estates and auctions), missing_punch (worked, no check-out recorded), half_day, leave (approved leave), absent_lop (absent without leave, unpaid), comp_off (a day off in lieu of a Sunday worked), holiday, or weekly_off (Sundays, and for five-day offices the second and fourth Saturdays). |
| `check_in` | timestamp, local wall clock, no zone | 27.9% | 2023-10-03 07:46:02 to 2026-09-30 12:48:59 | The first punch of the day, on the employee's office clock (India time). Empty on days not worked. |
| `check_out` | timestamp, local wall clock, no zone | 28.9% | 2023-10-03 16:55:29 to 2026-09-30 21:55:17 | The last punch of the day, on the employee's office clock (India time). Empty on days not worked and on a missing punch. |
| `source` | text | 27.9% | `biometric`, `mobile` | How the punch was recorded: biometric (the office reader) or mobile (the app, used when working from home or on duty, and in Bengaluru, which has no reader). Empty when there was no punch. |

## compensation

One row per employee: their pay as it stands on their last day or at the end of the period. Its history is compensation_versions.

287 rows; key `compensation_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `compensation_id` | integer, key | 0.0% | 1 to 287 | The row's key; compensation_versions points at it. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 287 | The employee. |
| `currency` | text | 0.0% | `INR`, `EUR`, `USD` | The pay currency, set by the employing entity: INR (PTPL), EUR (PEBV) or USD (PINC). Every amount on the row is in it, in major units. |
| `basic` | number, 2 places | 0.0% | 2325.0 to 312500.0 | Monthly basic pay. For India, the basic in the monthly salary structure; for the Netherlands, the agreed monthly salary; for the US, the monthly base salary. |
| `hra` | number, 2 places | 9.1% | 2800.0 to 125000.0 | Monthly house rent allowance, India only. Empty for the Netherlands and the US. |
| `special_allowance` | number, 2 places | 9.1% | 1010.0 to 47384.0 | Monthly special allowance, India only: what the monthly gross holds beyond basic and HRA. Empty for the Netherlands and the US. |
| `variable_target` | number, 2 places | 0.0% | -0.0 to 0.4 | The share of annual CTC that is variable at target: a yearly bonus by grade or a sales incentive in India, the 40% commission in US sales on-target earnings. 0 where pay is fixed. |
| `annual_ctc` | number, 2 places | 0.0% | 30132.0 to 7500000.0 | Annual cost to company: everything the employer pays for the person in a year, including the employer's contributions and the variable at target. For the Netherlands it includes the 8% holiday allowance. |
| `change_reason` | text | 0.0% | `appraisal; labour code restructure`, `labour code restructure`, `appraisal` | Why the pay last changed: opening (already employed when the HR system went live in April 2019), offer, appraisal, promotion, labour code restructure (India's April 2026 rebalancing toward a basic of half of CTC, at the same CTC), or two of these joined with a semicolon. |

## compensation_versions

Every version of each person's pay from the later of their hire and 1 April 2019. Pay changes only on an offer, on 1 April (the appraisal increment, a promotion) and in India's April 2026 restructure.

884 rows; key `version_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `version_id` | integer, key | 0.0% | 1 to 884 | The version's key. |
| `compensation_id` | integer, → `hr.compensation.compensation_id` | 0.0% | 1 to 287 | The compensation row (and so the employee) the version belongs to. |
| `valid_from` | timestamp, local wall clock, no zone | 0.0% | 2019-04-01 00:00:00 to 2026-09-30 00:00:00 | The first day the version applies. |
| `valid_to` | timestamp, local wall clock, no zone | 20.4% | 2020-04-01 00:00:00 to 2026-09-29 00:00:00 | The day the next version begins, so the version applies up to the day before. For a leaver's last version, the day after their last day. Empty for a version still current. |
| `basic` | number, 2 places | 0.0% | 2320.0 to 312500.0 | Monthly basic pay in the employee's pay currency, as on compensation. |
| `hra` | number, 2 places | 4.8% | 2373.0 to 125000.0 | Monthly house rent allowance, India only. Empty for the Netherlands and the US. |
| `special_allowance` | number, 2 places | 4.8% | 1010.0 to 136175.0 | Monthly special allowance, India only. Empty for the Netherlands and the US. |
| `annual_ctc` | number, 2 places | 0.0% | 30067.2 to 7500000.0 | Annual cost to company in the pay currency. |
| `change_reason` | text | 0.0% | `opening`, `offer`, `appraisal` | Why this version began: opening, offer, appraisal, promotion, labour code restructure, or two joined with a semicolon. |

## contract

One row per employment document issued from April 2019: offer letters and contracts, appointment and confirmation letters, each April's increment letter, promotion letters and fixed-term renewals.

1,313 rows; key `contract_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `contract_id` | integer, key | 0.0% | 1 to 1313 | The document's key. |
| `employment_id` | integer, → `hr.employment.employment_id` | 0.0% | 1 to 287 | The employment the document belongs to. |
| `kind` | text | 0.0% | `offer_letter`, `confirmation_letter`, `increment_letter` | The document: offer_letter, appointment_letter (required in India from 21 November 2025), confirmation_letter (at the end of probation), increment_letter, promotion_letter, fixed_term_renewal, nl_fixed_term_contract (a Dutch first contract, for a year), nl_permanent_contract, or us_offer_letter. |
| `signed_at` | timestamp, local wall clock, no zone | 0.0% | 2019-05-18 15:14:15 to 2026-09-30 09:37:44 | When the document was signed and issued, on the employee's office clock. An offer comes some days before the start date. |
| `annual_ctc` | number, 2 places | 0.0% | 30067.2 to 7500000.0 | The annual cost to company the document states, in currency. |
| `currency` | text | 0.0% | `INR`, `EUR`, `USD` | The currency of annual_ctc: INR, EUR or USD. |
| `document_ref` | text | 0.0% | `PTPL/HR/OL/2019/0001`, `PTPL/HR/OL/2019/0002`, `PTPL/HR/OL/2019/0003` | The document's reference: entity / HR / type / year / number, numbered within each entity, type and year. Types: OL offer, AL appointment, CL confirmation, IL increment, PL promotion, FT fixed-term renewal, AO Dutch employment contract. |

## employment

One row per employment: the entity a person is employed by, from when to when, on what terms. Each employee has one employment.

287 rows; key `employment_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `employment_id` | integer, key | 0.0% | 1 to 287 | The employment's key. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 287 | The employee. |
| `entity_code` | text | 0.0% | `PTPL`, `PEBV`, `PINC` | The employing entity: PTPL (India), PEBV (the Netherlands) or PINC (the US). |
| `start_date` | timestamp, local wall clock, no zone | 0.0% | 2017-03-14 00:00:00 to 2026-09-30 00:00:00 | The first day of employment. |
| `end_date` | timestamp, local wall clock, no zone | 62.7% | 2023-10-23 00:00:00 to 2026-09-28 00:00:00 | The last day of employment. Empty while the person is employed at the end of the period, including anyone serving notice. |
| `kind` | text | 0.0% | `permanent`, `fixed_term` | permanent or fixed_term, as at the last day or the end of the period. India's fixed-term operators and associates are hired for the busy seasons; a Dutch first contract is fixed-term for a year, then permanent. |
| `probation_end` | timestamp, local wall clock, no zone | 0.0% | 2017-09-13 00:00:00 to 2027-06-29 00:00:00 | The last day of probation: six months in India (nine where it was extended), one month in the Netherlands (two for the managing director), 90 days in the US. |
| `notice_days` | integer | 0.0% | 14 to 90 | The notice period in the contract, in days: by grade in India (30 to 90), 30 in the Netherlands, 14 in the US. |

## expense_claim

One row per expense claim an employee filed, with its outcome. Who approves depends on the claim's total and the expense policy version in force.

3,433 rows; key `claim_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `claim_id` | integer, key | 0.0% | 1 to 3433 | The claim's key, in order of submission. |
| `claim_no` | text | 0.0% | `EXP-2023-00714`, `EXP-2023-00715`, `EXP-2023-00716` | The claim number: EXP-, the year of submission and a number counting within that year. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 278 | The employee who claimed. |
| `submitted_at` | timestamp, local wall clock, no zone | 0.0% | 2023-10-01 22:12:18 to 2026-09-30 22:07:49 | When the claim was filed, on the employee's office clock. |
| `purpose` | text | 0.0% | `Local conveyance`, `Phone and internet`, `Business travel` | What the claim is for: Local conveyance, Client meeting, Business travel, Mileage, Phone and internet, or Trade fair. |
| `total` | number, 2 places | 0.0% | 5.48 to 118043.0 | The claim's total, the sum of its lines, in currency. |
| `currency` | text | 0.0% | `INR`, `EUR`, `USD` | The claim's currency, the employee's pay currency: INR, EUR or USD. |
| `status` | text | 0.0% | `paid`, `rejected`, `returned` | submitted (not decided at the end of the period), approved (not yet reimbursed), paid, returned (sent back, mostly for a missing receipt) or rejected. |
| `approver_employee_id` | integer, → `core.employee.employee_id` | 0.7% | 1 to 260 | Who decides the claim: the manager, the unit head, the CFO or the CEO, by the claim's total against the policy's limits; from April 2024 the managing director Europe for Rotterdam staff. Empty while the claim is undecided. |
| `approved_at` | timestamp, local wall clock, no zone | 8.9% | 2023-10-03 18:06:04 to 2026-09-30 17:29:57 | When the claim was approved, on the employee's office clock. Empty unless approved or paid. |
| `paid_at` | timestamp, local wall clock, no zone | 9.6% | 2023-10-06 11:29:05 to 2026-09-30 09:26:55 | When the reimbursement was paid: in India the next Friday's bank transfer run, in the Netherlands a SEPA transfer 5 to 10 working days on, in the US with the next pay date. Empty until paid. |
| `policy_version` | integer | 0.0% | 1 to 2 | The expense policy version in force when the claim was filed: 1 until 31 March 2025, 2 from 1 April 2025, which raised the manager's approval limit. |

## expense_line

One row per line of an expense claim: one expense, its day, category and merchant.

8,901 rows; key `line_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `line_id` | integer, key | 0.0% | 1 to 8901 | The line's key. |
| `claim_id` | integer, → `hr.expense_claim.claim_id` | 0.0% | 1 to 3433 | The claim the line belongs to. |
| `expense_date` | timestamp, local wall clock, no zone | 0.0% | 2023-08-30 00:00:00 to 2026-09-28 00:00:00 | The day of the expense. A fare is dated the day it was booked, before the trip; a hotel line is dated the last day of the stay. |
| `category` | text | 0.0% | `local_conveyance`, `phone_internet`, `rail` | The expense category: local_conveyance, mileage, meals, client_entertainment, hotel_per_night (the whole stay, every night in one line), air, rail, phone_internet (a month's bill) or trade_fair. |
| `merchant` | text | 22.0% | `Banjara Cabs`, `Haveli Mobile`, `Chembaka Rail Travels` | Who was paid. Empty for mileage and for auto-rickshaw rides in India, which have no merchant. |
| `amount` | number, 2 places | 0.0% | 2.14 to 62766.0 | The line's amount, in currency. |
| `currency` | text | 0.0% | `INR`, `EUR`, `USD` | The line's currency, the claim's. |
| `has_receipt` | boolean | 0.0% | False to True | True when a receipt is attached. Mileage carries a trip log and counts as having one. |
| `note` | text | 41.8% | `Auto fare to printer for label check`, `Local conveyance to the hotel client`, `Local conveyance to station` | What the claimant wrote on the line: the thing bought, where it took them, sometimes why. Empty where they wrote nothing. |

## leave_request

One row per leave request: what was asked for, which days, and what was decided. Requests made before October 2023 for leave inside the period are included, and leave asked for near the end may start after it. Each entity keeps its own leave types; India's policy changed on 1 January 2025.

5,388 rows; key `leave_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `leave_id` | integer, key | 0.0% | 1 to 5388 | The request's key, in order of the request. |
| `leave_no` | text | 0.0% | `LV-004613`, `LV-004614`, `LV-004615` | The leave number, issued in order of the request; it continues the numbering from earlier years. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 286 | The employee asking. |
| `applied_at` | timestamp, local wall clock, no zone | 0.0% | 2023-08-07 21:34:28 to 2026-09-30 20:52:54 | When the request was made, on the employee's office clock. A sick day is often reported after it began. |
| `leave_type` | text | 0.0% | `earned`, `casual`, `sick` | The kind of leave: in India earned, casual and sick (until 2024), then earned, sick_casual (casual and sick combined) and floating (an optional holiday the employee picks) from 2025; vacation in the Netherlands; pto and sick in the US. Dutch sick days are reported here as sick. |
| `start_date` | timestamp, local wall clock, no zone | 0.0% | 2023-10-03 00:00:00 to 2026-11-27 00:00:00 | The first day of leave. |
| `end_date` | timestamp, local wall clock, no zone | 0.0% | 2023-10-03 00:00:00 to 2026-12-05 00:00:00 | The last day of leave, inclusive. |
| `days` | number, 1 places | 0.0% | 0.5 to 15.0 | The working days the request covers on the employee's calendar; a half day, or a half-working Saturday, counts 0.5. |
| `status` | text | 0.0% | `approved`, `rejected`, `cancelled` | approved, rejected, cancelled (withdrawn, before or after approval) or pending (not decided at the end of the period). |
| `approver_employee_id` | integer, → `core.employee.employee_id` | 0.7% | 1 to 278 | Who decides: the manager the employee reports to on the day of the request, or that manager's own manager while they are on leave. Empty for the CEO's requests, which the system approves. |
| `decided_at` | timestamp, local wall clock, no zone | 0.6% | 2023-08-08 10:54:53 to 2026-09-30 17:48:21 | When the decision was made, on the employee's office clock. Empty while pending or when withdrawn before a decision. |
| `reason` | text | 1.6% | `family function at kunnamkulam.`, `native. kindly approve.`, `personal` | What the employee typed as the reason, as written. Sometimes empty. |

## payroll_run

One row per payroll run: PTPL and PEBV monthly, PINC twice a month, and PTPL's off-cycle final settlements for leavers.

143 rows; key `run_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `run_id` | integer, key | 0.0% | 1 to 143 | The run's key, in order of run date. |
| `run_code` | text | 0.0% | `PR-2023-10-PTPL`, `PR-2023-11-PTPL`, `PR-2023-12-PTPL` | The run's code: PR-, the year and month, and the entity; PINC's two runs end -A (the 15th) and -B (the last day), and a PTPL final settlement run ends -FF and a number. |
| `entity_code` | text | 0.0% | `PTPL`, `PEBV`, `PINC` | The entity paying: PTPL, PEBV or PINC. |
| `period` | text | 0.0% | `2023-10`, `2023-11`, `2023-12` | The pay period as year and month; for PINC with its half, -A or -B. For a final settlement, the month of the run. |
| `run_date` | timestamp, local wall clock, no zone | 0.0% | 2023-10-31 00:00:00 to 2026-09-30 00:00:00 | The pay date: the last working day of the month for PTPL and PEBV, the 15th and the last day (moved to the business day before a bank holiday) for PINC. |
| `status` | text | 0.0% | `paid` | The run's status. Every run in the export is paid. |
| `employees_count` | integer | 0.0% | 1 to 161 | The number of payslips in the run. |
| `gross_total` | number, 2 places | 0.0% | 3550.0 to 20797751.0 | The sum of the run's payslips' gross pay, in currency. |
| `net_total` | number, 2 places | 0.0% | 2637.82 to 19181353.0 | The sum of the run's payslips' net pay, in currency. |
| `currency` | text | 0.0% | `INR`, `EUR`, `USD` | The run's currency, the entity's: INR, EUR or USD. |

## payslip

One row per payslip: one employee's pay in one run. Gross is the sum of its earning lines, deductions the sum of its deduction lines, and net is gross less deductions.

5,489 rows; key `payslip_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `payslip_id` | integer, key | 0.0% | 1 to 5489 | The payslip's key, in order of release. |
| `payslip_no` | text | 0.0% | `PS-2023-10-EMP-10001`, `PS-2023-10-EMP-10003`, `PS-2023-10-EMP-10004` | The payslip number: PS-, the year and month, and the employee number, with -A or -B for a PINC half-month and -FF for a final settlement. |
| `run_id` | integer, → `hr.payroll_run.run_id` | 0.0% | 1 to 143 | The payroll run the payslip belongs to. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 286 | The employee paid. |
| `released_at` | timestamp, local wall clock, no zone | 0.0% | 2023-10-31 19:11:02 to 2026-09-30 20:57:00 | When the payslip was emailed from the HR system, on the employee's office clock. A run's payslips go out in one batch. |
| `days_paid` | number, 1 places | 0.0% | -0.0 to 31.0 | The days of the pay period the payslip pays for: the calendar days employed in the period, less loss-of-pay days in India. |
| `lop_days` | number, 1 places | 0.0% | -0.0 to 15.0 | Days of loss of pay deducted, read from the attendance register (absences without leave, half for a half day). India only; 0 elsewhere. |
| `gross` | number, 2 places | 0.0% | 83.24 to 1772719.0 | Gross pay: the sum of the earning lines, in currency. |
| `deductions` | number, 2 places | 0.0% | -0.0 to 191484.0 | The sum of the deduction lines, in currency. |
| `net` | number, 2 places | 0.0% | 21.84 to 1582485.0 | Net pay, gross less deductions, in currency. |
| `currency` | text | 0.0% | `INR`, `EUR`, `USD` | The payslip's currency, the entity's: INR, EUR or USD. |

## payslip_line

One row per line of a payslip: an earning, a deduction or a contribution the employer pays on top, worked out from the payroll law in force on the pay date.

56,402 rows; key `line_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `line_id` | integer, key | 0.0% | 1 to 56402 | The line's key. |
| `payslip_id` | integer, → `hr.payslip.payslip_id` | 0.0% | 1 to 5489 | The payslip the line belongs to. |
| `component` | text | 0.0% | `BASIC`, `HRA`, `SPECIAL` | The pay component's code. India: earnings such as BASIC, HRA, SPECIAL, OT, BONUS_STAT, VARIABLE, INCENTIVE, LEAVE_ENCASH, GRATUITY, NOTICE_PAY, ARREARS; deductions such as PF_EE, ESI_EE, PT (professional tax), LWF_EE, TDS (income tax); employer lines such as PF_ER_EPF, PF_ER_EPS, EDLI, ESI_ER. The Netherlands: SALARY, HOLIDAY_ALLOWANCE, LOONHEFFING (wage tax), PENSION_EE, PENSION_ER, AWF, WHK, ZVW. The US: SALARY, COMMISSION, FED_WH, STATE_WH, SS_EE, MEDICARE_EE, 401K_EE, HEALTH_EE, SS_ER, FUTA, SUTA. |
| `kind` | text | 0.0% | `earning`, `deduction`, `employer` | earning (adds to gross), deduction (comes off gross to give net), or employer (the employer's contribution on top, in neither gross nor net). |
| `amount` | number, 2 places | 0.0% | 0.1 to 1325250.0 | The line's amount, positive, in the payslip's currency. |

## performance_review

One row per employee per April review cycle in the period (reviews written in March 2024, 2025 and 2026), for everyone who joined by 31 December before and was employed on 31 March.

398 rows; key `review_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `review_id` | integer, key | 0.0% | 1 to 398 | The review's key. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 1 to 239 | The employee reviewed. |
| `cycle` | text | 0.0% | `FY24`, `FY25`, `FY26` | The fiscal year reviewed: FY24 is April 2023 to March 2024, reviewed in March 2024. |
| `submitted_at` | timestamp, local wall clock, no zone | 0.0% | 2024-03-08 11:54:28 to 2026-03-20 20:07:01 | When the manager submitted the review, between 8 and 22 March, on the employee's office clock. |
| `self_rating` | number | 0.0% | 1.0 to 5.0 | The employee's own rating, 1 (does not meet) to 5 (exceeds strongly). |
| `manager_rating` | number | 0.0% | 1.0 to 5.0 | The manager's rating on the same 1 to 5 scale, before calibration. |
| `calibrated_rating` | number | 0.0% | 1.0 to 5.0 | The final rating after calibration, which sets the April increment. |
| `reviewer_employee_id` | integer, → `core.employee.employee_id` | 0.8% | 1 to 216 | The manager who wrote the review: the employee's manager on that day. Empty for the chief executive. |
| `comments` | text | 0.0% | `Thomas had an outstanding FY24. Brought real rigour to month end.`, `Performance was in line with the role. Handles routine tasks well. Needs to take more initiative. Self assessment was ge`, `A steady year for Bibhu. Needs to work on attention to detail.` | The manager's written comments on the year, in line with the rating and, where the self rating was higher, saying so. |

## separation

One row per employee who left during the period or was serving notice at its end, whose last day may then fall after it.

114 rows; key `separation_id`.

| Column | Type | Empty | Range or values | Meaning |
|---|---|---:|---|---|
| `separation_id` | integer, key | 0.0% | 1 to 114 | The separation's key, in order of notice. |
| `employee_id` | integer, → `core.employee.employee_id` | 0.0% | 4 to 270 | The employee leaving. |
| `kind` | text | 0.0% | `end_of_fixed_term`, `resignation`, `absconding` | resignation, termination, absconding (a floor worker who stopped coming and was terminated) or end_of_fixed_term. |
| `notice_given_at` | timestamp, local wall clock, no zone | 0.0% | 2023-10-16 00:00:00 to 2026-09-28 00:00:00 | The day notice was given (a resignation) or the decision made (a termination or the end of a term). |
| `last_day` | timestamp, local wall clock, no zone | 0.0% | 2023-10-23 00:00:00 to 2026-11-20 00:00:00 | The last day of employment. For someone serving notice at the end of the period, the day their notice ends. |
| `reason_code` | text | 0.0% | `end_of_term`, `relocation_family`, `career_growth` | Why the person left. For a resignation: better_pay, career_growth, relocation_family, abroad, manager, shift_or_hours, higher_studies, marriage or health; for a termination: performance, conduct or attendance; otherwise absconding or end_of_term. |
| `regretted` | boolean | 0.0% | False to True | True when the business wished it had kept the person. Only resignations can be regretted. |
| `exit_interview_at` | timestamp, local wall clock, no zone | 44.7% | 2024-01-12 11:57:39 to 2026-09-24 11:21:47 | When the exit interview was held, in the days before the last day, on the employee's office clock. Empty for most separations other than resignations, and for some resignations. |
| `reason_text` | text | 0.9% | `Contract completed, not renewed. Handover completed.`, `Spouse transferred; relocating.`, `Felt growth was limited in the current team. Eligible for rehire.` | HR's note of why the person left, in the words of the exit record, sometimes with whether they may be rehired. Empty where HR recorded nothing. |