Leaver return.
The leave date could book a return locker, and the deposit confirms the device is back before access closes.
Tools you may already run, plus the one that hands the device over.
From the first signal to a device in hand.
A leave date is set in Workday or SAP SuccessFactors.
ServiceNow books a return locker and schedules the access change in Microsoft Entra ID.
The leaver deposits the device, and the locker confirms it is back before their access closes.
The full sequence
- A leave date is set in Workday or SAP SuccessFactors.
- ServiceNow opens the leaver case and lists the assets to recover.
- Smart Collect® books a return cell at the leaver's site for their last days.
- The leaver gets return instructions and a code.
- They deposit each device, and the deposit confirms it is back.
- Access is disabled in Entra ID on the agreed date, with device returns already recorded.
- Anything still outstanding is chased with the leaver and their manager.
What you need in place
- Workday or SAP SuccessFactors as the HR system of record
- ServiceNow with leaver processing, and assets assigned to users
- Microsoft Entra ID for account access
- Smart Lockers at leavers' sites
How the pieces connect
- Workday or SAP SuccessFactors
- Sends termination events to ServiceNow through the HR integration or spoke.
- ServiceNow
- Runs the leaver case and lists every asset assigned to the user.
- Microsoft Entra ID
- Called through the IntegrationHub spoke to disable access on the agreed date.
- Smart Collect®
- Books the return cell and confirms each deposit, inside the same instance.
The physical steps stay the same, whichever system makes the decision.
Run this recipe from a standard ServiceNow workflow today, and let AI take the decision later. Nothing on the physical side changes.
One record of what was decided, and what physically happened.
A reference design for your technical team.
The Blueprint shows how this recipe would work in your ServiceNow instance and what a build would involve. It is a design, not a step-by-step installation guide.
- What you need in place. Workday or SAP SuccessFactors as the HR system of record · ServiceNow with leaver processing, and assets assigned to users · Microsoft Entra ID for account access · Smart Lockers at leavers' sites
- How the pieces connect. The role of Workday, SAP SuccessFactors, ServiceNow and Microsoft Entra ID and Smart Collect®, and what stays in your instance
- Step by step. All 7 steps, from the first signal to the returned device
- Approval and policy. Book returns automatically for every assigned laptop and phone.
- Handover rules and exceptions. Reservations, codes, expiry, returns, and what happens when stock runs out or nobody collects
- What to measure. Share of leaver devices recovered by the last day · Days from leave date to device recovered · Value of unrecovered devices per quarter
- What a build involves. The questions to settle first, the roles involved, and how we would scope a six to eight week pilot
Request the Blueprint
A four-page reference design for your technical team. Tell us who you are and the Blueprint downloads straight away.
Before you ask
What about people who work remotely?
The same leaver case can send remote leavers a courier route instead. Lockers serve the people who come into a site.
Is this an off-the-shelf integration?
No. It is a recipe concept that shows what becomes possible when these tools are combined with Smart Collect®. We build it with you, and where needed with the vendor, when it fits your estate.
Where does the data live?
In your own ServiceNow instance. Smart Collect® does not keep a separate database of your users or devices.
Do we need AI for this?
No. A standard ServiceNow workflow can run every step today. Otto or Flow can take over the decision later without changing anything on the physical side.