The Hidden Cost of Unmanaged Mobile Devices in South African Field Operations

The Hidden Cost of Unmanaged Mobile Devices in South African Field Operations

A mobile device may cost a few thousand rand to purchase.

But that is rarely the full cost of using it in a field operation.

The real cost may also include:

  • Mobile data waste
  • Device downtime
  • Manual IT support
  • Delayed reports
  • Lost or stolen devices
  • Unauthorised applications
  • Inconsistent configurations
  • Repairs and replacements
  • Security exposure
  • Poor operational visibility

These costs are easy to miss because they are spread across different departments.

Finance may see a rising mobile bill.

IT may see more support requests.

Operations may see delayed job completion.

Managers may see incomplete reports.

Employees may lose time waiting for devices or applications to work.

Clients may experience slower service.

The common cause may be the same: mobile devices are being used for business work without enough central control.

For South African field operations, this issue is particularly important because devices are often used across vehicles, client sites, warehouses, guard posts, construction areas, remote locations and distributed branches.

This article explains how to assess the cost of unmanaged mobile devices and how mobile device management software in South Africa can help businesses improve control.

It also explains where rugged devices and workforce management software fit into the wider solution.

Quick Answer: What Do Unmanaged Mobile Devices Really Cost?

Unmanaged mobile devices can cost a business through a combination of direct expenses, lost working time and operational risk.

The main cost categories are:

  1. Unnecessary mobile data usage
  2. Device and application downtime
  3. Manual IT and administrative support
  4. Repairs, replacements and device loss
  5. Security and information-governance exposure
  6. Poor field visibility and delayed reporting

The most important point is this:

The cost of a mobile device is not only the purchase price. It is the total cost of keeping that device secure, available, supported and productive throughout its working life.

Why the Purchase Price Is Not the Real Device Cost

Businesses often compare mobile devices by looking at the upfront price.

That is understandable, but incomplete.

A lower-cost device may become more expensive if it:

  • Breaks frequently
  • Has poor battery performance
  • Requires repeated manual setup
  • Uses excessive data
  • Cannot be supported remotely
  • Is difficult to secure
  • Causes field workers to use workarounds
  • Needs frequent replacement
  • Does not suit the working environment

The same applies to device management.

A business may avoid an MDM subscription, but still pay for:

  • Manual configuration
  • Support time
  • Data waste
  • Lost productivity
  • Security incidents
  • Delayed reporting
  • Device replacement
  • Poor accountability

This does not mean every business needs the same level of control.

It means the decision should be based on total cost of ownership rather than purchase price alone.

What Makes a Mobile Device Unmanaged?

A mobile device is unmanaged when it is used for business work without sufficient central oversight, policy control or support capability.

Examples include:

  • Company-owned phones with no central management
  • Tablets configured manually
  • Shared devices with no handover process
  • Personal phones used for business without clear controls
  • Devices with unrestricted application installation
  • Devices without enforced security settings
  • Devices that cannot be locked or wiped remotely
  • Devices with inconsistent application versions
  • Devices that IT cannot support remotely
  • Devices with no reliable inventory record
  • Devices that are not linked to a user, role, site or department

A device can still function while remaining unmanaged.

The issue is not whether the device turns on.

The issue is whether the business can control, support and account for it at scale.

The Six Cost Categories Businesses Overlook

1. Mobile Data Waste

Mobile data is a recurring cost for many field operations.

Work-related usage may include:

  • GPS
  • Job cards
  • Proof of delivery
  • Photos
  • Attendance
  • Incident reporting
  • Messaging
  • Cloud applications
  • Supervisor communication

Unmanaged devices may also use data for:

  • Streaming
  • Social media
  • Personal browsing
  • Automatic backups
  • Unapproved downloads
  • Background synchronisation
  • Application updates
  • Duplicate file uploads

The cost of one device may appear small.

The cost across a large fleet can be material.

How to Assess Data Waste

Review:

  • Monthly data usage by device
  • Usage by employee, site or department
  • Applications consuming the most data
  • Background data activity
  • Devices with unusually high usage
  • Whether work applications are being used consistently
  • Whether personal use is permitted or restricted

Do not assume that all high usage is misuse.

Some field applications legitimately upload photos, maps or documents.

The objective is to distinguish necessary business usage from avoidable consumption.

