Maple Leafs Face An Unexpected Cap Wrinkle In Kucherov Pursuit

Despite securing a promising long-term extension with Kirill Marchenko, the Toronto Maple Leafs now face significant constraints under the NHL's tagging rules, leaving them with limited salary cap flexibility.

The Toronto Maple Leafs thought they had pulled off a major win when they landed Kirill Marchenko the day before the season and locked him up on a long-term extension right away. A month later, that move has put them in a bind few fans had on the radar. The issue is tagging room, and Toronto has less of it than any other team in the NHL.

That matters because the Leafs are now operating with just $648,000 left, the lowest total in the league. PuckPedia’s Hart Levine describes tagging room as the cap space a team has available to add commitments for next season while still playing the current one.

It is measured against the current cap plus 10%, which works out to $114.4 million for 2026-27. Every contract already on the books for 2027-28 counts, including deals for players in the minors.

In practical terms, the rule is there to keep teams from loading up too much salary into future seasons and stumbling into cap trouble later. Toronto got squeezed by handing out multi-year contracts to depth forwards over the summer, then making the Marchenko move and signing him to an extension worth $12.5 million per season beginning next year. That number is roughly $4.75 million more than Matthew Knies, the player Marchenko effectively replaced.

Hart also pointed out that tagging was part of the reason the Marchenko-Knies trade itself had to be reworked.

For Toronto, the consequences are pretty restrictive. Players on two-way contracts can’t simply be called up for next season.

Ben Danford, for instance, would immediately cost $780,000 in tagging room the moment he was recalled. The Leafs also can’t bring in anyone by trade, waivers or signing if that player already has a contract for 2027-28.

That leaves them with a narrow set of options: players without deals for next season, or players already in the organization on contracts that fit the rules.

LTIR does not solve the problem, either, because it only applies one season at a time. If the injuries pile up, Toronto could have a hard time dressing a full lineup. There are emergency exceptions in the CBA for current-year cap issues, but Hart said people around the league do not know how a shortage created by tagging would be handled.

The rule also adds another layer to the chatter around Nikita Kucherov. One of the bigger rumors floating around is that Toronto could be in the mix if the Tampa Bay Lightning decide to trade him. The tagging issue would not block that outright, but it would make the mechanics trickier.

Kucherov has told Tampa Bay he will not re-sign there, and Elliotte Friedman reports he would consider Toronto. If the Leafs wanted him on a long-term deal, they would need to extend him after the season or build significant money into the trade. The catch is that any extension hits the tag room the moment it is signed.

That means the extension could end up shaping how much Toronto is willing to give up in the first place. If the Leafs cannot get Kucherov extended right away, they would have to bank on him not walking at the end of the season. And if he is aiming for $20 million on his next contract, the math gets ugly fast.

The most realistic path would likely involve Toronto sending back players with term, which would clear room and make an extension possible. Even then, the margin is razor thin. The tagging rule is not necessarily a dealbreaker for the Leafs, but it is a major constraint on how any Kucherov deal would have to be built.

In Other News...

Maple Leafs Let A Vital Home Point Slip Over One Costly Mistake

Jack Roslovic did enough to give the Maple Leafs a chance at home, scoring both Toronto goals in a 3-2 loss to the Utah Mammoth at Scotiabank Arena. The Leafs had to grind for their offense, and Sergei Bobrovsky turned aside 33 of 36 shots, but the game still tilted on a late sequence that left Toronto staring at a missed opportunity for a valuable point.

With the score tied, a costly penalty put the Leafs on the penalty kill at the worst possible time, and Utah made them pay on the ensuing power play. It was the kind of finish that stings because Toronto had already done the hard part of getting back level, only to watch one mistake undo the work and send the home crowd away with a frustrating result. [Read more 🡒]

Maple Leafs Trade Piece Emil Andrae Suddenly Faces Another Uncertain Turn

Emil Andraes season has already taken one sharp turn, and it may be headed for another. After being dealt by the Maple Leafs to the Columbus Blue Jackets on Sept. 28 in a trade that sent several players between the two clubs, the young defenseman has now found himself on waivers as Columbus continues sorting out its roster picture.

Andrae has appeared in five games for the Blue Jackets this season, but his immediate future is now up in the air again. If he clears waivers, the next stop is expected to be the AHLs Cleveland Monsters, leaving the Leafs former trade piece once more waiting to see where he fits in a transaction that has already moved plenty of pieces around. [Read more 🡒]

Maple Leafs Suddenly Face An Emil Andrae Decision Again

Emil Andrae is back on the waiver wire, and with it comes another familiar question for the Maple Leafs: whether they want to get back into the mix on a player they already moved once this year. Columbus put the defenseman on waivers after a brief run of five games this season, reopening a situation that had seemed settled only after a busy stretch of transactions.

Andraes path has already been unusually winding, with two trades this year and Toronto among the teams involved in sending him to Columbus in a multi-player deal. Now the Leafs have a chance to consider whether a reunion makes sense, even if nothing has been confirmed yet, and the timing alone makes this one worth watching for a club that knows him well enough to at least revisit the conversation. [Read more 🡒]