Damaged or Lost Rental Units: Reporting and Responsibility

Damaged or lost units are a certainty on any reasonably sized fleet. What separates organisations is not whether it happens but how quickly and methodically it is handled.

This article sets out a flow that can serve as standing procedure, so handling does not depend on whoever happens to receive the report.

First Principle: Report Quickly, Do Not Repair It Yourself

The temptation to repair lightly damaged units in-house is considerable, especially when the damage looks trivial. For rented units, this is almost always a costly decision.

Disassembly or third-party repair generally affects liability terms in the contract. Damage originally covered by the provider can shift onto you purely because the unit was opened.

The same principle applies to component substitution, including apparently simple items such as power adapters. Using an adapter that does not meet specification is a frequent point of dispute.

Handling Damage

Secure the unit and stop using it. Damage that is worked around often develops into something worse, and that increases the cost.

Document the condition. Photograph the damage from several angles, including a photo showing the serial number. Record when and how the damage occurred according to the user.

Compare against handover documentation. If the condition existed from the beginning, that documentation resolves any disagreement. The documentation procedure sits in our rental handover article.

Report to the provider with complete information: serial number, damage description, photos, and urgency level. State whether the user is currently unable to work, because that affects replacement priority.

Handling Loss

Loss must be treated as a security incident rather than simply a missing asset. The order differs from damage.

Revoke all access for that device first, before any administrative matter. Remove it from device management, revoke certificates and network profiles, cancel stored sessions server-side, and remove it from trusted device lists.

If the device supports remote wiping and remains reachable, trigger it. If not, encryption enabled from the outset is your primary layer of protection.

Only then report to the provider and follow internal administrative process. This order matters because every hour of delay in revoking access adds risk.

Record the incident in writing, including what data was likely on the device. For organisations with data protection obligations, this record is required.

Limiting the Costs

Good handover documentation is the most effective cost control. Without it, every mark of use can potentially be counted as damage.

The boundary between fair wear and damage is best agreed in the contract. Light usage marks on a palm rest differ from a cracked screen, and that boundary is better written down than interpreted during a dispute.

Reporting quickly also limits cost, because spreading damage is more expensive than the original fault. A loose hinge left alone eventually damages the chassis.

For large fleets, keeping spare units reduces the time pressure that usually causes procedure to be skipped.

Turning It into Procedure

Create a single reporting sheet covering serial number, user, incident date, description, photos, and actions already taken. Designate who is authorised to contact the provider so there are no duplicate reports or mutual waiting.

Communicate one thing to all users: reporting damage early will not cause problems for them, while concealing it will. Many faults become expensive precisely because they were reported late.

Separating Fair Wear from Damage

The boundary between the two is the most common source of end-of-contract dispute, and the best way to avoid it is agreeing that boundary at the start rather than when units are already on the inspection table.

Fair wear is marks arising from normal use as intended. Examples include shine on the palm rest, key legends beginning to fade, and fine scratches on the lid from repeated placement in a bag.

Damage is anything affecting function or structure. Cracked screens, broken hinges, loose ports, dented casings and liquid damage fall here.

There is a grey area worth naming explicitly in the contract: deep scratches clearly visible from normal distance, adhesive residue from labels, and surface discolouration. All three get argued over because they do not affect function yet are not ordinary wear either.

Ask for these terms in writing before signing, and keep them with handover documentation. The format sits in our rental handover article.

Building a Reporting Flow That Does Not Depend on Individuals

Incident handling that depends on whoever happens to receive the report produces inconsistent outcomes. Several things make it consistent.

Establish one point of entry for reports. Users need not know who handles it, only where to report.

Establish who is authorised to contact the provider. Without this, providers can receive two different reports for one unit, or none at all because each party assumed the other had reported.

Establish internal deadlines for each stage: how quickly a report must reach the provider, and when to escalate if no response arrives.

Provide a simple form covering serial number, user, incident date, description, photos, and actions already taken. An overly long form will not get filled in.

Keep all reports in one place so recurring patterns become visible. A unit failing repeatedly is a different signal from a unit failing once.

Measuring Impact on Work, Not Only on Assets

When a unit fails, the largest cost is usually not the repair but the work that stops.

So when reporting to the provider, state the impact on work. A user unable to work at all carries different urgency from a user working with limitations.

Keep spare units so users can resume immediately while replacement proceeds. Without spares, the entire process duration becomes downtime. This is covered in our spare units article.

For roles that must not stop at all, agree faster replacement terms during contract negotiation rather than requesting them mid-incident.

Record downtime duration for every incident. That figure later becomes the basis for judging whether the agreed service terms are genuinely adequate.

Preventing Incidents Recurring from the Same Cause

Some incidents are not random but consequences of conditions that can be fixed.

If several units in one department suffer similar physical damage, examine how units are carried and stored there. Inadequate bags are the most common and most easily corrected cause.

If port damage recurs, examine how cables are unplugged and whether desks use docks. Desks with docks reduce unplugging events dramatically.

If liquid spills recur in one area, review where drinks are placed in that workspace.

If losses recur on a particular travel pattern, review the policy on carrying devices. This is covered in our physical device security article.

Addressing shared causes is far cheaper than treating every incident as an isolated event.

Frequently Asked Questions

Who bears the cost of damage?

It depends on cause and contract terms. Damage from unit defects generally falls to the provider, while damage from negligent use generally falls to the renter. The boundary should be clear from the start of the contract.

How quickly do replacement units usually arrive?

That depends on the agreed service terms. State the urgency level when reporting, because providers prioritise by impact on work.

Does a loss need reporting to the authorities?

For losses outside the office, an official report is often requested as part of administrative process. Ask the provider about requirements when reporting.

In Short

Reporting speed and documentation quality are the two factors that most determine the final cost. Both can be prepared long before the first incident occurs.

References & Sources

Under Indonesian law, a lessee's liability for damage to rented goods is set out in Article 1564 of the Civil Code (KUHPerdata); an explainer (in Indonesian) is at Klinik Hukumonline (accessed 24 September 2026). For handling a loss as a security incident, see NIST SP 800-61 Rev. 3 — Incident Response Recommendations (accessed 24 September 2026) and Microsoft's guide Find and lock a lost Windows device (accessed 24 September 2026).