How to Send Your Climbing Project: The Redpoint Protocol (2026)

The Reality of Sending a Project

You have been working this route for three weeks. You know every handhold, every foot beta, every micro-belay stance where you recover before the next sequence. You have linked the bottom section into the crux and sent the crux multiple times. But you have never the whole thing in one go. This is not a climbing problem. This is a protocol problem. Most climbers fail to send not because they lack the physical capacity but because they lack a system for managing fear, fatigue, and focus across multiple attempts spread across days or weeks. The redpoint protocol is that system. It is the difference between climbers who work projects forever and climbers who close them out.

The word redpoint comes from ground-up traditional climbing, where a redpoint meant you had completed the route after working it, replacing the red chalk marks you left on holds while figuring out the moves. In modern sport climbing, a redpoint means you have sent the route after a period of projecting, which includes working sequences, resting positions, and beta. This is distinct from an onsight, where you see the route for the first time and have no prior knowledge, and a flash, where you have beta but are climbing on sight. Redpointing is the act of converting project knowledge into a clean send after the necessary work has been done. The protocol that follows is about how to do that work efficiently and how to execute when the send comes.

Separating the Work From the Send

The first principle of the redpoint protocol is that projecting and sending are two different activities requiring two different mental states. When you are projecting, you are problem solving. You are trying holds, adjusting foot positions, discovering rests, and building sequences in your memory. You are allowed to fall. Falling during the working phase is information. When you are on a redpoint attempt, you are executing. You are not discovering. You are not adjusting. You are running the program you already built during the working phase.

The most common mistake climbers make is treating every session like a working session, then expecting a different outcome when they decide to "go for it" without changing anything about their approach. They climb the route tired, they try new beta on the wall, they take at positions they did not practice resting, and they expect to send. This is not a redpoint protocol. This is hope. Hope is not a strategy. The protocol requires you to be deliberate about when you are working and when you are attempting, and to treat those phases differently.

During the working phase, your goal is to gather data. Which holds are good? Where do you have decent rest positions? Where does the route get thin and sequential? How many attempts does it take before you fall at each section? This information builds the map you will navigate during your redpoint attempt. The working phase should feel exploratory, experimental, and relatively low pressure. You are allowed to be uncomfortable here because discomfort is how you learn. The redpoint attempt, by contrast, should feel like running a race you have already won in practice. You have done the training. Now you execute.

The Mental Protocol for Redpoint Attempts

Fear of falling is the primary obstacle to sending a project. Not the physical difficulty of the route, not the strength requirements of the crux, but the fear that accumulates when you are climbing above your last bolt or above your last clipped position. This fear is rational. Falling on a sport route can result in injury if you hit the ground or swing into a ledge. Managing this fear is not about ignoring it. It is about having a system for acting despite it.

The mental protocol for redpoint attempts begins before you tie in. Before you clip the draws, before you chalk up, you visualize the entire route from bottom to top. You see every hold, every foot position, every rest, every clip. You see yourself climbing through the crux without hesitation. You see yourself clipping the anchors. You rehearse this visualization at least three times before you climb. Visualization is not wishful thinking. It is motor program rehearsal. The same neural pathways that fire during physical climbing fire during detailed visualization. You are practicing the route without touching the rock.

When you tie in and begin climbing, your goal is to stay in the execution state. You do not want to be problem solving. You do not want to be evaluating beta. You want to be moving through the sequence you already know. If you feel yourself trying to analyze a hold or decide where to put your foot during a redpoint attempt, that is a signal you have not done enough work. The working phase was incomplete. This is not a reason to abort the attempt, but it is a reason to be conservative. You cannot send a route you have not solved. You can only send a route you have solved and are now executing.

Rest management is part of the mental protocol. You will arrive at rest positions on the route feeling pumped or slightly under control. The instinct is to rush, to clip quickly and keep moving. The protocol says the opposite. Take the rest you planned. Clip with calm hands. Do not rush. Rushing increases heart rate, accelerates blood flow to your forearms, and shortens your recovery window. You have earned these rests during the working phase. Use them. Clip with slow, deliberate motion. Breathe. Then commit to the next section when you are ready, not when you feel pressured by gravity or fear.

Physical Protocol: Session Structure and Attempt Management

