Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Nairobi · People & society

HR.
Inspect employee and hiring records.

Inspect employee records, hiring dates and organizational references alongside the employment layer they support.

Public sample available

Published domain facts

Employees · Nairobi
60,721
Payroll Runs, Nairobi
4.22M
Positions / City
36
Structural Checks PASS
17 / 17

Overview

Domain scope

Inspect employee records, hiring dates and organizational references alongside the employment layer they support.

Read the published guide →

Known limits

Pay progression and withholding are simplified modeling choices, unsuitable for payroll compliance or compensation decisions. Direct Finance and Business links are not asserted. Performance ratings do not affect pay, promotion or separation. Records do not represent actual employees or employer policies.

Review the source limits →
Full scope reference 3 documented sections
Published domain scope.

Published domain scope.

Inspect positions, payroll, training and performance records linked to formal employment. Employee references connect this administrative layer to residents and contracts.

  • Review employee and resident references
  • Compare hiring dates and employment status
  • Inspect position and department coverage
Employees · Nairobi
60,721
Payroll Runs, Nairobi
4.22M
Positions / City
36
Structural Checks PASS
17 / 17
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

FCTE models the organizational and payroll administration behind a formal job — real graded positions inside a grade-band hierarchy, statutory payroll deductions, training and performance review — for the same synthetic citizens already employed under a real Employment Contract, across Nairobi City Twin™.

Nairobi City Twin™ · 1940–2026

The organizational layer behind an employment contract.

The organizational layer behind an employment contract.

Inspect the published definitions and release context.

Read the published detail

FCTE's HR model represents how a synthetic resident's formal employment is organized — position and grade context, compensation, statutory deductions, training and performance history through time. The cards below describe the public semantic capabilities available in the Nairobi release.

Position and grade-band context captures jurisdiction-specific workforce structure and compensation ranges without publishing the physical grade mapping.

Payroll context represents recurring gross pay, statutory deductions and net-pay outcomes through time.

Statutory-deduction context represents cited jurisdictional pension, health-insurance and income-tax obligations.

Completed training history is role-sensitive so course mix reflects the employee’s position and jurisdiction. Exact catalogs and selection weights are controlled.

Performance-review context represents periodic workforce evaluations with numeric and categorical outcomes through time.

Historical workforce context allows major economic shocks and policy periods to affect synthetic payroll outcomes while keeping the internal propagation logic controlled.

Synthetic by design: no position, payroll run, training record or performance review on this page represents a real employer, a real employee, or an actual compensation decision. FCTE generates a synthetic organizational history from its synthetic population.

Both domains touch the same citizen, and both read from the same underlying employment relationship — but they answer different questions.

Employment's Job Catalog spans 262 jobs across the whole economy (manufacturing, education, legal and more, dating back to 1960). HR's Position catalog is a much narrower, formally graded set of 36 roles per city — the kind of civil-service-style hierarchy (Director, Chief Engineer, Assistant Director…) that has an explicit grade band, a compensation range, and statutory payroll deductions attached to it. Not every Employment Contract maps to an HR Position; HR is the administrative layer for the subset of employment that is formally graded.

Samples & fields

Published sample records.

Public sample · rows and field definitions

Public sample

Employee numberHire dateEmployment statusPosition referenceDepartment referenceWard referenceEmployee referenceResident reference
EMP-175432015-02-23Active101952175432173163
EMP-490552022-06-17Active2858049055409480
EMP-117082012-02-22Terminated274032117081069351

Showing 3 of 100 sample rows and 8 of 10 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Employee number

The published reference number associated with the employee.

Original field: EmployeeNumber
Example: EMP-17543

Hire date

The date recorded for the hire event.

Original field: HireDate
Example: 2015-02-23

Employment status

The state recorded for the employment in this extract.

Original field: EmploymentStatus
Example: Active

Position reference

The reference used to identify the position associated with this record.

Original field: PositionId
Example: 10

Department reference

The reference used to identify the department associated with this record.

Original field: DepartmentId
Example: 19

Ward reference

The reference used to identify the ward associated with this record.

Original field: WardId
Example: 52

Employee reference

The reference used to identify the employee associated with this record.

Original field: EmployeeId
Example: 17543

Resident reference

The synthetic resident reference used to connect this record to other city data.

