Governed Employee Document Management — from Onboarding Through Offboarding and Beyond — on AWS Infrastructure You Control
HR departments manage some of the most sensitive, legally consequential, and retention-intensive documents in any organization. Offer letters, employment contracts, I-9s, tax withholdings, policy acknowledgments, performance reviews, disciplinary records, benefits enrollments, accommodation requests, separation agreements, and COBRA notices — every employee generates a document trail that spans years or decades and crosses multiple regulatory jurisdictions.
Yet most HRIS platforms treat documents the same way CRM and ERP systems do: as file attachments. Employee documents get uploaded to the HRIS record with no independent metadata, no document-level access controls, no retention policies tied to employment law, and no archival strategy for the years (sometimes decades) that employment records must be preserved after separation. FormKiQ provides governed document management and archival storage for employee and HR content — deployed directly into your AWS account, integrated with your HRIS through the HRIS Integration Framework Module, and managed under access controls, retention policies, and audit trails designed specifically for the confidentiality requirements and regulatory complexity of employment documentation.
The HRIS Document Problem
HRIS platforms are designed to manage employee data and HR processes, not documents. This creates structural gaps that create legal risk and operational inefficiency:
| HRIS Limitation | Business Impact | FormKiQ Resolution |
|---|---|---|
| Documents as attachments | Employee documents uploaded to HRIS records with no independent classification or governance | Documents stored as governed records with structured metadata, document type definitions, and independent lifecycle management |
| No document-level access control | Anyone with access to the employee record can see every attached document — no separation between routine HR documents and sensitive records | Attribute-based access control (ABAC) at the document level — medical records, accommodation requests, investigation files, and compensation details restricted independently |
| No jurisdiction-aware retention | Retention tied to the HRIS record — no ability to apply different retention periods based on document type, jurisdiction, or regulatory requirement | Configurable retention by document type, jurisdiction, employment status, and regulatory framework |
| No legal hold | No mechanism to preserve individual employee documents for litigation or investigation independent of the HRIS record | Legal hold at the document level with audit trail, independent of employee record status |
| No full-text search | Documents searchable only by employee name or HRIS fields — not by document content | Full-text search powered by Amazon OpenSearch across all employee documents |
| No post-separation governance | When employees leave, documents remain in active HRIS storage indefinitely or are deleted with the record — no archival lifecycle | Automated archival with retention enforcement that continues after separation, independent of HRIS record status |
| Audit trail gaps | HRIS logs record-level changes, not document access events | Every document access, view, download, and modification logged — critical for sensitive HR records |
| Storage cost | HRIS storage priced per employee or per GB at premium rates | Documents stored in Amazon S3 with tiered storage from active through archival |
How FormKiQ Integrates with HRIS Platforms
FormKiQ's HRIS Integration Framework Module connects employee records to governed document collections. The HRIS remains the system of record for employee data; FormKiQ becomes the system of record for the documents the employment relationship produces.
Integration Architecture
HRIS System → FormKiQ
Employee Record ── link ──▶ Employee file (governed)
Onboarding Event ── trigger ──▶ Onboarding workflow + documents
Role Change ── trigger ──▶ Policy re-acknowledgment workflow
Leave Event ── trigger ──▶ Leave documentation workflow
Separation Event ── trigger ──▶ Offboarding workflow + archive
Employee data remains in HRIS | Documents + Metadata + Retention + Access + Audit in FormKiQ
What the Integration Framework Does
| Capability | Description |
|---|---|
| Employee record linking | Employee records linked to their governed document collection in FormKiQ via deeplinks and metadata cross-references |
| Metadata synchronization | Employee data (name, department, location, employment status, hire date, separation date) mapped to FormKiQ document metadata — keeping document classification current as HRIS records change |
| Event-driven automation | HRIS lifecycle events (new hire, role change, location transfer, leave, separation) trigger document workflows in FormKiQ — onboarding packet generation, policy re-acknowledgment, offboarding document collection, archival scheduling |
| Organizational mapping | Department, division, and location structures mapped from the HRIS to FormKiQ access control and metadata — ensuring documents are visible to the correct HR team and management chain |
| Post-separation lifecycle | When an employee separates, documents transition to post-separation retention and archival automatically — with retention periods calculated from the separation date based on document type and jurisdiction |
The Employee Document Lifecycle
Employee documents follow a lifecycle tied to the employment relationship — not to a transaction or project. FormKiQ manages each phase:
| Lifecycle Phase | Documents Created or Collected | FormKiQ Governance |
|---|---|---|
| Recruitment | Applications, resumes, interview notes, reference checks, background check results | Classification, access restriction to hiring team, retention per hiring record requirements |
| Offer and Acceptance | Offer letters, employment agreements, compensation letters, relocation agreements | Version control, eSignature, retention from hire date |
| Onboarding | I-9, W-4/W-9, direct deposit authorization, benefits enrollment, emergency contacts, policy acknowledgments, equipment agreements, training certifications | Document collection workflows, completeness tracking, eSignature, HRIS metadata synchronization |
| Active Employment | Performance reviews, goal-setting documents, training records, policy re-acknowledgments, compensation changes, promotion letters, commendation records | Version control, approval workflows, annual cycle tracking, access controls by management chain |
| Sensitive Events | Accommodation requests, statutory leave documentation (FMLA in US; parental, family, or medical leave under applicable jurisdiction), workers' compensation, disciplinary records, investigation files, grievance documentation | Heightened access controls (ABAC), restricted visibility, separate from routine HR file, legal hold capability |
| Separation | Resignation letters, termination documentation, separation agreements, exit interview records, COBRA notices, final pay documentation, non-compete agreements | Offboarding workflow, eSignature for separation agreements, transition to post-separation retention |
| Post-Separation Archive | Entire employee file — retained per jurisdictional requirements | Automated archival, jurisdiction-aware retention (1–30+ years depending on document type), legal hold, defensible disposition |
Access Control for Employee Documents
Employee documents demand the most granular access control of any document type in the organization. A single employee file may contain routine HR documents visible to the immediate manager alongside medical records, investigation files, or accommodation requests that must be restricted to specific HR roles:
| Access Control Layer | What It Controls | Example |
|---|---|---|
| Employment status | Active vs. separated employee documents — different access rules post-separation | Active employee documents visible to current manager and HR; separated employee documents restricted to HR and legal |
| Document sensitivity | Sensitive documents restricted independently within the employee file | Medical records, accommodation requests, and investigation files visible only to designated HR roles — not to the employee's manager |
| Management chain | Documents visible to the employee's direct management chain based on HRIS organizational structure | Performance reviews visible to direct manager, skip-level manager, and HR business partner |
| HR role | Access differentiated by HR function — recruiting, benefits, compensation, employee relations, compliance | Compensation documents visible to compensation team and HRBP; benefits documents visible to benefits team |
| Jurisdiction | Documents governed by jurisdiction-specific rules accessible only to HR personnel authorized for that jurisdiction | EU employee documents accessible only to HR personnel operating under GDPR-compliant access policies |
| Legal and investigation | Investigation files, litigation-related documents, and legal hold records restricted to employee relations, legal, and designated investigators | Workplace investigation files visible only to investigating HR representative and legal counsel |
Document Generation for HR Workflows
FormKiQ's Document Generation module automates the production of employee documents, triggered by HRIS events:
| HRIS Trigger | Generated Document | What Happens Next |
|---|---|---|
| New hire created | Offer letter generated from template with compensation, title, start date, and location data | Routed to hiring manager for review, then to candidate via eSignature |
| Offer accepted | Onboarding packet generated — I-9 instructions, benefits enrollment forms, policy acknowledgment bundle | Distributed to new hire; completeness tracking workflow initiated |
| Role change | Updated employment letter, revised policy acknowledgments for new role/department | Routed for eSignature; updated documents filed in employee record |
| Annual review cycle | Performance review templates generated for each employee with pre-populated data | Distributed to managers; completed reviews collected and filed |
| Separation initiated | Separation agreement, exit checklist, COBRA notice, final pay documentation | Routed through HR and legal review; eSignature for separation agreement |
| Policy update | Updated policy acknowledgment forms distributed to affected employees | Tracked distribution with completion monitoring and follow-up workflow |
eSignature Integration for HR Documents
FormKiQ's eSignature Integration streamlines the signature-intensive nature of HR document workflows:
- Offer letters and employment agreements — routed to candidates and new hires for electronic signature
- Policy acknowledgments — bulk distribution with individual signature tracking and completion monitoring
- Benefits enrollment forms — annual open enrollment signature workflows
- Performance reviews — employee and manager acknowledgment signatures
- Separation agreements — multi-party signing with legal review gates
- Return and classification — signed documents returned to the employee file with execution metadata and audit trail
Post-Separation Retention
Employment record retention is uniquely complex because retention periods vary by document type, jurisdiction, and regulatory framework — and the retention clock typically starts from the separation date, not the document creation date:
| Document Category | Typical Retention Requirement | Regulatory Driver |
|---|---|---|
| I-9 forms | 3 years from hire or 1 year from separation, whichever is later | IRCA (US) |
| Tax withholding (W-4) | 4 years after tax is due or paid | IRS (US) |
| Payroll records | 3–7 years depending on jurisdiction | FLSA, state wage laws |
| Benefits enrollment | 6 years from plan year | ERISA (US) |
| FMLA records | 3 years from leave event | FMLA (US) |
| OSHA records | 5 years from incident; medical records 30 years post-employment | OSHA (US) |
| Discrimination and harassment records | 1–7 years depending on jurisdiction; indefinite if litigation pending | EEOC, state civil rights statutes |
| Workers' compensation | Varies by jurisdiction — 5–30 years | State workers' compensation statutes |
| Employment contracts | 4–10 years post-separation depending on jurisdiction | State contract and limitation statutes |
| Employee medical records | 30 years post-employment (for exposure records) | OSHA 29 CFR 1910.1020 |
| Canadian employment records | 3–7 years depending on province and document type; payroll records typically 6–7 years; human rights complaints 1–2 years post-resolution | ESA (Ontario and other provinces), provincial employment standards, Canadian Human Rights Act, provincial human rights codes |
| EU/UK employment records | 6 years from separation (general); longer for pension and health records | GDPR, UK GDPR, national employment legislation |
| Australian employment records (Fair Work) | 7 years for pay records, time and wages records; general employee records during employment and typically 7 years after | Fair Work Act 2009 (Australia); state industrial relations legislation |
| UK employment records | Payroll records 3 years from end of tax year; contracts and disciplinary records typically 6 years post-separation; working time records 2 years | Employment Rights Act 1996, HMRC requirements, UK GDPR, Working Time Regulations 1998 |
FormKiQ supports jurisdiction-aware retention — different retention periods applied to different document types within the same employee file, with the retention clock configured to start from separation date, hire date, or another defined reference point.
AI-Powered HR Document Processing
FormKiQ's AI Processing and Analysis module — powered by Amazon Bedrock — automates classification and extraction for HR documents:
| AI Capability | HR Document Application |
|---|---|
| Document type classification | Automatically classify incoming HR documents — offer letters, tax forms, benefits enrollment, policy acknowledgments, performance reviews — and file to the correct section of the employee record |
| Metadata extraction | Extract employee name, employee ID, effective dates, compensation figures, and other key data from HR documents |
| Sensitivity classification | Identify documents containing medical information, accommodation details, investigation content, or other sensitive data for heightened access controls |
| Completeness analysis | Analyze onboarding document sets for completeness — flagging missing required documents before the employee's start date |
| Policy acknowledgment verification | Verify that policy acknowledgment documents are properly signed and dated |
All AI processing runs within your AWS account through Amazon Bedrock. Employee document content never leaves your cloud environment.
FormKiQ Editions for HRIS Document Management
HRIS document management and archives require the HRIS Integration Framework Module, available on Advanced and Enterprise editions:
| Capability | Core | Essentials | Advanced | Enterprise |
|---|---|---|---|---|
| Document Storage (S3) & API | ✓ | ✓ | ✓ | ✓ |
| Tagging, Search & Classification | ✓ | ✓ | ✓ | ✓ |
| OCR (Tesseract) | ✓ | ✓ | ✓ | ✓ |
| OCR & IDP (Textract) | ✓ | ✓ | ✓ | |
| SSO (SAML — Entra, Google, Auth0) | ✓ | ✓ | ✓ | |
| Workflows, Queues & Rulesets | ✓ | ✓ | ✓ | |
| Encryption (in-transit & at-rest) | ✓ | ✓ | ✓ | |
| Document Control & Versioning | ✓ | ✓ | ✓ | |
| Antivirus & Anti-Malware | ✓ | ✓ | ✓ | |
| HRIS Integration Framework | ✓ | ✓ | ||
| AI Processing & Analysis (Bedrock) | ✓ | ✓ | ||
| Document Generation | ✓ | ✓ | ||
| eSignature Integration | ✓ | ✓ | ||
| Document Gateway Modules | ✓ | ✓ | ||
| Enhanced Full-Text Search (OpenSearch) | ✓ | ✓ | ||
| Multi-Instance & Multi-Region Licensing | ✓ | ✓ | ||
| Vendor-Managed & Hybrid Deployment | ✓ | |||
| Custom SLAs & Compliance Consulting | ✓ | |||
| Support | Community (Slack & GitHub) | Support Portal (2-business-day SLA) | Private Slack + videoconference + 40 hrs onboarding | Rapid response (8-business-hour SLA) + strategic architecture support |
Who Uses HRIS Document Management and Archives on AWS
| Industry | HR Document Challenges | Key Drivers |
|---|---|---|
| Healthcare | Clinical staff credentialing, licensure tracking, OSHA exposure records, BAA acknowledgments across high-turnover environments | OSHA 30-year exposure record retention, HIPAA (US), HSE (UK), Safe Work Australia, provincial OHS legislation (Canada), Joint Commission requirements |
| Financial Services | Licensing documentation, background checks, compliance training records, compensation documentation | FINRA, SOC 2 (US), FCA (UK), APRA (Australia), OSFI (Canada), applicable state/provincial licensing requirements |
| Manufacturing | Safety training records, OSHA documentation, workers' compensation files, union documentation across multiple facilities | OSHA retention (US), HSE (UK), provincial OHS legislation (Canada), Safe Work Australia, multi-facility access control, union/collective agreement compliance |
| Government & Public Sector | Civil service documentation, classification records, security clearance documentation, pension records | NARA (US), UK National Archives, Library and Archives Canada, relevant national civil service requirements, security clearance retention |
| Higher Education | Faculty tenure documentation, credential verification, adjunct records, student employee files across campuses | FERPA (student employees), tenure review documentation, multi-campus governance |
| Technology | Global employee records across jurisdictions, equity documentation, visa and work authorization, remote worker compliance | Multi-jurisdiction retention (GDPR + state law), work authorization tracking |
| Retail & Hospitality | High-volume onboarding, seasonal employee documentation, multi-location compliance, minor work permits | High-turnover document volume, state-specific minor labor laws, multi-location access control |
HRIS Migration Resilience
Organizations change HRIS platforms as they grow, merge, or consolidate operations. When employee documents live only inside the HRIS, every migration risks document loss, retention gaps, and audit trail breaks — particularly for separated employees whose records must be retained for years or decades after their departure.
FormKiQ decouples employee document governance from the HRIS platform:
- No document migration during HRIS transitions — employee files stay in FormKiQ; only the integration layer is reconfigured for the new HRIS
- Post-separation retention uninterrupted — retention policies continue to enforce regardless of HRIS transition timing or vendor
- Complete employment document history preserved — every onboarding document, performance review, and policy acknowledgment remains accessible across HRIS generations
- No audit trail breaks — the document audit trail is continuous, which matters most for ongoing litigation, regulatory inquiries, and employment tribunal proceedings, human rights commission investigations, EEOC investigations (US), or equivalent regulatory proceedings that span HRIS platforms
- Multi-HRIS environments supported — organizations operating multiple HRIS platforms (through M&A or regional differences) can maintain a single governed employee document repository
Deployment Models
| Model | Description | Availability |
|---|---|---|
| Customer-Managed AWS | Deploys directly into your AWS account via CloudFormation. Full control of infrastructure, networking, encryption keys, and operations. | All editions |
| Vendor-Managed | FormKiQ manages the AWS infrastructure on your behalf — deployment, updates, and operational support. | Enterprise |
| Hybrid | You retain control of specific components (encryption keys, network config) while delegating operational management to FormKiQ. | Enterprise |
Every deployment is a dedicated, isolated instance in an AWS account owned by or designated by the customer. FormKiQ does not operate a shared multi-tenant environment.
Getting Started
FormKiQ Core can be deployed to your AWS account in fifteen to twenty minutes using a one-click install via AWS CloudFormation. HRIS Integration Framework, Document Generation, eSignature Integration, AI Processing, and Enhanced Full-Text Search are available on FormKiQ Advanced and Enterprise.
For organizations evaluating HRIS document management on AWS, FormKiQ offers a Proof-of-Value program — a three-month deployment in a FormKiQ-managed AWS environment that provides full platform access in a non-production setting.
Frequently Asked Questions
What is HRIS document management on AWS?
HRIS document management on AWS refers to managing the documents generated by and associated with the employment relationship — offer letters, tax forms, policy acknowledgments, performance reviews, benefits enrollment, and separation documents — in a governed document management platform deployed on Amazon Web Services, rather than as unmanaged file attachments within the HRIS itself.
Why not just use my HRIS's built-in document storage?
HRIS document storage treats employee documents as attachments to employee records. It doesn't provide document-level access controls (separating sensitive medical records from routine HR documents within the same employee file), jurisdiction-aware retention policies, legal hold, full-text search across document content, or cost-optimized archival storage for the years or decades that employment records must be preserved after separation.
Does FormKiQ replace my HRIS?
No. Your HRIS remains the system of record for employee data — personal information, employment status, compensation, benefits, organizational structure. FormKiQ becomes the system of record for the documents the employment relationship produces. The two systems are connected through the HRIS Integration Framework, with HRIS lifecycle events triggering document workflows in FormKiQ.
How does FormKiQ handle sensitive HR documents like medical records and investigation files?
FormKiQ provides attribute-based access control (ABAC) at the document level. Within a single employee file, routine HR documents can be visible to the employee's manager and HR business partner, while medical records, accommodation requests, and investigation files are restricted to designated HR roles. Access to sensitive documents is logged in the audit trail with timestamps and actor identification.
How does FormKiQ handle retention for employees in different jurisdictions?
FormKiQ supports configurable retention by document type, jurisdiction, and regulatory framework within a single employee file. For example, an I-9 (US) or equivalent work authorization document can have a different retention period than a performance review, and both can differ from occupational health and safety medical records (OSHA in US, HSE in UK, provincial OHS in Canada) — even within the same employee file. Retention clocks can be configured to start from hire date, separation date, or other defined reference points. For multi-jurisdiction organizations, different retention rules can apply to the same document type based on the employee's location.
What happens to employee documents after separation?
When an employee separates, FormKiQ automatically transitions their document file to post-separation retention. Retention periods are calculated from the separation date (or other configured reference point) based on document type and jurisdiction. Documents are archived to cost-optimized S3 storage tiers while remaining searchable and subject to access controls. Legal holds can be applied to preserve documents for ongoing litigation or investigation regardless of retention schedule.
What happens to employee documents when we switch HRIS platforms?
Employee documents managed in FormKiQ are independent of the HRIS platform. When you migrate to a new HRIS, your employee files, metadata, retention policies, access controls, and audit trails all persist — only the integration layer needs to be reconfigured. This is particularly important for separated employee records, which must be retained for years after departure regardless of which HRIS is in use.