No leaver process fires for somebody who never joined. An engagement does not end on a date anybody experiences, it ends when work stops arriving, and that is why hardware issued to contractors and agency staff is the population most likely to never come back.
TL;DR
- An engagement ending is not an event. Nobody experiences it, so nothing triggers, which is the whole problem.
- The contract end date exists on day one. Put a review date 30 days before it with a named owner.
- For agency and studio staff, the relationship is with the firm and the device is with an individual. Both need recording.
- Ask the budget holder, not the agency, because the agency may not know the engagement has finished either.
- Time-bound the access at the point of granting it, which is the only mechanism that prevents rather than detects.
- If the device was issued for a short engagement, decide before it starts whether it is worth recovering at all.
Why nothing triggers
An employee leaving generates a date, a notice period, a leaver process and a dozen tasks. A contracted engagement finishing generates none of those. Work tapers, a final invoice arrives at some point, and the relationship fades rather than ending.
So the device recovery process never starts, because the event that normally starts it did not happen to anybody. The usual arrangement, where the budget holder is expected to tell IT, fails for the same reason: the budget holder did not experience an ending either.
That is a structural gap rather than a discipline problem, and it has a structural fix. The engagement has a contract end date that existed on the day it was signed, and that date is the only reliable trigger available.
The four fields that fix it
| Contract end date | The trigger | As signed, not approximate. Record open-ended as open-ended rather than guessing |
| Review date, 30 days before | Converts a surprise into a decision | Somebody is asked whether this continues, in time to act |
| Named renewal owner | Who gets asked | A person. Teams do not renew engagements, people do |
| Supplier, where there is one | Who you have the relationship with | So four individuals from one studio roll up to one agreement |
All four fit in a spreadsheet and none requires a system. The review date is the one doing the work, because it is the only thing that makes anybody look at an engagement before it has quietly continued for another quarter.
The agency case is different
When a studio or an agency provides people, the commercial relationship is with the firm and the devices are with named individuals who rotate within the engagement. That mismatch breaks most tracking arrangements.
Three consequences. You cannot ask the agency who currently has your laptops unless you asked them to track it. A person leaving the agency is invisible to you entirely. And ending the engagement cleanly means recovering from several individuals rather than one, which needs a list rather than a conversation.
So record the supplier above the individuals and ask for named changes as a condition of the arrangement. One line in the operational handover: tell us when somebody joins or leaves the engagement, with their name and email. Without it you are relying on noticing.
A worked example
A company compared its identity provider against its employee directory and found 212 accounts against 148 employees. The difference was 64 contracted individuals, agency developers and two design studios, every one granted access legitimately.
Nineteen of the 64 had finished their engagements. Four had finished more than a year earlier. Eleven of the nineteen also held a company laptop, and none of the eleven appeared on any list of devices to recover. The quarterly access review had been running against the employee directory for two years and reporting completion.
The fix was two things rather than a system: contract end dates with review dates in the existing contract sheet, and time-bound access set at the point of granting. Within two quarters the gap between the two lists was in single figures.
Getting the device back
What to do:
- Ask the budget holder 30 days before the contract end date whether the engagement continues.
- If it is ending, book the collection then, while the person is still working and reachable.
- Send packaging with the label inside, exactly as for an employee, since the stall point is identical.
- Ask the agency or studio to confirm which named individuals hold equipment, if you did not track it.
- Remove access on the contract end date by expiry rather than by a task somebody has to remember.
- Wipe on arrival, record the date and method, and close the register row.
The second point is the one that changes the outcome. A collection booked while somebody is still being paid for work is an appointment; the same request a month after their last invoice is a favour you are asking of somebody with no remaining relationship.
And decide in advance whether a device is worth recovering at all for a short engagement. A machine issued for six weeks is worth collecting; a four-year-old laptop issued to somebody in another country for a three-month piece of work may genuinely not be, and recording that decision beats discovering it after two months of chasing.
Disclosure: RemoAsset is owned by the same people who publish PeopleOpsHQ. It is relevant here because the collection can be driven from a recorded engagement end date rather than from somebody noticing, and because it holds the serial and the delivery address from the original order. It publishes no price and requires a demo, it is much weaker for hardware it did not supply, and it is not a certified disposal vendor. The options are compared in our laptop retrieval comparison.
Final thoughts
This population is not harder to recover from than employees. It is that the process which recovers from employees is attached to an event that never happens here, so nothing runs at all.
Record the contract end date, put a review date 30 days ahead of it with a named owner, record the supplier above the individuals, and set access to expire on the end date rather than relying on anybody to revoke it. Then recover exactly as you would from an employee, because once a trigger exists the mechanics are the same.
Frequently asked questions
Why do contractors keep company laptops after an engagement ends?
Because the engagement ending is not an event anybody experiences. An employee leaving produces a date, a notice period and a leaver process; a contracted engagement tapers, a final invoice arrives at some point, and nothing triggers. The usual arrangement where a budget holder tells IT fails for the same reason, since the budget holder did not experience an ending either. The only reliable trigger is the contract end date, which existed on the day it was signed.
What fields do you need to track contractor equipment?
Four, and they fit in a spreadsheet. The contract end date as signed rather than approximated, with open-ended recorded as open-ended rather than guessed. A review date 30 days before it, which converts an end date from a surprise into a decision somebody makes. A named renewal owner, because teams do not renew engagements and people do. And the supplier where there is one, so several individuals from one studio roll up to one agreement.
How do you handle devices with agency or studio staff?
Record the supplier above the individuals, because the commercial relationship is with the firm while the devices are with named people who rotate. Then make named changes a condition of the arrangement: one line asking the agency to tell you when somebody joins or leaves the engagement, with their name and email. Without that you are relying on noticing, and a person leaving the agency is entirely invisible to you.
Who should you ask when an engagement has ended?
The budget holder, 30 days before the contract end date rather than after it, and ask whether it continues rather than whether it has finished. Asking the agency is less reliable than it sounds, because an agency may not know the work has stopped either if the engagement simply went quiet. If the answer is that it is ending, book the collection in that same conversation while the person is still working and reachable.
How do you stop contractor access outliving the engagement?
Set the access to expire on the contract end date at the moment you grant it, which is the only mechanism that prevents the problem rather than detecting it afterwards. This is the one case where you know the end date on day one, so expiry costs nothing extra to configure. Where your identity provider does not support time-bound access, run a monthly reconciliation between active accounts and current engagements and act on the difference.
Is a short-engagement device always worth recovering?
No, and deciding in advance beats discovering it after two months of chasing. Set the collection cost, including packaging and somebody’s time, against the device’s residual value by age. A machine issued eight months ago is worth collecting almost anywhere. A four-year-old laptop issued to somebody in another country for a three-month piece of work frequently is not, and the right action is a recorded write-off at residual value with the register row closed.