Original field: CitizenId
Example: 2173163

Complete published field dictionary · 10 fields
EmployeeIdEmployee reference
The reference used to identify the employee associated with this record.Example: 17543
CitizenIdResident reference
The synthetic resident reference used to connect this record to other city data.Example: 2173163
EmployeeNumberEmployee number
The published reference number associated with the employee.Example: EMP-17543
PositionIdPosition reference
The reference used to identify the position associated with this record.Example: 10
DepartmentIdDepartment reference
The reference used to identify the department associated with this record.Example: 19
HireDateHire date
The date recorded for the hire event.Example: 2015-02-23
EmploymentStatusEmployment status
The state recorded for the employment in this extract.Example: Active
GenderGender
The gender recorded for the synthetic resident; M and F denote male and female in these samples.Example: Male
WardIdWard reference
The reference used to identify the ward associated with this record.Example: 52
BirthYearBirth year
The calendar year associated with birth in this record.Example: 1967
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
From one contract to an organization.

From one contract to an organization.

Inspect the published definitions and release context.

Read the published detail

Employee-level generation has run in Nairobi. Below is a real join across Employee, Position and Payroll — one representative (near-grade-average) employee per band, for the most recent generated payroll month, 2023-04.

Direct output from Nairobi release, captured 2026-08-06 — one near-average employee per grade band, PayrollMonth 2023-04.

View HR Deployment Status →

Public entity familyRepresentsDisclosure boundary
Workforce position contextRole, organization and workforce-structure contextPhysical position data structure is controlled
Employee lifecycleResident-to-workforce relationship through timeExact employment dependency and fields are controlled
Compensation & payrollPay, grade and payroll contextExact band mapping, formulas and fields are controlled
Benefits & developmentSocial insurance, training and workforce-development contextAssignment and eligibility logic are controlled
PositionGrade BandHiredGross / MonthNet / Month

Connections

Known and possible relationships

Inspect the published definitions and release context.

Domain or contextRelationship and published scope
EmploymentEmployee and contract context connect personnel administration to the existing employment layer.
Grade and compensationPositions, grade bands and compensation context describe the employee within an organisation.
Payroll and deductionsPayroll, statutory deductions and social-insurance context sit alongside the employee record.
Training and reviewTraining and performance records describe activity within the employee lifecycle.
Business and Public FinanceEmployer and department context are represented within HR. Direct cross-domain joins are not asserted by the public guide.
Full relationship reference 1 documented sections
Known and possible relationships.

Known and possible relationships.

Inspect the published definitions and release context.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
EmploymentEmployee and contract context connect personnel administration to the existing employment layer.
Grade and compensationPositions, grade bands and compensation context describe the employee within an organisation.
Payroll and deductionsPayroll, statutory deductions and social-insurance context sit alongside the employee record.
Training and reviewTraining and performance records describe activity within the employee lifecycle.
Business and Public FinanceEmployer and department context are represented within HR. Direct cross-domain joins are not asserted by the public guide.

Domain guide

HR · archived guide edition

Striped Donkey V5.89 - 7 September 2026

Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.

Published scope and limits

Pay progression and withholding are simplified modeling choices, unsuitable for payroll compliance or compensation decisions. Direct Finance and Business links are not asserted. Performance ratings do not affect pay, promotion or separation. Records do not represent actual employees or employer policies.

Read the source limits →
Accessible HTML reference 2 documented sections
A workforce is not a headcount.

A workforce is not a headcount.

Published release reference · These recorded checks are not a current rerun.

Inspect the published definitions and release context.

Read the published detail

A headcount is a number. FCTE's HR model is a chain of dated, connected records: a contract becomes a graded position, a position becomes a monthly payroll run with named statutory deductions, and that run sits alongside training and performance history for the same persistent citizen — bounded, at both ends, by the citizen's own birth and death.

Female, DOB 1966-04-16, Nairobi. Employee 5363, hired 2006-02-13 as Officer I (grade JG-M) — a real, published, 20-year employment record with 21 Performance Reviews and 21 Training records, still Active today.

A real Employee row, linked to the same persistent citizen identity used across Demographics and Employment.

Her first Performance Review — the earliest of 21 real, dated review records on this employee.

Crossed into the "Meets Expectations" band within two years of hire.

Her most recent of 21 real reviews — two decades of dated performance history on the same employee, still employed today.

