Device Fleet Health Check: A 10-Point Diagnostic for IT Heads
08:40 on a Tuesday, and Manish had already lost the argument he came to win. He runs IT for a 180-person distribution company in Pune, and he had asked me over to prove his fleet was fine. His words. “The machines work, Priya. Nobody is complaining.” That last line is the one I have learned to worry about. A fleet nobody complains about is usually a fleet nobody has counted.
So we did the boring thing. We ran a proper device fleet health check, the ten-point version I use on every discovery call. By lunch, Manish had stopped defending the fleet and started making a list.
By Priya Sharma, Data Protection Consultant, Sirius Star Enterprise Technologies. Vashi, Navi Mumbai.
Floor one: the count that did not match
We started where every honest audit starts, with a headcount and a device count that are supposed to agree. His HR sheet said 180 people. His asset register said 164 laptops. The room had, once we walked it, closer to 190 machines. Nobody had retired the old ones, and a few had multiplied for second-screen setups.
This is not carelessness. It is what happens when device tracking lives in one person’s memory and a spreadsheet that gets updated on the day someone remembers. Manish knew his network cold. He did not know, on that morning, how many company laptops were sitting in drawers and car boots, or at a former salesperson’s home. Achha, once we accepted that, the rest of the day was just method.
Floor two: the amber signals nobody was reading
The second half of the fleet is always the interesting half. Average machine age was four years and change, which is past the point where repairs and downtime start eating any saving from holding on. A shade over a third were out of warranty. Two were running an operating system that stopped getting security updates last year. And when I asked the question I always ask, what happens to a laptop the day its owner resigns, the room went quiet for a beat too long.
I want to be honest about a mistake here, because the mistake is the lesson. Years ago I scored a client’s fleet a comfortable eight out of ten and moved on. I had ticked encryption, warranty, patching, all the visible things. I had read the offboarding gap as a paperwork issue, the kind of thing you note and fix later. It was not a paperwork issue. A field laptop from a resigned employee went home and never came back, and the client learned the hard way that a device you cannot account for is a data breach waiting for a date. I had read an amber signal as background noise. Now I read amber as the whole story.
The 10-point device fleet health check
Here is the diagnostic itself. Run it on your own estate before someone external runs it for you. Each point is a yes or no. Count your yes answers at the end.
- Live inventory. Can you produce, today, a device list whose count matches the machines actually in the building and in the field, to the unit? If the register and reality disagree, everything below is a guess.
- Fleet age. Do you know the average age of your laptops, and is it under your refresh threshold? Past three to four years, running cost climbs, and a fleet a year older is a year more expensive to run.
- Warranty and AMC cover. What percentage of the fleet is still under warranty or an active service contract? Every out-of-warranty machine is an unbudgeted repair with your name on it.
- Encryption on every device. Is disk encryption on, verified, on every laptop, not just the new ones? A lost unencrypted laptop is a reportable event under the DPDP Act, not just a lost asset.
- Assignment and sign-off. For each device, do you know who holds it, and did they sign for it? Custody you cannot prove is custody you do not have.
- Offboarding. When someone resigns, is there a written step that recovers and wipes their device before their last day? This is the single most common gap I find, and the most expensive.
- OS and patch currency. How many machines run an operating system still receiving security updates, and are patches actually applied? An unsupported OS on a company laptop is an open door.
- Backup and recovery. If a laptop dies this afternoon, is the company data on it recoverable from somewhere else by tomorrow morning? If the only copy lives on the device, you are one spilled coffee from a bad week.
- Lost or stolen response. Can you remotely lock or wipe a device that walks out the door? Without this, a lost laptop is a lost decision, made for you by whoever finds it.
- Spare pool and downtime plan. When a machine fails, how many hours until the person is working again? A ready spare and a clear process is the difference between a shrug and a lost sales day.
Eight or more, your fleet is in good shape. Keep doing what you are doing. Five to seven, you have gaps that are cheaper to close now than after an incident. Below five, you are not managing a fleet, you are hoping. Manish scored four.
The math the CFO understands
Every unhealthy point has a rupee number behind it. Here is the shape of it for a mid-size fleet.
| Weak point | What it quietly costs |
|---|---|
| Out-of-warranty repairs | Unplanned spend plus days of downtime per failure |
| Ageing fleet held too long | Rising running cost, falling resale you never actually collect |
| Offboarding gap | One unrecovered field laptop cost a logistics client ₹47 lakh |
| Unencrypted or unpatched device | DPDP exposure up to ₹250 crore for a serious breach |
The IBM Cost of a Data Breach work makes the same point in global numbers: the expensive breaches are the slow, unnoticed ones, exactly the kind an unmanaged fleet invites. India’s own DPDP Act now attaches a real penalty to the same gaps, and CERT-In reporting timelines assume you can already produce evidence. The health check is how you find that out on a quiet Tuesday, not on the worst day of your quarter.
What I told Manish
He asked the fair question every buyer should ask. “So do I need to replace all of this now?” No. A four out of ten fleet does not need panic, it needs a plan and an owner. We agreed on three moves. Reconcile the inventory to the unit this month. Write the offboarding step and make it non-optional. Put the oldest and out-of-warranty machines on a refresh schedule his CFO would sign, using the same device refresh policy we help clients build.
Then the part he did not expect. “You already have an IT guy,” I said, “keep him.” Device lifecycle management is not there to replace Manish. It is there to stop him spending his week chasing warranty claims and lost laptops instead of the network work he was actually hired for. We run the fleet grind, he runs the strategy. We say it out loud because it is true. We have seen a national insurer keep its own IT team while we run the lifecycle on 2,500 field devices.
If you are doing this yourself
You do not need us to run the ten points. You need an honest afternoon and a willingness to write down the answers you would rather not. Start with the inventory, because every other score depends on it. Fix offboarding next, because it is cheap to write and expensive to skip. Then look at age and warranty together, because that is where the money conversation lives, and where a plain total cost of ownership view usually changes the CFO’s mind.
If the count alone defeats you, that is not a failure, that is the finding. It is the most common place I start, and the fastest one to fix. Sometimes the list is the whole win.
FAQ
How often should I run a device fleet health check?
Once a year as a full pass, and again before any audit or budget cycle where you defend IT spend. The full ten-point version takes an afternoon. The inventory point alone is worth a quarterly glance.
We are only 60 devices. Is this overkill?
No. Sixty is exactly the size where one lost laptop is a real problem and nobody has a system for it yet. The DPDP Act has no headcount exemption, so device governance applies to you the same as it applies to a 2,500-device shop, just cheaper to set up now than to retrofit after an incident.
Is a health check the same as buying Device-as-a-Service?
No, and one does not force the other. The check tells you where your fleet stands. What you do with the score is a separate decision. Some clients fix the gaps in-house, some move to Device-as-a-Service so the lifecycle is handled on a fixed monthly cost. Both are valid. The check just makes the choice an informed one.
What is the single most common failure you find?
The offboarding gap. Almost every fleet I audit can tell me who was issued a laptop. Far fewer can tell me what happened to it the day that person left. That gap is where the real data loss risk sits.
Still deciding
If any of the ten points made you pause, that pause is the only reason to talk. We run this exact diagnostic as a free device audit, no card and no contract, for companies across India, delivered from Vashi, Navi Mumbai, with a response inside 24 working hours. Device-as-a-Service starts from ₹749 per device per month* once you decide the fleet needs a proper owner. WhatsApp us on +91 91375 93228 or write to care@siriusstar.in, and we will run your numbers, not ours.
P.S. Priya here. Manish called three weeks later. The inventory now matches to the unit, the offboarding step exists, and the salesperson’s laptop from February came back after one firm phone call. He scored his fleet again last week. Seven out of ten, and climbing. “Turns out counting was the hard part, sir.” It usually is.
*Indicative pricing, varies by device specification and fleet size.
