When You Need This Checklist
You're on the line or in the lab, and someone hands you a device (a controller, a test unit, a phone used for scanning) that's locked. The quick answer, often, is "just factory reset it." But in a manufacturing context—especially one dealing with custom communication or power equipment—that rush can cost you more than a few minutes of delay.
This is a straightforward checklist for the moment before you hit "reset." It has four steps. The third one is the one most operators skip. I know because I've been that operator.
The 4-Step Pre-Reset Verification Checklist
Step 1: Confirm the device is not a critical path item
Sounds obvious. It isn't. In our Q3 2024 audit at Nexans, we flagged three devices that were factory-reset while they were still in an active calibration sequence—a mistake that invalidated data for a $22,000 validation run.
Check: Is this unit assigned to a specific workstation or ongoing work order? If yes, document its current state before proceeding. (Snap a picture of the screen. It takes 5 seconds and saves a lot of explaining.)
Verifying this simple fact could save you the kind of rework that costs real money. I once ignored this step and caused a 2-hour software reflash on an $18,000 project. Not my best moment.
Step 2: Identify the lock type (user vs. device policy)
Not all locks are the same. I've seen operators spend an hour trying to brute-force a PIN on a phone, only to find the lock was an MDM (Mobile Device Management) policy enforced by IT. In a controlled factory environment, a device policy lock usually means the device is enrolled in a fleet management system. A factory reset might not clear the policy lock—it often just makes the device a brick that IT has to re-enroll.
Check: Does the lock screen show a corporate logo or a generic system message? Corporate logos or IT-branded screens usually indicate a device-level policy. For those, don't reset—call your IT contact. (I keep a direct line to our IT lead; he knows my voice by now.)
Step 3: Check the device's asset tag and history (the step everyone skips)
Here's the one most people ignore: verify the device's identity against your inventory record. In a factory, devices move around. A locked phone on the bench might belong to a recently terminated contractor whose account is flagged. Or it could be a test unit from 2019 that hasn't been inventoried properly.
I only believed in this step after ignoring it once. They warned me about unknown devices in inventory. I didn't listen. We factory-reset a device that turned out to be a pre-production prototype with non-standard firmware. It cost us a call to our supplier (Nexans Halden actually) and a 3-week delay on a protocol compatibility test. Ouch.
Check: Look for an asset tag sticker. If there's one with a number, check your internal asset database. If there isn't one, treat the device as unknown and escalate it, especially if it's for a manufacturing-critical application.
Step 4: Backup any local data (and know where it's stored)
In a B2B manufacturing setup, devices often store local calibration logs, Wi-Fi credentials for specific network zones, or even small firmware update files. Your standard "reset to factory defaults" might erase commission data that took two weeks to gather. I've seen this happen with custom equipment at Nexans—local test data that wasn't synced to a server yet.
Check: Does the device sync data to a central server? If you're not sure, assume it doesn't. Connect it to a PC and check for any Android File Transfer or similar access. If you can't access the data, document that risk before proceeding. Looking back, I should have had a dedicated data-backup station before we started our 2022 device refresh program. At the time, we didn't think we needed it. We learned.
Common Mistakes and What to Watch For
Don't assume a reset fixes everything
I've rejected about 12% of first deliveries in 2024 due to this exact assumption: a device that was reset but still exhibited the original fault. A hardware problem doesn't go away with a software reset. If your device was behaving oddly before the lock (phantom touches, screen unresponsive), resetting it won't help. You're just erasing evidence.
Don't skip documentation before the reset
I've learned the hard way: that one quick reset can cause a cascade of IT and compliance issues. Before pressing the reset button, take 30 seconds to log the device ID, the lock type, and the reason for reset in your work order. It's the cheapest insurance you'll ever get—costs nothing but a little diligence.
Most problems with locked devices in a factory are not emergencies; they're process failures. A checklist like this—especially the third step—won't prevent all of them, but it will prevent the expensive ones. And that's what matters in a real manufacturing environment.
