Framework

How do I handle players asking an NPC to "tell us everything you know"?

Treat 'tell us everything you know' as a request for the witness's best relevant summary, not an exhaustive transcript of memory. Resolve the scope first—everything about the burglary, the victim, or last night—then give the account, including what the witness recalls, believes, and remains unsure about. Follow the game's clue procedure, but keep investigation moving through a reliable route that does not depend on one exact phrase or fragile check. Targeted questions can clarify prepared or fictionally supported details, uncertainty, and sources without creating new evidence through repetition.

A Game Master describes a witness recounting a crime scene to investigators seated around a tavern table

Why ‘tell us everything’ still produces a summary

People do say ‘tell us everything you know’ in-world. The phrase is a natural request for a useful account, not a literal demand for every memory. The NPC answers what they reasonably think is being asked, using the scope established by the conversation. If that scope is unclear, they can briefly ask, ‘About the break-in, or everything that’s happened here this week?’

Resolve the scope first, then give the witness's best relevant summary. They do not know what the party is investigating or which details count as evidence, and their recollections may be incomplete or mistaken. Do not withhold a useful account because the players phrased the request broadly, or recite every note from the scenario in one monologue. Follow-up questions can focus attention on prepared or fictionally supported details the witness had not thought relevant, clarify uncertainty, or distinguish direct observation from inference; asking repeatedly does not create new evidence.

Resolve the scope, then give a useful account

The implied subject usually makes a broad request clear: everything about the burglary, the victim, last night, or a particular symbol. Once the scope is clear, give the witness's useful account in layers:

Initial broad summary What the witness thinks happened, the relevant observations and recollections they can readily bring to mind, and one or more leads that keep the investigation moving. Mark confidence naturally: “I saw…”, “I think…”, “I heard from…”, or “I'm not sure, but…”. A sincere witness can misremember timing, sequence, or identity without lying.
Targeted depth Follow-ups clarify uncertainty, sensory detail, source, relationships, contradictions, or context the witness did not initially think relevant. Keep those details consistent with where the witness was, what they could perceive, what had their attention, and what is already established.
External corroboration Records, physical evidence, another witness, or specialist interpretation can support, challenge, or add context to the account. The witness's recollection is evidence about what they remember, not automatically an objective record of events.

How targeted questions reveal depth

Specific follow-ups should focus the witness on details supported by the fiction, add context and clarity, or offer another angle—not serve as a mandatory password or generate facts through repetition:

Jogging sensory memory Asking what a witness heard, smelled, or felt can focus them on a prepared detail they dismissed as irrelevant, if the circumstances support it. They might recall lamp oil on a visitor's coat or the clank of a distinctive machine nearby.
Testing timing and sequence Asking what happened immediately before or after an event can help the witness place a recollection against daily habits and identify uncertainty, hurried departures, or unexpected pauses. It may also show that their remembered sequence is mistaken.
Probing deviations from routine Asking whether something was ordinary for this location reveals subtle anomalies: an unfamiliar delivery wagon, a lamp left unlit, or a guard absent from their post.
Surfacing personal relationships Asking who the victim spent time with or who stood to lose money shifts the conversation from passive observation to local politics, alliances, and grudges.
Asking how they know “How do you know that?” separates direct observation from inference, routine expectation, hearsay, or knowledge acquired afterwards. The witness may be certain, tentative, or mistaken; let the players hear which kind of account they are weighing.

Filtering testimony through NPC perspective

Profession, current task, training, relationships, and personal stakes all shape what an NPC was likely to notice. Treat these as attention tendencies, not rules for what a person must perceive:

The night watchman May be especially alert to access points, weapons, and unfamiliar movement because those are part of the job. An individual witness may notice something entirely different because of where their attention was at that moment.
The house servant May know household routines, regular visitors, and when something has been moved, while another servant in the same house might be focused on a particular person or task.
The dock clerk May pay close attention to cargo marks, manifests, and schedules, especially when checking an arrival, but may miss activity outside that task.
The street vendor May recognise regular customers, changes in foot traffic, or unusual loitering, depending on the stall, the day's trade, and what had their attention.

