How to keep NPC notes you can actually run from
A page of backstory is useless at the table; a single line you can read at a glance is gold. Here is the format that survives contact with real play.
The short answer
An NPC you can run needs four things and no more: a voice you can perform, a want that drives them, a secret that creates tension, and the ties that connect them to the story. Write those on one line each. Save the two-page history for the three NPCs whose history actually matters.
The four-line NPC
- Voice. One handle you can grab instantly — "clips her consonants, never finishes a sentence," or "too friendly, laughs at his own threats." Voice is what makes an NPC feel like a person the second they open their mouth.
- Want. What they are trying to get, right now. A want gives you their every line for free: everything they say bends toward it.
- Secret. Something true they will not volunteer. The secret is the engine of the scene — the reason there is anything to play out instead of a straight answer.
- Ties. Who and what they are connected to — the faction they serve, the player character they knew, the place they will not go. Ties are how a walk-on NPC becomes recurring.
Write it forward, not backward
Most NPC notes are written backward — from birth to now — and none of it is playable. Write forward from the table instead: the first thing the players will notice, the first thing the NPC will say, the thing they will do if the scene turns against them. If a detail does not change how you play the NPC in the next ten minutes, it is trivia, not a note.
A worked example
Verrin, harbor clerk. Voice: whispers, glances at the door mid-sentence. Want: to be transferred inland, away from the water. Secret: he has been forging the departure logs for a price. Ties: reports to the harbormaster, owes money to the buyer the party is hunting, grew up with the fighter’s late brother. Four lines, and Verrin can carry an entire session — he is frightened, purchasable, and already connected to two threads you did not have to invent.
When an NPC recurs, add a fifth line: what changed since the party last met them. That single line is what makes a returning NPC feel like the world kept turning while the players were away.
Questions GMs actually ask
What is the best way to organize NPC notes for a campaign?
Keep each NPC to a few playable lines — voice, want, secret, and ties — and link them to the sessions and places they appear in. Long biographies read well and run badly; the goal is a note you can glance at mid-scene, not an encyclopedia entry.
How much backstory does an NPC need?
Almost none for most of them. A want and a secret give you everything you need to improvise a scene. Reserve real backstory for the handful of NPCs whose history is going to become a plot the players engage with.
How do I make recurring NPCs feel alive?
Track what changed since the party last met them. A single "since last time" line — a promotion, a grudge, a new fear — makes a returning NPC feel like the world moved while the players were elsewhere.
Where Storywright fits
In Storywright every NPC is an entity you can link to the sessions, places, and factions they touch, so "who is Verrin again?" is one click, not ten minutes of scrolling. GM-only details — the secret, the forged logs — stay GM-only by default, while what the players have actually learned is theirs to see. Write the NPC once, link it as you go, and the web builds itself. Free to start; players free forever.