Company Phones: Handover Day Checklist

Confirm that the phone belongs to the company

Start by establishing who owns the device and who is authorized to make decisions about its configuration. A company-owned phone issued to an employee is different from a personally owned phone used occasionally for work. The distinction matters because an employer should not assume that providing access to business systems automatically grants permission to monitor every aspect of an employee's device activity.

Record the device's intended business purpose, the employee receiving it, and the person responsible for administration. If the phone is part of a shared equipment pool, identify the individual responsible for it during each assignment. These details help prevent confusion when devices are transferred, returned, replaced, or reassigned.

• Confirm company ownership and the intended business use.
• Identify the employee receiving the phone.
• Assign responsibility for device administration.
• Clarify what happens when the device is returned or reassigned.

What should employees know before installation?

An employee should receive the monitoring policy before installation begins, not after the device is already configured. Explain why the organization uses monitoring, which categories of information may be collected, who can view the information, and how it relates to legitimate business responsibilities. A general statement that a phone is monitored is less useful than a clear explanation of the actual scope.

A company phone handover checklist should also identify the communication and acknowledgment process. Employees should have an opportunity to ask questions about personal information, working hours, data retention, and access to collected records. Use a written policy and clear notice, and obtain any consent required under applicable local rules. A signature or acknowledgment should not be treated as a substitute for legal compliance.

• Explain the business purpose of monitoring.
• Describe the categories of information that may be collected.
• Identify authorized people who can access monitoring information.
• Explain how personal use and working hours are addressed.
• Provide a contact for privacy or policy questions.

Use handover day to establish physical access

Installation requires physical access to the company phone. This is why handing over the device in person is a practical opportunity to address installation readiness. Remote access to an online dashboard is a separate matter: having an account or being able to view a dashboard does not mean the monitoring app can be installed on a phone that is elsewhere.

Allow the employee and authorized administrator to be present while the device is made available for the agreed setup. If the phone is still being prepared, belongs to another department, or cannot be accessed, record the outstanding issue and arrange another appointment. Do not treat an installation deadline as a reason to bypass normal device security or privacy controls.

Check compatibility and monitoring scope

Before committing to a particular configuration, check the current mSpy feature list and device requirements on the official website. Available functionality depends on whether the phone uses Android or iOS, its operating system version, the selected plan, and the way the app is configured. Some functions also require permissions on the monitored phone. Physical possession alone does not guarantee that every listed feature will be available.

The listed functions may include GPS location information, route history, geofence alerts, Wi-Fi network lists, supported messaging and social app information, SMS, email, keyword alerts, call logs, browser history, bookmarks, website and app blockers, contacts, calendar entries, and photo or video viewing. More intrusive capabilities include keystroke logging, periodic screen capture, live screen streaming, and call recording where legally permitted. These functions require especially careful consideration because they can expose sensitive personal information.

Monitoring should be limited to what the organization genuinely needs for a legitimate business purpose. A feature appearing on a product website does not establish that it is suitable for every employee, device, or workplace. Nor does it establish that the feature is lawful in every jurisdiction.

Document permissions, responsibilities, and unresolved issues

Before the employee leaves with the phone, confirm that the organization's policy, notice, and required permissions have been addressed. Identify who manages the monitoring account, who reviews information, and how access is restricted when an employee changes roles or returns the device. The administrator should also know where to find the current product documentation and how to raise questions about supported features.

Consent and transparency should remain part of the employment relationship, not merely a formality at handover. Employees should understand the monitoring arrangement and know whom to contact if the device is used outside its intended business context. Laws differ by country, and workplace monitoring requirements can depend on the information collected and the circumstances. Consult a qualified local lawyer or relevant official authority when the policy's legal basis is uncertain.

• Record policy acknowledgment and any required consent.
• Identify the monitoring account administrator.
• Document who is authorized to review collected information.
• Set a process for device return and reassignment.
• Postpone setup if permissions, access, or policy questions remain unresolved.

Questions readers ask