Onboarding software: move the start date

Start with the system you already pay for

This brief assumes 200 employees, 40 hires a year, an existing HRIS and separate IT service management. It evaluates coordination from accepted offer to day-one readiness. Country-specific employment checks and forms remain separate requirements; a workflow demonstration does not establish legal eligibility.

Start with the incumbent because a second platform adds a second configuration to maintain. Invite a specialist when the existing process cannot reach the required participants, handle changes or expose unfinished work. Do not replace payroll to obtain a better welcome sequence unless payroll itself needs replacing.

The vendor examples below illustrate documented behaviours, not a product ranking. They are deliberately different: a journey tool, an HRIS, an onboarding product and an enterprise suite. The question is which behaviour your purchased configuration can demonstrate.

Run the three-hire test

Use fictional records only. Run the test on 2 November 2026, with a simulated clock if available. Define all offsets below as calendar days; agree a local time zone and dispatch time separately. These are procurement assumptions, not statutory deadlines. If the vendor cannot simulate time, schedule the test and retain the resulting evidence before acceptance.

For O01, a seven-days-before task moves from 2 November to 16 November; a two-days-before reminder moves from 7 November to 21 November. For O02, the same preparation deadline moves from 16 November to 27 October. It is already late on the test date. A neat future schedule for O01 tells you nothing about O02’s recovery.

Keep the initial export or screenshots, then change the date once in the agreed source system. Record where each downstream value changes, where it stays fixed and who resolves the difference. Do not let the demonstrator repair the evidence off-screen.

Who hears about the new date?

Enboarder documents an option to notify participants about key-date changes. It must be enabled before the change. The described recipients are stakeholders who have already received at least one sequence. Participants who have not yet received a sequence need a separate notification plan.

In O01, include a manager who has received a sequence and an IT owner who has not. Require the vendor to show the intended communication route for both. A person whose task is rescheduled may need an update now, even if their original reminder was due later.

Check the employee-facing message too. It should make the revised date clear without sending an irrelevant second welcome packet. Previously delivered messages cannot be treated as though they never existed; the correction needs its own understandable communication.

Keep the signed version

SAP’s public start-date article distinguishes changes before, during and after Manage Pending Hires. It says that reflecting a new date in completed tasks or forms requires restarting onboarding; already signed documents cannot simply have their date changed, so the e-signature step must be triggered again through restart.

Test which tasks restart, which records are preserved and who receives new assignments. In O01, request the original document, replacement if required, their dates and the outstanding signature status. A dashboard that says “complete” while everyone refers to a different version fails this test.

The authorised HR owner decides which documents need correction under the employer’s process. The demo must show how that decision is carried through. Do not use an actual employment contract or real candidate identity in this exercise.

Today can be too late for today’s trigger

Personio’s lifecycle-survey guide says date triggers are evaluated at 06:00 UTC and past trigger dates are ignored. Its example explains why changing a hire date to today after that evaluation does not activate an event-date workflow that day. This is evidence about that documented workflow, not a claim that all Personio tasks behave identically.

Use O02 to ask a better question than “does it update automatically?” Show the missed trigger, the visible exception and the authorised way to recover it. If a manual task is the agreed recovery, that can pass. A hidden missed action cannot.

Greenhouse separates when a task is assigned from when it is due, and supports assignment after another task completes. Changing a due date therefore needs a second inspection of assignment and dependencies. A task with the correct deadline is useless if its owner never receives it.

A ticket is a request for work

Enboarder’s Jira guide describes pushing data to create an issue. That establishes an outbound request, not laptop delivery, app access or completion of the ticket. In O01, retain the original issue identifier and establish how its dates are updated or reconciled. In O03, distinguish cancelling the HR workflow from cancelling an already accepted order.

Ask the IT operator to show the receiving system’s state. If an order cannot be cancelled automatically, the purchase may still work with an explicit exception, an owner and evidence of resolution. “The integration ran” is an inadequate answer to “does this person still have an active account?”

Replay O03’s original accepted-hire event after withdrawal, in the test environment. The result must not silently create another laptop order or another active onboarding journey. The supplier can prevent, detect or reconcile the duplicate; require an observable outcome and include any manual effort in the operating cost.

Handle a withdrawal

SAP’s cancellation documentation says a pending hire awaiting workflow approval cannot be cancelled until that workflow is completed, rejected or deleted. It also says signed documents stored in its document system remain after onboarding cancellation. Those are different states: process cancelled does not mean every record deleted.

For O03, require an explanation of both the pending-approval route and the ordinary cancellation route. Record stopped future messages, unresolved external work and retained records under the employer’s chosen retention process. Do not demand blanket deletion as a substitute for understanding what happened.

Personio distinguishes a delayed start from a correction after employment has begun; changing the hire date also affects reporting and calculations. Its guidance for former employees uses a new employment/profile rather than merely reactivating an old one. That does not establish the right route for a candidate who never started. Demonstrate O03’s later return separately from a former employee’s rehire, preserving each history without silently reviving withdrawn tasks.

Five outcomes decide acceptance

Use the following record for each of O01–O03. Mark each row demonstrated, supported by an agreed manual procedure, or unresolved. Record the product edition and integration configuration alongside it. This is a buying test, not a claim that we have run the named products.

If a step remains manual, name its owner and include the time in your cost estimate. Do not mark the case complete until the outstanding work is resolved. Record one accountable internal owner for the combined result.

Do not inflate the business case

For the fictional 40-hires-a-year employer, suppose four start dates change and each takes 45 minutes to reconcile. That is three hours a year. At an assumed loaded cost of £45 an hour, the capacity value is £135. It is neither cash automatically saved nor a vendor price. This small repair workload alone is a poor argument for buying another platform.

A larger purchase may be justified by the whole onboarding workload, readiness failures or communication needs. Measure those separately. Request the incremental subscription, required base modules, integration setup, messaging charges, ongoing maintenance and implementation support. Keep internal time separate from supplier cash.

Use the test to count the date changes, messages and IT requests that HR would still have to chase. Compare that work with the cost of the proposed software.

Questions buyers ask