A mobile device management (MDM) policy is a short written rulebook that says which phones, tablets and laptops may touch your business data, how they must be secured, what you can see or erase on them, and what happens when one is lost. For a small business the policy does two jobs. It sets the rules your staff agree to, and it tells your IT provider exactly what to configure and enforce. A policy that nobody signs, or that nobody enforces, protects nothing.
This guide gives you the sections to include, the security settings to require, the privacy wording that makes employees comfortable enrolling personal phones, and a rollout plan. It is written for owners and office managers at dental practices, law firms, manufacturers, nonprofits and other small organizations in Oklahoma and beyond.
Key Takeaways
- Write the policy as a governance document: who is covered, which devices, what is required, what you can see, and what happens if rules are broken. Keep technical settings in a separate standard your IT team can update.
- Separate rules for company-owned devices and personal (BYOD) devices. Company devices can be fully wiped. Personal devices should only lose work data.
- A policy without a signed employee acknowledgment is hard to enforce, especially for remote wipe on a personal phone.
- Regulated offices (dental, legal, defense suppliers) need the policy to map to HIPAA, professional ethics duties or CMMC, with evidence kept on file.
- Review the policy at least once a year, and again after an incident, a major OS change or a new regulation.
Table of Contents
- What a mobile device management policy covers
- Decide your device model first
- The sections your policy needs
- Security requirements worth writing down
- Lost or stolen devices: write the procedure, not just the rule
- Privacy, monitoring and remote wipe
- Industry rules that shape the policy
- Roll it out in four steps
- Common mistakes to avoid
- Getting the policy written and enforced
- FAQ
- Sources
What a mobile device management policy covers
MDM refers to the software and settings that let a business enforce rules on phones and tablets: encryption, passcodes, app control, remote lock and wipe. The policy is the written side of that. It states the rules in plain language so that the software has something to enforce and the employee knows what to expect.
Two distinctions help you plan:
- Policy versus standard. The policy says what must be true (devices must be encrypted, lost devices must be reported promptly). The standard or procedure says how (which setting, which app, which menu). Policies change rarely. Standards change whenever Apple, Google or Microsoft change something.
- Mobile device policy versus acceptable use policy. An acceptable use policy covers how staff may use all company technology, including email, internet and software. The mobile policy narrows to devices that leave the building. Many small businesses write the mobile policy as an addendum to the acceptable use policy.
Decide your device model first
Before you write a line, decide who owns the devices. This choice shapes every other section.
| Model | Who owns the device | Typical rule set |
|---|---|---|
| Company-owned | The business | Full management, full wipe allowed, no expectation of personal privacy on the device |
| BYOD (bring your own device) | The employee | Work apps and data separated from personal ones, only work data can be removed |
| Hybrid | Both, by role | Company phones for field or regulated staff, BYOD for everyone else |
Many small businesses cannot buy a phone for every employee, so BYOD tends to become the default. The key is to keep work data in a managed container, such as a Microsoft 365 work profile or app protection policies, so that you never need to touch personal photos or messages. Our guide to Intune app protection policies explains how that separation works in a Microsoft 365 environment.
The sections your policy needs
Templates from different sources vary, but they converge on the same core. Mobile security guidance from TechTarget lists an acceptable use section, separate rules for company-owned and personal devices, device registration, training and acknowledgment, incident response, enforcement and device return. A practical ten-part outline for a small business looks like this:
- Purpose and scope. State why the policy exists and who it covers: employees, contractors, temporary staff and volunteers, using phones, tablets and laptops that reach company email, files or applications.
- Roles and ownership. Name who approves exceptions, who administers devices, and who handles incidents. In a small office this is often the owner, an office manager and your IT provider.
- Eligibility and issuance. Which roles get company devices, which may use personal ones, and any stipend or reimbursement.
- Enrollment. Devices must be enrolled in management before they can read company email or files.
- Security requirements. Encryption, passcodes, auto-lock, updates, no jailbreaking (see the table below).
- App management. Which apps are approved for work data, and whether staff may install others on company devices.
- Acceptable use. No use while driving or operating machinery, no storing company data in personal cloud accounts, no pirated software.
- Lost, stolen or compromised devices. Who to tell, how fast, and what IT will do.
- Privacy and monitoring. In plain words, what the company can and cannot see.
- Offboarding and return. How company data is removed and company devices returned when someone leaves.
Add a signature block, a version number and a review date. Those last items matter more than they seem, as the rollout section explains.
Security requirements worth writing down
Good requirements are specific enough to check. "Devices must be secure" cannot be audited. "Devices must auto-lock within 5 minutes" can.
A real example helps. Jefferson County, Colorado, publishes a mobile device management policy that requires county data on mobile devices to be encrypted, requires auto-lock after 5 minutes of inactivity, prohibits jailbroken or rooted devices and denies them access. It also attaches consequences: loss of privileges and discipline under personnel rules. A small business can borrow that structure with simpler language.
| Requirement | What to write | Why it matters |
|---|---|---|
| Encryption | Device storage must be encrypted | A lost phone is unreadable without the passcode |
| Passcode | Minimum length, no sharing; biometrics allowed for convenience | Blocks casual access |
| Auto-lock | Screen locks after 5 minutes or less idle | Limits exposure when a device is left on a desk |
| Updates | Operating system updated within a stated window; unsupported versions blocked | Closes known vulnerabilities |
| Multi-factor authentication (MFA) | Required for email and cloud apps | Stolen passwords alone are not enough |
| Jailbreak and root | Prohibited; detected devices lose access | Removes built-in protections |
| Malware protection | Required where the platform supports it | Catches malicious apps and links |
| Reporting | Loss or theft reported to a named contact within a stated time | Starts the response clock |
Guidance from TechTarget also recommends conditional access, which checks device health, operating system and sign-in context before granting access to company data. In a Microsoft 365 setup, this is how a policy becomes enforceable: a device that falls out of compliance simply stops getting mail. Our walkthrough of Intune device compliance shows how those rules are deployed.
If your team also plugs removable drives into office computers, add a short cross-reference to your USB device control policy so that phones and storage devices follow one consistent standard.
When you document each requirement and keep records of how it is encrypted and where the data lives, a plain description of your data security and encryption practices is the kind of material auditors and customers ask to see.
Lost or stolen devices: write the procedure, not just the rule
The most useful page of the whole policy is the one people read at 6 p.m. when a phone goes missing. Keep it to a short sequence:
- Report the loss immediately to a named contact. Give a phone number, not just a department.
- IT locks and locates the device through the management tool.
- IT revokes access: signs out sessions, resets the password and revokes tokens.
- If the device is not recovered within a set time, IT wipes it. If it held regulated data such as patient or client records, wipe immediately.
- Log the incident and decide whether it is a reportable breach.
The federal NIST guidance on mobile device security adds an important caution: remote wipe should be one layer of protection, not the only one, because an attacker may reach the data before the wipe or power the device off to block the signal. That is why encryption and a strong passcode come first in the requirements.
Privacy, monitoring and remote wipe
This is the section where most BYOD programs succeed or fail. Employees hesitate to enroll a personal phone because they fear the company will read their texts or erase their photos. The fix is plain disclosure. List what IT can see (device model, operating system version, whether the device is compliant, work apps) and what it cannot (personal photos, messages, browsing history, personal app data).
NIST describes two kinds of wipe. A full-device wipe is typical for company-owned devices. An enterprise-only wipe deletes just work data and is the right choice for a personal device. Write both into the policy and say which applies to which device.
The legal side deserves attention:
- Employment lawyers at Littler note that U.S. employers are generally presumed to have the right to monitor their own resources, but intercepting communications in transit can trigger federal and state wiretap laws, which in most states depend on consent. Your policy should say that company systems are company property and that monitoring may occur.
- A legal analysis from Smith Anderson warns that without separation of company data and an employee's consent to wipe, a company may be liable for destroying personal information. It also notes that a policy without a signed user agreement is not contractually binding on the individual.
In practice: keep work data in a managed container, have each BYOD user sign a consent to enrollment and selective wipe, and have a lawyer review the BYOD and wipe wording before launch. If you offer a phone stipend, document it in the same agreement.
Industry rules that shape the policy
The recommendations above are good practice for any business. Some offices have rules that make parts of them mandatory.
Dental and medical practices
If staff read email or patient messages on phones, those devices touch electronic protected health information, which brings HIPAA safeguards into scope. In policy terms that means encryption, remote lock, a wipe procedure, and an incident log. Write the lost-device step so that a device holding patient data is wiped immediately, and keep records of who was enrolled and when.
Law firms
The Michigan State Bar's cybersecurity FAQs state that a lawyer's duty to safeguard client information on a personal device is the same as on a firm device. The bar suggests two approaches: an MDM-created sandbox that separates firm data from personal data, or virtualization over an encrypted connection so that no confidential information is stored on the personal device. Other states have their own ethics opinions, so check yours.

