Build your own HR system: ATS, onboarding, and employee records

What to look at first

HR systems handle sensitive data, so permissions and audit logs matter from day one.

• Define HR workflows.
• Map employee data.
• Set permissions.
• Automate onboarding tasks.

What the result should be

HR gets one controlled workflow instead of scattered files and subscriptions.

Make the decision from the operating process

A unified HR workflow helps when recruitment, onboarding and records are fragmented. Sensitive data makes minimisation, role-based access, retention and audit logs first-release requirements.

• Separate candidate, employee and manager access.
• Define where AI may only support, never decide.

A realistic operating example

An accepted candidate triggers contract, equipment and access tasks. Offboarding revokes accounts and records evidence. AI summarises documents but does not make employment decisions.

A controlled implementation sequence

Deliver the smallest complete workflow first. Test exceptions with the people who perform the work before adding more features.

• Design roles and data categories.
• Build tasks, documents and approvals.
• Run privacy and security tests.

Measure adoption and operating value

Set a baseline before launch and review both business results and manual recovery.

• Onboarding completion time.
• Late access removal and unauthorised access.

Important limits and safeguards

Avoid black-box scoring of candidates or staff. Keep decisions explainable, reviewable and human.

Design one employee lifecycle with clear boundaries

A custom HR system becomes valuable when recruitment, contracts, onboarding, leave and offboarding are spread across products and inboxes. Map the transition from applicant to employee and former employee. Information should not move forward indefinitely: interview notes have a different purpose and retention need from an employment contract. For every phase, state the responsible role, permitted audience and point of deletion or archive.

• Candidate, application, vacancy and review.
• Offer, contract, screening and start date.
• Onboarding, equipment, accounts and training.
• Leave, development, records and changes.
• Offboarding, access removal and retention.

Separate workforce data by task and sensitivity

A manager does not need the complete personnel file to approve leave. Finance, IT and recruitment each need different fields. Define permission by data category and action, not job title alone. Sensitive documents receive stricter access, logging and retention. Use secure invitations and multifactor authentication for administrators, and test that exports, search and notifications cannot disclose information outside the intended role.

• Self-service for personal records and documents.
• Manager rights limited to their team and task.
• HR access by file category and responsibility.
• Technical administration without default content access.
• Audit reading, changes, exports and deletion.

Automate onboarding and offboarding as connected workflows

A signed contract can trigger equipment, identity, training, scheduling and welcome tasks, each with an owner, deadline and proof. Offboarding needs even tighter control: accounts close on time, assets return and handover is recorded. Share only required fields with identity, payroll and planning. Failed synchronisation must enter an owned work queue rather than silently leaving access active.

• Templates by role, location and contract type.
• Dependencies between contract, screening and access.
• Reminders and escalation for incomplete work.
• Access blocked on the agreed final date.
• Regular reconciliation of HR status and active accounts.

Use AI as an assistant, not an invisible assessor

AI can structure CVs, summarise documents, answer policy questions and draft communication. It should not independently reject, score or promote people. Define permitted data, show evidence and uncertainty and keep authorised people responsible. Test language and outcomes for systematic differences. Corrections can support evaluation, but should not quietly create a new permanent profile of staff or applicants.

• Objective extraction with a link to evidence.
• Draft communication with human review.
• Permission-aware assistant over approved HR sources.
• No sensitive inference or hidden productivity scores.
• Explainable criteria and genuine reconsideration.

Deliver modules and measure process quality

Start with a coherent module such as onboarding and offboarding instead of replacing payroll, ATS and performance at once. Migrate only necessary, checked records. Have employees and managers test realistic exceptions and provide support. Track cycle time, missed tasks, delayed access removal, corrections and HR enquiries. Add the next module only after stable use and clear ownership of content, workflow and integrations.

• Baseline time, error and manual hand-off.
• Pilot across contract types and exceptions.
• Reconcile old and new employee status.
• Privacy and security testing before wider rollout.
• Named owners for content, workflow and connections.