How to Catch Up a Player Who Missed a Session (and What to Do With Their Character While They're Gone)

Decide what happens to the character before game night

A missed session is two separate problems, and mixing them up is what makes it stressful. One is logistical: the party is mid-adventure and one character has no player tonight. The other is human: next week, someone at your table will have a session-sized hole in their memory of the campaign. The first gets solved at the table; the second gets solved before the next one. This guide takes them in that order.

The logistical half goes best when nobody is deciding anything at seven o'clock on game night. Pick a standing rule with your table — one of the three options below, or a rule for which option applies when — and say it out loud once, so an absence triggers a routine instead of a negotiation while everyone waits to start.

Whichever option your table prefers, one piece of it is close to universal: while a character is unattended, they do not die, they do not spend anything permanent, and they do not make decisions their player would want to be in the room for. Everything else is taste. That floor is what makes the rest safe to improvise.

Option one: the character fades into the background

The lightest option: the character stays with the party, and the camera just never finds them. They are walking at the back of the group, holding the torches, watching the door during the fight. Nobody plays them; nothing important happens to them.

This is the right call when the party is somewhere a character cannot plausibly leave — three levels into a dungeon, mid-voyage, camped in hostile territory — and for one-off absences generally, because it needs no fiction and leaves nothing to retcon. The character was there, quietly, and next week their player picks them up exactly where the party is standing.

Two things make it work better. First, settle combat up front: either the character hangs back and the encounter is fought by whoever is present, or someone rolls their basic attacks and touches none of their limited resources. Do not run them at full power from a sheet nobody at the table knows well — a full-strength character piloted by nobody is the one most likely to end up in trouble the table then has to undo. Second, give them one small off-screen contribution when it is natural: they kept watch, they carried the injured guide, they held the rope. It costs one sentence, it keeps them canon, and it heads off the running joke where the absent character becomes the party's luggage.

Option two: another player runs them

Handing the sheet to another player keeps the character fully in the game, which matters most on the nights the party needs the body: the group's only healer, the only one who can open the lock, a fight you have already built for five.

It is also the option with the most ways to go wrong, so it comes with ground rules. Pick the stand-in deliberately rather than asking for volunteers — the player whose own character has the least to do tonight, or the one who actually understands the build — and get them the sheet before the session, not during the first fight. Then say the rules when you hand it over, every time. They take fifteen seconds:

• Keep them alive over playing them well. The stand-in's job is to return the character in the shape they found them, not to optimize.
• Spend nothing permanent and as few consumables as the night allows. The scroll, the last potion, the favor the character is owed — those are the owner's to spend.
• No character-defining choices. The stand-in does not accept oaths, start romances, betray anyone, or volunteer the character for the ritual. If the story corners the character into a real decision, the DM steps in and defers it, or makes the smallest call available.
• The owner gets an amnesty. Anything the stand-in did that feels wrong to the returning player can be quietly softened or re-decided next session. Saying this up front is what lets the stand-in relax enough to actually play.

Option three: write them out of the fiction

The character is somewhere else tonight: guarding the camp, escorting the merchant back to town, laid up with a fever, called home by a letter. This is the cleanest option narratively — no ghost walking with the party — and the best one for planned absences, town sessions, and episodic campaigns where the group returns to a home base between jobs.

Its weakness is the dungeon problem. If the party is five rooms into somewhere dangerous, an exit excuse strains the fiction. Strain it anyway, lightly, and off-screen: "Dara stayed at the last safe landing," said once, beats an elaborate teleportation accident, and nobody will interrogate it — the table understands what is actually happening. A light hand reads as confidence; a heavy explanation reads as apology.

Two practices worth stealing. Give the absence a small return value: the character comes back having done something modestly useful off-screen — the supply run worked, they overheard a rumor, the message got delivered — so the player re-enters with a line to say instead of an apology to make. And never run the off-screen errand as a highlight. If the absent character's side story turns into the best content of the month, the table learns that missing sessions is where the good stuff happens.

What the absence should never be is a punishment. The character does not get robbed, kidnapped, or demoted because their player had a work thing. An empty chair is a calendar fact, not a character choice, and in-fiction consequences for it poison exactly the goodwill that keeps a campaign alive through everyone's busy months.

XP and loot: parity is the point

None of this is a rules question. Every table settles it as house practice, and the practices that survive are the ones that keep the group playable together.

On experience, argue from structure rather than fairness. A character who lags a level behind the party makes every later session slightly worse for everyone: encounters are harder to pitch at a split-level group, the gap compounds with each absence, and the person being penalized is the one whose attendance the table is trying to encourage. Docked XP feels like accountability and functions as a tax on the whole table. If your game levels by milestone, the question never arises — the party levels together when the story says so, which is a genuine argument for milestones in any group with a lively calendar. If you award XP, the version that creates no future problems is the simple one: everyone gets it, present or not.

Loot has an easy half and a hard half. Coin and sellables are easy — split evenly, with the absent character's share set aside; the party is a household, not a shift job. The hard half is the unique items, because those are really decisions about who the party wants holding what. The practice that reliably avoids arguments is to defer: the item rides in the bag unclaimed, and the table decides who keeps it when everyone is in the room. That costs the party nothing tonight, and it converts a potential grievance into a five-minute scene next week.

If your table genuinely wants showing up to matter, make the reward flat, small, and outside the power curve — first pick from the mundane haul, the deciding vote on where the party stays the night. Not levels, and not the magic item. The goal is a nod to the people in the room, not a growing gap between them and the person you want back in it.

The absent-player note is not the table recap

If you write a session recap for the table — and the recap guide makes that a ten-minute job — the temptation is to point the absent player at it and call the catch-up done. Post it, absolutely. But the table recap is written to reload a story people experienced. The absent player needs something slightly different: a version addressed to them, about their character, sent where they will actually see it.

Send it as a direct message rather than a channel post, within a day or two of the session rather than an hour before the next one. A personal note signals that the campaign noticed they were gone, which does more for whether they stay in the campaign than anything written in the note. And a mid-week send gives them days to ask questions in the group chat, which is catch-up happening for free.

It runs three to six sentences, in this order:

• Where the party is now and what they are in the middle of — one line, present tense.
• What changed that affects their character directly: the plan they were part of has moved, the contact they trusted is gone, the thing they were carrying got used.
• What their own character did off-screen, in one sentence, so they return owning a small piece of canon: you kept the watch, your supply run worked, the message got through.
• Anything now owed, promised, or decided that binds them — especially decisions the party made on their character's behalf.
• The image the next session opens on, so their first thought is forward, not backward.

How much to spoil

The recap guide's rule — write from what the characters observed — needs an amendment here, because this character observed nothing. Write from what the party would have told them. That filter earns its keep twice: it keeps GM secrets safe automatically, since the party cannot repeat what they never learned, and it renders the session as the party's version of events, which is the version the campaign actually runs on.

Split what happened into two piles. Information goes in the note: anything the character would be told promptly and plainly — a death in the party, a change of destination, a decision that binds them. Experiences stay out: the perfect one-liner, the absurd plan that worked, the reveal the table gasped at. Name that these exist — "ask the table about the bridge" — and let the players retell them before the session starts. The retelling is a better catch-up than your summary, it costs you nothing, and being told the group's stories is half of what makes someone feel they still belong to the group.

Two hard edges. Never let a player walk into a session not knowing something their character would obviously know — discovering live at the table that a party member died three weeks ago is not a fun reveal, it is evidence nobody thought about them. And never write something false to protect a secret; omit instead. The note becomes canon exactly the way a posted recap does.

The three-minute ritual before the session starts

Whatever you sent, assume it half-worked. A written note reloads facts; it does not reload footing. The last three minutes before play is where footing comes from, and it is a ritual precisely so that it stays three minutes.

1. Get them in a couple of minutes early, or pull them aside while the table settles. This is a two-person conversation — performed for the whole group it turns into the twenty-minute recap you are trying to avoid.
2. One sentence of situation: where the party is standing and what is mid-motion. The line that opens your table recap usually works verbatim.
3. One sentence about their character: position, condition, what they are holding, and anything different about their sheet since they last saw it.
4. One question that hands them a live decision: the innkeeper still has your deposit — are you letting that go? A question puts a player back in character faster than any amount of summary, because answering it requires being the character.
5. Then start, and get them a line inside the first ten minutes — an NPC addresses them, the party asks their opinion, the watch order needs them. Re-entry is complete the first time they speak in character, and not before.

Do not spend twenty table minutes re-explaining

The failure mode this whole page exists to prevent: the session opens, the returning player asks what they missed, and the DM performs last session while five other people re-read their phones. Do the arithmetic once and it stays done — twenty minutes of catch-up at a table of six is two person-hours of game, spent on content five of the six already experienced. It is also bad catch-up: a monologue delivers less than a note, one question, and ten minutes of actual play.

If the table wants to help, timebox it and make it in-character: one minute, each player telling the returner one thing their character would actually tell them. That is a scene. It moves the session forward while it catches someone up.

Know which problem you have. One player, one missed session is this page. The whole table coming back from a two-month gap is a different job with different tools — the amnesty, the player recap round, the one-page restart note — and the campaign memory guide covers that one. Using the whole-table tools on a single absence is exactly how the twenty-minute recap happens.

And accept the residual. The returning player will be missing texture for a session — in-jokes, small NPC moments, the reason everyone winces at the word "ferry." That is fine. Texture is re-acquired by playing, and the fastest way to hand it back is to get them playing.

Make the catch-up cheap, and it will actually happen

Everything above is maybe fifteen minutes of DM work per absence: a five-line note, a three-minute ritual, a fifteen-second hand-off rule. The reason it still gets skipped is that the raw material is missing — reconstructing a session you half-remember in order to summarize it for someone else is real work, and it lands in the busiest week of your month at exactly the moment you least want a writing assignment.

So the durable fix is the same one that fixes prep, recaps, and your own memory: capture the session while it happens. A one-line-per-beat note habit or a phone recording from the middle of the table turns the absent-player note into a two-minute edit of something that already exists, and a pinned recap channel gives "what did I miss" a self-serve answer that works even in the weeks when you are the busy one.

One honest caveat about recordings: do not send the absent player four hours of audio. Nobody listens to it, and sending it feels like catch-up while accomplishing none. The usable forms are text — a recap, a transcript they can search, a campaign log they can browse. If you want those produced automatically, that is the specific job DM Scribe was built for: the recording becomes a transcript and a drafted recap, the campaign wiki grows from what was said, and a read-only share link gives players somewhere to look things up without asking you — though a running shared doc maintained by hand serves the same purpose, at the cost of maintaining it.