Hire to Retire

Why does the time it takes to make someone productive vary so widely for the same role?

Requisition approvedThe role is authorised
Exit completedThe obligation ends

Why this process resists visibility

The employee lifecycle is measured in separate pieces by separate functions and rarely assembled into one journey.

  • Each stage has its own measure

    Time to hire, time to onboard and payroll accuracy are each reported by a different team. The elapsed time from an approved role to a productive person is rarely reported anywhere.

  • The journey leaves the HR system repeatedly

    Access, equipment, workspace, cost centres and payroll sit with IT, facilities and finance, and the handoffs between them are often the least documented part of the process.

  • Provisioning failures are absorbed silently

    A new joiner without a laptop or an account waits, works around it, or is helped informally. The delay is real and often goes unrecorded.

  • Payroll corrections are treated as routine

    Retrospective adjustments are accepted as normal, so their volume, their repetition by team and the upstream errors that cause them can go uninvestigated.

  • Offboarding stops at the leaving date

    Access, assets, approvals and final settlement often remain open long after the person has gone, which is a security and audit exposure that tends to sit between functions.

Where time and effort accumulate

The process is normally drawn as six clean stages. Execution data shows what actually collects at each one, and how much of the cycle is spent waiting rather than working.

  1. Stage 1

    Requisition and approval

    • Roles raised ahead of approved budget
    • Approval chains re-run after every edit
    • Requisitions reopened and reposted
    • Incomplete job and grading data
  2. Stage 2

    Sourcing and selection

    • Candidates waiting between stages
    • Interviews rescheduled repeatedly
    • Feedback captured after the decision
    • Shortlists rebuilt from the beginning
  3. Stage 3

    Offer and pre-boarding

    • Offer approvals routed as exceptions
    • Contracts re-issued after correction
    • Background checks started late
    • Start dates moved after acceptance
  4. Stage 4

    Onboarding and provisioning

    • Access and equipment requested after the start date
    • Provisioning split across several teams
    • Day-one blockers reported by the joiner
    • Required training assigned but not completed
  5. Stage 5

    Payroll and changes

    • Changes entered after the payroll cut-off
    • Retrospective corrections and back pay
    • Approvals handled outside the system
    • The same change keyed into two systems
  6. Stage 6

    Movement and exit

    • Internal moves processed as new hires
    • Leavers notified to IT and payroll late
    • Access and assets left open after departure
    • Final pay and settlement corrected afterwards

What runs underneath all six

These four behaviours recur across the stages and often account for a large share of the cycle: work waiting in a queue without a clear owner, work looping back to a stage it already passed, work changing hands between teams with little record of the handoff, and the same employee journey type running through materially different routes depending on who touched it.

How RE-ViVE observes it

No process remodeling. No new workflow instrumentation. Read-only source access.

You provide the relevant source records and limited subject-matter support. RE-ViVE does the reconstruction and the analysis.

  1. Step 1

    Read-only extracts

    Requisition, candidate, employee, payroll and provisioning records from the systems that already hold them. Nothing is written back.

  2. Step 2

    Execution reconstructed

    RE-ViVE maps source records into its Execution Data Model, allowing each employee journey to be reconstructed across the systems involved.

  3. Step 3

    Followed end to end

    Each employee journey can then be followed from requisition approved to exit completed, with dwell time, loops and handoffs measured rather than estimated.

  4. Step 4

    Kept current

    The view refreshes as new hires, internal moves and exits are recorded, so the effect of any change is visible in the same measure.

What you are left holding

Evidence specific enough to act on, and traceable back to the individual employee journey behind it.

  • The journey people actually take

    Every path present in the data, from approved requisition to productive employment and eventual exit, ranked by volume and by the effort it consumes.

  • Where the days sit

    Elapsed time broken down by stage and split between work in progress and work waiting, including the wait a new joiner experiences before they can work.

  • Rework made countable

    Re-approvals, re-issued offers, rescheduled interviews, repeated provisioning requests and retrospective payroll corrections, counted and costed.

  • Cause attributed

    Delay and rework attributed by role, location, business unit, hiring manager and the function that owns each handoff.

  • Access and compliance exposure

    Provisioning that outlived a leaver, training that was never completed and approvals that were never closed, surfaced as evidence rather than assertion.

  • A monitored process

    Continuous visibility once the first view is built, giving a baseline that employee experience and automation changes can be measured against.

Where the evidence lives

Hire to Retire leaves a record in systems you already run.

  • HR information system
  • Applicant tracking
  • Payroll
  • Service management
  • Identity and access management
  • Learning management
  • Asset management
  • Finance and cost centres

RE-ViVE works with the systems an enterprise already runs, including platforms such as Workday, SuccessFactors, Oracle HCM and ServiceNow, along with other HR, recruitment and service platforms, payroll engines, identity tooling, spreadsheets and custom applications. Where execution moves outside the available system evidence, RE-ViVE makes the unexplained interval visible for investigation.

Processes next door

The employee lifecycle shares its evidence with the processes it depends on.

See how your employee lifecycle actually runs

Give us read-only access to the HR and provisioning data you already hold, and we will show you where people are waiting and where work is repeated.

See all processes