The transfer that reached three systems and one record: onboarding and employee movement software

A supervisor was promoted to site in-charge in March. Payroll was told, because her pay changed. The HRMS was not, so the org chart still showed her old manager and her old team, and the leave requests from her new team continued to route to someone who had moved to a different site. The attendance system knew nothing about either move. Nobody found out until a new joiner on her site asked who approved his leave and three people gave three different answers.

Nothing was hidden. A movement had happened, and the systems that needed to know about it had each been told separately, or not at all. Onboarding and movement software exists to make one event change everything it should, once.

JOIN      record created; role, manager, location, cost centre;
          access, assets, inductions, probation date
TRANSFER  location, manager, cost centre; site induction;
          access adjusted; roster moved
PROMOTE   grade, designation, manager, pay; approval limits;
          new access; team reassignment
EXIT      the mirror of JOIN: everything issued, returned;
          everything granted, revoked

Each is a dated event with an owner, that starts
tasks for HR, IT, payroll, the manager and the site.

Seeing the four as one workflow is what changes the design. A transfer is a partial exit from one site and a partial join to another; a promotion is a change of role with the same person; an exit is a join in reverse. A system that handles joining well and treats the others as record edits will produce exactly the situation in the opening, because the edits do not start the tasks.

The first day is the wrong trigger for onboarding for the same reason the last day is the wrong trigger for exit: it relies on someone acting on the day. The reliable trigger is the accepted offer. From that moment, IT has a task to provision access dated to the first day, facilities has a desk or a locker or a uniform to prepare, the manager has an induction plan to confirm, and the joiner has documents to submit through a portal rather than by email on the morning they arrive. A joiner whose access works at nine on the first day has been onboarded by a system; one who waits a week has been onboarded by memory.

1. 1

   Documents before day one

   Collected through a link, checked against a list, stored against the record. Not photographed on a phone on the first morning.

2. 2

   Access provisioned to the start date

   IT's task appears at acceptance with the date on it. What is provisioned is recorded against the person, because it is the exit list later.

3. 3

   Assets issued and recorded

   Laptop, phone, uniform, keys, ID card — each with a date and a signature. This is the return list at exit and the change list at transfer.

4. 4

   Induction and probation scheduled

   The site or role induction on the first day; the probation review date set now, so it cannot be missed later. This is the confirmations that never get missed, made automatic.

The recording of what was issued is the step that pays for itself twice: it is the list that a transfer adjusts and an exit reverses. Businesses that skip it at joining spend the exit guessing what to recover, which is how a leaver keeps access for three weeks.

The promotion in the opening reached payroll and nowhere else because there was no single place a movement is logged from which the others are told. The system's job is to be that place: the movement is entered once, against the system of record for each field, and every copy — payroll, attendance, the org chart, the roster, access — is updated or notified from there. This is the change-control discipline of employee information management with the tasks attached. Without the tasks, the record is right and the site still does not know.

• One movement form, one approver. A transfer is approved by whoever has the authority, in the system, and nothing changes until it is.
• Effective date, not entry date. The movement takes effect on a date; the record shows both what is true now and what will be true then.
• Downstream tasks, named. Payroll adjusts pay from the effective date; the roster moves the person; the old site's access ends and the new site's begins.
• History kept. The record shows the sequence of roles, managers and locations, dated — the answer to 'who was her manager in February' a year later.

The probation review is the movement most often lost, because it is a date rather than an event — nobody resigns or transfers to trigger it. The system sets it at joining, reminds the manager thirty days out, and requires a decision: confirm, extend, or end. A missed confirmation date in a system is a task overdue with a name beside it; in a spreadsheet it is a discovery made at appraisal. The same applies to a promotion's probation, where one is applied, and to the review point on an internal move that the employee movement process should build in.

Movements go wrong at the approval step more often than at the record step. A manager agrees a transfer with another manager over the phone, one of them tells HR, and the record is updated before anyone with the authority to approve a cost-centre change has seen it. Three months later finance asks why a salary moved between budgets. The system's job is to hold the movement in a pending state until the named approver acts, and to make the pending state visible — so a transfer everybody assumes has happened, but which is waiting on an approval nobody sent, is a task overdue rather than a mystery. Configure the approval matrix once, by movement type and by what changes: a location move needs one approver, a pay change another, a promotion both.

Head office sees movements as records. A site sees them as people arriving and leaving, and the site supervisor needs their own view: who joins next week, who is transferring in, who is on probation and due for review, who is leaving and what they must return. A system that serves only HR leaves the site working from a message somebody remembered to send. The supervisor's view — on a phone, for the sites that have no desk — is what makes movement real where the work is.

Onboarding, movement and exit belong together, in the system that holds the employee record, feeds payroll and — ideally — runs the roster. A standalone onboarding tool handles joining nicely and hands the record to somebody else at the end of week one, which is where the promotion in the opening went missing. The onboarding and employee movement module of an HRMS that also holds attendance and payroll inputs is the version in which one event actually changes everything it should.

Test it with a transfer, not a joiner: move a fictional person from one site to another in the demo, and check what the old site, the new site, payroll and the roster each see. Joining is the case every vendor has polished. The transfer is where onboarding and employee movement software is either doing the coordination or leaving it to memory.