MDM may help by applying application policies, restricting non-work activity and improving visibility. The level of control depends on the platform, device type, policy design and business requirements.

2. Device and Application Downtime

A field device can be unavailable even when it is not physically broken.

Examples include:

  • The required application is missing
  • The application is outdated
  • The device has insufficient storage
  • The battery is flat
  • The device is locked
  • The network configuration is incorrect
  • The user cannot access the required system
  • The device has been damaged
  • The device is waiting for manual support

Downtime affects more than the employee using the device.

It may delay:

  • Job completion
  • Customer updates
  • Proof of delivery
  • Incident reporting
  • Inspection records
  • Supervisor approvals
  • Attendance capture
  • Maintenance updates

How to Measure Downtime

Track:

  • Number of device-related incidents
  • Average time to resolve each incident
  • Number of employees affected
  • Work delayed during the incident
  • Whether a workaround was used
  • Whether the issue could have been resolved remotely

A useful measure is:

Device Downtime Cost = Unproductive Hours × Loaded Hourly Cost + Delayed Work Impact

The “delayed work impact” may be difficult to calculate precisely, so businesses should state their assumptions clearly.

3. Manual IT and Administrative Support

Without central management, device support often becomes repetitive.

IT or operations staff may spend time on:

  • New device setup
  • Application installation
  • Password and access issues
  • Configuration changes
  • Device replacement
  • Lost-device response
  • Application troubleshooting
  • Data usage queries
  • User offboarding
  • Device collection and reassignment

The cost is not only the employee’s time.

It also includes the interruption caused when field workers wait for support.

How to Measure Support Cost

Track:

  • Device-related tickets per month
  • Average handling time
  • Number of tickets that require physical access
  • Number of tickets caused by inconsistent settings
  • Number of devices requiring manual setup
  • Number of incidents that could be resolved remotely

A simple estimate is:

Monthly Support Cost = Device Tickets × Average Handling Time × Loaded Support Cost

This calculation should include internal labour costs where possible.

4. Repairs, Replacements and Device Loss

Field devices are exposed to more physical and operational risk than office devices.

They may be used in:

  • Vehicles
  • Warehouses
  • Guard posts
  • Construction areas
  • Farms
  • Mines
  • Industrial sites
  • Outdoor facilities
  • Remote locations

The cost of a lost or damaged device may include:

  • Replacement hardware
  • Accessories
  • Configuration time
  • Application setup
  • Data recovery
  • Employee downtime
  • Delivery or collection
  • Temporary replacement equipment

A device that is unsuitable for the environment may cost more over time than a better-specified device.

This is where rugged hardware can become relevant.

However, rugged devices do not eliminate the need for management. They reduce certain physical risks, while MDM helps with configuration, security, application control and remote support.

5. Security and Information-Governance Exposure

Business devices may provide access to:

  • Customer information
  • Employee information
  • Site details
  • Photos
  • Work orders
  • Attendance records
  • Incident reports
  • Location information
  • Internal communication
  • Business applications

If a device is lost, stolen or misused, the business may face information-security and governance concerns.

Risk may increase when devices lack:

  • Strong authentication requirements
  • Remote lock capability
  • Remote wipe capability
  • Application controls
  • Update processes
  • Access restrictions
  • Device inventory
  • Offboarding procedures
  • Incident-response processes

MDM can support these controls, but it is not a complete security programme.

Businesses should also consider identity management, application security, network security, user training, data classification and incident response.

For South African organisations, mobile-device controls should form part of the wider information-governance approach, including appropriate safeguards for personal information where relevant.

6. Poor Field Visibility and Delayed Reporting

A device is often the link between field activity and management information.

It may be used to capture:

  • Attendance
  • Patrols
  • Job progress
  • Photos
  • Inspections
  • Proof of delivery
  • Customer signatures
  • Exceptions
  • Maintenance records
  • Supervisor approvals

If devices are unreliable or inconsistently configured, the information flowing into business systems may also be unreliable.

This can create:

  • Missing reports
  • Delayed updates
  • Duplicate work
  • Manual reconciliation
  • Disputes about task completion
  • Poor customer communication
  • Limited management visibility

MDM does not replace a workforce management system.

It helps create a more controlled device environment so that workforce applications can operate more consistently.

How to Calculate Your Exposure

A business does not need perfect data to begin assessing the problem.

Start with a practical baseline.

Step 1: Count the Devices

