The Downtime Tax: How "What Are You Doing Between Sessions" Quietly Eats Your Prep Time

Downtime between sessions either vanishes into nothing or eats a whole extra session in real time. Here's the one-line-per-character log that gets you the good parts of both without the cost of either.

"What's your character doing between sessions?" is one of the most dangerous questions a GM can ask, because there's no good answer to it. Say nothing and the two weeks between game night just vanish -- nobody trained, nobody healed, nobody's contact in the thieves' guild ever got paid off. Ask the question seriously and you can lose forty-five minutes of your next session to one player narrating a shopping trip while four other people check their phones.

Neither outcome is really about the players. It's that most tables never decided what downtime is for, so it defaults to whichever extreme the loudest person at the table prefers that week.

Downtime isn't nothing, and it isn't a second session

The activities themselves aren't the problem -- crafting a weapon, training a skill, running a shop, calling in a favor, digging through the archive for that prophecy nobody's translated yet. All of that is good material. What breaks is the resolution: either it gets hand-waved so hard it might as well not exist, or it gets played out in real time with the same pacing as a combat encounter, which nobody signed up for on a Tuesday night with two hours on the clock.

The fix isn't picking one extreme. It's separating what happens from how long it takes to say.

The one-line log

Before the table breaks for the night, ask each player one question: what is your character doing, and roughly how long does it take -- days, until next session, until some specific date. Write it down as one line per character: activity, time cost, and the one thing that changes when it resolves. "Marren, forging the sword, ready by session 14, costs 40gp and a favor from the smith." That's the whole entry.

Next session, you open with a thirty-second roundup instead of a scene: "Marren's sword is ready, the smith wants that favor collected, Dez's contact never wrote back." Anyone whose downtime hit a complication gets a real scene for it -- the sword came back cursed, the contact went dark because they're dead -- because that's actually interesting. Everyone else gets closure and the game moves on. You're not skipping downtime, you're compressing the parts nobody wants to watch and keeping the parts that matter.

This is the same discipline as tracking an NPC's promise or a faction's grudge: the value isn't in playing every beat out, it's in not losing track of the beat at all. A downtime line that nobody wrote down is just as gone as an NPC nobody remembers existed. Keep it in the same place you're keeping session notes and continuity tracking -- GameMasterCraft's notes are built for exactly this kind of running list -- so "what did my character actually spend that month doing" has an answer six sessions later instead of a shrug.

The part worth remembering isn't the format. It's that downtime only feels like dead time when nobody decided what it costs and what it changes. Write both down, and the two weeks between sessions stop being empty -- they just stop needing to be played.

The Downtime Tax: How "What Are You Doing Between Sessions" Quietly Eats Your Prep Time