Most Canadian frontline fleets need more than one device ownership model. Use COBO (corporate-owned, business only) for shared work devices like scanners and rugged handhelds, COPE (corporate-owned, personally enabled) or CYOD (choose your own device) for supervisors who need a phone, and keep BYOD (bring your own device) to email and scheduling. Personal phones can’t be locked down, shared or monitored the way frontline work usually needs.
If you’re the IT leader whose drivers, store staff, technicians or nurses are on a mix of personal phones and shared devices, this guide compares the four models, maps each frontline role to the model that fits, and covers the Canadian privacy and monitoring rules that shape the choice.
Key takeaways
- Device ownership models should be chosen per role, not per company. A driver’s scanner and a manager’s phone need different models.
- COBO fits shared frontline work devices. Corporate-owned, business-only devices can be locked to work apps and handed from shift to shift.
- COPE and CYOD fit staff who need one phone for work and personal use. The organization owns the device and keeps control of work data.
- BYOD fits light communication, not frontline workflows. Personal phones limit what IT can control and raise privacy questions.
- Canadian privacy and monitoring rules affect every model. Ontario employers with 25 or more employees need a written electronic monitoring policy, for example.
BYOD, COPE, CYOD and COBO compared
The four device ownership models differ on who owns and picks the device, whether personal use is allowed, and how much IT controls. The table below compares them on the points that matter most for a frontline fleet. It’s a general comparison, and your device management platform and policies will change some of the details.
| Model | Who owns and picks the device | Personal use | What IT controls | Best for |
|---|---|---|---|---|
| BYOD (bring your own device) | Employee owns and picks | Yes, it’s the employee’s phone | Work apps and data only, usually in a separate work profile | Email, scheduling and messaging for staff who don’t need a work device |
| CYOD (choose your own device) | Organization owns, employee picks from an approved list | Usually allowed | The device, with work data kept separate | Supervisors and managers who want some choice |
| COPE (corporate-owned, personally enabled) | Organization owns and picks | Allowed within policy | The device, with work data kept separate | Staff who need one phone for work and personal use |
| COBO (corporate-owned, business only) | Organization owns and picks | No | The whole device, often locked to set apps | Shared and single-purpose work devices such as scanners and rugged handhelds |
How to choose a device ownership model for each frontline role
The right device ownership model depends on what the device does in each role. If the device is a work tool that’s shared or used for scanning, delivery or clinical work, it should be corporate-owned and business only. If it’s mainly for communication, COPE, CYOD or BYOD can work.
The table below maps common frontline roles to the model that usually fits.
| Role | Model that usually fits | Why |
|---|---|---|
| Delivery driver | COBO | Scanning and proof of delivery need a rugged device locked to delivery apps |
| Store associate | COBO, shared across shifts | Inventory and mobile point-of-sale devices are shared and stay in the store |
| Field technician | COBO or COPE | Work orders need a managed device, and COPE fits if the technician also needs one phone |
| Nurse or care worker | COBO, shared on the unit | Health information and shared use need full control and remote wipe |
| Supervisor or manager | COPE or CYOD | Needs calls, email and work apps on one phone |
| Office or seasonal staff | BYOD | Email and scheduling only, with no work device to issue and recover |
What each device ownership model means for security and device management
Each device ownership model maps to a different way of setting up the device in your mobile device management (MDM) platform. The setup decides what IT can see, restrict and wipe.
BYOD and work profiles on personal phones
BYOD devices are usually managed with a work profile, which Google describes as a separate, self-contained space for work apps and data on Android. Other platforms offer similar separation. IT manages the work side and can remove it, but doesn’t control the rest of the phone.
That limit is the point of BYOD and its weakness for frontline work. You can’t lock a personal phone to one app, hand it to the next shift, or make sure it’s charged and working at the start of a route.
COPE and CYOD on company-owned phones
COPE and CYOD devices belong to the organization, so IT can manage the whole device while still allowing personal use. On Android, Google notes that work profiles can also be used on company-owned devices to allow mixed work and personal use. The organization recovers the device when the employee leaves, which simplifies offboarding compared with BYOD.
COBO dedicated and shared devices
COBO devices are fully managed and used only for work. Google describes fully managed deployments as company-owned devices intended exclusively for work purposes, and dedicated devices as fully managed devices that serve a specific purpose, such as a scanner locked to one app.
COBO devices are the devices that can be staged to a standard, shared across shifts and swapped from a spare pool. See how to stage and deploy rugged devices.
Canadian privacy and monitoring rules that shape the device ownership choice
Canadian privacy and employment rules apply to every device ownership model, but they bite hardest on BYOD, where work and personal information share one phone. Treat the points below as what to ask your privacy officer and legal team, not as legal advice.
What to ask about BYOD under PIPEDA and provincial privacy law
The Office of the Privacy Commissioner of Canada, with the Alberta and British Columbia commissioners, says a BYOD program introduces privacy and security risks that could impact both personal and corporate information. Its guidance recommends a BYOD-specific policy, keeping corporate information logically separated from personal information, and deciding in advance what happens to information on the device when an employee leaves.
Ask whether your policy covers each of those points, and whether your MDM setup actually enforces the separation the policy promises. Read more on PIPEDA compliance for mobile device management.
Ontario’s written policy on electronic monitoring of employees
Ontario employers with 25 or more employees on January 1 of a year must have a written policy on the electronic monitoring of employees in place before March 1 of that year. The policy must describe how and in what circumstances the employer may monitor employees electronically, and Ontario’s guide says it must cover monitoring through an employee’s own device used for work.
If your MDM platform collects location, app usage or other data from work or personal devices in Ontario, ask whether your written policy describes it.
Device ownership models in Quebec under Law 25
Quebec’s Law 25 is in force and adds obligations for businesses that handle personal information, including employee information collected through devices. If you have staff in Quebec, ask your privacy officer how your device setup, especially any location or monitoring features, fits your Law 25 obligations before you change ownership models.
The costs that change with each device ownership model
Device ownership models move cost between the organization and the employee, and between hardware and administration. BYOD looks cheapest because the organization doesn’t buy the phone, but it often comes with a monthly stipend, more complex support and less control over whether the device works on shift.
COPE, CYOD and COBO put the device, the plan and the replacement cost on the organization. In return, devices can be bought at fleet pricing, staged once to a standard, covered by a spare pool and retired with a certified data wipe through secure decommissioning. MDM licensing applies to every model, so it rarely decides the choice on its own.
Device ownership models for retail, logistics and healthcare fleets
Retail, logistics and healthcare fleets tend to land on the same pattern of COBO for shared work devices and COPE or BYOD for communication, with differences in what drives the choice.
Device ownership models for retail store teams
Retail stores usually run shared COBO devices for inventory, price checks and mobile point of sale, kept on chargers in the back of the store. Seasonal hiring makes BYOD tempting for scheduling apps, but store transactions belong on store-owned devices.
Device ownership models for transportation and logistics fleets
Drivers and warehouse teams in transportation and logistics depend on rugged scanners for every pickup and delivery, so COBO is the norm. Dispatchers and supervisors often get COPE phones, and some carriers allow BYOD for messaging and pay stubs only.
Device ownership models for healthcare and clinical teams
Healthcare teams handle health information, so clinical devices are usually shared COBO devices with full management and remote wipe. Personal phones are a harder fit for clinical work, because health privacy laws add obligations on top of PIPEDA. Ask your privacy officer before allowing clinical apps on BYOD.
Questions to ask before changing your device ownership model
Before changing your device ownership model, answer seven questions with IT, HR and privacy at the table.
- Which roles use the device as a work tool, and which only for communication?
- Which devices are shared across shifts or sites?
- What personal information, including health information, will the devices hold?
- What data does our MDM setup collect, and does our written monitoring policy describe it?
- What happens to work data and devices when someone leaves?
- Who pays for the device and plan, and will BYOD users get a stipend?
- Who stages, supports, replaces and retires the devices under each model?
When BYOD is the better device ownership choice
BYOD is the better device ownership choice for staff who only need email, scheduling and messaging, and for contractors or seasonal workers you’d otherwise have to issue and recover devices from. It also suits very small teams where buying and managing devices would cost more than a stipend. Just know that BYOD still needs a written policy, a work profile and a plan for removing work data when people leave.
Where PiiComm fits in device ownership models
PiiComm’s MDM as a Service (MDMaaS) team sets up and runs your MDM platform for each ownership model you choose, from work profiles on personal phones to fully managed COBO devices locked to work apps. Our Canadian team stages COBO devices before they ship and retires company-owned devices with certified data destruction and chain-of-custody records.
It doesn’t fit everyone. If your staff only need email on personal phones, a BYOD policy and your MDM platform’s built-in work profile may be all you need.
Questions IT leaders ask about device ownership models
What’s the difference between COPE and COBO?
COPE and COBO devices are both owned by the organization. COPE (corporate-owned, personally enabled) allows personal use within policy, with work data kept separate. COBO (corporate-owned, business only) is used only for work and is often locked to specific apps, which suits shared and single-purpose frontline devices.
Is BYOD secure enough for frontline workers?
BYOD is secure enough for email and scheduling when work data sits in a managed work profile, but it’s a poor fit for frontline workflows like scanning, delivery or clinical work. IT can’t lock a personal phone to work apps, share it across shifts or guarantee it’s working at the start of a shift.
Can employers monitor personal phones in Canada?
Employers’ ability to monitor personal phones in Canada depends on privacy law, employment law and what the employee has been told. Ontario employers with 25 or more employees must describe electronic monitoring, including on personal devices used for work, in a written policy. Ask your privacy and legal teams before collecting data from personal phones.
Should we pay employees a stipend for using their own phones?
A BYOD stipend is common when employees use personal phones for work calls and data, because it offsets their plan cost. Set it by role and usage, put the terms in your BYOD policy, and check the tax treatment with your payroll or finance team before you start paying it.
Which device ownership model is best for shared rugged devices?
COBO is the device ownership model that fits shared rugged devices. Shared scanners and handhelds need to be fully managed, locked to work apps, set up for multiple users and charged between shifts. They should also be easy to swap from a spare pool when one fails.
Can we mix device ownership models in one fleet?
Yes, most frontline fleets mix device ownership models by role. A common pattern is COBO for shared work devices, COPE or CYOD for supervisors and BYOD for email and scheduling. Your MDM platform applies a different policy to each group, so document which roles get which model.
What happens to work data when a BYOD employee leaves?
When a BYOD employee leaves, IT removes the work profile and the work apps and data inside it, leaving personal data alone. The OPC recommends deciding this in advance and putting it in your BYOD policy, so employees know what will be removed and when.
Where to start with a device ownership policy
List your frontline roles and decide whether each one uses its device as a work tool or for communication. Give shared and work-tool roles COBO devices, give supervisors COPE or CYOD, and limit BYOD to light communication. Then update your BYOD and monitoring policies so they match what your MDM setup actually does.
Run every ownership model from one managed MDM platform.
PiiComm’s certified technicians set up and manage work profiles, COPE phones and locked-down COBO devices for Canadian frontline fleets.
References
- Office of the Privacy Commissioner of Canada, with the Alberta and BC commissioners, Is a Bring Your Own Device (BYOD) program the right choice for your organization? (2015, modified 2025). BYOD privacy risks, policy, separation and departure.
- Government of Ontario, Your guide to the Employment Standards Act, Written policy on electronic monitoring of employees (updated 2024). 25-employee threshold, March 1 deadline, policy contents, personal devices.
- Google for Developers, Android Enterprise overview (updated 2025). Work profile, fully managed and dedicated device definitions.