Avoiding conversational pixel-hunting

Conversational pixel-hunting happens when a Game Master decides that an essential clue will only be revealed if players ask a single exact question or utter a specific keyword. If the players ask about the victim's visitors, the GM stays silent about the delivery courier because a courier is technically not a visitor. This turns investigative roleplay into an adversarial guessing game where players feel punished for failing to read the GM's mind.

Keep player skill focused on interpreting accounts, recognising contradictions, and deciding which leads to pursue. When players ask an open question, answer generously within the understood scope. If they ask about a nearby detail, share it when the witness could reasonably know or recall it; do not withhold it on a technicality or invent it because they repeated a question.

Example

Worked example: The burgled apothecary

Master Vane, a nervous herbalist in a river ward, has had his storehouse ransacked. The party arrives to investigate and immediately asks him to tell them everything he knows.

The weak approach: The GM treats 'tell us everything' as an invalid prompt. Vane stammers that he does not know where to start. When players ask about intruders, the GM withholds the smashed skylight because the players asked who came through the door, forcing four rounds of guessing before the party discovers how the thief entered.
The framework approach: The GM clarifies, “Everything about the break-in?” Vane gives his best account: he found the rear storeroom trashed at dawn, two jars of dried ghostleaf missing, and his apprentice nowhere to be found. He thinks the apprentice left before closing, but admits he did not see them go. The party has leads without a roll or magic words. Asked, “How do you know the apprentice left early?”, Vane explains that a neighbouring shopkeeper told him. The GM has prepared the brief midnight doorbell and the smell of wet rope by the back steps; when the party asks about the night before, Vane can place them in the account as uncertain details that point toward the river docks.
Why it works: The broad summary gives the party actionable leads, and the follow-up clarifies where Vane's knowledge came from before adding supported detail. The investigation has a reliable route forward without making every secondary clue automatic or every uncertainty a hidden test.

Checklist: Running broad witness questions

Keep these checks in mind whenever players ask an NPC to tell them everything they know:

Resolve what the request is about, briefly clarifying in character if its scope is unclear.
Give the witness's useful summary, including relevant recollections, confidence, and one or more leads.
Follow the game's clue procedure, with a reliable route to progress that does not depend on one exact phrase or fragile check.
Use targeted questions to clarify prepared or fictionally supported detail, source, uncertainty, and inference.
Account for the witness's task, training, relationships, and attention without treating role as destiny.
When the witness has given their useful account and more questions would only repeat material, say so plainly. Remind the table of the leads already available, then let the players choose what to pursue.

Know when the interview is done

For example: “You think Vane has told you everything relevant he can currently recall about last night. The missing apprentice, rear storeroom, and river smell are your clearest leads.” This signals that further questions would repeat the account while leaving the next move to the players.

Was this useful?

Systems built for this

GUMSHOE
Investigative abilities ensure that any character with a relevant skill automatically gains the core clue without a roll, while point spends provide extra nuance, context, or tactical edges.
Monster of the Week
The Investigate a Mystery move resolves questioning through a structured list of targeted questions, giving players clear inquiry angles rather than requiring them to guess the Keeper's thoughts.
Brindlewood Bay
The Meddling Move provides open-ended clues that players combine through the Theorise Move, removing the need for the GM to withhold testimony until a specific keyword is spoken.

Organise witness accounts on the campaign graph

When multiple NPCs give overlapping or conflicting testimony, keeping track of who said what can quickly overwhelm session notes. Codex Cryptica lets you link witness statements directly to NPC profiles, locations, and discovered clues in an interconnected knowledge graph.

By separating direct observations from witness interpretations in entity notes, you can easily spot discrepancies and trace follow-up leads as your investigation unfolds.

Explore the campaign knowledge graph