Onboarding
The handoff from 'hired' to 'first day' is where hiring systems most often lose continuity.
The period between a candidate accepting an offer and their actual first day is a common point of process failure — not because any single step is hard, but because it usually involves a handoff between systems (the ATS, an offer-letter tool, an HRIS, a payroll system) that don't share data, forcing someone to re-enter the same information multiple times or, worse, lose it between handoffs entirely. This page covers what Expertini does and does not solve in that handoff.
On this page
01Offer generation and tracking
An offer — salary, currency, proposed start date, and any notes — is created directly from a candidate's application record and generates a formatted PDF offer letter carrying the employer's details, without needing a separate document tool. The offer's status (draft, sent, accepted, declined, withdrawn) is tracked in the system, and accepting an offer automatically moves the candidate to the "hired" pipeline stage rather than requiring a manual update.
02What stays with the record
Everything accumulated during hiring — the CMS score and its dimension breakdown, every interview's feedback, team notes, the accepted offer terms — remains attached to the candidate's application record indefinitely (subject to the same 24-month candidate-data retention policy described on the Candidate Experience page). A hiring manager or HR team member handling onboarding six weeks later has the full history available rather than a bare "hired" status with no context.
03What this doesn't do
Expertini ATS does not currently replace a dedicated HRIS, payroll system, or IT-provisioning workflow — it hands off a complete, structured record of the hiring process, but the actual mechanics of setting up a new hire's equipment, benefits enrolment, or payroll record happen in whatever systems an organisation already uses for those functions. We'd rather state this limitation plainly than imply a broader onboarding suite than currently exists.
04Why the offer-to-start gap matters more than it seems
The period between accepting an offer and a candidate's first day is when a meaningful share of accepted offers quietly fall through — a competing offer arrives, a counter-offer from a current employer changes the calculation, or simply too much silence from the new employer during a multi-week gap erodes a candidate's confidence in the decision. None of this is really an "onboarding" problem in the traditional sense of paperwork and equipment; it's a continuity-of-communication problem, and it's exactly where systems that don't share data between hiring and onboarding tend to go quiet at precisely the wrong moment.
Keeping the full hiring record — the interview feedback that made a team excited about this candidate, the notes on what mattered to them in negotiation, their actual start-date preference — attached and visible through this gap means whoever owns onboarding communication isn't starting from a blank "new hire" record with no context, which is a small thing that measurably affects whether that early enthusiasm survives the administrative gap before day one.
Platform architecture & operations
A1How this is architected in the platform
Onboarding is not a bundle of point products — it is a slice through one platform. The platform is deliberately server-rendered: every view is prepared by the application server and shipped as complete HTML, with no client-side framework, no third-party CDN scripts, and no build pipeline between the data and the page. What renders is what the server computed — the property that makes the interface auditable.
All persistence runs on a single search-native document store; every query carries the organisation's identifier as a mandatory filter at the lowest query layer. Tenant isolation is therefore structural — a property of how every request is composed — rather than a policy that relies on application code remembering to check.
Every capability referenced on this page resolves to a registered tool or connector: the tools directory and the integrations catalogue are renderings of the same registries the application enforces at runtime, so what this page describes and what the product gates can never drift apart.
A2Operational and audit posture
Screening is deterministic and published — the same inputs produce the same outputs, hard requirements block rather than average away, and the methodology is public on the research page. Actions that touch external systems are explicit and journalled per event; usage reporting aggregates the same journals the actions write, not a parallel telemetry system.
Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.
Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.
Frequently asked questions
Does accepting an offer automatically update the candidate's pipeline stage?⌄
Is the offer letter a legally binding employment contract?⌄
Does Expertini integrate with payroll or HRIS systems for onboarding?⌄
At a glance
- One-click PDF offer letter generation
- Offer status tracked: draft through accepted/declined
- Auto-move to Hired on offer acceptance
- Full hiring history retained through onboarding
- No manual re-entry of candidate data at handoff
- Not a replacement for payroll/HRIS/IT provisioning
See onboarding on your own hiring.
Bring a real job description to a 30-minute demo — free trial included.
Book a demo