The commands that hold a rope team together: clear standard calls, pre-tour agreements and rope-tug signals for when you can no longer hear each other.
## Introduction The honest answer to "What commands do I need on a multi-pitch?": surprisingly few — but they must be crystal clear and agreed before the tour. On the wall, 50 metres of rock, wind and an overhang soon separate you. Then what matters isn't how many commands you know, but whether you can rely blindly on the few important ones.
Why this is a safety topic, not an etiquette one: misunderstandings are one of the main causes of lowering and belaying accidents. The classic: the leader calls "anchor" meaning "I'm secured", the second hears "off belay" and takes the leader off the belay before they're even tied in. A single misunderstanding like that can be fatal.
Then there's the basic alpine problem: you often can't see or hear each other. In the large Austrian analysis the most common alpine emergency pattern was climbers getting lost or stuck — and poor communication is a direct route there.
The solution is two-tier: a small set of unambiguous calls for the normal case — and rope-tug signals for when calling no longer works. You settle both in 60 seconds at the base. That's exactly what we'll do now.
## What You Need - A clear pre-tour agreement: which commands, which meaning, which language. - A small, fixed vocabulary instead of improvised shouts. - Agreed rope-tug signals for loss of earshot (wind, distance, overhang). - The habit of adding the name when other rope teams are nearby. - A radio if in doubt for long, complex walls.
## Step by Step ### 1. Set the commands before the tour Settle at the base: which calls do you use, what does what mean, and in which language? If you climb with changing partners, run through this each time — habits differ, and that's exactly where misunderstandings arise.
### 2. Master the standard set The few core commands: "anchor" (I'm secured), "off belay" (take me out of the belay), "climb on" (you're secured, climb), "take/hold" (keep the rope tight), "slack" (give rope), "rock!" (rockfall warning). The normal case needs no more.
### 3. Always add the name On popular walls several rope teams hang at once. An "anchor!" without a name can be picked up by the wrong team — with fatal consequences. Add your partner's name: "Anna, anchor!". It costs nothing and rules out mix-ups.
### 4. Agree rope-tug signals When wind and distance swallow every call, only the rope helps: e.g. three short, firm tugs = "anchor built, you can climb on" (practice). Set the number and meaning before the tour — improvised tugs mean nothing to anyone.
### 5. Confirm instead of guessing If you're not sure you understood a command, never guess — ask or wait. A "got it!" as confirmation closes the loop. When in doubt the safest assumption applies: until you've heard a clear "climb on", the partner stays on belay.
## Common Mistakes - Commands not agreed: everyone uses their own calls. Fix: align briefly before the tour. - No name added: a stranger's team picks up the command. Fix: always add the name. - Guessing instead of asking: an uncertainly understood command executed. Fix: ask, or wait on the safe side. - No emergency layer: drilled in calm, helpless in a storm. Fix: agree rope-tug signals (practice).
## Safety Notes The most dangerous misunderstanding always involves the belay: if the leader is taken off belay too early because "anchor" was confused with "off belay", they fall unsecured. Exactly such communication errors are among the main causes of belaying accidents.
So the iron rule: when in doubt, whoever is climbing stays secured. Take your partner off belay only once you've unambiguously heard and confirmed the agreed command. Hear nothing clear, and you keep holding — better wait two minutes longer than have someone hang unsecured on the wall. Communication is part of the safety chain on the mountain, not an add-on.
## Pro Tip Agree an unmistakable switch-over call that can never be confused with anything else — many use the full sentence "Anna, you're on the anchor, off belay!" instead of a single word barely distinguishable in the wind.
Short syllables like "take" and "slack" sound almost the same over distance. A whole, distinctive sentence still comes across right even chopped up. It sounds cumbersome, but it's exactly why well-drilled teams rarely have communication problems. Train Smart. Play Hard.
## FAQ ### What commands do I really need on a multi-pitch? Just a handful: "anchor" (I'm secured), "off belay" (take me off the belay), "climb on" (you're secured, climb), "take/hold", "slack" (give rope) and "rock!" as a rockfall warning. More important than the number is that both attach the same meaning to them — so align briefly before every tour.
### What do I do when we can no longer hear each other? Agree rope-tug signals before the tour: a set number of firm tugs replaces the call, e.g. three tugs for "you can climb on" (practice). For long, wandering walls a radio is worth it. When in doubt the safe assumption always applies: without a clear signal, the partner stays secured.
### Why should I add the name to the command? Because on popular walls several rope teams climb at once and an "anchor!" can be picked up by the wrong person. A second reacting to a stranger's command might take their leader off belay too early. The name makes the command unambiguous and rules out exactly this mix-up.
### Are communication errors really dangerous? Yes. Misunderstandings are among the main causes of lowering and belaying accidents, and poor communication quickly leads to getting lost or stuck on the mountain. The most dangerous case is always someone being taken off belay too early. Clear, agreed commands are therefore part of your safety equipment.
Alpine Climbing: Objective Hazards — Rockfall, Weather and Lightning