Manufacturers and defense suppliers
If you handle controlled unclassified information for the Department of Defense, mobile devices fall under CMMC and NIST SP 800-171 requirements. A policy in that setting needs enrollment and de-enrollment steps, allowed apps, no local storage of controlled data, incident reporting, an exception process, and signed acknowledgments with version control. See our summary of CMMC 2.0 requirements for what contractors must do.

Nonprofits
Nonprofits often rely on volunteers and personal devices. Scope the policy to include volunteers, limit what they can reach, and favor app-level protection so that a volunteer's phone never stores donor records.
Roll it out in four steps
The policy only works if it is communicated and enforced. A workable rollout for a small team:
- Legal review. Have an attorney check the BYOD, remote wipe and consequences language. Employment law differs by state.
- Owner and HR sign-off. Decide consequence tiers before launch so enforcement is consistent. Name one person as the approver whose signature goes on the document.
- Distribute and collect signatures. Require a signed acknowledgment before a device gets access to company email or files. Jones Day's guidance on mobile device policies points to acknowledgment and periodic certification of compliance as standard elements, alongside purpose and scope, encryption and password requirements, and rules for when remote wiping is allowed.
- Enforce and keep evidence. Keep signed agreements, an inventory of devices matched to users, enrollment records and compliance reports. If an auditor, insurer or client asks, you can show the policy working rather than just existing.
Set a review date when you publish. Once a year is a sensible minimum for a small business, with extra reviews after a security incident, a major operating system change, new regulations or a change in how people work.
Common mistakes to avoid
- Copying a template unchanged. Templates written for large enterprises include committees and roles you do not have. Cut them down to the people you actually employ.
- Writing technical settings into the policy. Put them in a standard so you do not rewrite the policy every time a setting moves.
- Skipping the BYOD privacy language. Vague wording makes employees refuse to enroll, which leaves unmanaged phones reading company mail.
- No exceptions process. Someone will need an older device or a special app. Give them a way to ask and a record of the answer.
- No one watching compliance. A rule that nobody checks is a suggestion.
Getting the policy written and enforced
We help small businesses in Norman, Moore and Oklahoma City turn a mobile policy into settings that actually apply. Our managed IT support includes 24/7 monitoring, same-day response and no long-term contracts, and our Microsoft 365 support covers setting up and managing the accounts your devices connect to. For offices with compliance duties, our cybersecurity work includes guidance on HIPAA, IRS and CMMC requirements.
If you want to know where your devices stand before you write anything, start with the 10-minute readiness audit or ask for a free network assessment.