Include:

  • Company-owned phones
  • Tablets
  • Rugged devices
  • Shared devices
  • Spare devices
  • Devices used by supervisors
  • Personal devices used for business work

Separate active, inactive, lost and unassigned devices.

Step 2: Record Monthly Direct Costs

Review:

  • Mobile data
  • Device finance or rental
  • Repairs
  • Replacements
  • Accessories
  • Support contracts
  • Application subscriptions
  • Delivery and collection

Step 3: Estimate Lost Working Time

Review:

  • Device-related support tickets
  • Time spent waiting for support
  • Delayed job cards
  • Missed reports
  • Repeated data capture
  • Workarounds using paper or messaging apps

Step 4: Assess Risk Exposure

Ask:

  • Can lost devices be locked remotely?
  • Can business applications be removed or restricted?
  • Are devices linked to users or sites?
  • Are former employees’ access rights removed promptly?
  • Are shared devices governed?
  • Can the business identify non-compliant devices?

Step 5: Compare the Cost of Control

Compare the current exposure with the cost of:

  • MDM licensing
  • Implementation
  • Device enrolment
  • Policy design
  • Training
  • Support
  • Rugged hardware where required
  • Workforce application improvements

The objective is not to claim that MDM will eliminate every cost.

The objective is to determine whether better control is commercially justified.

A Practical Cost Framework

Use the following framework to organise the business case.

Cost Area What to Measure Possible Business Impact
Mobile data Usage by device, app and team Higher recurring connectivity costs
Downtime Hours lost and incidents Delayed work and lower productivity
Support Tickets and handling time Higher IT and administration workload
Repairs Damage and replacement frequency Increased hardware expenditure
Security Lost devices and control gaps Greater information-security exposure
Reporting Missing or delayed field updates Poor visibility and customer service
Accountability Unassigned or shared devices More disputes and weaker governance
Lifecycle Age, condition and replacement timing Unplanned capital expenditure

This table should be used as an assessment framework, not as a promise of guaranteed savings.

South African Field Operations Example

Consider a security company operating across estates, warehouses, shopping centres and industrial sites.

Its guards use mobile devices for:

  • Patrol updates
  • Incident reports
  • Photos
  • Supervisor communication
  • Attendance
  • Site instructions

The company may experience the following problems:

  • Some devices use more data than expected
  • Required applications are not consistently installed
  • Devices are shared without clear handover
  • Location settings are changed
  • Lost devices are difficult to secure
  • Supervisors spend time chasing updates
  • IT handles configuration manually
  • Incident reports arrive late
  • Damaged devices remain in circulation

These problems may initially appear to be employee-performance issues.

Some may be.

But the business should also examine whether the device environment makes the correct behaviour easy and the wrong behaviour difficult.

A more controlled approach could include:

  • Standard device profiles
  • Approved applications
  • Remote support
  • Lost-device procedures
  • Shared-device accountability
  • Suitable hardware
  • Clear user and supervisor responsibilities
  • Workforce reporting linked to operational processes

The result is not automatically lower cost.

The result is better visibility into where cost and risk are occurring.

That visibility allows management to make better decisions.

Which Businesses Face the Greatest Risk?

The risk is usually higher when a business has several of the following characteristics:

  • More than one operating site
  • Mobile workers
  • Shared devices
  • High employee turnover
  • Remote or outdoor work
  • Sensitive business information
  • Frequent device replacement
  • High mobile data usage
  • Manual application installation
  • Limited IT resources
  • Customer-facing service commitments
  • Time-sensitive reporting
  • Devices used across shifts
  • Employees using personal phones for work

Security

Security teams depend on devices for patrols, incidents, photos, attendance and supervisor communication.

The main risks are shared-device control, lost devices, inconsistent applications and delayed reporting.

Facilities Management

Facilities teams use devices for inspections, maintenance, job cards and customer updates.

The main risks are device downtime, incomplete records and poor task visibility.

Logistics and Warehousing

Drivers and warehouse teams use devices for routes, scanning, proof of delivery, stock and exception reporting.

The main risks are data usage, device availability, application consistency and delayed delivery information.

Construction and Engineering

Construction and engineering teams often work in demanding physical environments.

The main risks are device damage, battery limitations, poor connectivity and delayed site reporting.

Utilities, Mining and Agriculture

These teams may work across remote or distributed locations.

