How to Balance D&D 5e Encounters: Prep and Table Guide
An encounter that looks reasonable on paper can become dangerous when the party is exhausted, trapped in a doorway, or unable to reach the enemy. I find encounter prep more useful when it answers two questions: what pressure should this scene create, and what could make it go wrong?
This guide uses 2014 D&D 5e encounter building as its baseline, with a separate 2024 method. The checklists, encounter setup, and suggested responses during play are DM advice rather than additional rules.
Quick answer: how do you balance an encounter?
Choose the intended stakes, calculate the encounter using the correct ruleset, then check the monsters against the party’s actual capabilities and likely starting positions. Do not add challenge ratings together or compare total CR to total character levels.
Prepare a way for the scene to end besides everyone on one side dying. During play, use the enemies’ established goals, morale, and the battlefield to resolve what happens. A quick victory can be a successful encounter, especially when the players earned it through planning.
| When you need it | Use this section |
|---|---|
| Building tonight’s fight | The preparation checklist |
| Checking the numbers | 2014 encounter math |
| Seeing a complete example | The tollhouse encounter |
| Handling an unexpected result | The table reference |
| Using the revised rules | 2014 vs. 2024 |
Before the session: prepare these six things
- Purpose. Is this a warning, an obstacle, an optional risk, or the session’s major confrontation? Decide what success changes.
- Party state. Note who is attending, their levels, current hit points, important resources, and whether they can rest beforehand.
- Opposition. Select the exact stat blocks, calculate difficulty, and read every ability that could remove a character from the fight.
- Starting situation. Mark distances, cover, exits, and what each side can see. Decide what information the party can discover before committing.
- Enemy behavior. Write a goal, an opening tactic, and a reason to retreat, surrender, or negotiate.
- Consequences. Prepare outcomes for victory, withdrawal, and defeat. If reinforcements exist, specify where they are and what brings them.
“Four characters fight some guards” leaves most of the important decisions for the session. “Four tired characters must cross a guarded bridge; the guards want a toll and will not pursue beyond their post” gives you something you can run.
For broader scene design, pair this checklist with creating memorable encounters.
Calculate the 2014 XP difficulty
Add each character’s XP thresholds; total monster XP; apply the monster-count multiplier; compare adjusted XP with the highest party threshold reached. These are difficulty estimates, not promises. Deadly signals a risk of character death, not certain defeat. See the official 2014 encounter-building rules and full level table.
Deadly has no upper ceiling. An encounter far above that threshold can be overwhelming even though it carries the same label as one just above it.
XP thresholds per character
| Character level | Easy | Medium | Hard | Deadly |
|---|---|---|---|---|
| 1 | 25 | 50 | 75 | 100 |
| 2 | 50 | 100 | 150 | 200 |
| 3 | 75 | 150 | 225 | 400 |
| 4 | 125 | 250 | 375 | 500 |
| 5 | 250 | 500 | 750 | 1,100 |
For higher levels, use the linked official table. For mixed levels, add individual rows rather than averaging levels.
Monster-count multiplier
| Monsters | 1 | 2 | 3–6 | 7–10 | 11–14 | 15+ |
|---|---|---|---|---|---|---|
| Multiplier | ×1 | ×1.5 | ×2 | ×2.5 | ×3 | ×4 |
With fewer than three characters, move one multiplier higher (×5 beyond ×4). With six or more, move one lower (×0.5 below ×1).
Exclude much weaker creatures from the count unless they contribute meaningfully. Adjusted XP measures difficulty; award unmultiplied monster XP. An encounter below Easy remains below Easy.
Save the party thresholds in your session notes. Recalculate when attendance changes.
What does challenge rating tell you?
CR describes an individual monster’s threat. The 2014 rules use a rested, appropriately equipped party of four of the same level as the monster’s CR as a broad reference point. It does not describe every matchup. Monster XP also rises unevenly with CR, so two CR 1 creatures are not interchangeable with one CR 2 creature. See the official monster statistics explanation.
Use the exact version of each stat block. A familiar monster name does not tell you whether the book, website, or encounter tool is using its 2014 or revised statistics.
Check the dangers the XP total misses
Use the following as a practical review after calculating difficulty. There is no reliable universal conversion such as “one magic weapon means one extra party level.”
| Check | Ask during prep | Possible change before play |
|---|---|---|
| Damage spikes | Can one ordinary hit, critical hit, or opening burst drop a vulnerable character? | Choose a less damaging foe, reduce attackers, or give warning and room to avoid engagement |
| Lost turns | Can paralysis, incapacitation, or another effect leave someone unable to contribute? | Check saves and recovery conditions; give allies a practical response |
| Reach and access | Can everyone meaningfully affect a flying, distant, or protected enemy? | Add accessible routes, usable cover, or an objective within reach |
| Defenses | Do resistances, immunities, or exceptional AC shut down the party’s main tools? | Provide discoverable information or choose a different creature |
| Combined abilities | Does one enemy restrain targets while another exploits that weakness? | Review the combination as a whole |
| Starting position | Can the party be surrounded or attacked before reaching safety? | Establish distances and escape routes before rolling initiative |
| Current resources | What healing, spell slots, and defensive features remain? | Remove an enemy or make an alternate approach available |
Check the opening round, not just a monster’s average output over several rounds. An attack that defeats a healthy low-level character before they act deserves special attention. For example, the deals an average of 13 damage on a hit; that can overwhelm a fragile adventurer even when the encounter’s overall XP looks modest.
Count useful actions, not just bodies
Several enemies can concentrate attacks on one character, guard different routes, and keep acting after one falls. A lone monster can lose much of its threat if the party prevents it from acting. These are reasons to examine the matchup, not a second formula that guarantees balance.
For a solo boss, check how its printed abilities let it stay involved between character turns and respond to control. A monster with suitable legendary actions or resistances may fit better than simply choosing a much higher CR. Raising CR can make individual hits more lethal without solving the scene’s pacing. Changing abilities or adding allies creates a new encounter to review.
Terrain changes who can use their abilities
An enemy behind cover on a balcony presents a different problem from the same enemy in an open room. A narrow passage might protect the party from being surrounded, but it could also block allies from reaching the front line. Sketch the actual approaches instead of assuming a map feature always helps one side.
Make relevant terrain understandable: how high is the balcony, where are the stairs, and which barriers block sight? If the players can scout, negotiate, or approach from another direction, let those choices affect the starting situation.
An ambush also needs the correct procedure. In 2014 combat, determine surprise for each creature, then roll initiative. There is no separate surprise round before initiative; a surprised creature loses movement and actions on its first turn and cannot react until that turn ends.
Plan around resources and rests
Write the likely sequence of pressure and recovery. A party arriving with everything available can commit resources very differently from a party that has already survived two fights and a hazardous crossing.
Use three questions:
- What is likely to be spent before this scene: hit points, healing, spell slots, or limited class features?
- Where could the party realistically recover, and what would waiting cost?
- Can the players learn enough about the next threat to decide whether to continue?
Treat daily encounter budgets as planning aids. Do not turn an expected adventuring day into a compulsory number of combats or punish a group for choosing to rest. If your sessions usually have one major fight, start with a moderate threat for that group and learn from its results; jumping straight to an extremely dangerous opponent can produce a sudden defeat rather than sustained tension.
Noncombat scenes can affect resources when the fiction and rules support it. Climbing a safe ladder is not automatically an attrition encounter. A dangerous crossing might cost spells, equipment, or time if those consequences follow from the players’ approach.
Worked example: the tollhouse
Party: four 3rd-level characters. Opposition: one and two . Purpose: a tense obstacle with a negotiated route through, rather than a mandatory fight to the death.
The is worth 450 XP; each is worth 100 XP. Both orcs can threaten this party and count toward the multiplier.
| Calculation | Result |
|---|---|
| Party thresholds: four times the level-3 row | Easy 300; Medium 600; Hard 900; Deadly 1,600 |
| Monster XP | 450 + 100 + 100 = 650 |
| Three-monster multiplier | 650 × 2 = 1,300 adjusted XP |
| Estimate | Hard: at least 900, below 1,600 |
| Monster XP to share if awarded | 650 total, not 1,300 |
That result starts the review. It does not account for the party’s injuries, their approach, or who reaches whom first.
Notes you can run from
| Prepare | Tollhouse notes |
|---|---|
| Visible situation | A broad road passes a tollhouse. An ogre and two armed orcs stand beside a supply cart; the approach is open and both groups can see each other |
| Starting distance | The guards call out when the party is 60 feet away; nobody begins surrounded |
| Enemy goal | Collect 20 gp to replace missing supplies; willing to accept supplies of similar value |
| Information | They state the demand and explain the shortage if asked; negotiations do not require initiative |
| Terrain | A waist-high stone wall offers half cover when it actually obstructs an attack; the cart blocks the middle of the road but leaves routes around both sides |
| If combat starts | Roll initiative; the ogre defends the cart while the orcs approach visible attackers using their printed movement and attacks |
| Morale | When either orc falls, the survivors offer a ceasefire if allowed to keep their cart; they do not pursue a withdrawing party beyond the tollhouse |
| Other outcomes | Payment, a supply bargain, bypassing the post, withdrawal, or a fight can all resolve the obstacle |
These demands and morale triggers are choices for this example, not monster traits. See the site’s ogre and orc guides for other motives and encounter setups.
Adjust it before the session
Removing one orc gives 550 × 1.5 = 825 adjusted XP: Medium for this party. That may be a better starting point if the group is injured or still learning its abilities.
Adding a third orc gives 750 × 2 = 1,500: still Hard. Adding a fourth gives 850 × 2 = 1,700: Deadly. Notice how adding one creature can cross a threshold even though the multiplier stays the same. More opponents also take longer to run.
If only three characters attend, their Hard threshold is 675 and Deadly is 1,200. The original 1,300-adjusted-XP encounter is now Deadly, even without changing a monster.
At the table: a quick difficulty reference
Use this after the opening exchange and whenever the situation changes substantially. The goal is to understand what is happening and keep choices clear, rather than force a close result.
| What you see | Check first | Useful response |
|---|---|---|
| A character drops immediately | Was a rule misread, or was this a known damage spike? | Correct an error openly; otherwise make the remaining options and enemy intentions clear |
| Several characters cannot act | Which effects allow saves, require concentration, or can be ended by allies? | Track the exact recovery rules and describe what the characters can observe |
| The party is losing ground | Is retreat possible? Do the enemies want capture, payment, territory, or revenge? | Let established motives support an offer, withdrawal, or another objective |
| The party wins quickly | Did scouting, positioning, or resource use earn the advantage? | Let the victory stand and move to its consequences |
| The outcome is clear but turns drag on | Do surviving enemies still have a reason to fight? | Use their prepared morale; end initiative once immediate opposition ends |
| Someone discovers a major prep mistake | Did the encounter rely on incorrect numbers or an unintended ability? | Explain the mistake briefly and agree on a correction if necessary |
Keep positions, conditions, and limited abilities in your notes or the initiative and combat tracker. Accurate tracking often resolves what initially looks like a balance problem.
Make adjustments through established circumstances
Before play, choose hit points and other stat changes deliberately. Once the fight starts, a useful default is to keep those numbers stable. Quietly adding hit points whenever the party succeeds can make their choices stop mattering; reducing them whenever the fight turns dangerous makes the stakes hard to understand.
You can still respond to events. Mercenaries may bargain when their employer falls. A beast defending food might stop chasing intruders who leave it alone. A guard may spend a turn carrying a wounded ally to safety. Choose behavior that fits what these creatures know and want.
Reinforcements need a cause, a route, and a limit. Write down who can hear an alarm and how long reaching the scene takes. If the party prevents that alarm, honor the result. If enemies arrive before the first group is defeated, review the combined threat; overlapping attackers can be much more dangerous than separate fights. Avoid adding attackers solely because the party is winning.
If you made a serious error, an honest correction is available. There is no need to disguise a mistaken damage calculation as a surprise plot twist.
Make withdrawal playable
“You can always run” is unhelpful when the enemies are faster and every exit is blocked. Before a dangerous encounter, provide usable information and decide where pursuit ends or what could interrupt it. Explain visible escape routes before the group needs them.
Resolve movement and attacks normally while those details matter. Under the 2014 combat rules, Disengage prevents opportunity attacks for the rest of that turn, but does not stop an enemy following on its own turn. If the scene becomes a prolonged pursuit, move into your agreed chase procedure.
Capture, lost supplies, or an enemy achieving its objective can be useful defeat outcomes when they fit the fiction. Establish those possibilities; do not assume every opponent will spare the party.
2014 vs. 2024 encounter building
The 2024 free rules use Low, Moderate, and High XP budgets. Add the per-character budgets for the chosen difficulty, then spend that total on monster XP without exceeding it. The 2014 monster-count multipliers are not part of this method.
For four 3rd-level characters, a 2024 Moderate budget is 4 × 225 = 900 XP. The tollhouse’s 650 monster XP fits within that budget, leaving 250 XP unspent. That describes a budget comparison, not a guarantee about its outcome. Check the exact monsters you intend to use.
Do not carry the 2014 Hard label into that calculation or assume the two systems give identical results. When using an encounter calculator, check both its ruleset and the version of its monster entries. The practical reviews of damage spikes, party resources, objectives, and starting positions remain useful with either method.
After the session: record what will help next time
Keep a short note: who attended, what resources remained at the start, what caused the biggest swing, and whether anyone lacked useful choices. Ask whether the danger was understandable and whether the fight lasted longer than it stayed interesting.
Change one major factor in the next comparable encounter so you can learn from the result. A difficult fight caused by an exposed starting position calls for a different response from one caused by an unexpectedly lethal attack.
Frequently asked questions
Does a balanced party need a tank and a healer?
No particular role lineup is required. Prepare for the abilities the actual characters have: how they handle distance, recover from setbacks, and help someone in trouble. A party without a familiar role is a design consideration, not a defective group.
How do I make an encounter harder without adding monsters?
During prep, give the opposition a defensible position or a goal that competes with attacking, such as escaping with a document. Explain the terrain and stakes, then review how they change the party’s options. Increasing damage, AC, or hit points also changes the creature; its printed CR may no longer describe it accurately.
Can I use encounter math with milestone advancement?
Yes. XP can be a planning measure even when characters level up at story milestones. Keep the difficulty calculation separate from your advancement method.
Should every encounter challenge the party equally?
No. Easier scenes can show progress, establish a threat, or let a good plan pay off. Optional overwhelming threats can also belong in the world if the party receives usable warnings and ways to avoid them. Choose the intended experience for each scene rather than making every fight equally close.