Loading
Because they start as a handful of files per person and no decision is made about where they live. They end up in a drive nobody audits, and an expired check is discovered by whoever asks for it first.
Documents attached to the personnel record with type, date and expiry — contracts, identity checks, signed policies and certificates.
Each document carries a type and an expiry where one applies. Expiries surface in advance to HR and the person, rather than on the day they lapse.
A contractor's right-to-work check expires in thirty days. It appears on the HR queue and in the person's own view, with time to act rather than as an incident.
It does not do e-signature. Signed documents are stored; getting them signed happens elsewhere.
Onboarding and offboarding checklists reference documents as steps. Learning records hold certifications separately, because those have renewal cycles rather than a single expiry.
Yes, for types you permit — usually identity and qualification evidence.
Retention is configurable. The published privacy policy will state the defaults; it does not exist yet.
Yes, in the platform audit trail alongside every other record access.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.