End-of-Contract Collection: Preparing Without Chaos

Collection day is often the messiest day of the rental cycle. The cause is almost always the same: preparation begins only once the provider confirms a schedule, when several steps require days of lead time.

This article works backwards from the collection date so every step has adequate room.

Four Weeks Before: Reconcile the Unit List

Start by matching the list of units received against where they are now. For fleets that changed hands during the contract, the original list is almost certainly inaccurate.

The most frequent problem is units held by employees who have changed departments or left. The earlier this surfaces, the greater the chance the unit is found.

If any unit cannot be traced, report it now rather than on collection day. The process takes time and cannot be resolved at short notice.

Three Weeks Before: Give Users a Deadline

Communicate the collection date and the deadline for users to move their personal files. Without a firm deadline, this step invariably causes delay.

Also communicate what must come back with the unit: adapter, bag, dock, cables and mouse. Missing accessories are the most frequent source of additional charges after damage.

For users working outside the office, determine the return method now.

Two Weeks Before: Ensure Work Continuity

If replacement units are arriving under a new contract, ensure the schedules overlap rather than run consecutively. Even a one-day gap means the whole team cannot work.

Migrate work files to the new units and verify everything functions before releasing the old ones. This verification is frequently skipped and causes problems once the old units have gone.

One Week Before: Data Security and Access Revocation

This is the step that must never be rushed, and precisely the one most often squeezed for time.

Revoke device access from management systems, networks and trusted device lists. Wipe data according to its category. The full procedure sits in our company data on unit return article.

Record the evidence per unit. That record is what you will need if questions arise later.

Collection Day: Joint Inspection

Gather all units in one room before the provider arrives, complete with accessories. Hunting for units while the provider waits is the main source of chaos.

Inspect condition jointly with the provider, compare against original handover documentation, and record differences on the spot. Comparing directly is far better than receiving a one-sided report days later. The documentation procedure sits in our rental handover article.

Ensure the collection record is signed by both parties and that you keep a copy, complete with the serial number list.

Damaged or Dead Units

Non-functioning units must still go through the same process. These are precisely the units most likely to leave without procedure, even though their storage still holds data.

If a device cannot be powered on to be wiped, state this in writing to the provider and agree how it will be handled.

Building a Per-Unit Checklist

An orderly collection depends on one simple thing: every unit having its own line to tick rather than being processed as a group.

That line covers serial number, last user, whether files were migrated, whether access was revoked, whether data was wiped, whether accessories were gathered, and whether condition was photographed.

Processing by group sounds faster but almost always leaves gaps. When asked which unit has not yet been wiped, a group record cannot answer.

Establish that collection is only scheduled once every line is ticked. Scheduling first creates time pressure, and time pressure is the most common reason security steps get skipped.

For large fleets, split the list by location or department and assign an owner to each.

Handling Units Scattered Outside the Office

Units not physically in the office are the biggest source of delay, and handling them must begin considerably earlier.

Identify early who holds units outside the office: remote employees, field teams, and users currently posted at client sites.

Determine the return method for each and communicate the deadline. Return shipping takes time that cannot be compressed on the final day.

Ensure data security happens before units ship rather than after they reach the office. A unit travelling while still holding company data is an avoidable risk. The procedure sits in our preparing devices for remote employees article.

For employees who have already resigned but whose units have not returned, handle these as separate cases with their own deadline, because resolution usually takes longer.

Keeping Work Running During Changeover

The mistake with the most visible consequence is scheduling collection of old units before new ones are genuinely ready to use.

Ensure new unit arrival and old unit collection overlap rather than run consecutively. Even a one-day gap means the whole team stops working.

Migrate files and verify users can genuinely work on the new unit before releasing the old one. This verification is often skipped because it feels like a formality, yet problems only surface once the old unit has gone.

For users with specialised configurations, allow more time. Specialist applications and customisations accumulated over years do not always transfer automatically.

For large fleets, change over in phases by group rather than all at once. This reduces preparation load and limits the impact if something goes wrong.

Frequently Asked Questions

How long does this take for a large fleet?

For dozens of units, the four-week window above provides comfortable room. What matters is not the unit count but how many units are dispersed outside the office.

What if the contract is partially extended?

Separate the lists from the outset. Units continuing and units returning should be physically grouped apart so they are not mixed at collection.

Do users need to be present at collection?

Not necessarily, provided units have been gathered and inspected beforehand by the responsible team.

In Short

An orderly collection is the product of four weeks of preparation rather than quick thinking on the day. What matters most is reconciling the unit list early, because a unit whose location is unknown cannot be prepared.

References & Sources

Data sanitisation before a device changes hands follows NIST SP 800-88 Rev. 2 — Guidelines for Media Sanitization (accessed 24 September 2026). Under Indonesian law, a lessee's duty to return goods in the condition they were received is set out in Articles 1562–1564 of the Civil Code (KUHPerdata); an explainer (in Indonesian) is at Klinik Hukumonline (accessed 24 September 2026).