A D&D faction tracker for continuity: what they want, what the party did, and where they stand
An NPC card holds one person. A faction's stance toward the party is a different kind of fact: it is a consequence of what the party did, it changes between sessions, it is carried by several members at once, and it needs a standing line the NPC card has no room for. This is one card to copy, a filled-in example, and a rule for keeping the standing honest.
· 10 min read
What a D&D faction tracker is for, and why a score is not enough
Most D&D faction trackers come down to one number: a reputation score that goes up when the party helps and down when they hurt. A number is easy to keep and easy to read, and it answers the only question a score can answer, which is whether they are friendly. It does not answer the question that actually comes up at the table, which is why. A company that is hostile because the party sank its skiff opens the next scene very differently from one that is hostile because the party was seen with the harbormaster, and the score is the same in both cases.
The official sheets show the gap. D&D Beyond's free Tracking Sheets page has no faction sheet at all; the nearest thing on it is Campaign Conflicts, which is three numbered "Adventurers vs. ____" blocks with blank note lines beneath each — the sheet and what it records are in the table at the end of this guide. It is a place to write down that a conflict exists. There is no line for what the party did, none for when, and none for where things stand now, so the moment the conflict moves, the sheet is a title over a paragraph you have to reread.
That missing line is what this template adds. It treats a faction's standing the way a ledger treats a balance: the entries are what each side did and when, and the standing is the one-word summary at the bottom that you work out again from them. Keep a score as well if you like one. It just stops being the record.
The DM's faction tracker template (copy this)
One card per faction that matters, in plain text, so it pastes into the same notes app, shared doc or spreadsheet cell the NPC cards already live in. The shape is deliberate: the two middle blocks are a ledger with a session number on every line, and STANDING NOW is the only line you are ever allowed to overwrite.
Fill it in one sitting, straight after the session the faction first mattered in. FACTION is the name the party uses, not the formal one. WHAT THEY WANT is one sentence written as an outcome in the world — the harbour chain left down, the mine reopened — rather than a motive, because an outcome tells you what they will do about the party. WHO SPEAKS FOR THEM is whoever the party actually talks to, with a note on whether that person decides anything; everything else about that person belongs on their own NPC card. The two ledgers get one line per session the faction was touched, written as acts rather than opinions: what the party did, then what the faction did back. STANDING NOW is one word and a because, with the session that settled it. WHAT THEY KNOW ABOUT THE PARTY is the line that stops a faction acting on something it never learned, so write what they know and, under it, the one thing they must not. NEXT MOVE is what the faction does next if the party does nothing — the line you read before the session.
Faction tracker card (copy this)
FACTION TRACKER FACTION: ______________________________________ (the name the party uses for them) WHAT THEY WANT: _______________________________ (an outcome in the world, one line) WHO SPEAKS FOR THEM: __________________________ decides? yes / no NPC card: _____________ WHAT THE PARTY DID TO THEM (one act per line) session ___: ________________________________ session ___: ________________________________ session ___: ________________________________ WHAT THEY DID BACK session ___: ________________________________ session ___: ________________________________ session ___: ________________________________ STANDING NOW: hostile / wary / neutral / warm / allied because: _______________________ (session ___) WHAT THEY KNOW ABOUT THE PARTY: _______________ and do not know: _____________________________ NEXT MOVE (if the party does nothing): ____________________________________________
A filled-in example: one faction, three sessions in
Here is the card for a smugglers' company the party has crossed three times. A faction never walks into a scene as itself; it arrives as a captain, a tavern and a lookout, which is why WHO SPEAKS FOR THEM carries more weight on this card than a name does on an NPC card.
Notice what the two ledgers do that a score could not. The standing is wary, and the because line says it was the harbormaster, not the skiff, that put it there — which tells you exactly how Vane opens the next conversation. The do-not-know line is what keeps the Lantern from acting on a manifest only the party has seen. And NEXT MOVE is prep already done: it is the scene you walk into next session with, written before you forgot why.
Example card (delete it, keep the shape)
FACTION TRACKER
FACTION: the Hollow Lantern ("the Lantern")
WHAT THEY WANT: the harbour chain left down on moonless
nights, and nobody asking what comes in on them
WHO SPEAKS FOR THEM: Captain Idris Vane
decides? no - "Mother Quill" does, and the party has
never met her NPC card: Vane
WHAT THE PARTY DID TO THEM
session 4: sank the Lantern skiff at the breakwater
(took it for pirates)
session 7: returned the crates they pulled out of it,
unopened, and refused payment
session 11: met the harbormaster, in daylight, on the
Lantern's own quay
WHAT THEY DID BACK
session 5: Vane's crew warned them off the docks -
no blood
session 8: Vane paid their tab at the Drowned Lamp and
asked for nothing
session 11: nothing yet - the lookout reported it
STANDING NOW: wary
because: a skiff is forgivable, the harbormaster is
not (session 11)
WHAT THEY KNOW ABOUT THE PARTY: they can fight, they
keep their word, they talk to the harbormaster
and do not know: the party has the second manifest
NEXT MOVE (if the party does nothing): Vane asks them
to carry one crate upriver, no questions - a testWhen a faction earns a card
Not every banner in the setting gets one. A tracker with a card for every guild you named in a rumour table is a tracker you stop opening, and most factions never touch the party at all. Use a promotion rule instead of good intentions.
- During play, write the faction's name and the act, nothing more — "Lantern: sank their skiff" — in the same place you write a new NPC's name. The ledger line can be rebuilt after the game from that; the fact that it happened cannot.
- After the session, give a card to any faction the party has acted against or for twice, any faction that has acted on the party at all, and any faction that now knows something about them. One rumour and one sighting is not a card; it is a line on the campaign sheet.
- A faction with one member the party deals with is usually an NPC card, not a faction card, until the party does something the organisation rather than the person has to answer for. Sinking a skiff is answered by the company that owned it.
- When a faction is destroyed, absorbed or made irrelevant, close the card and keep it. Its members are still alive, its debts transfer, and a player will remember exactly which guild they burned.
Keeping the standing line honest
STANDING NOW is one word, and it is re-earned every session the faction appears in. That is the rule that keeps the line honest: you do not adjust it, you work it out again. Read the two ledgers, ask what this faction would do if the party walked in tonight, and write the word that answers. If the word has not changed, leave it, but write the session number anyway so you know it was checked.
The reason for the discipline is that standing drifts in the DM's head faster than it does in the world. Three sessions of the party being charming to a captain feel like a thaw, and the ledger says the company is still a skiff and a harbormaster down. What the party did is the record; the standing is the summary. When they disagree, the record wins, and the because line is where you write down why you were tempted.
Keep the vocabulary small and fixed — hostile, wary, neutral, warm, allied, or your own five — so that two cards written months apart mean the same thing. "Complicated" is not a standing; it is a sign that the because line needs another sentence. And resist writing a number next to the word. The instant there is a number, the number becomes the thing you update and the ledger becomes the thing you forget.
Where the cards live: beside the NPCs, on the campaign sheet, or in a wiki
The card is app-agnostic on purpose. The right home is the one you will open on a Tuesday night, and it is usually the one the NPC cards are already in. Three shapes work, and nothing stops you using two at once.
- Beside the NPC cards. The NPC tracker template is built on the same lines — session numbers, a because, a log you append to — so a faction card filed next to Vane's card reads the same way. Put the faction's name on the NPC card's one-line WHO, and the NPC's name on the faction card's WHO SPEAKS FOR THEM, and the two find each other.
- On the campaign sheet. The campaign notes sheet carries one line per faction — name, stance, what changed — and that is the roster. This card is what a line gets promoted to when it starts needing a ledger. Keep the one-liners there and the cards elsewhere, or the sheet stops fitting on a page.
- In a wiki, one page per faction. Each ledger becomes a section, the standing goes in the first line, and the members link to their own pages. How to make a campaign wiki covers the structure, including the part that matters here: a faction page is the one place a wiki beats a card, because the members, the places and the acts already have pages to link to.
What players can see, and what stays behind the screen
Players keep faction notes too, usually worse ones, and a table that disagrees about whether the Lantern is a friend is a table about to make a decision the DM has to walk back. Showing them part of the card fixes that, and it costs nothing you did not already say aloud.
Three lines are theirs by right: WHAT THE PARTY DID TO THEM (they were there), WHAT THEY DID BACK (they were there for that too), and the standing word, if a character in the party could plausibly read it. Read those three aloud at the start of a session the faction will matter in, or paste them into the group channel. The player note-taking guide has the matching shape from the other side of the screen — who they are to us, what we owe, what we have not told them — and a shared copy of those three lines is the cheapest way to get the party's notes and yours to agree.
Everything else stays behind the screen. WHAT THEY WANT is a secret until the faction acts on it. WHO SPEAKS FOR THEM is public; who decides is not. WHAT THEY KNOW ABOUT THE PARTY and the do-not-know line are the whole game, and NEXT MOVE is next session. The because line is yours as well: the party should feel the standing, not read the reasoning.
If you record your sessions: the version that fills itself in
If your table records its sessions, the two ledgers mostly already exist — they are just spread across four hours of audio, under whatever the party called the faction at the time. A transcript makes an act findable: a search for Lantern returns the session where the skiff went down and the one where the crates went back, and the ledger lines become quotes you can check rather than lines you had to remember to write.
Tools built for tabletop go a step further. DM Scribe, which publishes this guide, extracts the factions a session mentioned into the campaign wiki as entries filed under organisations, each with an Appearances list that shows the session and a snippet of how the faction came up — which is the first ledger, in draft, with the session numbers already filled in. On the Dungeon Master plan and above, the relationship map draws the connections the transcript supports, faction to faction and person to faction, so WHO SPEAKS FOR THEM and which companies are feuding come out of the sessions rather than out of your memory. The map is not on the free plan.
Be clear about what it cannot fill. The map shows connections, not a standing: it can tell you that Vane and the Lantern are linked and that the party has dealings with both, and it has no line for wary or for why. The transcripts carry no speaker labels, so a quote tells you what was said rather than who said it. WHAT THEY WANT, the do-not-know line and NEXT MOVE were never spoken aloud, so they are on no recording. Those stay on the card. The free Adventurer plan's 2.5 hours of transcription a month plus 3 one-time bonus hours cover one full session, with no credit card to start, which is enough to see what comes back before deciding whether the ledger is worth a recording.
The official tracking sheets, from D&D Beyond
Every third-party figure quoted above, with where it came from and when it was checked. Prices move — if a date here is old, verify before relying on it.
| What | Value | Source |
|---|---|---|
| Where the official sheets live | Nine downloadable PDF sheets on the Tracking Sheets page of D&D Beyond's free Basic Rules — Game Expectations, Travel Planner, NPC Tracker, Settlement Tracker, Campaign Journal, DM's Character Tracker, Campaign Conflicts, Magic Item Tracker and Bastion Tracker. None is a faction tracker; the nearest is Campaign Conflicts | sourceas of 2026-10-23 |
| What the Campaign Conflicts sheet records | Three numbered conflicts, each headed "Adventurers vs. ____" with blank note lines beneath; no field for standing, for what changed, or for the session it changed in | sourceas of 2026-10-23 |
| Copying the official sheet | "TM & © 2024 Wizards of the Coast LLC. Permission is granted to photocopy this page for personal use." (printed at the foot of the Campaign Conflicts sheet) | sourceas of 2026-10-23 |
How we sourced this: The first row was read from D&D Beyond's Tracking Sheets page; the sheet's contents and the photocopy permission were read from the Campaign Conflicts PDF that page links to, hosted on D&D Beyond's own media domain, on the date shown. The page does not say which rulebook the sheets come from, so this guide does not either.
Related guides
- How to make a D&D campaign wiki your table will actually use
What a D&D campaign wiki needs, four ways to build one — World Anvil, Kanka, Obsidian or your recordings — and why most go stale. Which fits your table?
- How to record your D&D session — in person or online — so the audio is actually usable
Where to put the mic at a real table, how to record Discord and Zoom games, cheap gear that helps, and what good enough session audio actually means.
- How to Take Notes During a D&D Session Without Wrecking the Game
You cannot run the game and write it down at once. What earns one line mid-session, what can wait until after, and who takes the notes when nobody will?