Looking for On-Demand Tech Support?
Techmate has the boots-on-the-ground IT Support where and when you need it.
Schedule a Discovery CallThe Remote Hands Task Catalog: 50 Common Requests Ranked by Complexity
Quick answer: Remote hands tasks range from basic (power cycling, visual checks, reseating cables) to intermediate (hardware swaps, cable tracing, console connections) to advanced (rack and stack, cutovers, migrations). Ranking all 50 requests by complexity tells you which technician to send, how long to plan for, and when to bring in onsite hardware support from a smart hands provider like Techmate, with vetted technicians in 450+ US cities.
“Can remote hands do that?” is a question every infrastructure team asks eventually. The answer depends on the task, the technician and the provider. Some requests are simple enough for any facility technician. Others need someone who can read a rack elevation, follow a runbook under pressure and know when to stop.
Getting this wrong is expensive in both directions. Send a skilled technician to read a status light and you overpay. Send a facility tech to swap a core switch and you risk an outage. And finding skilled people in-house is not getting easier: in Uptime Institute’s Data Center Staffing and Recruitment Survey (Uptime Institute, 2025), 37% of operators named hiring new staff as one of their two greatest challenges of the past year.
This catalog lists 50 of the most common remote hands and smart hands requests, grouped into three complexity levels. Use it to scope requests, set expectations and brief providers, whether the work is in a colocation cage, a branch office IDF or a closet at headquarters.
How are remote hands complexity levels defined?
| Level | What it covers | Typical technician | Instructions needed | Engineer on the line? |
|---|---|---|---|---|
| Basic | Simple physical actions with clear instructions and minimal risk | Facility remote hands or entry-level technician | Exact device location and the action to take | Helpful, not always required |
| Intermediate | Hardware work or tasks requiring identification skills and care | Experienced field or data center technician | Step list with verification points | Yes, for anything in production |
| Advanced | Multi-step work requiring judgment, planning or specialized skills | Skilled smart hands technician with documented experience on similar work | Full runbook with stop conditions and rollback | Yes, for the entire task |
A task’s level is not fixed. Reseating a cable is basic in a lab rack and a lot riskier on the uplink of a production firewall with no redundancy. Rate each request by the task and by what breaks if it goes wrong.
Level 1: What are basic remote hands tasks?
Basic tasks are physical actions with one clear outcome. The technician does exactly what the ticket says and reports back. Most facility-included remote hands programs are built for this list.
- Power cycle a device
- Press a power or reset button
- Visually check status lights and report colors
- Photograph a device, rack or cabling
- Read a label, serial number or asset tag
- Reseat a network cable
- Reseat a power cable
- Confirm a device is physically present in a location
- Insert or remove removable media
- Receive and store a shipment
- Unbox and inventory delivered hardware
- Connect a monitor and keyboard (crash cart) for a remote engineer
- Read on-screen messages to a remote engineer
- Check environmental conditions (temperature, visible leaks)
- Apply labels to devices or cables
The risk in basic work is almost always identification, not skill. “Power cycle the switch” fails when there are three switches in the rack. Every basic request should name the device by rack, U position, hostname label and, ideally, a photo from a previous visit.
Level 2: What are intermediate remote hands tasks?
Intermediate tasks involve handling hardware or making changes to physical connections. They need a technician who can identify components, follow anti-static and handling practices, and confirm the result with the remote engineer before leaving.
- Replace a hot-swap drive
- Replace a power supply
- Replace a fan module
- Replace an SFP or optic
- Swap a failed network switch with a pre-configured replacement
- Replace a failed server component (memory, NIC) under guidance
- Connect a console cable and provide access to a remote engineer
- Trace a cable end to end
- Patch or move cables per a port map
- Install a pre-configured device into existing rack space
- Package and ship a failed part for RMA
- Perform a basic cable cleanup in a rack
- Reset a device to factory defaults on instruction
- Test a network port with a cable tester
- Replace a UPS battery module
- Install or replace a KVM or console server
- Update a rack elevation document with current contents
- Perform a physical asset audit of a rack or cage
These tasks make up a large share of real-world dispatches because hardware fails on its own schedule. In an Opengear survey of 1,000+ CIOs, CSOs and network engineers (Business Wire, 2025), 26% of network engineers named server hardware failures as a common cause of outages. A failed power supply or drive is a routine intermediate swap, as long as the replacement part and the instructions are ready when the technician arrives.
Level 3: What are advanced smart hands tasks?
Advanced tasks are projects or high-risk changes. They take hours, touch multiple devices and require the technician to make judgment calls inside the limits of a runbook. This is where smart hands services earn their place.
- Rack and stack new servers, including rails and cabling
- Install and cable a full rack of equipment
- Perform guided hardware troubleshooting and diagnosis
- Install or re-terminate structured cabling
- Execute a network cutover during a change window
- Replace a firewall or core switch with rollback plan
- Support a server or storage migration between racks or facilities
- Decommission and remove equipment with data handling
- Install and verify fiber cross-connects within your cage
- Set up out-of-band management infrastructure
- Perform a cabling audit and remediation
- Reconfigure power distribution within a rack (PDU replacement)
- Assist with storage or backup appliance maintenance
- Execute a multi-step runbook across several devices
- Stage, burn in and test new hardware
- Coordinate onsite with multiple vendors during an incident
- Perform a complete cage or closet build-out
Several of these have their own guides. For out-of-band management setup, see setting up out-of-band management with remote hands. For the broader scope of advanced work, see our guide to smart hands IT services.
Which tasks come up most at offices and branches, not just data centers?
Most remote hands catalogs are written for colocation. Distributed companies send just as many requests to offices, branches and network closets, where there is no facility staff at all. The same three levels apply, but the common tasks shift.
| Site type | Common basic tasks | Common intermediate tasks | Common advanced tasks |
|---|---|---|---|
| Colocation cage | Power cycle, status lights, receive shipment | Drive and PSU swaps, optics, RMA shipping | Rack and stack, migrations, cross-connects |
| Branch office or bank branch | Reboot firewall or modem, photograph the closet | Swap pre-configured switch or access point, trace a cable | Firewall or SD-WAN cutover, closet rebuild |
| Law firm or professional services office | Check printer or conference room connections, label ports | Patch per port map, replace a UPS battery | Office move or expansion, AV and network build-out |
| Retail or multi-site network | Confirm device present, reseat cables at POS or IDF | Replace edge switch, test ports | Store refresh or new-store network install |
For closet and IDF work at offices, our onsite IT network services cover the full range from basic checks to advanced cutovers.
How should complexity change the way you write a request?
- Time estimates. Basic tasks often take minutes. Advanced tasks can take hours. Minimum billable time matters most for basic tasks, so batch small requests at the same site where you can. See smart hands services pricing models.
- Instructions. Basic tasks still need precise device identification. Intermediate and advanced tasks need full runbooks with verification and stop conditions. See how to write a remote hands request.
- Engineer availability. Anything that could affect production should have a remote engineer on the phone.
- Change windows. Advanced tasks affecting live services usually belong in scheduled windows.
- Parts and access. Intermediate and advanced tasks fail most often because the replacement part, rail kit or access badge was not ready. Confirm all three before dispatch.
Procedure is the biggest lever. Uptime Institute’s Annual Outage Analysis (Uptime Institute, 2025) found that 85% of human error incidents stem from staff not following procedures or from flaws in the procedures themselves. The more complex the task, the more the written runbook matters. Our guide to field IT support runbooks shows how to write them.
What should every remote hands request include, by level?
| Item | Basic | Intermediate | Advanced |
|---|---|---|---|
| Site, rack and U position | Required | Required | Required |
| Device label, hostname or serial | Required | Required | Required |
| Photo or rack elevation | Recommended | Required | Required |
| Step-by-step instructions | One or two steps | Numbered steps with checks | Full runbook |
| Stop conditions and rollback | Not usually | Recommended | Required |
| Parts and shipping tracking | If relevant | Required | Required |
| Remote engineer contact and bridge | Recommended | Required | Required |
| Closeout photos and notes | Recommended | Required | Required |
When should you escalate from facility remote hands to skilled smart hands?
Facility remote hands teams are often well suited to basic tasks. Consider a skilled smart hands provider when:
- The task is in the intermediate or advanced list and could affect production
- You need the same standards across multiple facilities
- You need someone to follow a complex runbook or make judgment calls
- The work spans your colo cage and your offices or closets
- You need consistent documentation and photos
Our article on when your colo’s included remote hands isn’t enough goes deeper on that decision.
What mistakes do teams make when scoping remote hands work?
- Rating by task name only. “Swap a switch” is intermediate with a pre-configured spare and advanced if it is the only core switch at the site.
- Splitting one visit into many tickets. Five basic tasks at the same branch, sent on five different days, cost more and create more risk than one planned visit.
- No stop conditions. Technicians who are told only what to do, not when to stop, will keep trying. Tell them when to pause and call.
- Assuming the facility knows your gear. Facility staff see hundreds of cages. Give them labels and photos, not hostnames alone.
- Skipping closeout. Without photos and notes, the next request starts from scratch.
How do you use this catalog?
- Tag your ticket types with a complexity level
- Map each level to a provider or technician tier
- Set default time estimates per task for scoping and budgeting
- Write runbooks starting with the intermediate and advanced tasks you request most often
- Review quarterly as your environment changes
If you are new to working with an outside provider, read how Techmate dispatch works to see how a request moves from ticket to technician.
The bottom line
Not all remote hands requests are equal. Ranking tasks by complexity helps you match the right technician, set realistic estimates, write the right level of instructions, and decide when basic facility help is enough. Keep this catalog as a starting point and tailor it to your environment.
Techmate provides remote hands and smart hands services across data centers, colocation facilities, offices and closets in 450+ US cities. See IT network services or contact us.
Frequently Asked Questions
What tasks can remote hands perform?
Common remote hands tasks include power cycling, checking status lights, reseating cables, photographing equipment, reading labels and serial numbers, receiving shipments and connecting a crash cart for a remote engineer. Many providers also handle intermediate work such as hot-swap drive and power supply replacements, cable tracing and installing pre-configured devices into existing rack space.
What is the difference between basic remote hands and smart hands?
Basic remote hands covers simple physical actions done on instruction, with little judgment required. Smart hands covers more complex work such as rack and stack, guided hardware troubleshooting, structured cabling, cutovers and migrations. The difference is the skill of the technician and the amount of planning, runbook detail and engineer involvement the task needs.
Can remote hands replace hardware?
Yes, for many components. Hot-swap drives, power supplies, fans, optics and UPS battery modules are common intermediate tasks. More complex replacements, such as a firewall, core switch or server components inside the chassis, typically need an experienced technician, a written runbook with stop conditions and a remote engineer on the line throughout.
Is rack and stack a remote hands task?
Rack and stack is usually considered a smart hands task. It involves installing rails, mounting equipment at the right U position, power and network cabling, labeling and verifying with the engineer. It takes longer than a basic request and mistakes are costly to unwind, so it belongs with a skilled technician working from a rack elevation.
How long do remote hands tasks take?
Basic tasks often take minutes once the technician is at the device. Intermediate tasks commonly take up to an hour or more, depending on access and verification. Advanced tasks can take several hours or span a change window. Batching several small tasks at one site into a single visit usually makes better use of minimum billable time.
When should I use a third-party smart hands provider?
Use one when tasks are complex or production-affecting, when you need consistent standards and documentation across facilities, or when work spans colocation cages and office sites. A third-party provider is also useful when your facility’s included remote hands program does not cover intermediate or advanced work, or when your sites have no facility staff at all.
Not sure which of your recurring requests belong at which level, or who should handle them? Book a free 30-minute IT support audit and we will map your remote hands and smart hands work to the right coverage model.
