Presented here is a set of basic doctrinal schema for Random Battles, to guide teams that in all likelihood, have never fought together before.

1st RBAT Doctrine Statement (RBAT-1DS) - Structure of battlefield.
In RBAT, the WOT battlefield can be divided into the following functional areas: a Primary Front (1F), a Secondary Front (2F), Defensive Fronts (DF), Defence Zones (DZ) and Areas of Interest (AI). See separate
monograph on RBAT combat doctrine when fighting on the Fronts.

2nd RBAT Doctrine Statement (RBAT-2DS) - The top 2 manuevre tanks.
The top 2 manuevre tanks in a company shall always fight together, on the same Front, and be supported initially by at least 2 other tanks.

manuevre tanks are defined as light, medium and heavy tanks. TDs and SPGs are defined as specialist tanks. At all tiers, this doctrine applies. In our experience, when the top 2 manuevre tanks split up and advance on different fronts, the chances of overall victory are reduced. The supporting tanks can be a combination of specialist (usually TDs) and other manuevre tanks. This doctrine remains true even when you experience match making mayhem!

e.g. : The Top 2 manuevre tanks are a KV (T5) and a M2 Medium (T3). In between them are four TDs. The two manuevre tanks should still stay together. In this example, the supporting tanks should include at least 2 of the TDs to maintain combat strength.

A common criticism of this doctrine is when the two tanks are of dissimilar speeds, commonly seen when the tanks are a heavy and a medium. That is why the doctrine is phrased as “fight together” and not necessarily “move together”. A medium can proceed 10-15s ahead of the heavy to gain a key defensive position while waiting for his buddy. What the medium should not do is engage decisively with enemy forces before his heavy (and support tanks) are in position.

Another example is when the top 2 manuevre tanks have clearly different strengths e.g a Panther with the 7,5cm L/100 gun ("sniping" tank) and a KV3 ("brawling" tank). Again the tanks need not move together but must fight together. Classically this would mean that the Panther is about 200m behind the "brawling" tank and firing at targets that the KV3 is engaging or lighting up.

Another compelling viewpoint is that the top medium tank should organise and lead a medium “wolf pack”, even if he is a top 2 tank and, if necessary, separating from the other top tank. Admittedly, we ourselves have, on occasion, experienced success with this, where a trio of VK3601s (number 2,3 and 4 tank in the
orbat) in a T6 fight wreaked havoc on the secondary front and captured the base whereas our KV-3 (top tank) was bogged down on the primary front. However, the key reason that we allow DS1 to supersede wolf pack theory is that not every map is wolf pack friendly. In certain maps, for example El Halluf, it is of very limited utility. Do note that to us at TACT, wolf pack theory is not simply about mediums fighting together but describes a specific style of medium play. Please see the separate monograph on wolf pack theory.

3rd RBAT Doctrine Statement (RBAT-3DS) - The 3rd manuevre tank.
The 3rd manuevre tank shall be responsible for a different Front from the top two manuevre tanks, and be supported by at least 3 other tanks.

This doctrine statement underlines the belief at TACT that teams need to divide their assets on two fronts and not throw everything into a single front push. Single front (“all-in”) assaults often result in their own base falling to capture as enemy fast mediums flank the entire assault force and take the base.

Although we have, on occasion, seen single front assaults succeed, they often fail as good teams will exploit the weaknesses inherent in a single front push. Thus single front strategies should be viewed as high risk gambits and not as core strategy.

4th RBAT Doctrine Statement (RBAT-4DS) - Manuevre tanks fight in pairs.
All manuevre tanks, except those executing a scout role, should initially fight in at least pairs (squad). They may pair with a TD.

During the initial distribution of forces, manuevre tanks (except those scouting) should, at a minimum, buddy up with another tank. This allows concentration of fire and improved survivability of forces. When manuevre tanks operate independently, there are vulnerable to rapid destruction and significantly reduce their combat options. This is frequently seen by players who are trying to play a “lone hunter”, roaming the battlefield with the intent to further their personal agenda, but with little regard to the overall team strategy.

We do encourage TDs to also consider fighting in pairs, either with another TD or manuevre tank but this is not core doctrine as it is not always possible or desired and is heavily dependent on the terrain/ map. On certain maps, TDs do venture out alone to take up possible ambush positions. What prevents TDs from pairing up in ambush? Nothing! It is just that we are limited to 15 tanks and pairing up in ambush may not always be possible.

Once again, the emphasis is on “fight together”, not necessarily “move together”. “Fight together” means that both tanks can effectively
engage the same enemy. Two tanks on different sides of a hilltop firing at different groups of enemy tanks are not strictly “fighting together”!

5th RBAT Doctrine Statement (RBAT-5DS): Manuevre tanks lead on 1F and 2F.
Manuevre tanks should lead the action on primary and secondary fronts.

The key point here is that we believe manuevre tanks should dictate the structure of battle, and “lead” the primary and secondary fronts, even if they die first! Hence, a Tier 3 light tank “leading” two Tier 5 TDs down a secondary front should not be viewed as wrong. The light tank may die early and the TDs may win the battle for the team, which is the desired outcome.

The key reason for this is that manuevre tanks are more versatile than specialist tanks. This versatility is defined by a balance of mobility, survivability and firepower whereas specialist tanks often trade one for the other. This versatility allows manuevre tanks to transition positionally faster from PUSH to HOLD (or vice versa) or execute
Dynamic Defence.