The main risks are limited support access, physical exposure, device loss and unreliable reporting.

What MDM Can and Cannot Solve

MDM can help businesses manage the device environment.

Depending on the platform and configuration, it may support:

  • Device enrolment
  • Application deployment
  • Application restrictions
  • Security policies
  • Remote lock
  • Remote wipe
  • Device inventory
  • Configuration management
  • Compliance monitoring
  • Remote troubleshooting
  • Device grouping by role, site or department

MDM does not automatically solve:

  • Poor workforce processes
  • Inadequate network coverage
  • Weak application design
  • Poor user training
  • Incorrect device selection
  • Unclear accountability
  • Inaccurate workforce data
  • All forms of mobile data usage
  • Every security or compliance requirement

This distinction is important.

MDM is a control layer.

It should be implemented alongside suitable devices, secure applications, clear policies, user training and operational processes.

Tsukuru’s mobile device management software can help South African organisations create more consistent control across company-owned and field devices.

Where Rugged Devices Fit

Rugged devices are designed for environments where standard consumer hardware may be exposed to greater physical stress.

They may be appropriate for:

  • Security sites
  • Warehouses
  • Construction areas
  • Farms
  • Mines
  • Industrial facilities
  • Vehicles
  • Outdoor maintenance
  • Remote field work

When evaluating rugged hardware, consider:

  • Drop resistance
  • Dust and water protection
  • Battery capacity
  • Charging options
  • Screen visibility
  • Glove use
  • Camera requirements
  • Connectivity
  • Repairability
  • Application compatibility
  • Device lifecycle

Rugged hardware should not be selected only because it appears stronger.

It should be matched to the actual environment and workflow.

Learn more about rugged devices in South Africa.

Where Workforce Management Fits

MDM helps manage the device.

Workforce management helps manage and measure the work.

A workforce management platform may support:

  • Attendance
  • Shifts
  • Tasks
  • Job cards
  • Site activity
  • Inspections
  • Supervisor approvals
  • Exceptions
  • Productivity reporting

The two systems address different questions.

MDM asks:

  • Is the device enrolled?
  • Is it secure?
  • Is the correct application installed?
  • Is it compliant?
  • Can it be supported remotely?

Workforce management asks:

  • Did the employee attend?
  • Was the task completed?
  • Was the site visited?
  • Was the report submitted?
  • Was the exception resolved?

For field operations, the strongest approach is often to plan both layers together.

Explore workforce management software in South Africa.

Procurement and Business-Case Checklist

Before investing in new devices or management software, ask:

Fleet

  • How many devices are active?
  • How many are shared?
  • How many are unassigned?
  • How many are lost or inactive?
  • Which devices are company-owned?
  • Which employees use personal devices?

Cost

  • What is the monthly data cost?
  • What is the annual repair and replacement cost?
  • How much support time is spent on devices?
  • How much work is delayed by device issues?
  • Are device costs allocated to the correct department?

Security

  • Can lost devices be locked?
  • Can devices be wiped remotely?
  • Are security settings enforced?
  • Are applications controlled?
  • Are former users removed promptly?
  • Are shared devices governed?

Operations

  • Are required applications installed consistently?
  • Are devices suitable for the environment?
  • Are devices available at the start of each shift?
  • Can supervisors identify device-related delays?
  • Are field reports reaching management on time?

Implementation

  • Who owns the project?
  • Which devices will be enrolled first?
  • Which policies are required?
  • How will users be trained?
  • How will exceptions be handled?
  • How will success be measured?

Common Mistakes to Avoid

Mistake 1: Comparing Devices Only by Purchase Price

A cheaper device may have a higher lifecycle cost if it fails more often or requires more support.

Compare total cost of ownership.

Mistake 2: Assuming Every High Data User Is Misusing the Device

Some work applications legitimately use significant data.

Review the application and workflow before applying restrictions.

Mistake 3: Treating MDM as a Complete Security Programme

MDM is one control layer.

It should work with identity, application, network, user and incident-management controls.

Mistake 4: Ignoring Shared Devices

Shared devices need clear ownership, handover, charging, storage and incident procedures.

Mistake 5: Choosing Rugged Hardware Without Testing the Workflow

A rugged device may still be unsuitable if the screen, battery, camera, connectivity or applications do not meet operational needs.

Mistake 6: Measuring Only Device Cost

