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 Data Protection Officer
The digital personnel file is substantial: complete historization and revision-safe archiving, salary development and cost-centre data held in the record, personnel documents generated straight into the e-file, batch scanning of paper files, and organisational management that covers subsidiaries. What I could not find on the captured pages is field-level permission control, effective-dated contract and compensation versions, and retention rules per document type — the difference between a good file and one an auditor can defend. 5 2 1