Guides & Blog · 2026-07-14 · eWEB TEC

How to Write a Smart Hands Ticket / MOP So Remote Techs Don't Fail You

A good smart hands ticket tells a technician exactly which rack, which device, which steps, how to verify success, and when to stop and call you. A weak ticket produces the classic Reddit complaint: remote hands refuse the work, or botch it, and you fly out anyway.

This is the practical companion to what smart hands means and smart vs remote hands.

Minimum fields every ticket needs

• Facility, suite/cage/rack, and asset labels or serials
• Change window and maximum acceptable impact
• Named remote contact with phone + authority to approve
• Step-by-step MOP with success criteria after each critical step
• Rollback or stop conditions
• Photos or diagrams for cabling and port maps when relevant

MOP structure that works on the floor

1. Pre-checks: power, link lights, current state photos
2. Action steps numbered and one action each
3. Verify: command output, LED state, or remote console confirmation
4. Document: time, serials, photo of finished state
5. Close: confirm with remote owner before leaving the rack

Common failure modes

• Vague labels ("the top switch")
• No serial or port map for cable moves
• Assuming the tech has your VPN or passwords they should not need
• No bridge contact overnight
• Scope creep mid-ticket without a written add

Sydney facilities note

Access rules differ across Equinix, NextDC, Global Switch and others. Include escort/access method and any site-specific rules you already know. Orientation: Sydney data centres guide. Service: smart hands.

FAQ