FAQ
What is a mobile device management policy?
It is a written set of rules for how company-owned and personal phones, tablets and laptops may be configured, used and secured when they access business email, files and apps. It covers security requirements, privacy, lost devices and what happens when someone leaves.
Do I need a separate BYOD policy?
Not always a separate document, but you need separate sections. Company-owned devices can be fully managed and wiped, while personal devices should keep work data in a managed container and lose only work data when removed. Employees should sign a consent to enrollment and selective wipe.
What should a mobile device security policy require at minimum?
Encryption, a passcode with auto-lock at 5 minutes or less, timely operating system updates, MFA for company accounts, a ban on jailbroken or rooted devices, and a named contact for reporting a lost or stolen device. Add the rules your industry requires, such as HIPAA safeguards for a dental practice.
How often should we review the policy?
At least once a year, and again after an incident, a major operating system change, a new regulation or a change in how your team works. Update the version number and collect fresh acknowledgments when the changes affect employees.
Can we monitor employees' personal phones?
Only within the limits your policy and the law set. Limit visibility to device model, operating system version, compliance status and work apps, and tell employees in plain words what you cannot see. Have an attorney review the wording, because monitoring and consent rules differ by state.
Sources
- NIST SP 800-124 Rev. 2: Guidelines for Managing the Security of Mobile Devices in the Enterprise
- Jefferson County Mobile Device Management Policy
- How to create a mobile device security policy, TechTarget
- Michigan State Bar Association Cybersecurity FAQs
- Littler: Ten Tips for Preparing an Effective Acceptable Use Policy
- Smith Anderson: BYOD policy and legal considerations
- Jones Day: Considerations for Addressing DOJ's Corporate Compliance Guidance
- Data Security and Encryption
