The document landscape: what HR actually manages
The volume and variety of documents that an HR function manages across a workforce of any meaningful size is substantial. At the hiring stage, the documentation trail begins before employment: job applications, CV submissions, interview notes, assessment results, reference checks, offer letters and — once accepted — the employment contract itself. Each of these is a record of a decision made during the selection process and may need to be retained for legal defence if that decision is challenged.
During active employment, the document library grows considerably. Salary letters document every pay change. Annual performance reviews create a longitudinal record of how an employee has been assessed over time. Training completions, professional qualifications and certification records belong in the HR file for regulatory compliance in many industries. Right-to-work documentation — passports, visa records, work permits — must be stored and reviewed on expiry. Disciplinary proceedings generate investigation notes, hearing records and outcome letters. Grievances produce correspondence, investigation reports and resolution documentation. Each of these categories has its own retention requirement and its own access consideration.
Company-level documents — policies, handbooks, procedural guides, organisational announcements and terms and conditions of employment — require their own management alongside individual employee files. Version control is critical: when a policy is updated, the HR system must be able to distinguish the current version from prior versions, track which employees have acknowledged the current version, and retain old versions for the period during which claims might arise under the policy that was previously in effect.
At exit, the documentation requirement continues. Resignation letters, termination notices, settlement agreements, reference letters and final pay documentation all need to be stored and retained for the relevant period after the employment relationship ends. GDPR makes this retention period active rather than passive — it cannot be indefinite, it must be purposeful, and it must be followed by documented deletion at the appropriate time.
Problems with paper and fragmented digital files
Paper-based HR document management fails in several distinct ways. Physical security is the most fundamental: paper documents in filing cabinets cannot be encrypted, cannot have user-level access controls applied to them, cannot detect or log unauthorised access, and are vulnerable to physical theft, fire and flood in ways that cloud storage is not. An HR filing cabinet is a concentration of highly sensitive personal data with minimal technical protection.
Retrieval is the operational failure. When an employment tribunal claim arrives requiring access to an employee's disciplinary records from three years ago, the HR team must locate those records from physical files that may be organised inconsistently, may be stored in multiple locations and may have been misfiled at any point in the intervening period. The time cost of this retrieval under time pressure is significant — and the failure cost if documents cannot be found is potentially severe.
Fragmented digital storage — the typical evolution of paper-based systems, where documents migrate to a combination of shared drives, email attachments and cloud folders without centralised structure — creates different problems. Naming conventions drift: the same type of document is stored in different folders by different HR team members, under different filenames, without consistent metadata. Access control is folder-level, not document-level: giving someone access to an employee's general HR folder gives them access to all documents in that folder regardless of their specific need. Version control is nonexistent: when a policy is updated and the new version is dropped into the shared folder, the previous version may or may not be archived, and employees who download the document may end up with an old version without realising it.
GDPR creates the compliance dimension of this problem. Data subject access requests require an HR team to locate and compile all personal data held about an individual — including documents — and provide it within one month. Right to erasure requests require confirmation that data has been deleted across all storage locations. Neither obligation can be met reliably by a team that does not have centralised, structured storage with comprehensive search capability.
The Seven-Year Employment Record Myth
Many organisations apply a blanket "seven years" retention period to all HR documents, believing this covers their statutory obligations. In practice, retention requirements vary significantly by document type. Employment contracts are typically retained for six years after termination. Payroll records: six years. Disciplinary records: one to five years depending on outcome and severity. Medical and health records: duration of employment plus three to six years, with specific categories requiring longer periods. Recruitment records for unsuccessful candidates: typically six to twelve months under GDPR storage limitation principles. Applying a single retention period to all documents simultaneously over-retains some data (a GDPR breach) and may under-retain others (a compliance gap). A structured retention schedule by document category is the correct approach.
What a centralised HR document system provides
A centralised HR document management system is not simply a shared drive with better organisation. It is a structured system with specific capabilities that address the compliance, security, retrieval and retention requirements that HR document management demands.
Structured categorisation is the foundation. Every document uploaded to the system is assigned to a category — employment contract, performance review, disciplinary letter, right-to-work document, and so on — at the point of upload. This categorisation is mandatory, not optional, which means that every document has the metadata necessary for search, retention scheduling and access control from the moment it enters the system. Documents cannot be stored without being categorised, preventing the accumulation of unclassified files that makes retrieval and compliance management impossible.
Employee-level organisation ensures that every document is associated with the specific employee it relates to. When HR needs to retrieve all documents for a specific employee — for a data subject access request, an employment tribunal, an exit process or an internal audit — those documents can be retrieved as a complete set immediately, rather than by searching across multiple shared folders. The completeness of this retrieval is only as good as the discipline with which documents were filed when they were created, which is why structured categorisation at upload is critical.
Version control enables HR to maintain a complete document history. When a contract is amended, the amendment is stored alongside the original, with the version date recorded and the current version clearly marked. When a policy is updated, previous versions are retained (with their effective dates) in the system archive. This version history is practically important when disputes arise about what terms were in effect at a particular time, and legally important when claims are made under policies that have since been changed.
Document Management Module in Treegarden
Treegarden's document management module provides centralised, searchable storage for all employee documents with predefined folder templates per document category and configurable role-based access. Documents are organised within each employee's record, categorised at upload using a structured type system that ensures consistent metadata. Search spans the full document library — by employee name, document category, date range or content — returning results immediately rather than requiring manual folder navigation. All documents are stored with encryption at rest and in transit, with access logging for every retrieval event.
Security requirements: access control and encryption
The security requirements for HR document storage are more demanding than those for general business documents because HR documents contain concentrated personal data — precisely the data that attackers seek and that regulators scrutinise most carefully when investigating breaches.
Encryption at rest and in transit is the baseline technical requirement. Documents should be encrypted when stored on disk, ensuring that unauthorised access to the underlying storage does not expose document contents. Data transmitted between the user's browser and the document storage system should be encrypted in transit using current TLS standards. Encryption key management should be documented — keys should be rotated on schedule and access to keys should be restricted to the minimum necessary personnel.
Role-based access control determines who can see which documents. The access model should be granular: different roles should have different permissions across different document categories. An HR generalist may have read access to most employee document categories but not to medical records. A payroll administrator may have access to salary letters and right-to-work documents but not to disciplinary records. A line manager may have access to their direct reports' performance review records but not to their personal data or medical documentation. These distinctions must be enforced at the system level — not by instructions to staff about which folder they should and should not open.
Audit trails record every interaction with the document system: who accessed which document, when, and what action they took. These logs serve multiple compliance purposes. Under GDPR, data subject access requests may require disclosure of who has accessed an individual's personal data and when. Audit trails also support internal investigations when a data breach or inappropriate access is suspected. For regulated industries, audit trails demonstrate to regulators that access controls are enforced and monitored rather than merely documented in a policy.
Retention policies and compliant deletion schedules
Retention management is one of the most practically neglected areas of HR document compliance. Most organisations have a retention policy — they have stated, in a document, how long different types of records should be kept. Far fewer organisations actually implement that policy, because implementation requires a systematic mechanism for tracking which documents have reached their retention period and a process for reviewing and deleting them. Without this mechanism, retention policies are aspirational rather than operational.
A compliant retention system assigns a retention period to every document category at the point of document creation or upload. For employment contracts, the retention clock starts at the date of employment termination and runs for six years (or the locally mandated period). For recruitment records, the clock starts at the point the candidate was notified of an unsuccessful application. For disciplinary records, the clock may start at the date of the disciplinary outcome, with different durations depending on the severity of the sanction.
When documents reach the end of their retention period, the system should generate a review notification — not automatically delete the document, because there may be active litigation, a regulatory investigation or another specific justification for extended retention that the HR team needs to assess. The review process confirms whether an exception applies or whether deletion should proceed. Deletion, when it occurs, should be a secure deletion process that removes the document from storage, and the deletion event should be logged for the audit record. This log — confirming that a document was deleted at a specific date — is itself part of the compliance record.
Compliance Retention Engine
Treegarden's retention engine allows HR teams to configure retention periods by document type — employment contracts, payroll records, disciplinary letters, right-to-work documents and other categories each carry their own schedule. When a document reaches its configured review date, the system generates an automated notification to the assigned HR administrator, presenting the document details and prompting a retention decision: delete, extend with documented reason, or reassign to a different retention category. Every decision is recorded in the audit log with the reviewer's identity, timestamp and the reason given — creating a comprehensive compliance record without requiring manual tracking in a spreadsheet.
Electronic signatures: removing the paper bottleneck
The employment contract signature process illustrates the inefficiency of paper-based document workflows with particular clarity. The traditional process: HR prepares the contract, prints two copies, posts or couriers them to the new employee, waits for the signed copies to be returned, scans the signed copies, files the scan and stores the original. This process takes days and sometimes weeks, creates multiple physical handling points where documents can be lost, and requires a physical presence or postal system that is increasingly difficult to coordinate for remote or internationally dispersed hires.
Electronic signatures compress this process to minutes. HR prepares the contract digitally, sends it through the e-signature workflow, and the new employee signs using a click-to-sign interface from any device. The signed copy is automatically generated and filed in the employee's HR record. HR receives a completion notification and can confirm the signed contract is on file immediately — no waiting for post, no scanning, no physical filing.
The legal validity of electronic signatures for employment contracts is established by legislation in the UK (Electronic Communications Act 2000), the EU (eIDAS Regulation 910/2014) and most other jurisdictions. Simple electronic signatures — a typed name in a signature field, or a click-to-sign acknowledgement — are sufficient for the vast majority of employment documents. The evidential weight of an electronically signed document is supported by the audit trail that e-signature platforms generate, showing who signed, when, from which IP address and that the document has not been modified since signing.
Beyond contracts, electronic signatures apply to: contract amendments, additional agreements (such as non-disclosure or non-compete clauses), policy acknowledgements, settlement agreement sign-offs, and any other HR document that currently requires a wet signature but does not have a legal requirement for one. The cumulative time saving across a year's worth of employment documentation events is considerable.
Electronic Signature Workflow
Treegarden's e-signature workflow allows HR to send any employment document for digital signature directly from the HR system. The recipient receives an email with a secure link, reviews the document in their browser and applies their signature using a click-to-sign process that works on any device without requiring software installation. The fully signed document is automatically generated, timestamped and filed in the employee's HR record. HR receives a completion notification and can view the audit trail confirming signature identity, timestamp and document integrity — providing the evidential record that validates the electronically signed contract.
Searchability and audit: finding documents when you need them
The true test of a document management system comes at the moment of urgent need: an employment tribunal claim, a data subject access request, a regulatory audit or a dispute about the terms of someone's employment. In that moment, the HR team needs to find specific documents quickly, with confidence that the search is complete — that there are no relevant documents that the search has missed.
A properly implemented centralised document system makes this search reliable and fast. Searching by employee name returns all documents filed under that person's record, across all categories, in chronological order. Searching by document type returns all documents of that category across the workforce — useful for compliance audits that require reviewing whether a specific document exists for every relevant employee. Searching by date range allows HR to retrieve the documents that were active during a specific period. Full-text search across document content (where documents are stored in searchable formats) allows retrieval by keyword when the specific document type or date is not known.
The audit trail — which records every access event, every modification, every upload and every deletion — serves a different but equally important retrieval function. When a dispute arises about whether a specific document was received, reviewed or acknowledged, the audit trail provides the factual record. When a data subject access request requires disclosure of who has accessed an individual's data, the audit trail provides the answer. When an internal investigation requires understanding who accessed a specific document and when, the immutable audit log is the authoritative source.
Index Documents at Upload, Not at Search
The time to apply consistent naming and categorisation to a document is when it is added to the system — not when someone needs to find it six months later under time pressure. HR document management systems that enforce mandatory metadata fields at upload (document type, employee, date, author) create a searchable index as a by-product of normal document storage. Systems that allow documents to be filed with minimal metadata create a storage problem that only reveals itself when urgent retrieval is required and the document cannot be found quickly. The investment in metadata discipline at upload pays compound dividends every time a search is needed.
Frequently asked questions about HR document management
What documents does an HR department typically manage?
HR departments manage a wide range of documents across the employment lifecycle. At hiring, these include job applications, interview notes, assessment results, offer letters and employment contracts. During employment, they include performance reviews, salary letters, training records, right-to-work documentation, disciplinary records, grievance correspondence and absence documentation. At exit, they include resignation letters, termination notices, settlement agreements and exit interview notes. Supporting all of this is a library of company documents — policies, handbooks, procedural guides and organisational announcements — that require version control and distribution management.
How long do HR documents need to be retained?
Retention periods vary significantly by document type and jurisdiction. Employment contracts are typically retained for the duration of employment plus six years. Payroll and tax records are generally retained for six years in the UK and similar periods across the EU. Disciplinary records may be retained for one to five years depending on the nature of the matter. Health and safety records for workplace injuries or occupational exposure may be retained for 40 years in some jurisdictions. Medical records have their own specific requirements as special category GDPR data. HR teams should establish a documented retention schedule that specifies periods for each document type, reviewed by employment counsel, rather than applying a single blanket retention period.
What is an electronic signature and is it legally valid for employment contracts?
An electronic signature is a digital confirmation of agreement — ranging from a typed name in a designated field to a cryptographically secured unique signature. Under the EU eIDAS Regulation and equivalent UK legislation, electronic signatures are legally valid for most employment documents including contracts of employment, amendments, policies and offer letters. Simple electronic signatures (a typed name or a click-to-sign) are sufficient for most employment documents. The practical effect is that employment contracts can be signed and returned electronically in minutes rather than requiring printing, signing, scanning and emailing.
What is the difference between a document management system and a shared drive?
A shared drive provides storage and access but no structure beyond what users impose manually. Documents can be stored anywhere, named inconsistently, accessed by anyone with folder permissions and never deleted. A document management system provides structured metadata, mandatory categorisation at upload, role-based access controls, version history, retention scheduling, audit trails and search capabilities. For HR documents, this distinction is significant because compliance requires knowing what documents exist, who has accessed them, how long they should be retained and when they need to be deleted — none of which a shared drive tracks automatically.