Municipal Laptop Security: Plan for a Missing Work Device

Make the first call before the search is finished

Imagine a township employee returning from a building visit and discovering that the work laptop is missing. The employee is checking the meeting room and vehicle while the office needs that afternoon’s documents. A useful plan gives staff a reporting contact, gives IT enough information to identify the device, and gives the department a way to continue approved work.

For Michigan townships, villages, and cities, treat a missing work device as something to report promptly while checking likely locations. The employee does not need to prove that it was stolen or decide whether information was exposed. Those assessments belong with the responsible technical team and municipal leadership. Staff should know how to reach both through an approved channel without using the missing laptop.

Keep a device record the office can find

Maintain a record of each issued laptop’s asset tag, serial number, assigned employee, and support contact. Keep it in an approved location accessible to the people handling the report. A description such as the clerk’s silver laptop can start a conversation, but a specific identifier helps IT distinguish that device from a spare or an older computer still listed in inventory.

For a hypothetical village office with a shared meeting laptop, record who has checked it out and how it is returned. Ask IT to connect the inventory record with its management record and document when protection settings were last reviewed. Include the staff reporting instructions, but keep passwords and encryption recovery keys out of the ordinary checkout sheet.

Confirm drive protection before the laptop travels

Microsoft describes BitLocker as Windows drive encryption that helps address data theft or exposure from lost or stolen devices. Ask IT to verify that the intended drives are encrypted and protection is active on each Windows work laptop. A sign-in screen alone does not establish that the stored files have that protection. Record the verification result and date in the technical inventory.

Automatic Device Encryption has its own requirements and setup behavior. Have IT check the actual state rather than assuming a new computer arrived fully protected. Ask how protection is rechecked after maintenance or replacement. For other operating systems, have the technical team verify the appropriate encryption and recovery arrangement. Encryption also leaves a separate question to answer: where can staff obtain the working documents if the laptop never returns?

Give recovery keys an approved home

An encrypted laptop can require a recovery key after certain hardware or startup changes. Microsoft recommends central storage of BitLocker recovery information in an organization, with the storage method matched to how devices are joined and managed. Ask IT where your municipality’s recovery information is held and which authorized people can retrieve it when needed.

Confirm that the stored recovery information belongs to the correct device and that the approved support process can locate it. Discuss that process before an urgent repair. Keep the key separate from the laptop bag and from general staff instructions. Staff should contact the approved support team when a recovery screen appears and use its secure procedure for any requested information. Recovery access needs to remain available when an employee changes roles or leaves.

Understand what remote management can actually do

Ask your provider which response actions are available for your devices and who can authorize them. Microsoft Intune, for example, requires enrollment and an internet connection for a device to receive remote commands. Available actions also depend on the platform and prerequisites. A missing laptop may be offline, so submitting an action does not establish that it has reached the device.

Have IT explain how it checks action status and distinguishes a pending request from a completed response. Microsoft documents remote actions that can remove information, including a factory reset. Decisions about those actions should follow the municipality’s approved incident process, including data needs and authorization. Staff should report the loss and follow directions; the technical team should handle device commands and any appropriate account response.

Write down the report and the next work step

Give employees a short reporting prompt: their name, the device identifier if known, when and where it was last seen, whether it was left signed in, and what work was being handled. They can describe the kinds of information involved without copying sensitive records into an ordinary message. Separate observed facts from guesses and record later updates, including when the device is found.

Agree on how the department continues while IT assesses the situation. For a city employee preparing a meeting packet, that might mean using an approved spare computer to reach the authorized document location. Confirm which work exists only on the missing device and who coordinates the next steps. If the laptop is recovered, notify the response contact and obtain IT’s direction before returning it to normal use.

Review one laptop with this checklist

Practical IT support for municipalities connects device protection with the employee’s first call and the department’s next task. Bring one issued laptop to your next Michigan IT services review and work through these questions.

• Can the office identify the laptop and its current assigned user?
• Has IT verified encryption and active protection on the intended drives?
• Can authorized support locate the correct recovery information?
• Do staff know the reporting contact and what details to provide?
• Which remote actions are available, and how is their outcome checked?
• Where can the department reach its documents using an approved replacement?