A Site Tablet Just Went Missing. Here's What Happens Next (If You're Managed).

Who This Is For

Anyone responsible for site devices when one of them doesn’t come home — office managers, IT leads, and superintendents who’ve had this exact phone call.

The Unmanaged Version of This Story

A tablet doesn’t turn up at the end of a shift. Here’s what that actually means, in an environment where devices were handed out but never enrolled in anything:

• Nobody’s sure what was on it. Cached emails, saved logins, project drawings, maybe a client contact list — “probably nothing important” is a guess, not an answer.
• There’s no way to lock it remotely. Whatever was on the device stays accessible to whoever has it now, for as long as the local passcode holds (if there was one).
• Replacement means starting from scratch. New device, manual setup, re-adding every app and account by hand, and hoping nothing sensitive leaked in the meantime — because there’s no way to confirm either way.

The Managed Version of This Story

Same incident, different starting point — the device was enrolled the day it was issued:

• The device can be located, or its last known location retrieved. Not always precise, but not nothing.
• Remote lock and wipe trigger immediately, from the same console that manages every other device, without waiting on the device to be recovered first.
• Nothing is actually “lost,” because nothing lived only on the device. Files synced to the managed source of truth, not the tablet’s local storage — the device itself was disposable.
• A replacement is provisioned and enrolled quickly, using the same compliance baseline the original device had, not a fresh manual setup.

What “Managed” Requires Before the Incident

The response above only works if this was in place before the tablet went missing:

• Enrollment at the point the device is issued — not “we’ll get to it,” which in practice means never, once the device is already in someone’s truck.
• Full-disk encryption verified, not assumed. A device can ship with encryption capability and still not have it turned on. Confirm it’s active, don’t take it on faith.
• A compliance baseline every new device inherits automatically — passcode requirements, app restrictions, remote-wipe capability — applied at enrollment, not configured device-by-device after the fact.

The Real Cost Comparison

A managed lost device is an inconvenience and a provisioning task: someone spends part of an afternoon setting up a replacement. An unmanaged lost device is a potential data-exposure incident — one that, depending on what was on it and who the client was, might require notification, and definitely requires an uncomfortable conversation about what “probably nothing important” actually covered.

The difference isn’t the device. It’s whether the five minutes of enrollment happened on day one.

What This Looks Like in Practice

Enrollment, encryption verification, and a compliance baseline are standard capabilities in Intune (Windows/Android) and equivalent MDM platforms for Apple hardware — this isn’t a custom build, it’s configuration that has to actually be turned on and applied to every device, including the one that’s already in the field. The gap is almost never “the tooling doesn’t exist.” It’s that devices were issued before anyone set the baseline, and retrofitting a fleet is a task people mean to get to.

The Bottom Line

A lost device is inevitable eventually — tablets get left on site, in trucks, at a client’s office. Whether that’s a shrug or an incident is decided entirely by decisions made before the device went missing, not anything done after.

This is a service we deliver. If this article describes your operation, skip the DIY weekend — see how we build it → or send the brief →.