Skip to content
Foundation5 min

How Cricket Partnerships Are Built: Communication, Strike Rotation, and Risk Management

A batting partnership in cricket requires two batsmen to function as a single strategic unit — communicating between deliveries, managing running between the wickets, making joint decisions about when to attack and when to consolidate, and supporting each other's mental state during difficult passages. The art of partnership-building is distinct from individual batting skill: two excellent individual batsmen can fail as a partnership (if they run poorly, take unnecessary risks, or have no shared tactical plan), while two modest technical batsmen can thrive through excellent communication and complementary styles.

Written by GeoCric EditorialUpdated Invalid Date
ShareShareWhatsAppFacebook

The partnership's tactical components: a batting partnership in Tests or ODIs has several joint responsibilities: (1) Communication between deliveries: batsmen meet at the midpoint of the pitch between overs (during bowling changes, at strategic moments) to share information — which bowlers are swinging, which fielders are positioned, what the pitch is doing, what the required run rate demands. This communication is continuous and evolving. (2) Strike rotation: one of cricket's most undervalued partnership skills is rotating the strike effectively — ensuring neither batsman faces too many consecutive balls from a single dominant bowler. If a left-handed and right-handed batsman are together, rotating the strike means the fielding team must constantly adjust their field positions. If a spinner is dominant against one batsman, the other should take more of the bowling. (3) Running between the wickets: the two batsmen must have shared calling conventions — who calls ('yes,' 'no,' 'wait') on which shots. The batting end batsman (facing) calls on straight shots; the non-striker calls on square and behind-square shots (where they have the better view). Poor running costs wickets — the run-out, cricket's most avoidable dismissal. (4) Risk management: in a partnership, risk decisions are shared — if one batsman is new to the crease (fresh, less settled), the other (established, higher score) should bear a greater proportion of the singles and running. The established batsman 'farms' the strike, allowing the incoming batsman to see a few balls before facing a bowler consistently.

Famous Partnerships and Their Characteristics'

Hobbs and Sutcliffe (England, 1924-30): the greatest opening partnership in cricket history by average. In 38 Tests together: 3,249 runs at 87.81 average per partnership — 26 century partnerships. Their method: Sutcliffe described Hobbs as the greatest batsman he had ever seen; Hobbs described Sutcliffe as his 'most reliable partner.' Their partnership method was based on complete trust — each knew the other's game so thoroughly that calling was rarely needed beyond the conventional 'yes' and 'no.' Their Oval 1926 partnership on a difficult pitch (after rain — a turning, unreliable surface) — where they scored 172 together to set up England's Ashes win — is the most celebrated individual partnership in Ashes history. Laxman and Dravid (India, 2001 Eden Gardens): the most significant rescue partnership in Test history. India were following on against Australia (281 runs behind), and within the first session of the follow-on innings had lost 4 wickets cheaply. At 81/4 following on (effectively 362 runs from extinction), Laxman (281) and Dravid (180) put on 376 runs together — the highest 5th-wicket partnership in Test history at the time, and the partnership that won India the match. Their method: Laxman attacked; Dravid defended. Laxman described Dravid as the 'perfect partner' — 'he was a wall; I could attack freely because I knew he would not play a rash shot.' The complementary style model (attacker + defender) is the most effective partnership type in Tests. Sehwag and Gambhir / Sehwag and Tendulkar (India, 2000s): Sehwag's attacking opening role required a partner who would not panic when he was scoring at 80+ balls per 100. Gambhir provided a measured but scoring partner; Tendulkar (when opening) was a natural attacking partner. The most prolific Indian ODI partnership is Tendulkar-Ganguly's 136 stands for 6,609 runs — the most runs in any ODI opening partnership in history.

