What is CYOD? Choose Your Own Device & Global Fulfillment

CYOD lets employees choose a company-owned device from an IT-approved list, balancing choice and control. The policy is easy to write; the hard part is sourcing, configuring, delivering, and retrieving mixed hardware across countries. Keep the catalog to 2–3 models per category and plan offboarding from day one.

An employee in the US chooses a MacBook. Another in Germany chooses a Dell. Someone in India picks a Lenovo.

That sounds simple enough. Give employees a few approved options, let them choose, and get the device to them.

But now someone has to find those devices in three different markets, deal with different prices and taxes, configure each one, get them to the right employees on time, keep track of where they are, and eventually get them back.

That's where CYOD gets complicated.

The device choice is simple. The work behind that choice continues throughout the device's lifecycle.

And when your employees are spread across countries, an approved device list is only the starting point. You also need a process to source, deploy, track, replace, retrieve, and redeploy those devices wherever your employees are.

For a global team, a CYOD policy therefore needs more than an approved device list. It needs a repeatable device lifecycle management process that can make those choices work across countries.

In this guide, we’ll break down what CYOD means, how it compares with BYOD and COPE, what it really costs, and why managing the full device lifecycle becomes the hard part for global teams. Let’s start with what CYOD means.

What is CYOD?

CYOD (Choose Your Own Device) is a policy where employees choose a company-owned device from an IT-approved list. A CYOD policy gives employees more choice than COPE while keeping more IT control than BYOD.

The company still owns the hardware, defines approved models, and sets security and lifecycle requirements. Employees simply choose from that approved catalog.

CYOD vs. BYOD vs. COPE: What's the Actual Difference?

The biggest difference between these models is who owns the device and how much choice the company allows. COPE (Corporate-Owned, Personally Enabled) means the company owns and issues one standard device, but employees can use it for approved personal activities. In a BYOD vs. CYOD comparison, ownership is the dividing line: employees own the device in BYOD, while the company owns it in CYOD.

In practice:

• CYOD fits organizations that want to balance employee choice with IT control.
• BYOD can work where minimizing hardware spend matters more and security requirements are relatively limited.
• COPE is more suited to environments that prioritize standardization and tighter control, including highly regulated or security-sensitive organizations.

Note: COBO (Corporate-Owned, Business-Only) and COSU (Corporate-Owned, Single-Use) are stricter variants of company-owned device models. COBO allows no personal use, and COSU locks a device to a single task, such as a kiosk or scanner.

Advantages and Disadvantages of CYOD

CYOD sits between BYOD and COPE, so it takes some of the strengths and some of the costs of each.

Advantages

• Choice without the BYOD security gap. Employees pick a device they'll want to use, and the company still owns it, configures it and can recover it.
• A consistent security baseline. IT supports a defined set of models instead of whatever employees bring.
• Simpler support than BYOD. A short approved list means fewer hardware variations to troubleshoot.
• Cleaner offboarding. Company-owned hardware can be retrieved, sanitized and redeployed. A personal device can't.
• A better experience than one standard device. Choice can improve satisfaction and adoption without opening the door to unmanaged hardware.

Disadvantages

• Higher cost than COPE. Supporting several approved models means less purchasing standardization and more spare stock to hold.
• The company carries the full cost. That includes the devices, replacements, repairs and retrieval.
• More fulfillment complexity. Each approved model has to be sourced, configured, delivered and tracked, and that multiplies across countries.
• Limited choice can still frustrate. Employees who want something off the list need an exception process.
• The catalog needs upkeep. Models, generations and regional availability change, so the list has to be reviewed on a schedule.

What Should a CYOD Policy Include?

A CYOD policy is short to write and easy to leave incomplete. These are the sections it should cover:

