Using AirWatch to manage wearable devices like smartwatches

Smartwatches are moving beyond step counts and notifications. In Australian workplaces, they can help field technicians receive job updates, let warehouse staff scan information without reaching for a phone, and give care teams quick access to alerts. When these devices connect to business systems, they need the same oversight as laptops, tablets and smartphones.

AirWatch, now associated with VMware through the Workspace ONE platform, gives IT teams a central way to enrol, configure, secure and support wearable endpoints. A thoughtful deployment can improve productivity without turning a smartwatch into an unmanaged route into company data.

What wearables add to a business

A smartwatch can provide glanceable information in situations where using a phone is inconvenient or unsafe. A maintenance worker might see the next service location, a courier may receive a delivery exception, and a hospital employee could receive a discreet alert. Retail, logistics, mining, construction and healthcare are all potential users of wearable technology.

The value comes from connecting the device to a controlled business workflow. Notifications should be relevant, brief and limited to what the worker needs. AirWatch can help administrators apply device settings, distribute approved applications where supported, and control access according to the organisation’s security policy.

Australian operating conditions make planning especially important. A mining business in Western Australia may need devices to work across remote sites with intermittent connectivity, while a Sydney office may focus on privacy in a bring-your-own-device programme. The right policy must account for coverage, ruggedness, battery life and the way employees actually work.

Choose a manageable wearable model

There are several ways to introduce smartwatches. The organisation can purchase and own every device, allow employees to connect personal watches, or issue rugged specialist wearables designed for industrial or clinical environments. Each option affects support costs, privacy, enrolment and the amount of control available to administrators.

A corporate-owned model is usually the simplest to secure. IT can assign a device to a worker, configure it before delivery and remove business access when the person changes roles. A BYOD approach may be cheaper, but it requires clear consent and separation between personal features and company information. Employees should understand what the organisation can see, collect or restrict.

Useful policy decisions include:

AirWatch can support the broader endpoint strategy, but compatibility should be checked before purchasing hardware. Some smartwatch functions depend on a paired phone, a vendor cloud service or a particular mobile operating system. A pilot with real devices will reveal these dependencies earlier than a procurement spreadsheet.

Enrol and configure devices consistently

A wearable programme should begin with an inventory. Record the asset owner, serial number, paired handset, mobile number where relevant, assigned department and replacement date. This information gives the service desk a reliable starting point when a device disappears or stops syncing.

Administrators can use Workspace ONE UEM capabilities to apply baseline settings and associate devices with smart groups. For example, construction workers may receive a different configuration from office staff, while a healthcare group may require stricter notification controls. Automated profiles reduce manual setup and make changes easier to audit.

Enrolment should be easy for the employee and controlled for the business. Corporate devices can be prepared by IT or a supplier before they reach the user. For BYOD, a privacy-conscious enrolment flow should explain the information collected and allow the business profile to be removed without wiping personal content.

Connectivity deserves practical attention in Australia. Telstra, Optus and Vodafone coverage varies significantly between metropolitan areas, regional towns and remote work sites. A smartwatch that performs well in Melbourne may be unreliable in a remote Queensland location, so offline behaviour and reconnection should form part of acceptance testing.

Protect identity, data and privacy

Wearables often display sensitive information even when they store very little locally. A message preview, patient reminder, customer name or location alert can be visible to anyone nearby. Configure short display timeouts, device passcodes and notification restrictions so confidential data is not exposed in a public place or shared vehicle.

Access should be based on identity and business need. Require authentication for company applications, use conditional access where available, and remove access when an employee leaves or a device is reported missing. A remote lock or wipe process is valuable, although administrators should confirm exactly what will be erased on the watch, its paired phone and any connected cloud account.

Australian organisations also need to align wearable programmes with the Privacy Act 1988 and the Australian Privacy Principles. A company collecting location, health or activity information should document the purpose, retention period and access rules. In workplaces, policies should distinguish between data needed for safety or operations and personal information that should remain private.

Security controls should be matched to the risk. A hospitality business sending roster alerts may need a lighter configuration than a healthcare provider displaying clinical notifications. AirWatch can provide policy enforcement and compliance signals, while the organisation remains responsible for deciding which data is appropriate for a wearable screen.

Support workers without creating friction

A good support model recognises that watches are companion devices. Problems may involve the watch, its paired phone, the mobile network, Bluetooth, an application or an account. Service desk staff should have a simple troubleshooting path that checks pairing, battery, connectivity and policy status in that order.

Remote assistance can reduce downtime for dispersed teams. A technician may be able to confirm whether a device is enrolled, compliant and communicating without asking an employee in regional New South Wales to bring it into the office. For remote workforces, spare devices and documented replacement procedures can be more effective than attempting complex repairs over the phone.

Workers should receive short, role-specific guidance rather than a long technical manual. Explain how to report a lost watch, how to recognise a suspicious prompt and what information may appear in a notification. Plain Australian workplace language works well: a quick “how-to” card and a short toolbox talk may achieve more than a lengthy policy document.

A support plan should also consider battery and hygiene. Staff in warehouses or on construction sites may need charging points and protective cases. Healthcare and food-processing environments may require cleaning procedures and approved straps. These operational details determine whether adoption feels useful or becomes a daily annoyance.

Measure value and refine the rollout

Management reporting should cover more than the number of enrolled watches. Track compliance, failed enrolments, application usage, help-desk incidents, battery-related disruptions and time taken to replace a device. These measures show whether the wearable programme is helping workers or simply adding another endpoint to maintain.

Security and health monitoring can reveal patterns that are difficult to spot manually. For a closer look at the kinds of information administrators may review, device health analytics can help frame discussions about compliance status, risk signals and fleet visibility. The exact data available will depend on the watch, operating system and management integration.

A phased rollout is usually safer than an organisation-wide launch. Begin with one use case, such as dispatch alerts for a transport team or task notifications for facilities staff. Gather feedback from employees, test lost-device procedures and confirm that notifications do not distract workers from safety-critical tasks.

The following comparison can help shape an initial decision:

Wearable model Best fit Main management benefit Key limitation
Corporate-owned smartwatch Office, retail and field teams Consistent configuration and clear ownership Higher purchase and replacement costs
BYOD smartwatch Low-risk notifications and flexible teams Lower hardware spend More complex privacy and support requirements
Rugged specialist wearable Mining, logistics and industrial work Stronger durability and task-focused design Smaller app ecosystem and higher unit cost
Clinical or care-focused wearable Healthcare and assisted living Fast alerts and workflow support Strict privacy, hygiene and integration needs

Turn a pilot into a controlled service

Before enabling production access, define success in measurable terms. A pilot might require 95 per cent enrolment completion, fewer missed dispatch alerts, no unauthorised data exposure and a support resolution time below an agreed target. These targets give IT and business leaders a shared basis for continuing or changing the programme.

Use AirWatch policies to keep the environment orderly as it grows. Group devices by department, location or ownership model, apply least-privilege access and review inactive endpoints regularly. Remove devices that have not checked in, confirm that former employees no longer have access, and reconcile the platform inventory with procurement records.

The Australian market rewards practical deployment. A transport operator serving Adelaide and regional South Australia may prioritise battery life and offline queues, while a financial-services firm in Brisbane may place greater emphasis on privacy and identity controls. Local conditions should influence the design rather than being treated as exceptions after launch.

A fully functional 30-day trial can give an IT team time to test enrolment, policies, application delivery and reporting with representative devices. Start with a small group, involve the service desk and document the results. When the use case is proven, contact the AirWatch or VMware sales team to compare packages and build a supported wearable strategy that protects company data while giving Australian workers timely information where they need it.