Plan an employee’s work sign-in before replacing a phone

Tell IT when the swap will occur, which systems the employee needs and who will verify their access afterward.

A laptop and phone seen from above on a work table
A laptop and phone seen from above on a work table Aleksi Tappura a · CC0 · Resized for display
In this article

An employee planning a phone replacement often knows roughly when the handover will happen. That tells you when they may lose access to a familiar sign-in method. It also gives the person who looks after workplace accounts time to confirm which equipment and approvals matter. Use that advance notice to agree on what to test, who can assist and how the employee will reach them during the swap. A short plan is especially valuable when the employee relies on the phone to approve sign-ins on a separate computer.

This guide is sponsored by Cross River Technology. Use the company-approved IT support process for a work account. CISA's multifactor authentication overview explains why services can ask for proof in addition to a password. The specific authentication system and device requirements are choices for the people who administer your work accounts.

Explain what is changing in a single message

Tell IT the planned day and time, whether the work computer is also changing and whether the old phone must be surrendered at the same time. A planned Friday pickup with the current phone still available until evening gives support a different window from a handover at a store where the old device will leave with you no longer in possession of it. Mention whether the new phone will be issued by work or personally owned, since the employer may have separate rules for the two arrangements. Ask which parts of the change require a person from IT to be available.

Describe the upcoming work task that would make a failure troublesome. One person plans to issue invoices early the next morning. Another needs to respond to support messages from the road. Both can mention the application and when it will be needed without disclosing the contents of a message or any financial information. That gives support a reason to put one verification step early in the schedule. Include the best company-approved way to contact you during the appointment, especially if the usual work messaging app is one of the systems you are replacing access to.

Pick the sign-ins that actually need verification

Make a short list of work services the employee will depend on right after the change. Start with services used to reach help, verify identity or get to other applications. A user who normally opens email and then follows a normal link to an internal project space can confirm those two steps in sequence. Somebody who uses an approved remote-access application may need an extra check at the normal work location. Ask the employee how their current phone enters the process. A person can identify an application name and describe the familiar prompt in broad terms without sending any codes or account screenshots.

Give each item a purpose. For example, “Open the approved mailbox so I can read IT replies” is more useful than “email.” “Open the scheduling page where I look up my own shifts” says where success can be seen. This will help when the same application functions on a computer that was already signed in but a new approved sign-in remains unverified. Ask the account administrator which checks they want completed and whether the checks should start in a particular environment. Use a safe ordinary task such as opening the expected work screen rather than submitting a live transaction just to test the sign-in.

Find out what to retain until the handover is done

Ask support what they need you to keep available on the existing device until the change is complete. With a planned purchase or trade-in, check when the seller expects to take the phone and when you can use the replacement at the store or back at work. Then compare those times with the IT appointment. If the handover happens before support can help, tell them in time to approve a different arrangement. The exact requirements depend on the work sign-in service and how the employer manages devices. Microsoft's work account guidance on moving its Authenticator app to a new phone is one product-specific example of why applicable provider instructions matter.

Ask who owns the return or disposition of the original phone and what the employee is expected to do. A managed phone might go through the employer's equipment coordinator. A personally owned device may have different arrangements if work information is present. Keep routine purchase and return details in the appropriate place and account details in the employer's support channel. If instructions from a retail employee concern the sale while instructions from IT concern a work account, confirm each part with the people responsible for that separate decision.

Schedule a check you can carry out during normal work

Choose an appointment when the user can use the new phone and, if appropriate, the computer or other work device normally involved in the sign-in. Have the approved support contact on hand. Plan a realistic amount of time to check the highest-priority systems before the person who can help becomes unavailable. It can be useful to leave a small buffer before a staff meeting, an evening shift or a customer call. The goal is to have time to say what happened and get the issue routed if one of the needed accounts still requires attention.

Use the employee's normal work workflow to check what is accessible. With IT's agreement, the employee can try opening a familiar approved application and tell support whether the expected sign-in showed up and whether the expected screen opened. A successful check on a shared office connection may answer a different question from a check completed from the approved place where that person regularly works remotely. Write down the context when it matters. A result with an ordinary task and a clear location is easier to interpret than a general message saying the phone seems fine.

Keep messages and screenshots within the approved process

Let staff know what a legitimate support exchange should look like at this company. The employee needs to know how to start a conversation on an approved channel and what kinds of messages to expect. Keep passwords, one-time codes and sensitive account screenshots out of casual chats and correspondence. Call or open a ticket using contact information the organization has already shared when a message arrives unexpectedly during this busy period. People can describe where they were in the process without providing another person access to their account.

If support requests information, send the minimum needed through the approved place. The date of a planned replacement, the application name and the fact that the normal sign-in did or did not finish may be enough to route the request. A phone photographed with unrelated customer messages visible creates an unnecessary record. The Federal Trade Commission's guide to protecting personal information in business recommends understanding where sensitive data is kept, limiting what a business retains and protecting information it must keep. Applied here, that points toward a small support record and clear control over who can see it.

Handle delayed access as a work scheduling issue

Decide ahead of time what the employee should do if the sign-in remains unresolved after the appointment. For a small team, that could be a named person who accepts calls on the central line, a handoff to another employee already authorized to manage the affected queue or moving a deadline if authority to do so has been confirmed. Give the owner of the affected workflow specific information, such as when the user needs access and which approved interim arrangement has been agreed. Keep the recovery itself with the account administrator.

If the employee has already turned in the old phone, tell support immediately and provide a reliable contact route. Explain which system is affected and when the normal sign-in last worked if that is known. When the phone disappeared or there is a security concern, report the circumstances through the company's established lost-device or incident channel so the right person can evaluate it. A planned swap can use the ordinary support workflow while a device that went missing presents a different problem. Give the facts needed to distinguish the two.

Agree on what closes the support request

The support record can end with a few concrete lines. List the systems verified, who confirmed the result, what happened to the old device if the business is tracking its return, and any item left open. For example, “Mail and shift scheduling checked on the new company phone. Remote access verification planned for Tuesday during the approved remote shift.” A record like that tells the next support contact which work still needs attention without capturing unnecessary information or creating a new account directory.

When multiple employees are replacing phones during the same month, use one small scheduling note for the project and separate account support records for individual issues. An office coordinator can see the sequence of handovers and know which employees still need an appointment. The IT team keeps any sensitive work within its usual controls. Record recurring snags such as trade-in timing or an employee discovering too late that they needed their work computer. These are planning details that can improve the next round without presuming the same sign-in system is used by every group.

After the appointment, the employee should know where to report an unexpected prompt or a work service that still needs testing. Give them the confirmed support route and mention any follow-up date. If the employee has a long gap before using an important service, include a reminder ahead of that task so there is still time to ask for help.

Explore more workplace procedures in the Plano Beacon partner guide collection.

Sources

Share by email