Digital personnel file & data model
How this is scored
The system of record: employee master data, the digital personnel file, org structure, custom fields, and whether history is kept rather than overwritten.
0 — A contact list with job titles; no document storage, no org structure, no history — changes overwrite what was there.
3 — Employee records with document upload, but a flat structure: no org chart, few or no custom fields, and no dated history of contract or salary changes.
5 — Digital personnel file with structured document types, an org chart, custom fields, and change history on the core employment fields.
8 — Complete record: versioned contract and compensation history with effective dates, document templates with e-signature, org structure supporting multiple entities and cost centres, and granular field-level permissions.
10 — The file is the single source of truth an auditor could work from: full effective-dated history on every field, retention rules per document type, delegated administration per entity, and export that reproduces the record intact.
The IT Integrator
The personnel file is real: document management, an org chart, custom modules for things like access cards and trainings, contracts stored in a private profile area, and a change log showing who edited profile data, with per-section read and edit permissions indicated by lock icons. What I want before making an HR system the source of truth for accounts — effective-dated contract and compensation versions, field-level permissions, multi-entity org structures — I found no public information on, beyond a salary overview and history. 2 3 4