I still remember playing my friend's first D&D campaign. A hand-drawn map, filed with vibrant cities, populated with citizens of a dozen different species each with their own political hierarchies and rich histories. Even the humans in this world were varied; some reliant on the orderly sects controlling the magic of the world while others invested deeply in otherworldly technology.
That first session was great and everyone had fun, but the next game wasn't for six weeks. We made it less than five sessions before the group fell apart.
Here's the trap my friend fell into: You open a blank document and start inventing kingdoms, trade routes and a rich history of events spanning four hundred years. It feels productive. It is, in fact, the most enjoyable way to never run a game.
This experience put me off becoming a DM for years; running a game seemed like a full time job. If my very creative friend couldn't manage to put regular sessions together what hope did I have?
So this is the guide I wish someone had handed me years ago.
1. Start with the Premise
Players do not need to start out with a full world, dozens of cities they may never visit, and hundreds of fully written out NPCs they may never meet. D&D is a game about having adventures, slaying the dragon and saving the local town so your players are not going to respond well to a mini novel.
What players will respond to is a premise: a single sentence containing a place, a threat and a reason to care.
Some examples of what I mean:
-
A mining town is slowly sinking into the earth, and something down there is pulling it.
-
The king has been dead for a year, and only the party knows.
-
Every child born this winter carries the same birthmark, and the church has started buying babies.
Each of those makes you ask a question. What's pulling the town down? Who's ruling in the dead king's name? Why does the church want those children? If your premise makes someone lean in and ask a question, you have a campaign. If it makes them nod politely, you have a setting, and settings don't run sessions.
A good test: can you say it in one breath, and does it suggest what the players actually do? "An ancient evil stirs" fails that test. "The harvest god stopped answering prayers three weeks before winter" passes it, because the obvious move is to go find out why, and fast.
My most recent campaign was based in the town of Rhinehaven. A once prosperous mining town which had turned into a ghost town and no-one knew exactly why. Only when prospective players were already hooked did I supply the varied theories of the townsfolk: an ancient evil stirring in the mines; a powerful wizard lost control of a spell; a corrupt mayor. As for their reason to care? I left that to the players and their characters backstory, be it a missing family member; a religious pilgrimage or simply a desire to claim the towns former riches for themselves.
When newer DMs ask me how to make a D&D campaign feel alive, they expect an answer about world building. My honest answer is much more boring: make the first town alive and ignore everything past the horizon. Give me one village with a nosy innkeeper, a feud between two farming families, and a road heading somewhere ominous, and I'll take that over a continent of dead lore every single time. You can invent the rest of the world later, when your players actually walk toward it.
2. Build Your Villain's Plan First
This is the single highest-value trick I know, so I'm putting it near the top. Before you write a single dungeon, write your villain's to-do list. Not their backstory, not their tragic childhood. Their plan. What are they doing, step by step, and roughly when?
The key rule: the villain's plan must work even if the heroes never show up. Your villain is not sitting in a throne room waiting for level-appropriate adventurers. They are busy, they have a schedule and if nobody stops them: they win.
Here's what that looks like in practice. Say my villain is Maravess, a necromancer who wants to raise an army from the kingdom's largest battlefield graveyard. Her plan might read:
-
Step one: quietly buy up land around the old battlefield through a shell merchant company.
-
Step two: steal the ritual focus, a funeral mask, from the temple in the capital.
-
Step three: silence the three scholars who could recognise the ritual for what it is.
-
Step four: begin the raising on the winter solstice.
-
Step five: march on the capital before the spring thaw brings reinforcements.
Now look at what that list just did for you. Every step generates adventure hooks automatically. The party hears about strange land purchases, or a temple theft, or a scholar found dead. You didn't have to invent plot. The plot is just the villain's plan, viewed from the outside, leaking evidence.
It also solves pacing. If your players spend four sessions running a tavern (they will, don't fight it), Maravess doesn't pause. She moves to step three. The world tightens around the party whether they engage or not, and when they finally notice, the stakes feel real because they are real. Nothing I've ever written has made players sit up straighter than realising the bad thing happened because they were busy elsewhere.
Word of warning: keep the plan simple loose, because a good villain adapts when the party wrecks step two, and if they don't? Well, we'll get onto consequences later.
3. Plant Three Story Threads
Early on I believed more hooks meant more player freedom. So I'd open a campaign with a corkboard's worth of mysteries: the haunted lighthouse, the missing merchant, the weird cult, the sad ghost, the mayor's secret, the thing in the well. My players, faced with thirty threads, grabbed none of them and went shopping.
Choice paralysis is real, and it kills momentum. What works is three threads. Exactly three, and each a different flavour:
-
The villain thread. This is your main arc, the visible leakage from the villain's plan we just built. It's the biggest and slowest thread.
-
The regional thread. A local problem with no connection to the villain. A trade war, a bandit trouble, a feud, a monster with territory. This gives the world texture and gives players a break from the main plot when they want one.
-
The personal thread. Something tied directly to one character's backstory. A sister who stopped writing letters. A debt with interest. An old mentor spotted in a city where he shouldn't be.
Three threads means every session, your players have a real choice about what to pursue, but you can actually track all of it in your head. And here's the part that makes you look like a genius: let the threads touch occasionally. The bandits from the regional thread are being paid in coin minted by the villain's shell company.
The missing sister was last seen near the battlefield graveyard. You don't need to plan these connections in advance. Just leave the door open, and when a crossover occurs to you mid-campaign, take it. Your players will assume you planned it from session one, and you should absolutely let them believe that.
When a thread resolves, plant a new one. Three is a garden. Thirty is a jungle nobody wants to enter.
4. Design a First Session That Hooks (How to Start a D&D Campaign)
Your first session has one job, and it isn't exposition. Its job is to make everyone want a second session. So let me give you a structure you could genuinely run tonight, and then I'll explain why each beat is there.
I call this one The Wake at the Broken Anchor, but the skeleton works for any premise:
-
Minute zero: start in motion. The party is already at the funeral wake of a mutual acquaintance, old Tam the ferryman. Everyone owed Tam something. That's the whole backstory requirement. Don't start with strangers meeting in a tavern and staring at each other.
-
First fifteen minutes: a scene with a decision in it. The innkeeper asks the party to say a few words about Tam. Small, personal, gets everyone speaking in character with zero pressure.
-
Around minute thirty: something goes wrong. Tam sits up in his coffin. Not a zombie shuffle, something worse. He's screaming a name nobody recognises.
-
By minute forty-five: your first fight, short and winnable. Whatever's wearing Tam doesn't want to be put down. Three or four rounds, tops.
-
Immediately after: a discovery. Sewn into the coffin lining, a letter addressed to a person who doesn't exist, in Tam's handwriting, dated two days after his death.
-
Final beat: a genuine choice with no correct answer. Report this to the town watch and stay legitimate, or follow the letter quietly and keep the head start? End the session the moment they decide.
Why this shape works: starting in motion skips the awkward introductions phase that kills more campaigns than any dragon. The funeral gives strangers an instant shared bond. The early fight teaches everyone their character sheet while adrenaline is high.
The letter points straight at your first story thread and ending on the decision means your players spend the whole week between sessions arguing about it in the group chat, which is exactly where you want them.
My Rhinehaven campaign started in a similar vein. The characters all wanting to travel to the town paid good money for protection on the dangerous road to Rhinehaven, all falling for the same scam and left to fend for themselves. A missing child provided the hook to unite the party in common cause and after claiming their reward they arrived in town to find a mysterious mages tower looking ominously out of place.
If you take nothing else from this section on how to start a D&D campaign, take this: hook first, explain later. Mystery is a debt your players will happily let you owe them.
5. Plan Consequences
Players never follow the plot, not the one you planned at least. You will write a beautiful scene where the party confronts the corrupt magistrate at the gala, and your players will burn the building down, fake their own deaths, and open a bakery.
This is not a bug. This is the entire reason tabletop games are better than video games, and your prep needs to be built for it.
The fix is to stop writing scripts and start writing branches. For every situation you prep, sketch two or three likely player responses plus one fallback, each with a consequence attached. Not a scene. A consequence. Here's a real example from my table. A cult is recruiting dockworkers in the harbour district:
-
If the party infiltrates: they learn the recruiter reports to someone in the harbormaster's office, and they're now on a membership list they might regret.
-
If the party attacks: the cult goes underground, recruitment continues invisibly, and the city watch now has questions about the corpses.
-
If the party ignores it: the cult grows. In three sessions, the dockworkers strike, and the harbour closes right when the party needs a ship.
-
If they do something I never predicted (they will): I ask myself one question. What would the cult, the watch, and the harbormaster each do in response? The world answers, even when my notes don't.
Notice that every branch, including "ignore it," moves the world forward. That's the engine. When players learn their choices echo, they stop asking "what does the DM want us to do" and start asking "what should we do," which is the moment a group of people rolling dice becomes a campaign.
Tracking those echoes is honestly the hardest part of the job, and it's the reason I started work on Dungeon Weave, a campaign planner built specifically around branching storylines. Its whole tagline is "every action has a consequence," which tells you exactly where its head is at.
You sow the threads, the tool tracks which ones your party wandered down, and nothing falls through the cracks between sessions. However you track it, though, the principle stands: prep decisions and their fallout, never scenes and their scripts.
6. How Much Should You Actually Prep? (How to Plan a D&D Campaign Without Burning Out)
Here's the number nobody wants to say out loud: after your initial setup, thirty to sixty minutes per session is enough. Sometimes more than enough.
I've run three-year campaigns on a lunch break's worth of weekly prep, and they were better than my over-prepared ones, because I was improvising from a strong foundation instead of flipping through forty pages looking for the paragraph I needed.
The initial setup, the campaign skeleton, is maybe eight to twelve hours total: your premise, your villain's plan, your three threads, and your first session. That's the whole buy-in. After that, my weekly hour looks like this:
-
A strong start. One sentence for how the session opens, ideally mid-situation. Five minutes.
-
A quick review of the three threads and the villain's clock. What moved since last time? Ten minutes.
-
Three to five secrets or clues the party could discover this session, written as single lines. These are the most valuable thing you'll prep, because they're portable. If the party skips the library, the same clue can surface in a letter, a drunk guard, or a dying cultist's last words.
-
A list of ten names. Trust me. The moment you improvise an NPC called "Bob the Second Bob," you'll wish you had the list.
-
One or two combat encounters and accompanying battle maps, in case the night goes loud.
Just as important is what you should not prep. Don't write dialogue, because you'll deliver it stiffly and your players will interrupt it anyway. Don't write read-aloud text longer than a couple of sentences.
Don't stat every NPC; a commoner with one interesting goal beats a fully statted nobody. Prep is fuel, not scripture. If a piece of prep doesn't survive contact with your players, it did its job by getting you confident enough to improvise.
FAQs: How to Write a D&D Campaign, Quick Answers
How long does it take to write a D&D campaign?
The honest answer: eight to twelve hours for a skeleton you can run for months, then thirty to sixty minutes per session after that. If someone tells you they spent two hundred hours before session one, they didn't write a campaign, they wrote a book.
The campaign gets written at the table, week by week, with your players as unwitting co-authors. Start sooner than feels comfortable.
Can I use a premade setting instead?
Absolutely, and please don't let anyone make you feel lesser for it. I'm currently having great fun running an Acquisitions Incorporated campaign. The Forgotten Realms, Eberron, or a published adventure like Curse of Strahd gives you maps, factions, and lore for free, which frees your energy for the parts only you can do: your villain's plan, your threads, your table's story.
I'd rather play in a stock setting with a DM who preps consequences than a bespoke world with a DM who preps scripts. Steal the scaffolding, keep the soul.
How many sessions should I plan ahead?
In detail? One. The next one. In loose outline, maybe three, and hold even that lightly. Anything past three sessions is fiction, because your players will have changed the board by then.
What should extend further than three sessions is your villain's clock, since that runs on its own schedule regardless of what the party does. Detailed prep is perishable; direction isn't. Stock up on direction.
Do I need to write an ending?
Not an ending, but a destination. Know what happens if the villain wins, and know what the final confrontation might feel like, then leave the details unwritten. Endings you script years in advance almost never fit the campaign you actually end up running, because the best final sessions are built from the debts, grudges, and callbacks your table generates along the way. Aim the ship at a lighthouse. Don't chart every wave.
My Rhinehaven campaign doesn't even have it's final villain decided upon yet, maybe it's some as of yet unidentified daemon, or perhaps it's actually a familiar face: the town mayor or someone connected to a character's backstory. I've not yet decided - we'll just have to see where the characters decide to start poking their noses into.
Go Write the Thing
One premise, one villain with a schedule, three threads, a first session that ends on a decision, and branches instead of scripts. That's the whole method. Everything else you'll learn at the table, which is the only place campaigns are ever really written anyway.
And when your branching storylines outgrow your notebook, that's exactly what I built my prep around Dungeon Weave for. It's free to try at dm.dungeon-weave.com. Sow your threads, track every consequence, and go give your players a world that remembers what they did.