Stealth Missions

Stealth Missions in D&D 5e: Prep, Detection, and Alarms

Last Update:May 27, 2026

A stealth mission becomes interesting when the players can read the place: a guard’s route, a lit crossing, a noisy gate, and somewhere to retreat. Success should follow from their approach and the characters’ abilities, rather than surviving an arbitrary number of Stealth checks.

This guide uses 2014 D&D 5e for its main rules. The 2024 Hide action has a materially different procedure. The mission, patrol schedule, alarm stages, and sample DCs below are original DM guidance.

A hooded figure moves through a shadowy stone passage with crates and distant torchlight

Quick answer: prepare information, routes, and consequences

Write an objective, two or three ways in, the defenders’ senses and routines, what can raise an alarm, and how the party can get out. Explain the visible risks. Call for checks only when the approach leaves an uncertain outcome that matters.

Being detected need not end the whole mission. A guard might investigate a sound, challenge an unfamiliar worker, or ring a bell after identifying intruders. Choose the response that follows from what that particular guard actually perceives.

Before the session: build a readable security plan

Prepare Useful notes
Objective What must be recovered, learned, planted, or reached?
Routes Public entrance, concealed entrance, difficult physical approach
Guards Exact stat blocks, senses, passive Perception, equipment, motives
Visibility Light sources, opaque barriers, open sight lines, special senses
Sound Loud machinery, quiet floors, doors, and sounds guards expect
Routine Patrol positions and a few observable time windows
Alarm Who can signal, how, and what response actually exists
Extraction Routes usable with the objective, including an injured companion

A patrol schedule is a preparation aid, not permission to make the defenders know the party’s location. Track what each guard has learned. A shouted warning carries information only to someone who can hear it.

Make routine information available through observation. A locked office may be a problem to solve; the existence of the office should not require three successful checks to discover.

Resolve 2014 stealth in this order

1. Establish what could reveal the characters

Describe positions, distances, lighting, and barriers. Consider sound as well as sight. A guard looking through an open doorway presents a different problem from one on the far side of a stone wall.

Under the 2014 hiding rules, the DM determines when hiding is possible; a creature cannot hide from someone who sees it clearly. A successful roll does not let a character cross an unobstructed view as though invisible.

2. Decide whether a check is necessary

If a route avoids meaningful observation and noise, it may simply work. If a character walks openly past an attentive guard in bright light, a Stealth check may not be an available solution. A disguise, distraction, or another route might be.

For an uncertain attempt to remain unnoticed, ask for Dexterity (Stealth). Establish the consequence before rolling: “If you make noise at that door, the clerk will come to investigate.” That is more useful than concealing every failure consequence until after the result.

3. Use the appropriate observer

Compare the Stealth result with passive Wisdom (Perception) when the observer is not actively searching. An active search can use a Wisdom (Perception) check. Passive scores include +5 for advantage or −5 for disadvantage; apply those adjustments only when they affect the relevant perception.

Keep a hiding result while it remains applicable, rather than rerolling every five feet. A different guard, changed lighting, noisy action, or exposed route can change the situation. Explain when and why a new check is needed.

4. Resolve what the guard noticed

A failed attempt might reveal a sound without revealing every intruder’s location. Someone clearly seen crossing a courtyard is a different case. Do not turn a failure into mere suspicion when the guard has directly identified an enemy, or into instant omniscience when they heard an unexplained scrape.

5. Update positions, knowledge, and time

Describe the response and let the players act. Record whether the guard investigated, challenged someone, called another guard, or reached the alarm. Start combat initiative when appropriate; do not award free attacks simply because a mission was previously using exploration time.

Light, cover, and invisibility are different tools

Feature What it helps with What it does not guarantee
Dim light Makes sight-based observation harder Automatic concealment from every observer
Darkness or heavy obscurity Prevents ordinary visual detection where the observer cannot see through it Silence or immunity to other senses
Solid cover Blocks a particular sight line Protection from a guard on another side
Darkvision Changes vision within that feature’s stated range A universal 60-foot range or daylight-quality vision in darkness
Invisibility Prevents ordinary sight of the creature Silent footsteps or automatic success at sneaking

The 2014 vision rules distinguish lighting and special senses. Apply a sight penalty to sight-based detection; it does not automatically penalize hearing a dropped shield. For a fuller explanation, use vision, light, and obscurement.

A wall that provides cover against attacks is not automatically sufficient to conceal every approach. Check the actual line of sight and the character’s features.

Use group checks when the task is genuinely shared

The 2014 group-check procedure succeeds if at least half the group succeeds. It is useful for a coordinated crossing where skilled characters can help the group move quietly.

It does not mean one scout’s success hides companions standing in plain sight. If the party splits between a rooftop and a public doorway, resolve those different approaches separately. The Help rules also require a task where assistance is actually possible.

Respect the equipment the characters chose. Apply an armor’s listed Stealth disadvantage, but do not invent an automatic failure or a general rule that wearing heavy armor halves jumping distance. Check the actual movement, armor, and encumbrance rules when they matter.

