Woman wearing headphones working at a computer, with an activity-tracking panel showing time spent in Safari, Sketch, and Slack.

A guide to flexible deployment across company, personal, and mobile devices

Most organizations don’t run on one kind of device: office staff use company laptops, contractors work from their own computers, and field teams log hours on their phones. As BYOD in the workplace becomes more common, one tracking setup rarely fits all three. With Hubstaff’s deployment options, organizations get workforce visibility across company-owned computers, personal computers, and mobile devices in one account, with tracking matched to who owns each device and how each team works. That lets BYOD monitoring sit alongside managed hardware without a separate tool for each group. 

This guide explains how each option works and who it fits, how to choose between personal and company-owned devices, and how to run all three side by side. It also addresses the privacy controls and rollout plans that apply to every deployment. 

Hubstaff deployment options at a glance

Device ownership determines who installs Hubstaff, who decides when tracking starts, and how much of a team member’s activity is recorded. The right configuration depends on the team using it. 

Company-owned computersPersonal computers (BYOD)Mobile devices

Who installs it

IT or an admin, centrally

The team member

The team member

How tracking starts

Automatically, based on admin policy

The team member starts and stops the timer

The team member starts and stops the timer

What’s captured

Time, keyboard and mouse activity levels, and optional screenshots and app/URL tracking

The same data, but only while the timer runs

Time, notes, and tasks, with optional location

Best for

Regulated, shared, or IT-managed environments

Contractors and distributed teams

Field, hybrid, and on-the-go roles

Organizations can also combine all three in one account, as we’ll cover in detail below.

Company-owned devices: automatic tracking your IT team controls

Company-owned device tracking gives IT teams consistent, complete time and activity data across managed computers, with no timers for users to remember.

Admins set the policy once, based on a schedule or a network for instance, and Hubstaff then collects the data in the background. Rollout runs through the management tools IT already uses, so the main decision left is which teams to track automatically. 

How rollout works on managed devices

Rolling out Hubstaff on company-managed devices is straightforward since IT controls the setup centrally and individual team members install nothing. Admins follow the same sequence on Windows, macOS, and Linux:

  1. Set the tracking policy. Admins configure when tracking starts and what is recorded. This includes optional screenshots and app and URL tracking in the admin settings.
  2. Deploy through existing tools. Push the installer with Microsoft Intune, Jamf, Group Policy, JumpCloud, an RMM tool, or a scripted install. Intune app deployment, for instance, can distribute the .msi installer for Windows, while macOS uses a .pkg and Linux a .sh script.
  3. Tracking runs automatically. Accounts are created on first install, and each device then follows the company’s policy with no team member sign-up.

Teams comparing employee monitoring software for Mac should plan for one manual step: each user approves the Screen Recording permission, though admins can pre-stage app and URL permissions with a .mobileconfig profile.

You can find full instructions in our setup guides for MDM deployment and deploying background tracking at scale. You can also read about resource usage on managed devices.

When company-owned device tracking is the right fit

Company-owned device tracking produces the most consistent results, but it depends on IT-managed hardware and a written policy, so it isn’t the right fit for every team. The best choice depends on a team’s structure and the industry it’s in. It’s a great fit for these situations:

  • Regulated industries that need audit trails. Teams under audit requirements often have to produce time and activity records on request. Policy-based tracking collects that data on every managed device without any individual action.
  • Shared or shift-based workstations. When several people use one computer over a day, a timer can easily be left running or never started. Tied to a schedule or shift, tracking starts and stops on its own. 
  • Client-issued equipment at business process outsourcing (BPO) providers. BPO providers often work on computers supplied by their clients. Where IT manages those devices centrally, the provider can deploy tracking through its existing management tools.
  • Teams that value consistent data over timer-based flexibility. Teams that bill clients from tracked time need every hour recorded the same way. With one policy applied to every managed device, records stay comparable across the team.

A written tracking policy and team member notice still apply in each of these situations. The guide to company device tracking policies explains how to draft one.

Personal devices (BYOD): tracking employees start and stop

Most of the advantages and disadvantages of tracking time on BYOD devices come down to ownership. When a team member uses their own computer, they stay in control. Tracking only runs when their timer is on and they pick the project and task for every entry. 

For BYOD monitoring, team members can use Hubstaff to track time in three ways: desktop app (macOS, Windows, or Linux), the Chrome extension, or the web timer. To help teams decide which option fits how they work, we put together a comparison of the web timer vs. desktop app.

