Built by IT. Designed for Growing Teams.
30 Day Free Trial
No Credit Card Required

A mobile device policy is a written set of rules that says which phones and tablets can touch company data, who owns them, how they must be secured, what employees may do with them, and what happens when one is lost or an employee leaves. A small business needs one as soon as the first work email lands on a phone. This guide shows what to put in it, how to match it to your ownership model, and how to roll it out so people actually sign it and follow it.

The short version: pick your device model first, write one to three pages in plain language, tie every rule to something you can enforce or check, and make the policy part of onboarding and offboarding rather than a PDF nobody opens.

CentriOps
Keep Device Records in One Place
CentriOps helps remote teams manage company devices, employee workflows, and onboarding and offboarding alongside daily operations.
Visit CentriOps

Table of Contents

Mobile device policy vs. acceptable use policy

People use these terms loosely, and the search results blur them. They overlap, but they do different jobs.

A mobile device policy can combine device security and acceptable use, or reference a separate company AUP. Choose the structure that makes responsibilities and approvals clear. One document does not automatically cover every privacy, employment or security requirement.

Decide your device model first

The most common drafting mistake is writing rules before deciding who owns the hardware. Rules that make sense for a company-owned laptop (full-disk encryption, remote wipe, no personal apps) are intrusive on someone’s personal phone. TechTarget identifies four ownership scenarios that call for different policy approaches: BYOD, COPE, COBO, and COSU (kiosk).

Model What it means Typical fit Policy emphasis
BYOD (bring your own device) Employee owns the phone and uses it for work Small teams, part-time staff, contractors Privacy limits, minimum security, reimbursement, what you can wipe
COPE (corporate-owned, personally enabled) Company buys the device, personal use allowed Managers, field staff, sales Personal use limits, data separation, return on exit
COBO (corporate-owned, business only) Company buys it, work use only Regulated roles, shared devices Strict app list, full management, no personal accounts
COSU (corporate-owned, single use) Locked into one purpose, such as a kiosk or scanner Warehouses, retail, check-in stations Lockdown settings, physical custody

Most small businesses end up with a mix: BYOD for phones, company-owned laptops. That is fine. Write a short section for each model you actually use, and leave out the ones you don’t.

Google’s SMB Security Best Practices Guide frames the choice as a ladder of control: user-initiated security guidance at the lightest level, device-trust access controls in the middle, and full enterprise mobility management at the top. It also notes that Android Enterprise supports a Work Profile that separates business data from personal data on BYOD devices, as well as corporate-owned personally enabled and fully managed setups. Pick the rung that matches the sensitivity of the data, not the biggest tool available.

Three levels of mobile device control

Who needs mobile access at all

The National Safety Council’s guide to creating an effective mobile policy recommends documenting the business reasons for mobile access and identifying the roles with higher mobile needs. In practice, that means a short eligibility table: which job functions get a company phone, which may use a personal phone for email and chat, and which have no mobile access to company systems. It makes approvals consistent and protects you from “why does he get one and I don’t?”

What to include in the policy

Sources differ on the exact list, but they agree on the core. The National Safety Council says a policy should state its scope and business requirements, define appropriate use and the obligations of both employee and company, set password and security-software requirements, address BYOD approval and reimbursement, describe rollout and compliance auditing, cover employee education and discipline, and collect an acknowledgment. Here is that list turned into sections you can draft.

1. Purpose and scope

One short paragraph on why the policy exists (protecting company data, keeping support manageable) and who it covers: employees, contractors, interns. The NSC advises stating whether it covers company-provided devices, BYOD devices, and personal phones brought on site for personal use only. That last category matters if your workplace has safety or privacy rules about phones on the floor.

2. Eligibility and issuance

Who can have a company device, who can enroll a personal one, who approves it, and how long a device stays in service. Name the approver by role (“the operations manager”), not by person, so the policy survives turnover.

3. Supported devices and operating systems

List the minimum OS versions and the device types you support. “iOS and Android versions still receiving security updates from the manufacturer” is easier to maintain than a hard-coded version number that expires in a year. Say what support employees can expect for personal devices: usually help connecting to work accounts, not repairing a cracked screen.

4. Security requirements

