Remote hands and customer access.

The ticket queue needs an electrical filter

Remote-hands tasks span an enormous range of electrical significance: rebooting a server is normal operation of IT equipment; swapping a cord into a rack PDU is normal operation while the seven conditions hold; resetting a tripped breaker is the likelihood table's abnormal-operation Yes; and opening any panel is energized-work territory the tech may have no qualification to enter. The failure is structural — the ticket system treats all four as 'remote hands' — so the fix is structural too: a screening question at intake that routes anything involving a breaker, a panel, or observed damage to the electrically qualified queue, with everything else flowing free.

The post-trip reset deserves its own line in the SOP, because it is the trap that recurs: the customer knows only that their gear lost power; the tech is standing at a breaker that opened for a reason nobody yet knows. Until the cause is known, that reset is not the routine operation row — and 'the customer authorised it' transfers no electrical judgment whatsoever. The customer is not the employer making 70E's demonstrations.

What the exemptions cover in this job, exactly

130.3(C)'s permit exemptions map cleanly onto the legitimate remote-hands scope: access and egress past energized equipment with no electrical work, general non-electrical tasks in electrical spaces, and — for qualified techs — testing and voltage measuring, all with the restricted approach boundary never crossed. That envelope, plus normal operation, is the entire lawful territory of an awareness-trained remote-hands tech. The moment a task exits it, the standard's answer is a different person, not a more careful version of the same one.

Held against the badge tiers from the colo page, this becomes an operable rule: the remote-hands queue runs on awareness training and stays outside every boundary; the qualified queue carries the tasks with section numbers on them.

The briefing survives contact with a one-line ticket

A job briefing before the task is the standard's habit worth keeping even at ticket scale — for remote hands it is thirty seconds, not a meeting: what the ticket asks, which cabinet, what is energized in reach, and what condition stops the work. The stop conditions are the same ones threaded through this whole series — evidence of impending failure, an open cover that should not be open, a breaker that has tripped, anything warm that should not be — and the tech's authority to invoke them has to be explicit in the SOP, because a remote-hands tech works alone, at night, against a customer's clock. The program that makes stopping cheap is the program that gets stops.