The 2006 England vs Pakistan — Inzamam and Younis Khan partnership that saved the series: in the Faisalabad Test (August 2005), Pakistan were in serious trouble against England — 80/4 in the second innings, needing to survive 5+ sessions for a draw. Inzamam-ul-Haq and Younis Khan came together and batted for almost 7 hours — Inzamam making 156, Younis 202. Their combined partnership of 363 runs saved the match and the series. The partnership's tactical model: Inzamam and Younis were both attacking players — the conventional attacker-defender model did not apply. Instead, they calibrated together: when England introduced the spinner (off-spinner Ashley Giles), both batsmen moved forward to attack; when pace was bowling, both went back. Their shared field mapping was efficient — after each over, they would consult briefly about bowling changes and field placements. The moment when England captain Michael Vaughan introduced 7 fielders in front of the wicket to dry up the singles, Inzamam and Younis both accelerated the boundary striking (playing lofted shots over the infield) rather than accepting the dot-ball pressure. The partnership also demonstrated the mental support function of a long partnership: both described moments of exhaustion and difficulty in which the other's presence — a word of encouragement, a tactical suggestion, a shared joke at the bowling — kept the concentration alive. Cricket's partnership record — psychological dimension: long partnerships (200+ together in a session) require a shared mental endurance that is distinct from individual focus. The batsmen enter a 'partnership flow state' — where their shared tactical awareness becomes almost intuitive.

Running Between the Wickets — The Partnership's Foundation'

Running between the wickets — the mechanics: all calling in cricket is the responsibility of the batsman who can best see the fielding disposition of the relevant fielding area: Facing batsman (striker) calls for all straight and near-straight shots — they can see the field ahead of them (to long-on, long-off, midwicket). Non-striker calls for all behind-square and fine-leg shots — they can see the field behind the striker (third man, fine leg, backward point). The calling convention: 'Yes' — run immediately. 'No' — do not run, stop. 'Wait' — hold position until the call converts to 'yes' or 'no.' The disaster — miscommunication: a failed calling convention is cricket's most common non-ball dismissal cause. A 'yes' called by the striker when the non-striker has already called 'no' creates a mid-pitch collision or a run-out situation. Good partnerships develop calling certainty through: familiarity (long-term partnerships like Hobbs/Sutcliffe), shared training (batting together in net practice), and clear convention (never change the call once made). Running between the wickets in ODIs and T20s: in limited-overs cricket, running aggressively (turning 1s into 2s, taking the 3rd run) is valuable — it increases the scoring rate without boundary risk. Rohit Sharma and Shikhar Dhawan (India's ODI opening partnership, 2013-2019) were considered the best-running ODI partnership of their era — their familiarity (from hundreds of innings together) made their 3s and 2s off average running-between-the-wickets situations almost automatic. Running between the wickets in pressure situations (run chases): in tight run chases, communication intensifies — the required run rate increases, the urgency of each running decision increases. Partnerships that run well under pressure (Jos Buttler and Dawid Malan in England's ODI team, 2016-2022) can convert 1s into 2s consistently, keeping run rates competitive without the batsman taking false shot risks.

Frequently asked questions

What is a batting partnership in cricket?

A batting partnership is the two batsmen at the crease working as a tactical unit — communicating between deliveries, rotating the strike, managing running between the wickets, and making shared decisions about attack and defence. Partnership totals are recorded for each wicket that falls: the '4th-wicket partnership' is the runs scored by the 4th and 5th batsmen together before either is dismissed. The largest partnerships are significant enough to determine match outcomes.

What is the highest batting partnership in Test cricket?

The highest partnership for any wicket in Test cricket is 624 runs — by Mahela Jayawardene (374) and Kumar Sangakkara (287) for Sri Lanka's 3rd wicket vs South Africa in Colombo, 2006. This is also the all-wicket Test record. The highest individual wicket records are listed by wicket number — all discussed in the batting partnership records article.

How does strike rotation help a batting partnership?

Strike rotation — converting deliveries into singles and twos to change which batsman faces the next over — helps a partnership by: (1) Preventing one batsman from facing a dominant bowler for too many consecutive balls; (2) Changing the fielding team's setup (a left-right hand combination forces constant field adjustments); (3) Allowing a new batsman to 'settle in' while the established batsman takes more of the strike early. In Test cricket, rotating the strike also helps when one batsman is struggling against a specific bowler type (e.g., aggressive against left-arm spin) — reducing their exposure.

What was the Laxman-Dravid partnership in 2001?

The Laxman-Dravid partnership at Eden Gardens in 2001 (India vs Australia, Kolkata) is the most celebrated rescue partnership in Test history. India were following on at 81/4 (362 runs behind when including the follow-on deficit) when VVS Laxman (281) and Rahul Dravid (180) came together. They put on 376 runs — saving the follow-on, then winning the match by 171 runs. Australia's 16-match winning streak ended. Laxman attacked; Dravid defended — the perfect attacker-defender complementary style.