Build a rumour table as a clue-delivery tool: each entry should raise a question and point towards a person, place or event the characters can investigate. Mix accurate, incomplete and false information, record what each rumour can lead to, then share it through people the party meets. Update entries as the campaign changes.
Key facts
- A rumour is unverified information circulating among people, especially without solid evidence. [F1]
- A simple rumour table can offer plot hooks that encourage players to take action. [F14, F16]
- One guide recommends making rumours from a whole truth by leaving details out, exaggerating or lying. [F19]
- A useful rumour creates a question, points towards a person or place, and leaves uncertainty for the group to judge. [F48]
Rumour tables turn loose talk into playable clues
A rumour is not the same as a confirmed fact: it is information in circulation without solid evidence. [F1] That uncertainty makes it useful in a fantasy campaign. Players can decide whether a claim sounds convincing, seek another source or act before they know the whole story. Give them something to investigate, not an answer that ends the discussion.
A rumour table can provide several possible directions when characters reach a settlement or speak with local people. One campaign account describes using a table to offer several plot hooks and give a sandbox immediate direction. [F10] Treat each entry as an invitation rather than an instruction: the party can follow it, question it, ignore it or turn it into a new plan.
Make each entry do practical work at the table. A useful design puts the rumour alongside what it is true about and how it can be used in play. [F30] The use column helps you check that an intriguing line leads somewhere: a person to approach, a place to inspect, a choice to make or a clue to compare. Without that purpose, entries can sound interesting but fail to prompt action. [F33]
Build a mix of accurate and misleading claims
Write the underlying truth before you draft what people say about it. Then decide how each speaker might know that truth, misunderstand it or choose to distort it. A guide describes turning a whole truth into rumours through omission, exaggeration and lies. [F19] This gives you a consistent reference point while letting accounts differ.
Use true entries to reward characters who investigate, partial entries to make interpretation matter, and false entries to test judgement. The mix should serve the campaign rather than punish curiosity. A false claim can still reveal what someone fears or wants, while a partly accurate one can point to a real lead through mistaken details. Keep the distinction clear in your notes, even when characters cannot know it yet.
Do not let every rumour sound like a complete, polished clue. A rumour table becomes more believable when its entries are not all perfectly accurate. [F44] Let some claims trail off, conflict with another account or leave the cause uncertain. Give players enough to form a question, but preserve room for them to weigh the risk of finding out.
Attach each rumour to a source and a possible lead. When possible, connect it to a place the players can visit, an NPC they can question or an event they can observe. [F46] That link turns gossip into something the group can test, rather than a piece of background detail they have no way to act upon.
Deliver and update rumours as the campaign moves
Put rumours in conversations, overheard talk or other moments that fit the scene. A rumour table can help common people take part in the campaign. [F32] Give a speaker a reason to share what they know: they may want help, want to warn someone or simply be passing on talk. Keep the source attached to the claim in your notes so characters can decide how much to trust it.
A roll can help when you need a prompt quickly. One approach has each player roll a d20 and receive a rumour of their own. [F17] Another suggests rolling a d20 to get a rumour or clue to roleplay or share. [F18] Use a roll to select material, not to override the scene or the group’s choices.
Keep the table responsive. A static table may serve for one visit, while a living campaign can benefit from updates. [F28] Once the party investigates, change the status of entries: a claim might be confirmed, disproved or made more complicated. You can also bring back an existing rumour with changed circumstances; repetition with variation is one suggested technique. [F35]
Leave room for discussion and a decision. Research on rumour describes a pattern in which a claim is introduced, discussed, and eventually resolved or dropped when interest fades. [F3] At the table, you can use that shape without forcing a conclusion: let the players choose what to pursue, then make the result matter to the information available later.
What this means for you?
For a sandbox GM, a rumour table is a compact way to prepare leads without deciding which one the party must follow. The entries can suggest activity beyond the characters’ immediate view, while their choices determine what becomes important. A rumour should prompt a decision: investigate, ask around, wait for better evidence or accept a risk.
If you are a GM preparing a market scene, write one claim about a nearby landmark and give it a source the party can approach. Decide privately whether the claim is accurate, incomplete or false. Add what following it could reveal, then let the players choose whether to pursue it. This gives you a usable next scene without forcing the group to take a particular route.
Keep the player-facing claim short and your preparation useful. Record the underlying truth, the source, the lead and what changes if the characters act. That way, a rumour can be wrong without becoming wasted preparation: the speaker’s motive or the characters’ reaction may still shape the scene. Avoid turning every line into a puzzle with one hidden answer. The group should be able to form its own judgement.
What to do now?
- Choose one situation the characters can investigate, then write its underlying truth in plain language.
- Draft a d10 table: make five entries true, three partial and two false. These proportions are a practical template, not a rule.
- For every entry, note the truth behind the claim and what action it might prompt.
- Give each rumour a source NPC and a location tie, such as someone to question or somewhere to visit.
- Check that every line creates a question or choice. Cut entries that offer only flavour and no possible next move.
- Share rumours when they fit the scene, and let the party decide which claims deserve attention.
- After the party acts, update the status of affected entries. Keep what is unresolved available, and change what the characters have learned.
Sources
- en.wikipedia.org/wiki/Rumour
- www.roleplayingtips.com/adventure-building-campaigns/power-your-plots-with-simple-rumour-tables
- www.roleplayingtips.com/adventure-building-campaigns/how-to-create-wicked-rumour-tables
- koboldrest.com/ttrpg-rumor-table-adventure-hooks
- www.sessionroll.com/blog/dnd-rumors-table
- coffeelock.com/2026/01/01/better-rumor-tables-how-to-make-them-pay-off
About this page
Written with AI assistance from the sources listed above, then checked by automated fact, source, repetition and quality checks before publishing.
Facts and links checked on 31 October 2026. Summarises the sources linked above; check the linked source for the latest version.
How we researched this: we compiled this guide from the official and independent sources listed above, and checked the facts on the date shown. Our editorial policy explains how we choose and check sources.