Employee records use the same persistent synthetic-resident identity used across Demographics, Employment and other City Twin domains. This enables longitudinal analysis without exposing the physical join design.

Payroll uses jurisdiction-relevant pension, health-insurance and income-tax context grounded in public law and policy. Exact rate application, caps and calculation logic remain controlled.

Performance Review's Rating is recorded but does not currently change Payroll, grade band, or separation likelihood for any synthetic employee. No causal effect is modeled or claimed today.

Two real, different grade-band systems — not a shared template.

Two real, different grade-band systems — not a shared template.

Inspect the published definitions and release context.

Read the published detail

FCTE represents Kenya-specific public-sector grade and compensation structures as distinct jurisdictional models rather than relabeling one shared model. Exact compensation mappings and internal rules are controlled.

Kenya Job Group conventions are represented at grade-family level. Detailed compensation bands and position-level calibration remain controlled.

Documented public institutions, occupational structures and labor-market evidence provide the external reference frame for the synthetic workforce.

Workforce counts, role distributions and tenure measures are computed from released synthetic HR records and aggregate certification views.

Workforce composition, role mix, tenure and organizational distributions are calibrated to documented institutional and labor evidence and checked at release level. Exact staffing weights and assignment rules remain controlled.

Individual synthetic assignments are generated under controlled domain rules. Exact sampling, assignment order and parameterization are not published.

View HR Generation Methodology →

Evidence & limits

Scope and known limits

Pay progression and withholding are simplified modeling choices, unsuitable for payroll compliance or compensation decisions. Direct Finance and Business links are not asserted. Performance ratings do not affect pay, promotion or separation. Records do not represent actual employees or employer policies.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

Pay progression and withholding are simplified modeling choices, unsuitable for payroll compliance or compensation decisions. Direct Finance and Business links are not asserted. Performance ratings do not affect pay, promotion or separation. Records do not represent actual employees or employer policies.

Read the published detail

Longitudinal synthetic pay can move beyond an entry/reference band through modeled tenure and career progression. This is a modeling choice rather than a payroll-compliance rule. Exact progression formulas, rates and grade-specific examples are not published.

Department and employer context is represented within HR, but this public release does not assert direct object-level relationships to Finance or Business. Those cross-domain boundaries remain explicit.

Payroll uses simplified withholding assumptions for synthetic analysis rather than a full statutory payroll-tax engine. The rates are not intended for payroll compliance, tax filing, or employer-specific compensation decisions.

Performance Review's Rating does not currently affect payroll, promotion or separation likelihood for any synthetic employee.

No position, payroll amount, training record or performance review represents an actual employer's policy, a real employee, or an identifiable person.

View All HR Limitations →

Do the deductions match the law? Yes, confirmed in the published source.

Do the deductions match the law? Yes, confirmed in the published source.

Published release reference · These recorded checks are not a current rerun.

Inspect the published definitions and release context.

Read the published detail

Open the HR Realism Report →

17 structural checks run against Nairobi: reference data (positions, grade bands, statutory schemes) and employee-level data (86,304 employees, 3.78M–10.68M payroll rows) both fully populated and passing.

Realism certification (5 checks, certification check–R05): ALL PASS, 0 WARN in Nairobi — every deduction rate lands inside its sourced statutory band.

Explore Every Domain's Certification Status →

  • certification check Health and Pension statutory schemes populated
  • certification check Grade Tier Map coverage across all defined grade bands
  • certification check / H10 Employee population available + resident-reference integrity, 0 unresolved references
  • certification check NetAmount ≤ GrossAmount, 0 violations
  • certification check–H17 death/separation-bound payroll integrity, 0 violations Nairobi

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 1 documented sections
Recorded example.

Recorded example.

Explore the supplied synthetic example and its source references.

Read the published detail

The same synthetic resident can appear across Demographics, Household, Employment and HR context.

The citizen holds a formal contract — 86,304 active contracts exist on Nairobi today.

Formal employment can be represented with position and grade context through time; exact release volumes are not a public engine parameter.

Gross-to-net pay context reflects named statutory deduction categories without exposing the calculation recipe.

Training and performance history can accumulate over the employment span as longitudinal workforce context.

Organizational history sits alongside health, household and demographic context through the shared resident identity.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™