How to Give a Companion NPC a Useful Role Without Letting Them Solve the Adventure

Write down the adventure’s central problem in one sentence, then name the decisions the players should make to address it. The companion’s role should support those decisions, not make them. For example, if the party must find who is diverting supplies and decide how to stop it, a traveling quartermaster could know which roads carry shipments and recognize a supplier’s mark. The quartermaster should not identify the culprit, select the party’s next move, and carry out the solution.

This boundary follows a useful distinction in scenario design: supporting characters can provide testimony and interact with the party, while the story proceeds through the players’ characters’ actions. GUMSHOE’s scenario guidance also cautions against structuring events so that supporting characters drive the story while players observe. GUMSHOE SRD: Rules

Choose a contribution that fills a specific gap. Useful roles include translating a language the party cannot read, navigating a familiar district, carrying a fragile object, recognizing a local custom, or offering a second perspective on a clue. Prefer a contribution that creates options or reduces friction over one that replaces a challenge the party came to face.

Use a simple sentence to describe the role: “Mara can identify old canal markers, but she cannot read the smugglers’ code.” The first half tells you when to make the companion helpful; the second marks a limit that preserves space for player investigation. A companion may have other personality traits, but avoid giving them several unrelated skills that make them the obvious answer to every obstacle.

A limit works best when it comes from the companion’s knowledge, resources, priorities, or circumstances. A guide might know the north bank but not the abandoned tunnels. A cartographer might explain what an old map depicts but lack the current information needed to choose a safe passage. A witness might offer a clear memory of one event and still be unsure what it means.

Decide what the NPC is willing to risk, too. Helping can cost time, supplies, reputation, or safety; the cost should fit the relationship and the situation. An adventure-design discussion of supporting NPCs recommends grounding their assistance in motivation and in what they are prepared to sacrifice, rather than treating support as unlimited. Gnome Stew: “Adventure Design: Supporting and Opposing NPCs”

Avoid limits that exist only to force a prepared scene. If a companion suddenly forgets a plainly established skill whenever the players ask for help, the boundary feels arbitrary. State the limit early, keep it consistent, and let the party’s choices determine whether the companion can contribute within it.

If the adventure depends on information, make sure the party has a fair route to it that does not rely on the companion being present or making the right deduction. Place essential information in more than one plausible location or make it discoverable through different approaches. The companion can point toward a lead, confirm a detail, or supply context; the players should still decide what the information means and what to do next.

GUMSHOE’s published guidance makes a related point for investigative scenarios: core clues should not depend on one obscure ability or one rigid sequence, and plausible alternate approaches should be allowed to yield the information. That advice supports a practical check for companion design: if the NPC is removed from the scene, can the players still find the essential clue and continue? GUMSHOE SRD: Rules

For a nonessential clue, the companion can add color or a useful lead without resolving the main question. For an essential clue, make the companion one possible route among several—not the only person who can deliver it.

A companion becomes more interesting when their useful contribution comes with a choice. The guide may know two routes: one quick and exposed, one slow but discreet. The quartermaster may recognize a mark but need the party to decide whether to approach its supplier openly or investigate first. These examples are design illustrations, not rules; their purpose is to show how expertise can open a decision rather than close it.

Give the NPC a motive that shapes how they offer help. They might want to protect a neighbor, recover a deposit, or avoid attracting attention. Their goal can align with the party’s in one scene and diverge in another. Supporting characters need a reason to assist and a degree of support tied to their capabilities and motivations, as Gnome Stew’s adventure-design article discusses. That gives the GM a practical basis for what the companion volunteers, withholds, or declines.

Before play, ask three quick questions: Does the companion act before the players have a chance to respond? Do they regularly succeed at the challenge the party is facing? Do scenes pause so the GM can explain what the companion thinks? If the answer is often yes, narrow their contribution or shorten their turns.

During play, let the companion answer a direct question, offer one relevant observation when the party stalls, and then hand the decision back to the players. In a rules-heavy scene, keep the companion’s mechanics modest and quick to resolve; follow the game’s existing rules for allies rather than giving the NPC an extra turn or special authority by default. The right level of mechanical detail depends on the system and the companion’s actual role.

Before introducing the NPC, complete these prompts in your notes:

• Useful at: one concrete task that helps the party act.
• Doesn’t know: one important boundary on their knowledge or skill.
• Wants: one personal goal that explains their involvement.
• Will risk: a specific cost they are willing to bear.
• Players still decide: the central choice the companion will leave to the party.
• If absent: another way for the players to reach any essential clue or scene.

Test the answers against the adventure. If the companion can identify the threat, find the route, choose the plan, and defeat the obstacle, reduce their scope until their help creates a meaningful next move for the players. A useful companion contributes something the party values, has a credible reason to contribute it, and leaves the adventure’s decisive choices in the players’ hands.

• GUMSHOE SRD: Rules — scenario structure, clues, player-driven progression, and supporting characters.
• Gnome Stew: “Adventure Design: Supporting and Opposing NPCs” — NPC motivations, limits on support, and what a supporting NPC is willing to risk.