The Late Call at Durban: Rabada's Load and South Africa's Hidden Risk

I was flipping through an old notebook on a corner of my Dhaka rooftop when a page stopped me — Durban, Friday. Kingsmead. South Africa versus Australia. Beside it, the name Kagiso Rabada, and right next to the name, a question mark I had drawn myself. After forty-two years moving in and out of this game, it has become a habit: when there is a question mark beside a star's name, the story is not finished. This one is not finished either.

The reason is plain. Since the Pakistan tour last October, Rabada has not bowled a single ball in a Test. His last competitive cricket was the IPL in May. Then nearly five months of silence, with no first-class match inside it. In between, a hamstring pull; before that, a rib injury. Whether he walks out at Durban on Friday is a decision still hanging until the eve of the toss.

A sun-baked rooftop, a glass of tea, and the weight of a Test series — put those three together and a man starts to think. And my thought is simple: how much risk is South Africa really taking, and exactly where does that risk sit?

Test cricket is an accounting of five days of patience. T20 death-over skill buys you nothing here; the real currency is the new-ball spell, session-by-session fatigue, and red-ball workload. Kingsmead is a coastal ground — seam early, spin later. That favours a fuller pace attack, and it explains why South Africa kept all seventeen players instead of trimming to fifteen.

The wider context is bigger still. In June, South Africa wrote history by winning the World Test Championship final at Lord's. This is their first home Test since that triumph, and the opponent is that same Australia. A champion's homecoming — the emotional weight is naturally heavy.

On top of that, they sit second in the current WTC table. Of their ten remaining Tests before January, eight are at home and two are in Sri Lanka. A home-heavy block is a ranking-consolidation window — if the pace corps stays fit.

That is where my first interest takes root. Retaining seventeen players is arithmetic self-defence. Eight home Tests before January is not just a fixture list; it is a workload budget. And in that budget Rabada is not a single line item — the entire fast-bowling unit is exposed.

I found the story on a Dhaka rooftop before the world had a camera there. When a side keeps seventeen instead of cutting to fifteen, it is quietly admitting: we know our best bowler will not last the whole way.

Head coach Ashwell Prince's own words are the most valuable testimony here — Rabada is "obviously not going to be at 100% straight away." That is not an admission of weakness; it is an honest sum. A bowler who has not sent down a single red ball since October will need time for his body to absorb a five-day spell — elementary cricket, and the plain conclusion of forty-two years of watching.

The two-day intra-squad match is the only recent evidence. And I say it repeatedly: validating five-day Test fitness through a two-day, net-like game means leaping from a small sample to a large decision.

This is where the core point sits: South Africa are not worried about Rabada's form; they are worried about his fitness and his load tolerance. Form is not the question — the body is.

Look at the injury sequence. A hamstring strain in the winter, which cost him the ODI series; a rib injury before that. At thirty, that is a clear signal on a fast bowler's body — the pace is still there, but durability is becoming ever more expensive.

From years of watching matches I have understood one thing: a fast bowler's real enemy is not the opposing bat but the number of matches. Eight home Tests before January means four to five sessions of load every other game. No medical team can carry that alone; it is a scheduling sum.

Yet the batting order is still messy. Tony de Zorzi has withdrawn with a hamstring problem — removing an opening/top-order option. And the No. 3 slot is undecided. Prince has said the top six is known internally, but No. 3 is open. Marques Ackerman, Tristan Stubbs, Wiaan Mulder, Matthew Bedingham — the names circle, none is final.

Ackerman's story is intriguing. He has banged the door down with domestic runs, and he has No. 3 experience. A home-ground debut is possible. But I have a warning, one I have seen repeatedly while working on youth development: banging the door down with domestic runs and converting those runs in a Test are two different skills. In many countries, a large share of domestic statistics halves when it meets international standard.

Still, there is a positive here. Keeping the domestic-to-national pathway open is real progress. Many boards now hoard talent in elite academies and never give younger players a first-team chance. South Africa, at least, is leaving the door ajar.

South Africa versus Australia is one of Test cricket's hardest rivalries. The contest between these two is never only runs and wickets; it is a mental examination. And this time it is sharper still, because the very Australia beaten at Lord's now arrives at their hosts' doorstep. This smells of revenge, and in a match thick with that smell, a selection error costs the most.

Now I come to the place where I disagree with the conventional view.

The conventional argument is strong, and I will not wave it away lightly: South Africa should take the risk, because Rabada is the spearhead, it is a home Test, and you need an X-factor to shake Australia's top order. That is not a point to dismiss. A fit Rabada can turn a series on his own — I have seen it with my own eyes many times.

Russia taught me that a single bet can turn a stadium into a mirror. The same is happening here: public pressure and home-Test emotion are forging a mirror that says "bring him back early." But the picture that mirror shows may not be real.

My objection is this — while everyone stares at Rabada, the real risk hides in the batting order, and that is this series' hidden story. Two top-order question marks at once (de Zorzi's absence at the top, uncertainty at No. 3) is a bigger continuity problem than Rabada's fitness.

And a second unease: two players in the same camp — Rabada and de Zorzi — with hamstring problems. It may be coincidence; but I note it as a possible signal of a camp fitness-programme issue, rather than dismissing it as mere chance.

The late-call strategy is itself an interesting thing. Deferring the decision does not remove the risk, only postpones it. At the same time it manages public opinion: by not confirming Rabada, the team dampens premature hype, and by resting him it reduces backlash. Administratively clever, cricketing-wise incomplete.

Consider the worst-case scenario once. Rabada is in the XI, bowls six or seven overs in the first innings, then pulls a hamstring. One bowler short in a five-day Test means extra load on the rest, and that does not stop with one match's result — it casts a shadow on the next Test too. That is why the late call is not merely about Rabada; it is the whole series' strategy.

So the risk account reads like this. The biggest risk is physical: a hamstring history, no first-class preparation, and a five-month competitive gap. The second is structural: eight home Tests before January means one man's injury can become a whole bowling unit's crisis. The third is selection: a messy top order.

The league-versus-national-team workload conflict is clear here too. Rabada's last real match-intensity was the May IPL — a high-intensity T20 tournament. Then a five-month gap, then straight into a Test. That transition is not only about skill; it is about the body. And the coaches have said it plainly — domestic T20 is running, but they want their quicks to bowl more red balls, to build the loads. It is a conscious choice: in this window, Test first, domestic T20 second.

And across this home block the real test will be rotation — who rests, who plays back-to-back. The best care for one fast bowler is never about him alone; it is the whole unit's plan. Eight Tests before January is a marathon for South Africa's pace coach, not a sprint.

My read: the thing to watch most this series is the length of Rabada's spells, not merely whether his name is in the XI. If he bowls full quotas from the start, that signals confidence in his fitness — but also the risk of a load spike. And watching how the quicks are rested after each Test will reveal how seriously the side treats workload management.

That leaves one big question hanging. A side second in the WTC table, with eight home Tests — to hold its final-qualification margin, it must win this block. That very urgency creates the temptation to rush a star back. But the question is this: if you burn one bowler for a single series, how do you fill the gap in the next two?

My notebook still holds that question mark. I am watching not from a Durban rooftop but from Dhaka — and sitting there, it seems South Africa's real test is not Rabada's hamstring but their patience. The answer will come when the match ends; until then, the story stays unfinished.