Responding when a work device goes missing
Report a missing work device promptly, assess stored data and account access, and coordinate supported containment, evidence and Canadian privacy review.

A missing laptop or phone can expose stored records and signed-in accounts. The response needs to address both, even if the device is personally owned and only used for work email.
Report the loss right away, using the route your business has set up for incidents. You don’t need to prove that someone has accessed the information before asking for help.
Give responders the facts you know
Use another trusted device or a known telephone number to reach the designated contact. Record the device, owner, last known location and approximate time it went missing.
Explain whether it was locked, which work applications it used and what records may be stored locally. Include authentication apps, saved browser sessions and any sign of theft.
Separate confirmed facts from assumptions. Keep any related messages and device-management records; don’t delete them.
Coordinate device and account containment
Have the people handling the incident check which lock, locate and management options the device supports. A feature may only work if it was set up beforehand, the platform supports it and the device receives the command.
Assess account sessions, recovery methods and tokens available from the device. Use each service’s supported containment procedure. A password change or central sign-out doesn’t guarantee that every application session ends immediately.
Revoking cloud access also doesn’t erase documents already downloaded. Encryption and the device’s locked state need their own assessment.
Choose removal actions carefully
Microsoft’s Intune action reference distinguishes actions such as retirement and wiping. Their availability and effects depend on the platform and enrolment.
Its wipe guidance explains that a wipe can remove personal and organizational data, with different options on different platforms.
Confirm ownership, authority, incident-evidence needs and the exact action before proceeding. Record whether the action completed. Sending a wipe to an offline device doesn’t mean it’s been erased.
Don’t remotely wipe a personal device on the assumption that any work use provides permission to remove everything.
Assess privacy obligations
Have the privacy lead identify the information, safeguards and likely access. A lost device isn’t automatically a reportable breach, and encryption shouldn’t be assumed effective without checking its state and key exposure.
The Privacy Commissioner’s business breach guidance explains PIPEDA obligations: report and notify where a breach poses a real risk of significant harm, and retain records of all breaches. Alberta and Quebec have their own breach reporting rules for private-sector organizations, and some sectors, such as health care, have more.
Use the Canadian incident-response guide to coordinate the assessment and decisions.
Recover work through a trusted route
Arrange a managed replacement and restore the records the user needs. Re-establish authentication securely, checking any recovery changes made during the response.
If the device is recovered, let IT assess it before reconnecting it to work systems. Avoid personally confronting someone based on a location report.
Review the incident for gaps in local storage, recovery contacts and management coverage. Test the revised process with harmless data before relying on it during another loss.