In Hubstaff, screenshots and app and URL tracking are optional. Admins can configure monitoring with privacy in mind by deciding which of these settings apply to each team or individual. Team members can also view their own data to check what was recorded.

The main BYOD pros and cons are the trade-offs between coverage and control. Since team members control when tracking runs on their own devices, organizations get records only when the timer is running, not the automatic, continuous tracking that’s possible on company-owned devices. That trade-off is often worth it to contractors and distributed teams where complete and consistent activity data isn’t essential. 

Since individual team members control the timer, agreeing on how tracking will run before anyone installs Hubstaff keeps expectations clear.

Setting BYOD expectations with your team

A BYOD policy for employees puts those expectations in writing. Team members and managers work from the same rules, and IT gets one reference to apply across personal computers. Building one means agreeing on a few points with your team:

  • When tracking runs. The employee always starts it. The policy should say when team members are expected to run their timer.
  • What is captured. Choose which optional settings each team will use, such as screenshots, and list them so team members know what to expect.
  • Who can see it. Identify which admins and managers can view each team’s data, and tell team members who they are.
  • How long data is kept. Confirm the retention period your plan provides and state that same period in the policy.
  • What happens at offboarding. Decide how a departing individual’s tracking and data will be handled and add that to the policy.

A complete policy goes into more detail on each point, and our company device tracking policy covers how to draft an effective one.

Mobile devices: time tracking for teams beyond the desk

For field or hybrid teams who aren’t at a desk all day, time tracking often happens on a phone.

But the experience is just as easy, and mobile hours land in the same timesheets as hours recorded on desktop apps. Managers review one set of timesheets whether hours came from the office or the field. A team can track entirely on phones or across phones and computers.

Hubstaff’s mobile app runs on iOS and Android and is included in every plan. As an employee tracking app, it lets team members start and stop timers, switch between tasks, and add notes to their entries.

Managers can review and approve timesheets from their phones too, without waiting until they’re back at a desk. Because team members install the app themselves, IT has no installer to push to each phone.

Mobile workforce tracking also continues without a connection. The app records time offline and syncs automatically once the device reconnects. Hours worked in areas with weak coverage still reach the timesheet, and team members don’t need to re-enter anything.

Mobile time tracking fits roles that move between locations, so begin with those teams and expand once their entries appear in timesheets as expected.

Location is a separate, optional setting that admins control, and it stays off unless an admin turns it on. Before launch, decide whether your team needs it and tell members what the app collects.

BYOD vs. company-owned devices: how to choose

In a BYOD vs. company-owned comparison, BYOD means bring your own device: employees use personal computers or phones for work, and they own the hardware.

CYOD, or choose your own device, lets employees pick from a company-approved list, and the organization buys and owns the hardware.

A COPE device, short for corporate-owned, personally enabled, is selected and issued by the organization, and employees may also use it for personal tasks.

What separates the three is who owns the device and who selects it:

  • BYOD. A laptop that a contractor owns and uses for client work, or a phone an employee uses to log hours in the field. Both belong to the person using them.
  • CYOD. A laptop that an employee selects from a short list of approved models. The choice is the employee’s, but the list and the purchase belong to the organization.
  • COPE. A phone that the organization selects and issues, which also carries the employee’s personal apps. The organization manages it, and the employee can use it outside work.

Ownership also decides who installs software on the device and who sets the rules for how it is used.

Hubstaff treats CYOD and COPE devices as company-owned, leaving two groups to plan around: personal and company-owned. Placing a team in either category starts with a few questions about the work:

ConsiderationPoints to company-owned trackingPoints to personal-device tracking

Device ownership

The organization, which manages devices through mobile device management (MDM)

The employee or contractor

Record completeness

Audits or client billing call for full records

Timer-based entries are sufficient

Work sensitivity

Regulated or confidential material

Lower sensitivity

Control over when tracking runs

Admins, through policy

The employee

Larger organizations most often choose a mix instead of a single model, because the answers vary from team to team. Hubstaff supports that mix in one account.

Running multiple deployments in one account

Organizations with a mix of devices don’t need a separate tool for each: Hubstaff runs manual (time-based) and automatic tracking side by side in a single account. Admins assign the tracking mode by team or by role, and the assignments follow how each group works:

  • In-office staff on company laptops use automatic tracking that follows admin policy, which keeps their records consistent.
  • Contractors on personal computers start and stop their own timers.
  • Field staff on mobile devices track time from the mobile app.

When a team’s devices or work change, an admin can reassign it later, moving it from timers to automatic tracking or the reverse, in the same account.

