Skip to content
Menu

Businesses & Employers Hub

Personal phones for work: agreeing the boundaries in a small business

Staff already checking bookings on their own phones? Start with the work they need to do, the information involved and clear boundaries before adding another app.

Two florist colleagues looking at a smartphone beside a laptop in their shop.

  • Businesses & Employers Hub

Before staff use their personal phones for work, agree which tasks are allowed, how work information will be protected and what happens if a phone is lost. The National Cyber Security Centre (NCSC) recommends defining responsibilities and permitted activities in a bring-your-own-device policy.[6]

For a small employer, start with what already happens. Does someone check bookings on their own phone, photograph a customer order or answer work emails? This is practical preparation for a discussion with your IT support, not legal advice or a ready-made security policy.

Find out what the phone is being used for

Choose one everyday task and ask the person doing it to explain the steps. In a florist’s shop, that might be receiving a customer request while away from the counter. Where does the message arrive, who needs to see it and where does the information end up?

Record the work purpose without inspecting anyone’s private messages or photographs. Ask colleagues to describe the route using a made-up example rather than opening a real customer’s details in front of the team. Include the owner’s phone in the conversation, too.

The NCSC describes personal-device working as a balance between protecting business information and respecting the device owner’s privacy. Its detailed guidance is mainly for medium and large organisations, though it says technically capable smaller organisations can use it too.[2] Take the questions to your support provider rather than attempting an unfamiliar technical setup alone.

Decide what is allowed before adding another app

Write down the tasks you want to allow and those you do not. The NCSC’s policy guidance distinguishes access to a service from permission to do everything inside it.[6] Being able to read an order need not mean being allowed to export the whole customer list.

Discuss where the boundaries should fall in your own business. Would staff only need a booking notification, or would they need access to the booking system? Is there a suitable business-owned device at the counter instead? Keep unanswered questions visible until someone with the right expertise has checked them.

Avoid treating a quick verbal agreement as a complete arrangement. Give the colleague a short written explanation they can read before deciding whether to use their own phone. Include whom to ask for help and what alternative working arrangement you will discuss if personal-device use is unsuitable.

Check the phone and the work access separately

The NCSC’s small-organisations guide recommends protecting devices with a strong screen lock and keeping devices, apps and browsers updated. It explicitly includes personal devices used for work.[3] Ask your support provider how these checks would work without collecting unrelated personal information.

A phone that still makes calls may no longer receive security updates. The NCSC recommends replacing unsupported devices with a supported model, which need not be the newest one.[3] Check the manufacturer’s support information before assuming an older handset is suitable for business access.

For the work account, ask about multi-factor authentication, which adds another check when signing in. The NCSC identifies it as a minimum requirement for personal-device access to business services.[6] Have support explain the recovery process as well as the normal login, so nobody discovers the gap after changing phones.

Explain what the business can see or remove

Ask your IT provider to demonstrate the proposed management arrangement before introducing it. The NCSC distinguishes whole-device management from managing work applications and their data; the available controls depend on the products and approach chosen.[7]

Get a plain explanation of what an administrator can see, what they can change and what any removal command actually deletes. Do not promise that personal photographs are untouchable, or that work data can always be removed separately, without checking the particular setup.

Make room for ordinary working boundaries as well. The NCSC warns that personal-device arrangements can affect work-life balance.[2] Discuss when work notifications should be checked and where urgent enquiries should go outside someone’s agreed working time. Test whether the arrangement makes sense to the person carrying the phone.

Prepare for a lost phone or a change of role

Agree a reporting contact and an alternative way to reach them if the phone is unavailable. The NCSC recommends planning for lost devices, incidents, replacement handsets and employees leaving.[6] Put the reporting route somewhere staff can find without signing into the missing phone.

Ask support to explain how it would remove work access and, where the chosen controls allow it, associated business data.[7] Do not ask a colleague to factory-reset their personal phone as an improvised first response.

For this week, map one task, identify the unanswered questions and arrange a short review with your IT provider and the people affected. You can find more practical reading in the MH360 Businesses & Employers hub. Leave that review with an agreed next step, rather than another app installed without a plan.

Sources

[2] Bring your own device

[3] Protecting your devices

[6] Action 2 – Develop the policy

[7] Action 5 – Put technical controls in place