©2023 Paul Gettings, assigned to Wasatch Mountain Club - distributed under CC BY-SA license (see https://creativecommons.org/licenses/)
Climbing Communication
Effective formal communication in a climbing system relies on commands that follow three foundational principles:
Command | Who Says | Communication | Action | Affirmation |
"On Belay(?)" | Climber | Is rope speed controlled? Or control the rope speed | Belayer assembles or double checks belay system. | "Belay On" |
“Belay On” | Belayer | Rope speed is controlled. | Belayer has constructed the belay system on the rope. | “Thank you”, “Climbing”, or none |
“Climbing” | Climber | Prepare to feed rope; rope will move | Belayer ensures rope feeds in/out of belay system to maintain safety. | “Climb On” |
“Climb On” | Belayer | Belay ready for rope movement; tension will be controlled along with speed. | Control rope tension for a safe belay while the climber climbs. | None |
“Slack” | Climber | I need some slack. | Belayer provides slack. | “Slack” or none |
“Tension” | Climber | I need the rope tight, because I am going to weight the rope. | Belayer provides a taut rope to take the climber’s weight. | “(I’ve) Got You” |
“Falling” | Climber | I’m falling. | Climber falls and the belayer catches the fall. | “(I’ve) Got You” |
“Off Belay” | Climber | Remove the belay system; allow uncontrolled movement of the rope. | Belayer deconstructs the belay system. Note: Belay is not removed unless "Off Belay" is clearly heard from the climber!. | “Belay Off” |
“Belay Off” | Belayer | Rope speed is uncontrolled | Belay system has been removed. | None or “Thank you” |
“Up Rope” | Climber | I need the belayer to remove slack. | Belayer removes all the slack, but does not take weight. | No need for affirmation |
“That's Me” | Climber | Stop pulling or feeding rope. | Belayer stops pulling or feeding rope. | No need for affirmation |
Following commands can only be used while the belayer is in view. Included for reference, but not recommended. | ||||
“Watch Me” | Climber | I am making a move in which I might fall. | Belayer continues to actively belay. | “Watching” |
“Clipping” | Climber | Pulling rope to clip into protection | Belayer provides correct slack to clip protection. | None |
“Clipped” | Climber | Rope is clipped into protection, remove excess slack | Belayer removes excess slack. | None |
Command | Who Says | Communication | Action | Affirmation |
“Belay On” | Belayer | Fireman’s belay of rappel system is ready | Provide an attentive fireman’s belay. | No need for affirmation or “Thank You” |
“On Rappel” | Rappeller | I want to start rappelling. | Rappeller rappels. | “Belay On” if providing belay; “Rappel On” if acknowledging without belay. |
Command | Who Says | Communication | Action | Affirmation |
“Ready to Lower” or “Lower” | Climber | I’m ready to lower immediately. | Belayer lowers the climber. | “Lowering” |
Command | Who Says | Communication | Action | Affirmation |
“Rock!” | Anyone | A rock (or object) is falling; beware! | All take measures to avoid the falling rock. | No need for affirmation |
“Rope!” | Anyone | A rope is falling; beware! | All take measures to avoid the falling rope. | No need for affirmation |
Note: Continue yelling “rock!” until the object has come to rest. The repeated warning allows people below to know when to come out of hiding.
Command | Who Says | Communication | Affirmation |
“Half Way” | Belayer | Half the rope is left for climbing. | No need for affirmation or “Thank You” |
“No More Rope” | Belayer | No more rope remaining. | No need for affirmation or “Thank You” |
Before leaving the ground, all members of a climbing team need to agree on their actions (a “protocol”) if communication is lost. This is most common in a multi-pitch setting, but can occur on single pitch climbs as well. The protocol to follow will depend on the type of climbing and whether a person is a belayer or climber. The goal of the protocol is to guarantee that all climbers are always on belay when not clipped to an anchor! Below are suggested protocols for troubleshooting loss of communication.
The American Alpine Club (2017, January 20). Climber Communication blog post]. Retrieved May 29, 2018, from https://americanalpineclub.org/resources-blog/2017/1/19/4xm1fcsag6b7xqf1p1w1qp7vdpp1ha .
As pointed out in the linked AAC document, climbing communication is an essential part of safety in climbing; more accidents (not fatalities) are caused by miscommunication than all other causes, combined (anyone have a reference for this claim?). Once a climber has left the belayer, both verbal and visual communication rapidly becomes very difficult. Difficulty arises due to environmental causes (wind, water, other climbers), distance, and limited visibility. Technological solutions to the problem (radios, phones, etc.) are excellent options, when they work. Thus, climbers need a consistent, minimal toolbox of commands that can be distinguished with minimal hearing. In addition to the 3 principles discussed in the AAC document, and summarized in this one, here are some rules to achieve a suitable command set:
Commands are about the rope, & hazards
The command set should only deal with the climbing rope, actions the belayer and climber can take with the rope, and hazards (falling rocks, etc.) The belayer can only change tension in the rope by allowing or preventing the rope to feed in or out of the belay stance. Only the climber’s changes to the rope matter to the belayer. Thus, commands related to anything other than the rope are pointless and just hinder understanding. Since the commands will be shouted, at maximum volume, long sentences are silly. Short, one or two word statements are best for shouting.
Only vowels matter
Research and experience has shown that vowel sounds transmit farther than consonants, so the important part of a command set is the number, order, and type of vowel sounds in each command. The included command set is developed for english; alternate command sets would need to be developed for other spoken languages. When looking at the suggested command set, pay particular attention to the number, type, and order of the vowel sounds. When developing commands, no commands related to safety can overlap number, type, and order of vowel sounds!
Limited command sets work, discussions don’t
While the list of commands is limited, the commands comprise a toolbox for total control of the rope and warning of hazards during climbing. Like a programming language, or the 10- codes used on CB radios, solutions to problems are built out of a sequence of precise commands in sequence. What sequence of which commands will solve a given problem is up to the climber to decide, but the capability is there.
Due to the difficulty in verbal communication in climbing, discussions simply don’t work when the team is separated. Have discussions and do the planning when next to your climbing partner at a belay stance, not when around a corner and 70 m away, in a windstorm next to a raging stream. Once the team is separated by 3 m or more, discussions should be shelved until the team reconnects at the next belay stance. Climbing short routes makes communication easier, but climbing command sets must work in the worst cases, not only the best.
Sequences help understanding, and current state matters
Clearly, some commands must occur in sequence to make sense: you cannot be ready to climb until the belay is ready, nor can a climber request a belay to be removed unless the belay is on. Most commands can be used in any order, as they are individual actions. Also, note that some commands can be both part of a sequence and used outside that sequence; a lead climber belaying the follower from the top will not wait for the follower to send “on belay” before rigging a belay. The lead climber rigs a belay and sends “belay on” to inform the follower that it can start preparing to climb.
Commands related to the belay do, generally, need to follow the sequence of call-and-response; the response indicates the requested action has been completed. Also, while “on belay” and “off belay” have the same vowel sounds, they can be interpreted by the current state of the belay. A climber or belayer can only request a change in the state of the belay; a climber should never ask for “on belay” while on belay! Similarly, a belayer should only, ever, disassemble the belay when “off belay” is clearly heard! Never should the belay state change if only “belay” (or something like it) is heard without the first word!
Responses happen after the action, not before or during
When responding to climbing commands, the response must be held until after the action requested is completed; do not send a response to a command to acknowledge before the action is completed! The affirmation response to a command is itself a communication that the requested action has been completed. Sending the confirmation before the action is completed leads to problems with rope management and safety; e.g. a follower will begin removing an anchor once “belay on” is heard, which could be fatal if the belay is not, in fact, rigged!
Everyone has to agree on a toolbox, or it doesn’t exist
Before leaving the ground, everyone on a team needs to agree to a common command set. Otherwise, there will be no effective communication. You can discuss the commands individually, trade printed sheets of commands, use the default set from your climbing club, or any other protocol to get a consistent set of commands agreed between the climbers.
Also, discuss what you will do, as a team, when you can’t communicate. A suggested protocol for loss of communication is included in this document, which prevents disastrous loss of belay during a loss of communication. Any similar protocol will work, but the time to discuss it is on the ground.
Common Words to Avoid, & Why
Many common words seem like they could be useful to a climbing command set, but they have issues. Some of the more common ones are collected here, with reasons to avoid using them.
Stop | Overlaps vowel sound with “rock”; action achieved by “That’s me” |
In direct | Does not indicate an action for the belayer to take, thus vague. |
Safe | Overlaps with “Slack”; does not indicate a belayer’s action, thus vague. |
OK | Common usage makes this word very vague; use “Thank you” for a generic acknowledgement |
Page of Communication for Climbers v23.09.06