1. Scope. Which employees and device categories (laptops, phones, tablets) the policy covers.
2. Approved catalog. Two or three models per category, and how often the list is reviewed.
3. Ownership. The company owns the device. State the employee's responsibilities for care, loss and damage.
4. Personal use. What is allowed, and how business and personal data are separated.
5. Security baseline. Enrollment, encryption, required software, and how to report a lost or stolen device.
6. Support and replacement. Who handles faults, how replacements are ordered, and expected timeframes.
7. Refresh cycle. When devices are replaced.
8. Offboarding and return. The return deadline, how devices are retrieved (including from other countries), and what happens to the data and the hardware afterward.
9. Exceptions. How off-list requests are handled, and what applies in countries where an approved model isn't available.

For global teams, items 2, 8 and 9 are where policies usually break down.

How Much Does a CYOD Program Actually Cost?

The device price is only part of the cost.

A global CYOD program also has to account for regional price differences, VAT or GST, import duties, shipping, configuration across approved models, replacement devices, and the retrieval, storage, redeployment, or disposition of hardware at offboarding.

• CYOD can cost slightly more per device than a standardized COPE setup because the company has to support multiple approved models.
• BYOD looks different: it can reduce upfront hardware spend while adding overhead for support, compatibility, security, and device standardization.

The better measure is to invest in a service that covers the total cost across the device lifecycle, not the purchase price alone. That becomes especially important when the same CYOD catalog has to work across multiple countries.

Cost is only one part of the tradeoff. A CYOD program also needs consistent security requirements across every approved device and location.

CYOD Security Considerations

Security starts before the employee receives the device. A CYOD policy should define security requirements across the device lifecycle, not just at deployment.

• Before deployment: Each approved model should have a defined security baseline, with enrollment and required configuration completed before or as part of deployment. If personal use is permitted, the policy should also define how business and personal data are separated.
• During use: The policy should cover lost or stolen devices, including how employees report an incident, what security actions follow, and when remote wipe is required.
• At offboarding: Security requirements do not end when an employee leaves. The offboarding process should define how the device is retrieved and what happens to company data before the hardware is redeployed or disposed of.

Compared with unmanaged BYOD, an approved CYOD catalog gives IT a defined set of hardware models and security requirements to work with. This makes it easier to apply a consistent security baseline across the approved device fleet.

But defining the policy is only one part of running CYOD. The harder question is whether those requirements can be executed consistently when employees choose different devices across different countries.

Why CYOD Sounds Simple But Isn't

However, each arrow is a potential failure point when the program operates across countries. Availability, pricing, configuration, delivery, tracking, and retrieval all depend on local conditions and reliable execution.

For globally distributed teams, those failure points turn a simple device-choice policy into a fulfillment challenge.

The 8 Challenges of Global CYOD

1. Local Device Availability

→ Can the employee actually get the approved device in their country?

An approved model only works if it can be sourced where the employee is. Regional stock shortages, different OEM lineups, and local availability can turn a standard device choice into a procurement exception. A global catalog needs a realistic local sourcing path behind it.

2. Regional Pricing

→ How do you maintain a consistent CYOD catalog when prices vary across markets?

The same device does not have one global price. Currency movements, regional pricing, taxes, and supplier availability can all change the landed cost. Procurement needs to account for those differences without turning every employee order into a separate pricing exercise.

3. Taxes, Duties, and Import Rules

→ Who handles VAT/GST, customs, duties, and country-specific restrictions?

Cross-border fulfillment adds requirements that do not appear on the device catalog. Import documentation, duties, VAT or GST, and local restrictions can affect both cost and delivery. Those requirements need to be accounted for before the device is ordered, not after it reaches customs.

4. Configuration and Provisioning

→ How do you configure different approved models consistently before delivery?

CYOD creates a mixed hardware fleet by design. Each approved model still needs the required operating system configuration, software, accessories, and device setup before it reaches the employee. The more models a company supports, the more important a repeatable provisioning process becomes.

5. MDM Enrollment and Security

→ How do you enroll employee-selected hardware into your security stack?

Each approved model still needs to fit the organization's existing device-management and security workflows. The fulfillment process needs to hand over hardware in the required state so enrollment and security controls can be applied consistently across the approved fleet.

6. Delivery and Onboarding

→ How do you make sure the right device reaches the right employee before Day 1?

