Framework

How do I start GMing for the first time?

Pick a system or a beginner-friendly published scenario you can actually run soon, prepare the next session rather than an entire world, and hold at least a short Session 0 to align expectations before play. Build only the NPCs, places, factions, and conflicts the players are likely to encounter, expect them to go off script and prepare situations rather than a fixed plot, and focus on clear choices, pacing, and spotlight over elaborate lore or performance. After the first session, keep only the notes that actually became real at the table. You do not need voices, acting skill, encyclopedic rules knowledge, or hours of prep to run a good first session.

A first-time Game Master with a single page of notes at a table, players' character sheets spread out ready to begin

You don't need to be a performer

The intimidating version of GMing, the one with character voices, encyclopedic rules mastery, and a binder of prepared lore, is optional flourish that experienced GMs add over years, not a prerequisite for running a good first session. A first session with plain narration, a handful of clear choices, and honest improvisation when players surprise you is a genuinely good session.

The actual skill a first-time GM needs is smaller than it looks: know roughly what's in the room, know what the people in it want, and be willing to say "let's find out" when the players do something you didn't plan for. Everything else can be learned session by session.

Seven steps to your first session

In roughly this order.

  • Pick something you can run soon A system or a beginner-friendly published scenario, not the perfect homebrew concept you'd need months to build. Running something imperfect this month teaches you more than planning something ideal you never start.
  • Prepare the next session, not a world You need enough for three to four hours of play, not a setting bible. A page of notes covering the immediate situation is enough to start.
  • Hold at least a short Session 0 Even twenty minutes to align on tone, safety, and what everyone wants from the game prevents most early friction. See the Session 0 answer linked below for a fuller framework.
  • Build only what players will likely encounter The NPCs, places, factions, and conflicts actually in scope for the opening scenes. Everything else can be invented later, once you know what the party actually cares about.
  • Expect the party to go off script Prepare situations with people who want things, not a fixed plot with one correct path. When players surprise you, that's the game working, not a failure of prep.
  • Prioritise choices, pacing, and spotlight Over elaborate lore or a polished performance. A session with clear decisions and even attention beats one with beautiful description and nothing for the players to actually decide.
  • Keep only what became real After the session, note the names, places, and threads the players actually engaged with. Discard the rest rather than carrying forward material nobody touched.

What you genuinely don't need

  • Character voices or acting skill A different tone of your own voice, or just saying "the guard says" before the line, works fine. Voices are a flourish some GMs enjoy adding later, not a requirement.
  • Encyclopedic rules knowledge Know the basics well enough to run a scene, and look up or improvise the rest. Nobody at the table expects you to have the entire rulebook memorised on session one.
  • Extensive worldbuilding A world only needs to exist as far as the players have actually gone. Build outward from there, session by session, not upfront.
  • Props, music, or a big budget These can add atmosphere for GMs who enjoy building them, but they change nothing about whether the choices and pacing at the table are good.

Example

A genuinely minimal first-session prep packet

Everything a first-time GM needs to run an opening session investigating a break-in at a merchant's warehouse, written in the time it takes to read this paragraph twice.

Situation
A warehouse was broken into overnight. The owner, Mira Kessel, wants it investigated quietly before her business partners hear about it.
People
Mira wants discretion above all. The night watchman, half-asleep on duty, is too embarrassed to admit he saw anything.
What's actually there
A forced side door, a missing crate of manifests, and a torn scrap of cloth caught on the frame.
If the party does nothing useful
Mira hires a second, less careful investigator in two days, and the truth comes out messily instead of quietly.

Before your first session

  • You've picked a system or scenario you can actually run within the next few weeks.
  • You've held or scheduled at least a short Session 0 to align expectations.
  • Your prep covers the immediate situation, not the whole setting.
  • You know what the two or three people in the opening scene want.
  • You're prepared to improvise if the party doesn't take the path you expected.
  • You know what you'll keep and what you'll discard from your notes after the session.

Somewhere for the notes that become real

Once a session produces NPCs, places, and threads worth keeping, a vault gives them somewhere to live as connected entities rather than a growing pile of scattered notes: a name from session one stays findable and linkable to whatever it connects to by session ten.

It doesn't decide what to prepare for tonight or how to handle the table going off script. Those judgement calls are the GM's, especially in the first few sessions.

See the campaign manager

Related

Tools

Other answers