Managers review one set of reports and timesheets, no matter how a team tracks time. Admins also manage access through one set of role-based permissions, which controls who can view and approve each team’s time.

Privacy, consent, and data controls across every deployment

Legal and HR reviewers want to know what each deployment collects and who can see it. Hubstaff’s guiding principles of transparency, access, and control shape the privacy settings across company-owned, personal, and mobile devices:

  • Data captured. Activity is recorded as keyboard and mouse activity levels, not keystrokes, and there’s no webcam access. Document this so reviewers can see what each team collects.
  • Capture by device. Company-owned computers track according to admin policy, personal computers track only while the employee’s timer runs, and mobile devices capture time, notes, and tasks, with optional admin-controlled location. List the device types your organization uses and the tracking mode assigned to each.
  • Employee visibility. Employees can view their own data. Tell them where to find it so they know what is recorded.
  • Role-based access. Permissions limit each person’s access to the data their role requires. Review role assignments whenever a team changes how it tracks.
  • Encryption. Data is encrypted in transit and at rest. Cite it in security questionnaires and vendor reviews.
  • Data retention. The plan determines how long data is kept. Compare it with the retention period your own policies require.
  • Single sign-on (SSO). Teams can sign in through Azure AD, Okta, OneLogin, or Google Workspace. Connect it to your existing identity provider.

Hubstaff’s compliance support includes SOC 2 Type II, GDPR, and HIPAA. For every deployment type, give employees notice and a written policy. Check local rules before launch, starting with employee monitoring laws.

For personal devices, document how your organization handles BYOD employee rights in that policy.

Rolling out Hubstaff across your devices

Set up Hubstaff across device types in order, since each step builds on the one before. That way, every team’s tracking mode and policy are in place before anyone starts tracking:  

  1. Map devices and teams. List each team, the devices its members use, and who owns them. The map shows which mode each group will need.
  2. Choose a deployment for each group. Assign every team a mode based on who owns its devices and what records its work requires. Write each assignment down so the plan is clear to everyone involved.
  3. Document the policy and tell employees. Write the tracking policy for each deployment type and share it before anyone starts tracking. Plain answers about what is collected and why support getting team buy-in.
  4. Pilot with one team. Start with a single team and confirm that the install method works and that its hours appear in timesheets. Fix any issues before adding more teams.
  5. Deploy and review the first reports. Extend the deployment to the remaining teams, then check the first reports to confirm each group’s hours are recorded as planned. Share what the reports show with team leads and adjust any assignment that doesn’t fit.

To help you better schedule each phase, this guide to realistic implementation timelines will show how long a rollout takes at different team sizes. Our team can also help you plan a mixed rollout across your device types.

Find the right deployment mix for your organization

Hubstaff supports company-owned computers, personal computers, and mobile devices in one account.

Each team gets the tracking mode that fits its devices and its work. This gives you consistent records where audits require them and flexible timers everywhere else. The privacy and compliance controls stay the same across every deployment, which gives legal and HR reviewers one set to evaluate.

Our team can show you how you can match tracking to every team and plan the rollout with Hubstaff’s deployment options.

Frequently asked questions

Can my employer track my personal phone or computer?

Yes, an employer can generally track a personal phone or computer when employees receive notice and give consent, though the rules vary by jurisdiction and organizations should check local requirements.

In Hubstaff, tracking on personal devices runs only while the employee’s timer is on, so the employee controls when it happens.

What is the difference between BYOD, CYOD, and COPE?

The difference between BYOD, CYOD, and COPE is who owns and selects the work device.

With BYOD (bring your own device), employees use their own. With CYOD (choose your own device), they pick from a company-approved list, and with COPE (corporate-owned, personally enabled), the organization issues the device.

Hubstaff treats BYOD as personal-device tracking and CYOD and COPE as company-owned.

Does Hubstaff track employees outside work hours?

Hubstaff tracks employees only within the limits set for each device type. On personal and mobile devices, the limit is the employee’s timer, so tracking runs only while it is on. On company-owned devices, the limit is the policy an admin sets, such as a schedule, a shift, or a network.

Can we switch a team from one deployment type to another later?

Yes, you can switch a team from one deployment type to another later. An admin can reassign the tracking mode by team or role, such as moving a team from timers to automatic tracking, and reporting and timesheets stay in the same account.

Increase transparency and trust with Hubstaff

Try Hubstaff’s employee monitoring features now. Free for 14-days. No credit card required.