Corporate mobile programs — carrier plans, devices, MDM licensing, and the admin infrastructure around them — are among the most consistently over-spent categories in IT budgets. Not because organizations make bad decisions, but because the programs grow through incremental additions that are never revisited. Here is how to tell whether yours has structural waste.
The structural problem with mobile programs
Mobile programs are designed to scale up. Adding a new line, provisioning a new device, activating a new feature — each of these is a straightforward operational task. Removing things is harder.
Deactivating a line requires a formal disconnection request through the carrier. Reclaiming a device requires a return process. Removing a feature requires a plan change. None of these happen automatically when the underlying need disappears. The result is a program that accumulates active lines, features, and devices that no longer serve an active purpose.
The carrier doesn’t flag this. The MDM platform doesn’t flag this. The billing system bills for what the account says it has until someone tells it otherwise.
Signs the program has structural waste
Lines per employee exceeds 1.0
For most organizations, the line count should track headcount. If the line count significantly exceeds current headcount — even accounting for intentional spare lines or shared devices — excess lines are a likely finding.
The gap is typically explained by lines that were provisioned and never deactivated: former employees whose lines weren’t disconnected, project lines that weren’t canceled, test lines from device evaluations, or lines from locations or roles that were restructured.
No defined process for employee offboarding that includes carrier deactivation
Ask the question directly: when an employee leaves, who is responsible for notifying the carrier and deactivating the line?
If the answer is “IT” but there’s no specific step in the offboarding checklist for carrier notification, or if the answer is “I’m not sure,” the program almost certainly has active lines for former employees. This is the most common mobile waste finding.
Features and add-ons that were never reviewed after activation
International roaming features, premium data packages, hotspot add-ons, and international calling features are frequently activated for specific use cases — a business trip, a project, a traveler — and then never removed.
If the program has features that were activated more than 12 months ago and no one has reviewed whether they’re still needed, waste is likely.
Multiple device tiers with no policy justification
Device programs that have evolved without a formal policy tend to accumulate tier inconsistency. Employees at similar roles have different device tiers based on when they were hired, who managed their provisioning, or the device that was available at the time.
This isn’t always waste — some role-based variation is appropriate. But programs with high variance and no written policy often have premium devices in roles where a standard device would be sufficient.
Rate plans that were set and never reviewed
Carrier rate plans should reflect actual usage patterns. A plan provisioned for heavy data users is wasteful for light users — and vice versa. Plans set at hire or at contract signing are rarely reviewed as usage patterns evolve.
The sign here is a data plan portfolio that shows significant variation in usage against plan allocation — heavy users on light plans paying overage, light users on premium plans paying for capacity they don’t use.
No renewal calendar for the carrier contract
If the carrier contract doesn’t have a known renewal date and notification window documented somewhere, the contract will auto-renew. Most carrier contracts auto-renew for 1-3 year terms. Organizations that aren’t watching renewal windows end up locked into pricing that should have been renegotiated.
The most common root causes
No single owner for the program. Mobile programs that live between IT (technical management), HR (new hire provisioning), and finance (billing approval) have no one watching the full picture. Each function sees its piece; no one sees the whole.
Offboarding doesn’t include carrier steps. The IT offboarding checklist handles directory deactivation and device return. The carrier step — submitting a formal disconnection request — requires a separate action that often isn’t in the checklist.
Provisioning is easier than deprovisioning. Adding a line is a standard operational request. Removing a line requires paperwork and follow-through. The asymmetry means the program accumulates.
Carrier billing is complex and rarely audited. Carrier invoices run to dozens of pages for medium-sized programs. Most finance teams approve the total on the basis that it’s “roughly consistent” with prior months. Actual line-level billing review is uncommon, which allows billing errors and unnecessary features to persist.
What a review of a mobile program typically produces
Organizations that do a structured mobile program review typically find:
- Active lines for 5–15% of headcount that cannot be attributed to a current employee or active business need
- Features and add-ons that can be removed without operational impact on 20–40% of lines
- Plan rightsizing opportunities on a meaningful portion of the line portfolio
- Carrier contract auto-renewal exposure or pricing above current market rate
The combined impact varies by program size and how long since the last structured review. Programs that have never been audited tend to surface more; programs with recent reviews tend to be cleaner.
