The modern TTRPG GM runs their campaign from a stack of disconnected tools: Discord for group chat, a Google Sheet for initiative and player details, a when2meet link for scheduling, a Notion doc for lore notes, and a private DM thread for each player. Every tool does its one job adequately. None of them talk to each other. And the GM is the manual integration layer holding the whole system together.
This is not a sustainable way to run a campaign that's supposed to last two years. It's especially not sustainable for GMs who are running more than one campaign at a time — which, as any experienced GM can tell you, is most of them.
The Limits of Chat as Campaign Management
Discord's strengths are its weaknesses in the campaign context. It's fast, it's informal, it's low-friction. That's great for a gaming community. It's a problem for structured campaign management, where you need permanence, searchability, and structured data rather than chat logs.
Consider what a GM actually needs to manage a living campaign. They need to know who is currently on the roster, when each player last attended, what characters those players are running, and what each player's history looks like across previous campaigns. They need to be able to send a message to the whole party at once and track who has read and responded. They need a session log that persists even when members leave and join. They need a scheduling tool that accounts for everyone's availability, not just whoever responds to the when2meet link.
None of this is unreasonable. All of it is routine for any recurring event with six participants. And none of it is well-served by a chat application, no matter how many bots you install. Chat is ephemeral by design. Campaign management is persistent by necessity.
What Real Infrastructure Looks Like
The shift from Discord-as-campaign-tool to purpose-built campaign infrastructure isn't about abandoning Discord entirely — it's about right-sizing each tool for the job it's actually good at. Discord is excellent for between-session banter, game-adjacent discussion, and the social fabric of a gaming community. It's not a database. It's not a scheduling system. It's not an accountability tool.
- A structured roster that shows each player's history, ratings from previous GMs, attendance record, and current character — visible at a glance without scrolling through a hundred chat messages.
- Persistent session logs that survive members leaving and joining, that are searchable, and that connect to each session's attendance record so you can see at a glance who was at which session and when they started drifting.
- Broadcast messaging that sends a single message to every active player and tracks who has read it — so "did everyone see the reschedule message?" is answered by data, not by who happens to be online when you ask.
The availability matching problem alone is worth solving with a real tool. When2meet works for one-off events. For a campaign that needs to recur every two weeks for eighteen months, you want to know about conflicts before they become no-shows — which means you need a system that tracks each player's standing availability and flags when a proposed session date conflicts with the majority of the table.
Making the Switch
The resistance most GMs feel toward adopting campaign management software is understandable. Learning a new tool has a cost. Migrating an existing group has friction. And the current setup, however cobbled-together, is at least familiar.
The way to think about it is in terms of the campaign you want to run, not the campaign you're currently limping through. If the goal is a campaign that runs for two years with a stable cast of committed players, you need the infrastructure to support it from the start. The spreadsheet and the Discord server will hold for the first six sessions. After that, the seams start to show.
Start with the roster and the session log. Those two tools, purpose-built for campaign management rather than repurposed from another context, will immediately reduce the administrative overhead you're carrying as a GM. The scheduling and the messaging come next. By the time you're running a campaign that's hitting its one-year mark, the infrastructure will feel less like overhead and more like the thing that's keeping the campaign alive.