Successful delivery depends on more than a shipping label. The employee, approved model, configuration, address, and start date all need to line up. For global teams, local delivery conditions can add another variable to an already time-sensitive process.

7. Replacement, Returns, and Offboarding

→ What happens when the device needs replacing, or the employee leaves?

A replacement is not always a simple swap when employees use different approved models. Offboarding adds another layer: the right asset has to be retrieved from the right location, processed appropriately, and either returned to inventory for redeployment or moved into disposition.

→ That retrieval problem is common: 71% of HR professionals surveyed by Capterra said at least one departing employee failed to return company-owned equipment.

8. Asset Visibility

→ How do you track different devices across locations, manage replacements, and know exactly where each asset is throughout its lifecycle?

A mixed fleet creates more assets and more lifecycle events to track. IT needs visibility into assignment, location, status, replacement history, and next action. Without that, a CYOD program can create inventory gaps even when the policy itself is well defined.

These aren't just theoretical operational risks. They are issues buyers are already raising when they plan global device programs.

So, the complexity doesn't end when the employee leaves. It becomes a retrieval problem: where is the device, how does it get back, and what happens to it next?

CYOD During Employee Offboarding: The Problem Most Policies Don't Plan For

What happens to all those different devices when employees leave?

The devices need to be retrieved, checked, and either returned to inventory for redeployment or sent for disposition. That sounds straightforward until employees are spread across different countries.

Shipping options, local requirements, and return logistics vary by location, so IT needs to know which device the employee has, where it is, how to retrieve it, and what happens after it arrives.

A mixed CYOD fleet adds another layer.
A returned MacBook, Dell, or Lenovo may need to be checked and sanitized before another employee can use it. Without a clear process for what happens next, recovered devices can sit in storage instead of going back into circulation.

For a deeper look at data sanitization and documentation, see the NIST 800-88 compliant data destruction guidance.

So how do you build a catalog that covers the full lifecycle and still works across countries?

How to Build a Global CYOD Device Catalog

A good CYOD catalog limits choice without making the program feel restrictive. The goal is to give employees enough flexibility while keeping the underlying fulfillment process repeatable.

1. Limit approved device tiers

Start with two or three approved models per device category rather than an unlimited list.

→ This will reduce fulfillment and support burden.

2. Plan regional procurement and support upfront

Before adding a device to the catalog, confirm that it can be sourced in the markets where employees use it. Define regional procurement and support partners, expected pricing, and delivery timelines before each device becomes an employee order.

→ This will reduce country-specific sourcing and fulfillment exceptions.

3. Build offboarding into the catalog

Retrieval is part of the device lifecycle, not an afterthought. Each approved model should have a defined path for return, sanitization, storage, redeployment, or disposition.

→ This will make device recovery easier to manage at offboarding.

4. Review the catalog on a fixed cadence

Revisit the approved list on a set schedule, such as annually. Device generations, regional pricing, availability, and supplier conditions change.

→ This will help keep the catalog practical to source and fulfill.

How GroWrk Supports Global CYOD Fulfillment

A CYOD catalog only works if approved devices can actually be sourced, configured, delivered, and recovered across the markets where employees are located.

That is where GroWrk fits in.
GroWrk handles the physical device lifecycle and fulfillment layer behind a CYOD program: sourcing approved hardware regionally, configuring and provisioning devices, delivering them to employees, tracking physical inventory, and retrieving, redeploying, or disposing of devices at the end of the lifecycle.

Your company can implement or continue a CYOD policy where a manager can send a list of available devices in the platform, and employees choose their preferred option for their country.
GroWrk handles the deployment across 150+ countries.

This matters most when an approved model isn't available in every market. The catalog can be adapted by country, with devices sourced locally rather than shipped across borders for every order.

Instead of managing each hire as a separate procurement and logistics task, the hardware follows a defined lifecycle:
source → configure → deliver → track → retrieve → redeploy or dispose

For global CYOD programs, this keeps the physical device lifecycle connected to the choices in the catalog, from deployment through offboarding.

→ See how GroWrk manages devices from procurement through offboarding.