Workplace operations

A desk move IT checklist for a small office reshuffle

A move checklist that covers ports, labels, network changes, and record updates so a seating reshuffle does not become a week of support tickets.

Short answer

Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.

Delegation playbook

Best fitRepeatable IT admin
OwnerManager or IT lead
Risk ruleEscalate technical judgment
PilotTwo-week sample workflow
On this pageJump to section

An office reshuffle looks like a furniture task until the first monitor does not wake up at the new desk. Printers disappear, cables go missing, and the asset register still shows the old floor. A desk move checklist treats IT equipment as part of the move plan rather than an afterthought. It covers the walkthrough, the labels, the reconnect order, and the records that must change.

Walk the floor before the move

Walk the new layout with the person leading the move and mark every desk that will receive equipment. Note the monitors, docks, phones, and printers that will move or stay. Photograph the current setup of any desk with unusual equipment. The walkthrough finds the exceptions before the move day. Ask each team to name the equipment that must be working on the first morning.

Check the network ports, power outlets, and cable routes at the new positions. Confirm that each desk has enough outlets for the planned equipment. Note the desks that need a longer cable or a switch port. Record the findings on the move plan with an owner for each fix. A desk with one outlet and three devices needs a plan before the move, not after.

Number every desk and port

Give each desk a number and label the network port beside it. Record the port number against the desk in the move sheet. Label the cables and the dock with the same number. A consistent label lets anyone reconnect the equipment without guessing. Use the same number on the move sheet, the port label, and the asset record, and check the labels before the move.

Photograph the back of each workstation before it is disconnected. Keep the photos with the move sheet and the asset tag. Note any cable that is damaged or missing. The photo is the fastest way to resolve a reconnect question later. A photo taken before disconnection answers most reconnect questions without a visit, so store it beside the move sheet.

Plan network and power changes

List the desks that need a new network drop, a switch change, or a power adjustment. Ask the building or network owner to complete the work before the move day. Test each new port with a laptop. A port that is patched but not tested will fail when the team arrives. Book the network work with the building owner and confirm it in writing.

Check that the new layout does not put equipment near water, heat, or a walkway. Confirm that extension leads and power strips are rated for the load. Record the changes in the floor plan. Safety and network work should be finished before furniture moves. Record the outlet test and the person who completed it, and keep the note with the floor plan.

Pack and label the equipment

Give each person a bag or a box with labels for the desk number and the equipment type. Ask them to pack the cables with the device they belong to. Keep the monitor, dock, and power supply together. Loose cables in a shared box create hours of matching later. A labelled bag also makes it easy to return an item that arrives at the wrong desk.

Record the asset tag of every item that leaves a desk and the desk it moves to. Note any item that stays behind or goes to storage. Photograph the packed box. The move sheet should show where each asset is expected to arrive. The move sheet should be checked at the door before equipment leaves the floor and signed by the person who packed it.

Reconnect and test in a set order

Reconnect the network cable, the power, the monitor, and the dock in the same order at every desk. Test the network link before moving to the next desk. Check that the monitor wakes and the keyboard works. A consistent order makes a failure easy to isolate. Keep a test account signed in so the first check does not wait for a password reset.

Test printing from one desk on each floor before the team returns. Confirm that the phone and the meeting room equipment work. Record each desk that passes and each that needs a fix. Keep a small kit of spare cables and adapters on site. Record the printer queue name at each test desk so a failure can be traced to a device.

Update records the same day

Update the asset register with the new location and the person assigned to each device. Change the printer map and the floor plan. Update any access record that depends on the desk or the floor. The records should match the new layout before the end of the move day. Ask each team lead to confirm the new location for their people before the end of the day.

Tell the support queue which desks are still incomplete. Add a note to the move sheet with the remaining fixes and the owner. Send the updated floor plan to the front desk. A record that is updated next week will be wrong for a week. The queue note should name the person who will close each remaining item and the date it should be closed.

Hold a short after-move review

Meet with the move lead and one person from each team on the first morning after the move. Ask what failed, what was missing, and what took too long. Review the tickets raised during the move. The review should produce a short list of fixes, not a blame session. Invite the building contact as well when the move included network or power work.

Update the checklist with the gaps found during the move. Add the spare parts that were needed and the ports that failed. Keep the review notes with the next move plan. The second move should be easier because the first one was recorded. Give the updated checklist to the next move lead before the review ends, and ask for one improvement to the template.

Sources and next step

Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the printer, domain, support rota, licence, and desk move practices discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and asset records, and the SBA cybersecurity guidance frames the vendor and account ownership checks. Apply your own policies, contracts, and system documentation to the workflow.

Compare this guide with the domain renewal register and the licence true-up worksheet before changing a live process. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.

Operating brief

What this guide should help you decide

Delegate

Routine intake, status updates, records, screenshots, and documentation upkeep.

Keep ownership

Approvals, risky system changes, security decisions, and final technical judgment.

How to use this guide

Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.

Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.

Workflow

Recommended operating workflow

1

Define the request

Write what a desk move it checklist for a small office reshuffle means in your company, where requests enter, and what finished work looks like.

2

Limit the access

Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.

3

Run a pilot

Use a two-week sample period so the manager can review accuracy before expanding the workflow.

4

Review patterns

Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.

Decision rules

QuestionVA fit signalEscalate when
Is the work repeatable?The same request appears weekly and can be described in steps.The request changes business policy or system design.
Can quality be reviewed?The manager can inspect the output without redoing the work.Only a senior technical person can judge correctness.
Is access contained?The assistant can work with read-only or role-limited access.Admin rights, customer data, or security settings are involved.

Delegation checklist

  • Write the intake source, expected output, and manager review cadence.
  • Confirm the assistant has only the permissions needed for the workflow.
  • List the events that require escalation before work continues.
  • Track examples for two weeks before changing the workflow.
  • Save examples of good and bad outputs so the assistant has concrete references.
  • Review the workflow monthly and remove permissions that are no longer needed.

Example first-week agenda

Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.

What to review before delegating

Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.

What should an IT virtual assistant handle first?

Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.

Get free IT support review