The policy should define both company and employee responsibilities for securing devices, networks, and proprietary data. The NSC names password complexity, required security or device-management software, and a security checklist for employee-owned devices as topics. A workable minimum for a small business:

Protect work accounts with MFA and supported access controls. A stolen unlocked device may still contain active sessions, so MFA does not remove the need for session revocation and a lost device response plan.

If you issue company hardware, the first-day sequence matters too. A small business device setup walkthrough covers creating admin accounts, turning on encryption, and enrolling in device management before the device ever reaches an employee.

5. Acceptable use

This is the AUP portion. Acceptable use guidance from device-management vendor Jamf says an AUP should address permitted use of company devices and networks, social media use, company information and trade secrets, permitted software and websites, personal use, and consequences for violations. Keep it concrete:

A good test for every line: could a new hire read it and know what to do in a specific situation? “Use devices responsibly” fails. “Do not forward work email to a personal account” passes.

Say what you enroll the device in and what that software can see. This is the line employees care about most. Spell out what the company can see (device model, OS version, installed work apps, compliance status) and what it cannot (personal photos, personal messages, browsing history, location outside of lost-device recovery, if that is your actual setup). Do not promise limits your tools cannot enforce, and do not write monitoring rights you do not intend to use.

7. Reimbursement and costs

Document who pays for required business use of personal devices and how reimbursement is handled. Do not assume that reimbursement is optional. Requirements vary by location and employment circumstances, so have HR or employment counsel review the approach for every state where staff work.

8. Lost, stolen, or compromised devices

Give employees one rule and one contact: report immediately, to a named channel, even if you are not sure the device is gone. The sources are consistent that speed matters more than blame. We cover the admin response in the next section.

9. Offboarding and device return

Set the required return date and shipping process for company equipment. At separation, remove authorized company access and work data according to the approved policy and retention requirements. Record who verifies completion.

10. Enforcement and acknowledgment

List the consequences for violations in proportionate terms, from retraining to loss of mobile access to formal discipline. End with a signature or e-acknowledgment line stating the employee has read, understood, and agreed to the policy.

When a device is lost, stolen, or compromised

This is the section that gets tested. Write it as a short sequence that both the employee and the admin can follow without guessing.

For the employee:

  1. Report the loss to the named channel immediately, not after searching the house for two days.

  2. Say what the device had on it: work email, chat, file access, saved passwords.

  3. Contact IT through a known, trusted channel and follow its recovery instructions. Use a trusted device when directed, and report any suspected credential exposure.

For the admin:

  1. Revoke the device’s access to company accounts and sessions.

  2. Quarantine the device in your management tool if you have one.

  3. Use remote lock or selective removal of work data only through the supported management system and approved incident process. Check ownership, authorization and evidence retention needs before a full wipe. A remote command may not execute while a device is offline.

  4. Assess which credentials and tokens may have been exposed, then revoke sessions and rotate affected secrets as the incident requires.

  5. Record the incident, the time of report, and the actions taken.

TechTarget’s guide ties written policy to technical enforcement in exactly this way: access revocation, quarantine, and, when necessary, remote wipe. NIST’s Mobile Device Security: Bring Your Own Device practice guide (September 2023) is built around protecting data from unauthorized access when a device is lost or stolen, and improving employee privacy protections in BYOD deployments. It is a technical document, but its example architecture is a useful reference if you have an outside IT provider.

A caution where employees act on it: wiping a personal phone can erase family photos if the device is fully wiped rather than selectively wiped. Say in the policy which one you will do, and have employees back up personal data on their own.

BYOD creates a tension that no template resolves for you. You need to protect company information on a device you do not own, and the employee needs to keep personal life private on a device they pay for. NIST’s BYOD guidance describes the goal as balancing protection of organizational information with enhanced privacy for employees.

Some practical ways to stay on the right side of that balance:

The point of all this is trust. A policy that reads like surveillance gets ignored or resisted. One that says “here is what we can see, here is why, and here is what we will never touch” gets signed.

Roll it out so it sticks

A policy that lives in a shared drive is not a control. The NSC recommends clear drafting, consistent implementation, employee education, compliance auditing, and an acknowledgment that employees read, understood, and agreed. A rollout checklist from Trio’s BYOD guide for SMBs adds practical steps: draft, get IT, legal, HR, and leadership review, publish, train during onboarding with annual refreshers, collect sign-off, enforce controls, track compliance, and review after incidents or at least annually.

