Last season Kaizer Chiefs released a few players from their DDC side after an incident where the youngsters refused to be ball boys at an FNB Stadium match.
One of those players, Puso Dithejane, subsequently joined TS Galaxy. Now, sources close to the club have indicated that Chiefs could be working to bring Dithejane back to Naturena in June.
READ: Pirates In Unlikely Pursuit Of KZN Striker?
Insiders with reliable information added that club scouts and the technical team are believed to be closely monitoring Dithejane, who has also attracted interest from Mamelodi Sundowns and a club in Germany.
"You remember the Sporting Director talked about short term and long term plans? One of the long term plans is believed to be working on bringing Puso (Dithejane) back to the team in the off season. We are all human and we make mistakes, and, so what if the team made a mistake and they want the player back?" asked the Siya source close to the club.
"After all he is a Kaizer Chiefs product. He would also want to play for the club just like his former youth teammates who are currently doing well for the first team. Obviously, there is going to be competition from other clubs but Chiefs are looking at what they can do to bring him back. That's their focus," the source added.
A second insider mentioned that TS Galaxy reportedly paid Chiefs compensation when the 20-year-old joined them. Chiefs are now willing to offer more to re-sign him.
READ: Magesi To Let Go Of Ex-Chiefs Winger?
"They have done something like this in the past. You know Zitha Kwinika was at the club before he left and they signed him with big money from Stellenbosch FC. So it wouldn't be for the first time. But if you look at what Puso can do it will be worth it to bring him back and join the youthful side to build the future for the team. I don't think he will be that expensive as well," the second insider told Soccer Laduma.
Since joining TS Galaxy in the second half of last season, Dithejane has featured in many games.
The Siya crew contacted Chiefs for comment, but there was no response at the time of publication.
