An encounter table is not just a list of things that interrupt the player. It is a tone machine. If the rows are too harsh, the game can become punishing. If the rows are too bland, the journey loses texture. Boundaries help you build a table that can surprise you without ambushing you.
Solo play still needs consent structure. You may be the only player, but you are still choosing what kind of fiction enters your room, your notebook, your mood, and any shared space around the table. A good encounter table makes that choice before the die rolls. It gives surprise a lane to travel in.
The point is not to make every session gentle. It is to make intensity intentional. A table can include danger, loss, pressure, and conflict while still respecting the rating and appetite you chose for tonight.
Start With Content Bands
Before writing rows, choose the band: all-ages nearby, gentle, tense but non-graphic, mature but bounded, or private intense. Then choose lines that will not appear. This is especially important for violence, cruelty, sexual threat, self-harm, body horror, harm to children, and real-world prejudice.
The table should not be allowed to smuggle in content you already declined.
Write the band at the top of the table before any row text:
Content band:
Lines:
Soft spots:
Visible-room rule:
Veto rule:
The visible-room rule matters when a notebook, card, image, or map can be seen by someone who did not opt in. “All-ages nearby” might mean no mature visible text and no intense images on the table. “Private mature but bounded” might allow darker stakes while still excluding specific material.
Use plain bands:
| Band | What it means | Encounter table shape |
|---|---|---|
| All-ages nearby | Someone else may see or overhear | Obstacles, requests, weather, puzzles, mild pressure |
| Gentle | Low emotional intensity | Inconvenience, social friction, sensory color, recovery |
| Tense non-graphic | Danger exists but stays bounded | Threat, chase, hard choice, cost, off-page harm |
| Mature bounded | Stronger themes with clear exclusions | Pressure, consequence, moral tension, recovery path |
| Private intense | Only for a chosen private session | Strong content still follows lines, stop rules, and aftercare |
These bands are not official ratings. They are working labels for your own table. The same game can move between bands on different nights. The table should follow the band you chose today, not the most intense version the genre could support.
If a published adventure or campaign already has content notes, keep them visible while writing encounter rows. Do not copy protected scenario text into a public table. Summarize the boundary in your own words.
Name Lines, Soft Spots, and Recovery
Lines are not in the table. Soft spots may appear lightly, indirectly, or off-page if you choose. Recovery is what helps the session return to playable ground after pressure.
Write all three:
Lines: no graphic injury, no sexual threat, no real-world hate
Soft spots: isolation, betrayal, illness
Recovery: safe rest, helpful stranger, clear exit, quiet scene
Recovery is easy to forget when designing encounter tables. Without it, every row can become escalation. That makes a campaign feel relentless. Add rows that let the world breathe: a sheltered place, a repair opportunity, a kind request, a quiet landmark, a clue that reduces uncertainty, or a chance to choose a different route.
The presence of recovery rows does not remove tension. It makes tension sustainable.
Mix Encounter Types
Use categories instead of only enemies. A balanced table might include person with need, person with offer, environmental obstacle, clue, resource, delay, strange sign, social friction, safe rest, and real danger. This keeps solo play from turning every surprise into combat or punishment.
For cozy games, danger can become inconvenience, cost, embarrassment, weather, broken tools, or a difficult request. For darker games, danger can be stronger, but recovery still matters.
A useful encounter table has more verbs than threats. It should give the player things to notice, negotiate, avoid, repair, accept, refuse, and follow.
Good category mix:
| Category | What it adds | Example row shape |
|---|---|---|
| Need | A request or problem | Someone asks for help with a limited cost |
| Offer | A chance with strings | A shortcut appears if you spend a resource |
| Obstacle | Friction without blame | The direct path is blocked or slowed |
| Clue | Campaign continuity | A detail points to an open thread |
| Resource | Relief or temptation | Useful supply appears with a choice attached |
| Delay | Time pressure | Progress takes longer than planned |
| Social friction | Human pressure | A misunderstanding needs careful handling |
| Safe rest | Recovery | A low-pressure pause becomes available |
| Real danger | Stakes | A threat appears inside the chosen content band |
Not every table needs every category. A six-row gentle travel table might include obstacle, offer, clue, delay, safe rest, and mild danger. A twelve-row tense table might include two danger rows, but also recovery and noncombat pressure.
Avoid the common pattern where every encounter is an enemy. Even in a combat-capable game, encounter does not have to mean fight. It can mean contact, complication, evidence, weather, terrain, social demand, resource shift, or a changed choice.
Write Rows With a Safety Handle
A safety handle is the part of the row that tells you how to soften, redirect, or stop without losing the table. It can be a phrase like “off-page,” “with exit,” “non-graphic,” “social cost,” “resource cost,” or “nearest safe version.”
Compare:
| Row without handle | Row with handle |
|---|---|
| Ambush | A threat blocks the path; resolve as chase, parley, or detour |
| Injury | A useful item is strained, lost, or marked |
| Betrayal | Trust is tested; keep the choice reversible |
| Despair | A delay makes the goal feel farther away; add one recovery cue |
| Horror image | A strange sign appears; keep details non-graphic |
The safer row is not bland. It is playable. It gives pressure while preserving options.
Use row shapes like:
- “A person needs help, but accepting costs time.”
- “A route closes unless you spend a resource.”
- “A sign points to an open question.”
- “A quiet place offers rest if you pause the goal.”
- “A threat appears at a distance, giving one clear exit.”
- “A social mistake creates a repairable cost.”
- “A tool fails, but a workaround is visible.”
Rows like these create decisions. They do not force the session into the harshest possible reading.
Choose the Table Size
Small tables are easier to keep bounded. Large tables create variety but make boundary drift more likely.
Use a d6 table when:
- You are playing tired.
- The content band is gentle.
- You want a travel or scene table for one session.
- You need rows you can scan quickly.
Use a d12 or d20 table when:
- The campaign will reuse the table.
- You want multiple categories.
- You have time to review every row against the boundary.
- The table has recovery rows as well as danger rows.
Use 2d6 when ordinary pressure should be common and extreme events should be rare. That is useful for long journeys, town reactions, weather, and social tension. A flat d20 makes every row equally likely, including intense rows. That is fine only if every row is acceptable tonight.
Add a Boundary Rule
Write a rule at the top: “If a result breaks tone, age rating, or access needs, shift it to the nearest safe category.” A violent ambush might become a blocked road. A horror image might become a strange sound. A despair prompt might become a costly delay.
This rule lets the table stay active without making the player endure every roll.
Make the rule visible and specific:
Boundary rule: If a result crosses a line, shift to the nearest safe category without adding a penalty. If it touches a soft spot, fade out, summarize, or lower intensity. If it creates access friction, replace with a result that can be played tonight.
“Without adding a penalty” matters. If every veto costs the character, the boundary becomes fake. The table should not punish you for keeping the session within the agreed frame.
Use conversion pairs:
| If the row crosses a line | Convert to |
|---|---|
| Graphic violence | Non-graphic threat, blocked route, damaged tool |
| Cruelty | Harsh demand, cold refusal, social distance |
| Sexual threat | Nonsexual boundary violation, unwanted attention, need to leave |
| Self-harm | Exhaustion, withdrawal, missed message, need for rest |
| Body horror | Strange trace, damaged object, unnerving environment |
| Harm to children | Threat to a place, plan, resource, or timetable |
| Real-world prejudice | Fictional faction friction without real-world slur or targeting |
These are examples, not obligations. The nearest safe category depends on your band and appetite. Sometimes the right conversion is simply “reroll” or “choose a different row.”
Build a Table in Three Passes
Do not try to write the perfect encounter table in one pass. Use three passes.
First pass: categories. Write only the type of row, such as clue, obstacle, offer, rest, social friction, danger. This checks the table’s shape before details sneak in.
Second pass: row text. Write each row as a playable change. Keep it short.
Third pass: boundary review. Read each row against the content band, lines, soft spots, access needs, and visible-room rule. Rewrite anything that relies on shock or unwanted intensity.
Example first pass for a d8 table:
| d8 | Category |
|---|---|
| 1 | Obstacle |
| 2 | Need |
| 3 | Clue |
| 4 | Delay |
| 5 | Offer |
| 6 | Social friction |
| 7 | Safe rest |
| 8 | Real danger |
Then add row text:
| d8 | Encounter row |
|---|---|
| 1 | The direct route is blocked; a slower route remains |
| 2 | Someone asks for help carrying, repairing, or explaining something |
| 3 | A detail points to an open question in the campaign log |
| 4 | Weather, crowds, or procedure costs extra time |
| 5 | A useful shortcut appears with a small obligation |
| 6 | A misunderstanding needs repair before progress continues |
| 7 | A quiet place offers rest, notes, or supply sorting |
| 8 | A threat appears at a distance; choose prepare, avoid, or approach |
This table has danger, but not only danger. It also has choice and recovery.
Keep Access Needs in the Table
Accessibility is part of encounter design. A table can fail because it is too emotionally sharp, but it can also fail because it is too dense, too slow, too hard to read, or too physically demanding to run.
Access-aware table choices include:
- Fewer rows.
- Larger print.
- Symbols or color bands.
- One threat type at a time.
- Shorter row text.
- A visible veto rule.
- A “choose directly” option.
- Token pulls instead of dense lookup.
- Voice notes instead of handwriting.
If scanning is difficult tonight, do not use a d20 table with long rows. If emotional load is high, reduce consequence rows and use sensory or logistical pressure. If fine motor handling is hard, use cards, larger dice, or a digital roller. The encounter table should meet the player where they are.
Make Encounter Results Active, Not Final
An encounter result is an opening move. It should not settle the entire scene before you act.
Weak result:
You are captured.
Stronger result:
A blocked exit and approaching voices force a choice: hide, talk, spend a resource, or retreat.
Weak result:
The stranger is evil.
Stronger result:
The stranger offers help, but the offer would expose one secret or cost one favor.
The stronger results preserve agency. They introduce pressure and then return the decision to the player.
This matters in solo play because the table can easily become both author and judge. Keep the table as the prompt. You remain the editor.
Use Different Tables for Different Bands
One universal encounter table is often weaker than two or three small band-specific tables. The all-ages version, gentle version, and tense version can use the same categories with different intensity.
Example category: obstacle.
| Band | Obstacle row |
|---|---|
| All-ages nearby | The path is closed for repairs; take a longer route |
| Gentle | Rain delays the errand and dampens one supply |
| Tense non-graphic | A watched checkpoint blocks the direct route |
| Mature bounded | A hostile authority controls passage; avoid graphic detail |
Example category: danger.
| Band | Danger row |
|---|---|
| All-ages nearby | A loud argument makes the route uncomfortable |
| Gentle | A risky shortcut could cost time or supplies |
| Tense non-graphic | A threat follows at a distance |
| Mature bounded | A serious threat closes in, with one clear exit |
This method lets you keep the structure of the campaign while matching tonight’s band.
Pair Pressure With Exit
The more intense the row, the more important the exit. An exit is not an easy win. It is a visible path back to agency.
Exits can be:
- Spend a resource.
- Take a longer route.
- Ask for help.
- Lose time.
- Mark a clue.
- Close the scene.
- Move the threat off-page.
- Choose a safer interpretation.
If a row has no exit, ask whether it belongs in this table. “Something terrible happens and you can do nothing” may be dramatic, but it is rarely useful as a random encounter. A strong table creates pressure that asks for a choice.
Add Recovery Rows on Purpose
Recovery rows are not filler. They are pacing tools.
Examples:
- A quiet place gives time to update the campaign log.
- Someone offers ordinary kindness without demanding trust.
- A route opens that avoids the current pressure.
- A small resource can be repaired, cleaned, or replaced.
- The scene reveals that one feared outcome did not happen.
- A safe landmark helps you reorient on the map.
These rows are especially useful after intense scenes, failed checks, or long travel. They remind the campaign that not every surprise must tighten the pressure.
Review After Play
After the session, mark rows that worked, rows that felt flat, and rows that pushed too far. Revise the table before next time. You are not building a universal encounter generator. You are building a table for this campaign, this tone, and this player.
Use a quick review mark:
+ worked well
~ usable but bland
! too intense or wrong band
x remove
Review only the rows that actually appeared. You do not need to audit the whole table after every session. If a row pushed too far, rewrite it before playing again. If a row felt flat, make it more actionable. If a row created a great choice, keep its structure and reuse that pattern.
Ask:
- Did the row create a decision?
- Did it respect the content band?
- Was the result easy to interpret?
- Did it add pressure without stealing agency?
- Did the table include enough recovery?
- Did any access friction slow play?
Then adjust one or two rows. Small revisions keep the table alive.
A Finished Bounded Encounter Table
Here is a compact d8 table for a gentle-to-tense travel session:
Content band: tense non-graphic
Lines: no graphic harm, no sexual threat, no real-world hate
Soft spots: isolation, confinement
Visible-room rule: keep notes and imagery all-ages if someone enters
Boundary rule: shift any result to the nearest safe category without penalty
| d8 | Encounter |
|---|---|
| 1 | The direct route is blocked; a slower route remains |
| 2 | Someone needs help with a repair, message, or lost item |
| 3 | A detail points to an open thread in the campaign log |
| 4 | Weather, procedure, or crowds cost extra time |
| 5 | A shortcut appears, but accepting creates a small obligation |
| 6 | A misunderstanding must be repaired before progress continues |
| 7 | A quiet place offers rest, supply sorting, or a log update |
| 8 | A threat appears at a distance; choose prepare, avoid, or approach |
This table can still surprise the player. It can still create trouble. But every row has a playable shape, and the boundary rule is present before the die rolls.
That is the aim: not less play, but more trustworthy play.
