Choose the timers that change a decision
A short basic ability may return before the team can use the information. A long ultimate, escape or skill that controls several players creates a larger and more useful window. Before the match, identify one important ability on each opponent, then narrow the list as the real threats become clear. Tracking four reliable timers is better than announcing ten uncertain numbers. The purpose is to answer whether the team can attack without missing the enemy movement that begins the fight.
Mark the use, not the result
Start the estimate when the ability is visibly used. Do not wait until its damage, movement or channel ends unless the current description says the cooldown begins later. Some abilities have changed this rule in updates, so old memory can be wrong. A simple report such as ultimate used now gives teammates a shared starting time. If the ability was canceled or reset by another effect, update the report. The team should never build a push around a timer that nobody actually observed.
Cooldown reduction prevents exact guessing
Ability cooldown reduction lowers a percentage of the base time, and several sources can combine without simple addition. Items, map bonuses and upgrades may change the value. Enemy builds are visible enough to improve an estimate, but a team should still use a window rather than promise an exact second. Say unavailable for this push when that is all the decision requires. If the fight is delayed, assume the ability is returning and seek fresh confirmation before committing.

Charges require two separate questions
A charged ability may hold more than one use. Its charge cooldown describes when a spent charge returns, while a separate delay can limit how quickly another stored charge is cast. Seeing one use does not prove the skill is unavailable. Track whether the opponent had already spent another charge and watch the interface or animation for repeated use. When uncertain, call one charge used instead of cooldown. That wording protects the team from treating a partially depleted resource as an empty one.
Your own timers set the earliest fight
Teams often track enemy ultimates and ignore that their own initiation or protection is still unavailable. Before moving toward an objective, each player with a major responsibility should state ready, seconds remaining or not joining. The caller then chooses whether to wait, take a smaller action or give up the contest. Entering early and hoping a cooldown finishes during the fight transfers control to the opponent. A deliberate delay behind cover is often stronger than arriving first without the tool needed to hold the space.
Item timers form another layer
Active and passive items can have cooldowns separate from hero abilities. Ability cooldown reduction does not automatically shorten every item timer. A defensive item may be the real reason a target survived the previous attempt, while a mobility item may determine whether initiation reaches the back line. Track the effect, not only the item name: cleanse used, movement unavailable or protection ready. This language remains useful even when an update changes a numerical cooldown.
Use replay to correct one estimate
After a failed objective fight, find the first important ability and note when it became available again. Compare that interval with the report and the opponent's build. The mistake may be timing, a hidden charge or simply waiting too long before acting. Correct the category before memorizing a number. A team that learns which abilities create real windows will make better decisions even after balance updates, because it can refresh the exact values without rebuilding the whole communication system.