The redpoint protocol requires you to manage your attempts across multiple sessions, not crush yourself into the ground in one day and then wonder why you cannot climb well for the next week. Attempt quality matters more than attempt quantity. Five high quality attempts where you are climbing with purpose and commitment are worth more than twenty attempts where you are running through the motions hoping something changes.

Each session should have a maximum of three to five redpoint attempts. These attempts should be your best efforts, not throwaway burns at the end of a warm up. If you are saving your best attempts for when you are already fatigued, you are sabotaging yourself. Structure your session around quality. Climb the route once, maybe twice if the first attempt went well and you feel physically capable of a second attempt. Then rest, evaluate, and plan for the next session. The protocol is not about grinding until you fall off from exhaustion. It is about building momentum toward a clean send through structured, quality attempts.

Rest between sessions matters. If you are projecting a route that requires multiple days of work, you need adequate recovery time between sessions. Muscle tissue repairs in forty-eight to seventy-two hours. Neural pathways consolidate during sleep. If you climb a route hard today, you will not be stronger tomorrow. You will be the same or slightly weaker until your body catches up. This means the protocol includes planning your sessions around recovery, not just around motivation. Motivation tells you to climb every day. The protocol tells you to climb when you are recovered enough to climb well.

Redpoint fitness is different from onsight fitness or flash fitness. When you are redpointing, you are climbing a route at your absolute limit while potentially carrying fatigue from previous attempts or previous sessions. This requires both finger strength and energy system work. Your training should include sustained power endurance, the ability to hold on to small holds and generate power after your forearms are already fatigued. The protocol for building this fitness includes specific training for the energy systems that support high intensity climbing, not just general climbing volume.

Building Redpoint Fitness

Redpoint fitness is built through targeted training that mimics the demands of the route you are projecting. If your project requires twenty moves of hard climbing with a crux at move fifteen, your training should include similar sequences. Repeating boulder problems near your limit, doing circuit work that matches the length of your route, and hangboard protocols that build your ability to hold on when pumped are all part of the protocol. General climbing volume alone will not build redpoint fitness. You need specific work that addresses the specific demands of your project.

The energy systems involved in redpoint climbing are primarily the glycolytic and alactic systems for efforts lasting thirty seconds to two minutes, with aerobic recovery playing a role in longer rests and between attempts. Training should address these systems through appropriately dosed efforts. Short boulder problems with long rest periods build alactic capacity. Circuit style climbing with minimal rest builds glycolytic capacity. The protocol does not require you to understand the biochemistry, but it does require you to understand that different training efforts target different capacities, and your project needs all of them.

You should be climbing at or above the difficulty of your project during training. If you are projecting 5.13a, you should be regularly climbing V5 to V7 boulder problems and 5.12 sport routes in training. This does not mean you send those routes easily. It means the effort required is similar to the effort you will face on your project. Climbing easier routes in training does not prepare you to climb hard routes. You prepare for hard routes by climbing hard routes in training. This is not gatekeeping. This is physiology.

When You Are Ready to Send

You are ready to send when you have completed the route in practice multiple times, when you have no remaining questions about beta, when you have built your redpoint fitness through specific training, and when you have managed your attempts across enough sessions that fatigue is not a limiting factor. Readiness is not a feeling. It is a checklist. If you cannot check those boxes, you are not ready to send regardless of how confident you feel.

The final push is not about adding effort. It is about removing interference. You have done the work. You have built the fitness. You have solved the route. The protocol says to trust what you have built and execute. Chalk up. Clip in. Breathe. Climb the route you already know. Rest where you practiced resting. Move through the crux the way you rehearsed. Clip the anchors. The send is not a mystery. It is the logical conclusion of the work you have already done. You either did the work or you did not. If you did the work, send. If you did not, go back to work.

The protocol ends when you send or when you decide the route is beyond your current capacity and you remove it from your active project list. The protocol does not include indefinite suffering on routes you are not strong enough to send. You will grow stronger. Routes that are beyond you today will become possible as you develop. This is not quitting. This is honest assessment. The protocol is about efficiency, not ego. Sending one route cleanly is worth more than falling on ten routes while claiming you are "still working them." Climb less. Send more. That is the protocol.