For a small team, that comes to six steps:

  1. Draft in plain language. Aim for two or three pages. If it needs a glossary, it is too long.

  2. Review once. One pass each from whoever runs IT, HR, and a senior leader. Add legal review if you have staff in states with stricter privacy or reimbursement rules.

  3. Publish in one place. One URL or folder that everyone knows.

  4. Train in ten minutes. Walk through the five rules that matter most: lock, update, MFA, report losses, return on exit.

  5. Collect acknowledgments. Record who signed and when. Make it a task with an owner, not an email chain.

  6. Audit and review. Check device compliance quarterly and revisit the policy at least annually and after any incident.

Build it into onboarding and offboarding

The moment a policy is most likely to be followed is the first week. Add three items to your new-hire checklist: policy acknowledgment, device enrollment, and MFA setup. Our IT onboarding checklist for SMBs lays out a phase-based sequence for this, and the remote onboarding process guide covers shipping devices to people who will never visit an office.

Offboarding is where policies quietly fail. The phone is not returned, the work profile stays installed, a shared app login is never rotated. Treat the last day as a checklist: collect or wipe the device, revoke access, rotate any shared credentials, and record it. For retired hardware, a hardware disposal policy ensures data is erased before a device is resold, recycled, or donated. Access to individual apps deserves its own attention; our software access management playbook covers that side.

Our perspective: a policy is only as good as your records

CentriOps is designed to help small and midsized teams keep device assignments and operational work organized. An accurate record of equipment, responsible people and completed policy tasks supports the technical controls in a device management system.

Assign a responsible person and due date to policy follow up work. Keep an equipment record, collect acknowledgments through your chosen HR or signing process, and record that the required onboarding or offboarding steps were completed. Checklists help coordinate the work; the relevant security tools enforce device controls.

Start with the smallest policy you can enforce, keep an accurate device and user list, and expand only when you find a real gap. That is cheaper, and more secure, than a thirty-page document nobody reads.

— CentriOps Team

Track devices, signatures, and exits in one place

CentriOps brings People, Devices, Requests, Tasks and Checklists into one workspace. Assign devices to people, track policy acknowledgment and equipment return as checklist steps, and schedule review tasks with due dates. Collect signatures through your chosen signing or HR tool and retain the evidence under your policy. CentriOps does not enroll devices in MDM, enforce device settings, monitor personal phones or remotely wipe them. Current plans and limits are at centriops.com/pricing/.

CentriOps

If you want to see how device records and checklists fit together, read about asset lifecycle management for SMBs or browse what the platform does.

A one-page policy skeleton you can adapt

Use this as a starting outline and fill each line with your own decisions:

Keep the owner and the review schedule at the bottom. A policy without an owner goes stale.

Common mistakes

FAQ

What is a BYOD policy?

A BYOD policy covers work performed on personally owned devices. It explains required security, permitted monitoring and data removal, cost arrangements and exit steps. Give employees clear notice, document acknowledgment as required and confirm the terms with HR or counsel.

Can a company legally say you can’t use your phone at work?

Phone use rules depend on the work, location and applicable employment, safety, privacy and accommodation requirements. Have employment counsel review restrictions, especially rules covering breaks, emergencies, recordings or personal devices. A general template is not a legal determination for your workplace.

Do I need a separate mobile acceptable use policy?

Not usually. For a small business, one document with a clearly labeled acceptable use section is easier to maintain and sign. Split them only if a different team owns each or your auditors ask for separate documents.

How often should we update the policy?

Review it at least once a year and after any security incident or major change, such as a new device type or a new MDM tool. Put the review on a recurring task with a named owner so it does not rely on someone remembering.

What should happen to a personal phone when an employee leaves?

Revoke company access and remove managed work data using the approved tools and process. Use selective removal where supported, respect retention requirements and record the result. Verify what the tool can actually remove; do not promise that a remote wipe eliminates every copy of company data.

Sources

Download Your Free Guide from CentriOps

A quick guide for non-IT staff suddenly managing tech at work.

By submitting, you agree to our Privacy Policy. No spam. Unsubscribe anytime.