Raids Raid Healing Strategies and Priorities
Raid Healing Strategies and Priorities
Raid healing is a sequence of decisions about the next dangerous event. A low health bar tells you that damage happened; it does not tell you whether that player will die before your next action. Effective triage combines health, incoming damage, existing healing effects, positioning, and the resources your team still has available.
This guide focuses on decisions during an encounter, with ability examples from Square Enix’s level-100 PvE job guides. Start with the next lethal event, assign prevention and recovery separately, and keep a backup ready. The healer class comparison covers kits; the role guide covers the whole group.
Prioritize the Next Lethal Event
Start with three checks: who is in immediate danger, what action can reach them in time, and what happens to the rest of the group while you use it? Prioritize the player whose next damage event is lethal. That can be the tank facing a heavy hit or a damage dealer carrying a required mechanic.
For example, a tank at 60% health may safely wait while you save a player whose next debuff tick would kill them. If the tank’s heavy hit comes first, redirect your immediate response there. Timing makes the priority clearer than comparing health bars alone.
Also distinguish a missing heal from a missing mechanic response. If a target is beyond range, an otherwise appropriate spell cannot solve the problem from your present position. If a mechanic requires mitigation before impact, a large heal afterward cannot rescue a player who did not survive. During the pull, choose a workable response. Afterward, review the cause without assuming that the healer or the damaged player was automatically at fault.
Match the Tool to the Damage Pattern
The official job guides show why “use a big cooldown” is too vague:
| Situation | Verified FFXIV example | Planning implication |
|---|---|---|
| Immediate single-target recovery | White Mage Benediction restores all of the target’s HP; 180-second recast | Reserve a deliberate use for a recovery problem, rather than treating it as a preventive shield |
| Damage arriving over time | White Mage Regen lasts 18 seconds | Allow the periodic recovery to work when the target can safely wait |
| Several repeated hits | Sage Panhaima supplies a barrier and 5 renewal stacks over 15 seconds | Its repeated protection is materially different from one large direct heal |
| Damage plus movement | Scholar Expedient provides 10 seconds of movement speed and 20 seconds of 10% damage reduction; 120-second recast | Schedule around both the movement and damage windows |
The numbers come from the linked White Mage, Sage, and Scholar guides. A useful healing assignment names the ability and event, so everyone knows whether the assignment provides prevention, recovery, or movement support.
Build a Cooldown Plan Around Events
Create a short event list from the encounter you are learning. Record the mechanic name, whether damage is a single impact or a series, where players stand, the assigned mitigation, and the assigned recovery. Keep approximate timestamps secondary to recognizable events; phase transitions can change the pace of an attempt.
For repeated hits, assign Panhaima to cover the sequence and have the co-healer plan the remaining recovery. When the group must move during incoming damage, Expedient can cover both needs. Record which part of the event each assigned tool handles, then adjust the plan to the jobs in your actual group.
Distinguish useful combined coverage from accidental duplication. Two direct heals landing on nearly full players may contribute little. A preventive effect plus recovery after damage performs two different jobs. Some effects also have explicit stacking restrictions: the Scholar guide says Adloquium’s barrier cannot stack with certain Sage barriers. Read the named effects rather than assuming every combination works.
Write a backup for the assignment most likely to fail. If its owner dies or uses the ability early, who can cover the next event? A plan with a replacement response is more useful than a perfect schedule that assumes every pull goes as intended.
Treat Resources as Part of the Plan
Check each ability’s resource cost alongside its cooldown. Sage Druochole consumes 1 Addersgall while restoring HP and 7% of maximum MP. Scholar Aetherflow restores 20% of maximum MP and supplies Aetherflow resources, has a 60-second recast, and requires combat. Spending a resource now affects which responses remain available at the next event.
FFXIV healers also have Lucid Dreaming, which restores MP over 21 seconds with a 60-second recast. White Mage Thin Air removes the MP cost of the next action, rather than making every action free for its full duration. These distinctions matter when preparing for repeated recovery or a resurrection: check the specific resource and effect rather than grouping everything under “mana-efficient.”
Compare resource state with the next required assignment. A healer with more MP may still have the wrong range, unavailable cooldowns, or a different mechanic to handle. Do not automatically transfer all healing work based on two MP percentages alone. State the concrete problem: which event you cannot cover and which ability you are missing.
Use Damage Windows Without Losing Coverage
Use offensive actions during windows when survival needs are covered. Plan the recovery first, identify the time until the next damage event, and use that interval for damage while keeping the next response available.
Sage’s Kardia assigns Kardion to a selected ally or the Sage, and certain offensive spells heal that recipient. Verify the recipient before the pull and when tank assignments change. Keep separate party healing and mitigation ready for raidwide damage.
Practice this sequence during a familiar encounter: finish planned recovery, use an offensive action, and prepare for the next event. Add more actions as the timing becomes comfortable. After a failed attempt, check whether healing was delayed, a required defensive was missing, or positioning put someone out of reach. That identifies the adjustment for the next pull.
Review Failures With Specific Evidence
After a wipe, select the first preventable failure rather than the last player to die. Ask whether the target was in range, whether a shield or mitigation was active before impact, and whether the assigned recovery was available. Change one assignment when the evidence supports it, then see whether that failure recurs.
Use the game’s permitted tools. Square Enix’s third-party program notice states that third-party tools are prohibited. In-game displays and permitted recordings can still help a group discuss what happened. For layout choices that keep health, casts, and positioning visible, see the raid UI guide.
Sources
- Square Enix: White Mage actions — Benediction, Regen, Lucid Dreaming, and Thin Air.
- Square Enix: Sage actions — Panhaima, Druochole, and Kardia.
- Square Enix: Scholar actions — Expedient, Aetherflow, and barrier restrictions.
- Square Enix: Third-party programs and player safety — tool policy.
Ability details checked November 2, 2026.