Rainbow Six breach planning and site defence

1. Identify the critical surface

Choose the wall, hatch or doorway that changes objective access. Consider the defender positions behind it and the attacker positions needed to use the opening. Opening every possible surface can create extra hostile sightlines without improving the planned route.

2. Coordinate denial removal

Before the breach, identify the defensive tools that prevent it and which teammate can address them. Sequence the actions so the opening and covering positions are ready together. Spending the breach tool before the team can remove denial risks losing the entire plan.

3. Defend with connected positions

A site setup should let players cover useful areas without trapping one another. Think about rotation routes and which teammate can respond to contact. A powerful isolated angle can collapse if attackers cut the defender’s only escape or supporting sightline.

4. Review the unused opening

When attackers breach successfully but still fail to progress, check whether they had information, cover and time to use it. The breach itself may have worked. The missing step can be follow-up movement or protection for the player interacting with the objective.

Practice worksheet: turn the lesson into a decision

Use one replay, training situation or recorded match from Rainbow Six Siege. Choose a sequence where the issue in this guide appears. Watch the lead-up once without pausing, then return to the point before the important commitment. The aim is to describe a choice clearly enough that you can recognise a similar situation again.

1. Describe the starting state. Write who can participate, what resources are available and which part of the map or objective matters. Separate directly visible information from assumptions. If a player or resource is not visible, record it as unknown instead of filling the gap with hindsight.
2. Check the first decision. Begin with “Identify the critical surface”. Describe the action that was taken and one realistic alternative. An alternative must respect what the player could know and reach at that moment; it cannot depend on seeing the rest of the replay.
3. Follow the consequence. Look for what the choice changed: access to space, a teammate’s options, a resource, or control of the objective. Record the consequence before scoring the final result. A good decision can still lose an exchange, while a poor one can survive through an opponent’s error.
4. Repeat one correction. Use a consistent practice setup where possible. Keep the same role, controls and starting task while changing one decision. In the next replay, check whether the intended action occurred. This is a self-review exercise; we have not measured a rank, win-rate or latency improvement.

Illustrative situation

Attackers open the planned wall but approach without covering a side room. A defender uses that route to disrupt the plant. The review should include side-room control and the post-breach sequence, rather than simply add another breach tool next round.

Use that example as a question, not a script. What information would justify the action in your own game? What new threat would make you stop? Write a short failure condition beside the plan, so the lesson includes when to change course as well as when to act.

Questions about this lesson

What should I practise first?

Start with “Identify the critical surface”. Choose a situation you can repeat or identify clearly in a replay. Add the next checkpoint only when you can explain why the first action was appropriate. This keeps practice focused on a decision rather than a collection of tips.

What is the most common review trap here?

Judging an execute only by whether a wall was opened. Compare the information available before the choice with what the replay reveals afterward. Those are different views of the same situation. The useful correction is a habit you can apply without knowing the future.

Does this replace the current game or event rules?

No. Check the publisher’s current client notes and the organiser’s rulebook for costs, timings, map pools, restrictions and competition format. This lesson explains a decision process and avoids fixed patch-specific values that could become stale.

Can a scoreboard prove this lesson worked?

A scoreboard can show a result, but it does not describe the choices that produced it. Review the relevant sequence and compare similar situations. Avoid attributing a win to one setting or tactic when opponents, teammates and the game state also changed.