Lost or Stolen Work Device
The Lost or Stolen Work Device page gives employees a clear route to report a missing work device, share useful facts without sending secrets, and follow up on replacement and return instructions.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Professional services · Healthcare · Manufacturing · Education
Overview
The Lost or Stolen Work Device page is a focused employee reference for reporting a missing organization-issued device and making the initial handoff clear. Its example guidance asks employees to contact their designated IT reporting route promptly, share the device type, last known location, time noticed missing, and available asset identifier, and clearly flag suspected theft or possible exposure of sensitive work information. A worked example and table show how to separate observed facts from uncertainty and what not to include, such as passwords, sign-in codes, or recovery keys.
Use this page when employees need a quick answer about who to contact, what details to provide, and what to do if the missing device was their usual way to access help. It also clarifies that the IT Service Desk receives the initial report and explains the replacement request route, while Information Security assesses reports escalated for suspected theft or possible exposure. Replacement availability, approvals, protective actions, and specialist handoffs remain governed by the organization’s own procedures.
This page is not a device-tracking tool, incident intake form, security response procedure, or promise of a replacement. Before publishing, add verified reporting and alternate contact routes, confirm the handoff roles, and replace or clearly retain the fictional Northstar Works example as sample content. Do not use it as the sole source for breach notification, account recovery, or local legal requirements; link to the organization’s authoritative procedures where applicable.
Standards & compliance context
- The page supports timely internal reporting by directing employees to the organization’s designated route, but it does not establish legal reporting deadlines or breach-notification duties.
- Organizations should link this guide to their authoritative security, privacy, and incident-response procedures rather than treating it as a substitute for them.
- The instruction not to send credentials or recovery secrets reduces unnecessary exposure in an initial report; receiving teams should use approved secure channels for any additional sensitive information they require.
- Use clear headings, readable table labels, and accessible contrast, and verify the page against WCAG 2.1 AA so employees can use it across devices and assistive technologies.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Report a missing work device promptly
This warning establishes the immediate action and clarifies that the page guides employees but does not monitor incidents.
-
Northstar Works is a fictional large, multi-site employer used for this example. If an organization-issued device is missing, contact your organization’s designated IT reporting route as soon as you can. If you suspect theft or the device may contain sensitive work information, say so clearly so the receiving team can route the report. This notice is employee guidance; it does not monitor incidents.
What to do
These ordered actions explain how to contact the designated team, share relevant details, request a replacement, and keep the follow-up clear.
-
Use your organization’s approved reporting and replacement routes. Worked example: “My work laptop was last with me on the 8:10 train between Central and North stations. I noticed it missing at about 9:00. The asset label reads NW-4821. I believe it may have been left on the train; I have not included any passwords or sign-in codes.” If you suspect theft, state that instead of describing it only as misplaced. Contact the designated reporting team Use your organization’s approved IT reporting route. If you cannot access it, use the verified alternate route published by your organization. Report suspected theft or possible exposure of sensitive work information explicitly; the receiving team determines any specialist handoff. Share the useful facts Give the device type, when and where you last had it, when you noticed it was missing, and any asset label or device identifier you can read. Say whether you believe it was lost or stolen and whether work information may be on it. Do not send passwords, sign-in codes, recovery keys, or other secrets. Request a replacement through the normal route Ask the designated IT team how to request a replacement and what work arrangements to use while you wait. Replacement availability and any approval steps depend on your organization’s process. Keep the handoff clear Note the report reference if the team provides one, and use the contact route they give you for updates. If you later find the device, tell the reporting team before using or returning it; follow their instructions.
A clear report, without unnecessary secrets
The example table shows which incident details help the receiving team and which sensitive or unverified information to leave out.
-
The same fictional incident as the worked example above. Separate observed facts from uncertainty. Report detail Example entry Keep out of the report Device Work laptop, asset NW-4821 Passwords, recovery keys and sign-in codes Last known location 08:10 train between Central and North stations Unrelated travel or personal history When noticed missing Approximately 09:00, after leaving the train A guessed time presented as certain Concern to flag May have been left on the train; theft is not confirmed Unverified allegations stated as facts
If the missing device was your usual way to get help
This guidance offers a safe fallback when the employee cannot use the missing device to reach the usual reporting route.
-
Use a verified alternative contact method your organization has provided. If you do not have one, tell a known manager or workplace contact that you need the designated IT reporting route. Explain that you cannot use the missing device to receive a response, and agree on a way the receiving team can reach you. Keep the report reference and any instructions the receiving team provides. Let the authorized team decide the account, device and information-protection actions; this page does not establish those procedures.
Who handles the next step
These role descriptions distinguish the initial IT report from the assessment of suspected theft or possible information exposure.
-
Receives the initial device-loss report and explains the organization’s replacement request route. IT Service Desk Assesses reports escalated for suspected theft or possible exposure of sensitive work information. Information Security
How to use this template
- Replace the Northstar Works example details with clearly marked sample content or remove them, then add the organization’s verified IT reporting route and alternate contact method.
- Confirm with the IT Service Desk and Information Security who receives the initial report, what replacement route employees should use, and which reports require specialist assessment.
- Publish the page where employees can find it without signing in on the missing device, and check that the alternate route is reachable through another approved method.
- Ask employees to report the device type, last known location, time noticed missing, available asset identifier, and any suspected theft or possible work-information exposure without sharing secrets.
- Have employees keep any report reference, use the response route provided by the receiving team, and notify that team before using or returning a device they later find.
- Review the page whenever contact routes, team responsibilities, or replacement procedures change, and remove outdated examples or instructions.
Best practices
- Put the verified reporting route and a usable alternate contact method near the top of the page so an employee without the device can still act.
- Label fictional incident details as examples and replace the Northstar Works asset identifier before adapting the page for internal use.
- Keep the report checklist limited to observable facts: device type, last known location, time noticed missing, and a readable asset identifier.
- Tell employees to label uncertainty plainly and avoid stating theft, exposure, or a precise time as confirmed when it is not.
- Repeat the warning not to send passwords, sign-in codes, recovery keys, or other secrets in any linked intake instructions.
- Verify that the named IT Service Desk and Information Security roles match the organization’s actual handoff before publication.
- State the replacement request route without implying that a replacement is automatic or that a particular approval timeline applies.
- Assign a content owner and review the page when contact details or reporting responsibilities change.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What situations does this page cover?
It covers a missing organization-issued device, whether it may have been misplaced or stolen. It also explains what to report if work information may be on the device. It is employee guidance, not an incident-monitoring system or a device recovery tool.
How quickly should an employee report a missing device?
The sample guidance says to contact the organization’s designated IT reporting route as soon as possible. The page does not set a universal reporting deadline, so organizations should add any confirmed internal timing requirement. Employees should state when they noticed the device was missing and distinguish that from the last time they know they had it.
Who receives the report and handles follow-up?
The IT Service Desk receives the initial report and explains the organization’s replacement request route. Information Security assesses reports escalated for suspected theft or possible exposure of sensitive work information. The receiving team determines any specialist handoff; employees should use the route and instructions their organization verifies.
What information should be included, and what should be left out?
Include the device type, asset label or identifier if available, last known location, when it was noticed missing, and whether theft or exposure of work information is suspected. Mark uncertain details as uncertain rather than presenting them as facts. Do not send passwords, sign-in codes, recovery keys, or other secrets.
Does this guide replace security or regulatory incident procedures?
No. The page directs employees to report the incident and flags suspected theft or possible exposure for the receiving team to assess. It does not define breach notification, account protection, investigation, or legal reporting procedures. Link it to the organization’s approved security and privacy procedures before publishing where those procedures are available.
What should an employee do if the missing device was their only way to contact IT?
Use a verified alternate contact method supplied by the organization. If none is available, tell a known manager or workplace contact that the designated IT route is needed, and agree on a way for the receiving team to respond. The organization should fill in and verify the alternate route rather than leaving employees to guess.
How should we customize this template for our organization?
Replace the fictional Northstar Works examples and asset details with clearly labeled sample content or remove them, and add the organization’s verified IT reporting and alternate contact routes. Confirm the actual replacement request process and the correct security escalation path with the responsible teams. Keep the instruction not to share credentials or recovery secrets.
Does this page connect to an incident system or device-management integration?
No live integration or reporting workflow is specified in this page structure. It provides employee-facing instructions and names the teams responsible for the next step. Add a link or connected component only when the organization has configured and verified that destination.
How is this guide better than an informal message to a manager?
It gives employees a consistent set of facts to report, cautions them against sharing secrets, and distinguishes observed details from uncertainty. It also identifies the initial IT recipient and explains how to handle an unavailable reporting route. A manager may help locate the approved route, but the page directs the report to the designated receiving team.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
-
Compare clinical communication platforms and workforce apps for hospitals. Learn how to reach frontline healthcare staff without EHR logins in 2026.
-
See how automated credential checks, labor rules, and real-time coverage tracking give charge nurses a schedule they can trust before every shift.
-
Clinical Staff Engagement with MangoApps: unify schedules, training, and HR self-service in one mobile app for frontline healthcare teams.
-
Healthcare employee engagement ideas to reduce burnout, boost retention, and improve patient outcomes in your health system.
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Lost or Stolen Work Device ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