Give other characters meaningful options: authenticate a delivery, watch a patrol, carry equipment, hold a route open, or negotiate an access request. These contributions need not all become extra rolls.

Spells should change the problem honestly

Pass without Trace adds its stated bonus to qualifying Dexterity (Stealth) checks; it does not lower the guard’s DC or make an exposed person unseen. Invisibility can solve a visual problem while leaving noise and physical obstacles relevant.

Fog can block sight for both sides and attract attention in an otherwise ordinary room. Teleportation can bypass an obstacle when its range, destination, and other requirements are met. Check each spell’s components, concentration, targets, and exact text.

If a spell defeats the security measure, let it. The next interesting question may be how to open the vault or carry the objective out, rather than inventing an unexplained countermeasure after the spell succeeds.

Optional alarm stages: track consequences, not extra lives

This is a homebrew organizational aid, not a replacement for perception or surprise rules.

State What defenders know Likely response
Routine No meaningful evidence of intrusion Continue normal duties
Suspicious A sound or irregularity needs checking One guard investigates a specific location
Confirmed intrusion Someone identified an intruder or clear sabotage Warn nearby allies and attempt the alarm
Lockdown The signal reached the prepared responders Close named exits and deploy actual available guards

Advance according to events. An obviously seen intruder can move directly from Routine to Confirmed intrusion. A guard who finds an ordinary explanation may return to Routine. Do not automatically erase witnessed evidence because someone later rolls high.

Worked mission: recover the customs ledger

Objective: take a duplicate shipping ledger from a dockside office and leave before the morning tally. Opposition: two 2014 guards, using their printed stat blocks; each has passive Perception 12. Their goal is to protect the warehouse and call the watch, not die defending paperwork.

This is an original mission layout and schedule. Decide whether two guards would be an appropriate combat threat using the encounter balancing guide, even if the players intend to avoid a fight.

Layout and routes

The warehouse is 60 feet east–west and 40 feet north–south. A 10-foot-wide, 20-foot-long office occupies its northeast corner. The ledger lies on an unlocked desk; a normal inspection of the office finds it without a check.

Route Visible opportunity Risk
South loading doors Workers are admitted with a delivery docket An unfamiliar delivery can be challenged
West service door A stack of crates hides the approach from the south post A locked door must be opened quietly
North office window The window is 10 feet above the ground; an opaque shutter blocks sight into the office Reaching and opening it without noise requires a workable plan

One guard remains at the south loading doors. The other walks outside from the southwest corner clockwise around the building, pausing to inspect each side and reaching each next corner after one minute, then repeats. The patrol rings a handbell if intruders are confirmed. The nearest watch patrol arrives three minutes after a bell, not instantly. State these timings in minutes during exploration; switch to rounds if an immediate confrontation starts.

Checks and fair consequences

  • Observe the patrol: watching a complete circuit reveals the pattern without a check if the observer has an unobstructed, safe vantage.
  • Reach the service door: a quiet, coordinated approach behind the crates uses one group Dexterity (Stealth) check against the relevant guard’s passive Perception 12 if their route leaves an uncertain noise risk.
  • Open the lock: a character proficient with thieves’ tools can attempt a DC 12 Dexterity check using those tools; an attempt takes one minute in this example. Failure leaves it locked and costs that minute. Forcing a clearly unsuitable method does not create the same opportunity.
  • Handle a squealing shutter: applying oil first prevents the squeal. Opening it untreated alerts a nearby guard if they can hear it. Do not add a roll merely to take away a successful precaution.
  • Use a delivery cover story: accept valid documents that settle the request; use a Charisma (Deception) check only if a plausible lie remains uncertain.

The DCs and task durations above are scenario rulings. A full patrol circuit takes four minutes, so a failed lock attempt can materially change the available window. Tell the party when they hear the guard coming around the next corner.

Resolve the exit as part of the mission

The party can leave by the route it prepared, use a public exit while its cover remains credible, or abandon the attempt. If someone raises the alarm, track who heard it and which route is now blocked.

A character reaching the ledger early can take it. Do not add a second locked chest or a hidden replacement ledger solely to extend the mission. If the group succeeds through good observation and one well-placed spell, that is a complete result.

2014 vs. 2024 hiding

The 2024 Hide action requires its stated concealment, being outside enemies’ line of sight, and a DC 15 Dexterity (Stealth) check. Success grants the Invisible condition while hidden; the recorded result becomes the DC to find the creature with Perception. The action specifies what ends hiding.

That procedure should not be blended into the 2014 contested/passive explanation above. Likewise, use the chosen edition’s surprise rules: in 2014 a surprised creature has first-turn restrictions; in 2024 surprise imposes disadvantage on initiative. Read 2014 combat or the 2024 initiative rules when a stealth mission becomes a fight.

At the table: five questions before another roll

  1. Who could detect this character, using which sense?
  2. Does the proposed approach make remaining unnoticed possible?
  3. Has anything changed enough to require a new check?
  4. What does failure actually reveal, and to whom?
  5. What choice follows that result?

Keep a short mission log: time, positions, current hiding results, defender knowledge, alarm status, and usable exits. Those notes are more useful than an escalating DC added whenever the players make progress.