Include support time, downtime, delayed reporting, data usage and replacement costs.

Mistake 7: Implementing Technology Without Ownership

A device programme needs clear responsibility across IT, operations, finance, procurement and users.

When Should a Business Act?

A business should review its mobile-device strategy when:

  • The device fleet is growing quickly
  • IT cannot maintain an accurate inventory
  • Devices are being configured manually
  • Mobile data costs are difficult to explain
  • Field workers regularly wait for device support
  • Lost devices create uncertainty
  • Shared devices are not properly handed over
  • Applications are inconsistent
  • Reports are delayed because devices fail
  • Devices are being used outside their intended purpose
  • Repairs and replacements are increasing
  • Personal devices are being used without clear rules

The right time to assess the problem is before a major security incident, operational failure or uncontrolled cost increase.

Why Tsukuru’s Approach Matters

Tsukuru helps South African businesses assess mobile devices as part of the wider field-operations environment.

That may include:

  • Device selection
  • Rugged hardware
  • Mobile device management
  • Workforce management
  • Application control
  • Field reporting
  • Device support
  • Operational visibility
  • Productivity improvement
  • Business-client implementation

The objective is not to add technology without purpose.

It is to help businesses understand where device-related cost and risk are occurring, then select an appropriate combination of hardware, management and workforce tools.

Explore Tsukuru’s business client solutions.

Final Verdict: The Real Cost Is the Cost of Uncontrolled Work

Unmanaged mobile devices can create costs that are difficult to see in a single budget line.

They may increase:

  • Mobile data waste
  • Device downtime
  • Manual support
  • Repairs and replacements
  • Security exposure
  • Reporting delays
  • Operational uncertainty

The answer is not automatically to buy more expensive devices or implement every available software feature.

The better approach is to assess the full device lifecycle:

  1. Select hardware suited to the environment.
  2. Enrol and manage devices consistently.
  3. Control applications and security settings.
  4. Create a lost-device and support process.
  5. Measure data, downtime and support costs.
  6. Connect device control to workforce operations where appropriate.

For South African field operations, this creates a more defensible business case for mobile device management, rugged hardware and workforce visibility.

If your organisation is struggling to understand the cost of unmanaged devices, contact Tsukuru to discuss a mobile-device assessment.

FAQ Section

1. What is an unmanaged mobile device?

An unmanaged mobile device is a phone, tablet or rugged device used for business work without sufficient central control over its applications, settings, security, inventory or support.

2. What is the biggest hidden cost of unmanaged devices?

There is no single cost for every business.

The largest cost may be data waste, downtime, support effort, device replacement, security exposure or delayed field reporting, depending on the organisation’s operating model.

3. How do unmanaged devices affect field operations?

They can make it harder to keep applications consistent, support employees remotely, protect business information, control data usage and maintain reliable field reporting.

4. Can MDM reduce mobile data costs?

MDM may help reduce avoidable data usage through application policies, configuration controls and better visibility.

However, legitimate work applications may still require significant data, so businesses should assess usage before applying restrictions.

5. Does MDM prevent all mobile-device security incidents?

No.

MDM can support device security through controls such as enrolment, policy enforcement, remote lock, remote wipe and application management.

It should form part of a broader security and information-governance programme.

6. Do rugged devices still need MDM?

Yes.

Rugged devices can reduce physical damage, but they still need application control, security policies, remote support, inventory management and lifecycle planning.

7. Is MDM suitable for small businesses?

MDM may be suitable for smaller businesses if they manage multiple company-owned devices, operate across sites, use shared devices or need stronger control over business applications and information.

The appropriate solution should match the size, risk and complexity of the device fleet.

8. Should businesses use MDM or workforce management software?

They serve different purposes.

MDM manages the device environment.

Workforce management software manages attendance, tasks, job cards, site activity and operational reporting.

Field-based businesses may benefit from using both, depending on their requirements.

9. How can a business calculate the cost of unmanaged devices?

Start by measuring device numbers, mobile data, support tickets, downtime, repairs, replacements, lost devices and delayed work.

Then compare the estimated exposure with the cost of improved device management, suitable hardware and implementation.

10. What should a business do first?

Begin with a device and cost audit.

Identify the active fleet, current applications, data usage, support workload, lost-device process, device condition and operational impact.

This creates a practical baseline before selecting technology.

Back to blog