Pregens Done Right: Building Characters Strangers Fall in Love With in One Session

Dear Readers,

I want to talk about the hardest character you will ever write, and the one who will get the least credit for being hard: the pregenerated character.

Every GM who's run a convention slot, a demo table, or a one-shot for a group of strangers knows the shape of the problem, even if they've never stopped to name it. You hand someone a character sheet. They have never met this person before — the character, I mean, though often the other players at the table too — and in roughly five minutes, while you're finishing your setup spiel, they need to go from "here is a piece of paper" to "here is someone I am prepared to make choices as, in front of a table of strangers, for the next three hours." That's not a small ask. It's arguably a harder design problem than building a character for a campaign, because a campaign PC gets built by the person who's going to play them, with all the investment that implies. A pregen has to earn that investment cold, from someone who didn't write a word of it.

Most pregens fail at this, and they fail in a specific, recognizable way. They read like character sheets that happen to have a paragraph of prose stapled to the top. A name, a race and class, a stat block, and then six inches of backstory about a tragic childhood or a mentor who died — interesting to write, almost none of it usable in the first twenty minutes, which is exactly when a new player most needs something to hold onto. By the time anyone needs that dead mentor, the player has already decided who their character is based on vibes, and the carefully constructed backstory just sits there, unread, like a warranty card nobody fills out.

I've spent a fair amount of time lately thinking about this problem directly, because I've been building pregenerated characters for a one-shot called "Hope's Last Day," set in the Aliens: Evolved starter set — a game that, by design, drops a table of strangers into a claustrophobic, high-tension situation with almost no runway for a session zero. There's no time to sit around discussing character motivations before the horror starts. The pregens have to do that work themselves, instantly, or the whole thing falls flat before the first xenomorph so much as scratches a bulkhead. That constraint turned out to be clarifying. When you can't lean on prep time, you find out very quickly what actually makes a pregen work.

THE FIVE-MINUTE TEST

Here's the standard I hold every pregen to now: could a total stranger read this character, put it down, and answer three questions without hesitating — what do I want, what am I afraid of, and what am I probably going to do in the next ten minutes if things go sideways? If a player can answer those three questions after one read-through, you've built a playable character. If they can't, you've built a biography, and biographies are for people with time to read them slowly. Nobody at a one-shot table has that kind of time.

This means the actual content of a pregen matters less than its shape. A tragic backstory isn't disqualifying — plenty of great pregens have one — but it has to compress into something that generates behavior, not just sympathy. "Her sister died in a colony collapse" is backstory. "She volunteers for every dangerous assignment because she can't shake the feeling that if she'd been braver, her sister would still be alive, and she'll get someone killed being reckless if nobody reins her in" is a want, a flaw, and a table dynamic, all in one sentence a player can internalize instantly.

BUILDING A WANT, NOT JUST A WOUND

When I sat down to write Miguel "Mig" Ortega and Diane Kessler for "Hope's Last Day," the wound-versus-want distinction was the first thing I forced myself through, character by character, before anything else went on the page.

Mig is the easier case to explain, because his want is almost mechanically simple: he needs to get paid, and he needs it more than he needs to be a hero. That's it. That's the engine. Everything else about him — his manner, his one-liners, the way he sizes up a room for exits before he sizes it up for threats — flows out of that single, ruthlessly legible priority. A brand-new player reading his sheet doesn't need three paragraphs of career history to know how to play him in the first tense scene. They know Mig wants to survive with money in his pocket, and that single fact tells them what he says when someone suggests a risky plan, how he reacts when the payout gets threatened, and what kind of tension he creates with anyone at the table playing a character who'd rather do the right thing than the profitable one.

Diane is a different kind of want, quieter and more procedural — she wants control over an uncontrollable situation, which in practice means she's the one pushing for protocol, double-checking the plan, getting frustrated when the group improvises instead of following procedure. That want does two things a pregen needs to do simultaneously: it gives the player a clear default behavior to fall back on when they don't know what else to do, and it creates automatic friction with characters like Mig, who couldn't care less about protocol as long as the money's good. Neither character needed a shared history for that tension to exist. The tension was baked into what each of them wants, which meant it showed up at the table in the first ten minutes without either player having to manufacture it.

That's the real trick of a good pregen ensemble, by the way — the wants have to interlock with each other, not just exist in isolation. A table full of pregens who each want something reasonable but unrelated to everyone else's wants is a table full of parallel monologues. A table where Mig wants money and Diane wants control and a third character wants to prove herself and a fourth wants everyone to just get along is a table that's going to generate friction, and therefore scenes, without the GM lifting a finger to force it.

SECRETS THAT ARRIVE ON A SCHEDULE, NOT ALL AT ONCE

The part of this project I'm most pleased with, and the part I think solves the session-zero problem most directly, is something we ended up calling act-structured personal agenda cards.

Here's the problem they're solving. A pregen with a secret is more interesting than one without, but a secret dumped onto the character sheet on page one creates a strange incentive: the player either ignores it because they're too busy absorbing everything else about the character in those first five minutes, or they play it immediately and it stops being a secret by scene two. Either way, you've spent good material too early or not at all.

The fix was to stop putting the whole character on the table at once. Each pregen comes with a small stack of agenda cards, handed to the player at specific points as the one-shot moves through its acts — not attached to the initial sheet, and not visible to anyone else. Early in the game, a player might get a card that simply reinforces their established want: a small, concrete goal for the current scene. Later, as the situation in "Hope's Last Day" gets more dire, a card might reveal something the character has been hiding, or force a choice between two things the character wants that can no longer both be true. Diane's control instinct, for instance, gets tested directly partway through by a card that puts her in a position where following protocol and keeping someone alive are suddenly at odds — a conflict that wasn't visible on her original sheet at all, because putting it there on page one would have telegraphed it and drained all the tension out of the moment it's actually meant to land in.

This does something a straight backstory paragraph never can: it paces the character's depth to match the pacing of the scenario itself. The player doesn't need to have internalized a whole life story before the game starts. They need to have internalized a want and a rough shape, and then the game itself hands them the rest of the character, one card at a time, exactly when it's dramatically useful rather than dumped in a pile before anyone knows what they're going to do with it. It also solves a second, quieter problem: it gives a new player permission to be surprised by their own character. That's normally something you only get from months of campaign play, where you discover who someone is through the accumulation of choices. Agenda cards fake that accumulation in the span of a single session, which for a one-shot format is about as close to real character development as you're going to get.

MECHANICS THAT PLAY THEMSELVES

None of this matters if the player can't actually run the character, so the last piece of the puzzle is purely functional: the sheet itself has to be legible to someone who may be brand new to the system, not just brand new to the character. This sounds obvious and gets ignored constantly. A pregen sheet dense with unexplained modifiers and a pile of abilities with no indication of when you'd actually use them is a trap for a new player, who will either freeze up trying to parse it or default to the same one ability every time because it's the only one they understood.

For Mig and Diane, that meant treating the sheet itself as a small piece of instructional design, not just a character record. Every ability gets a one-line "use this when" note instead of just its mechanical text. The want and the flaw sit at the top of the page, not buried below three columns of stats, because that's the part a new player actually needs first. Anything genuinely optional — flavor equipment, minor skills that rarely come up — gets pushed to a second page or cut outright, because a five-minute read-through has no room for material that isn't pulling weight.

THE PITFALLS THAT RUIN AN OTHERWISE GOOD PREGEN

A few mistakes show up over and over in pregen writing, and they're worth naming plainly, because they're the kind of thing that's obvious in hindsight and invisible while you're drafting.

The first is writing for the character instead of for the reader. It's tempting, when you know a character well, to write their sheet the way you'd describe them to a friend who already gets it — in-jokes, implied context, references to events the character supposedly lived through that the player has no way of understanding. None of that lands for someone meeting the character cold. Every sentence on a pregen sheet has to work for a reader with zero context, which is a much stricter constraint than writing prose fiction about the same person.

The second is symmetry for its own sake. It's easy, once you've settled on a structure — a want, a flaw, an agenda card schedule — to apply it identically to every character, delivering the same number of beats at the same act breaks regardless of whether the story needs it there. Diane's protocol-versus-survival card lands where it does because that's when "Hope's Last Day" actually puts her in that bind, not because the outline said act two needed a reveal. If structure starts dictating content instead of the reverse, the cards stop feeling like discoveries and start feeling like a checklist.

The third, and probably the most common, is over-explaining the flaw instead of trusting the player to find it. A flaw stated too bluntly — "Mig is greedy and this will cause problems" — reads like an instruction rather than a trait, and new players tend to follow instructions a little too literally, performing greed as a bit rather than living inside a priority that puts him at odds with the group. The better version gives the player the want and lets the friction emerge from play.

TESTING IT IS THE ONLY WAY TO SEE IF IT WORKS

None of this is theoretical for me, because the only real test for a pregen is putting it in front of someone who's never seen it and watching what happens in the first ten minutes. I ran Mig and Diane at a table of people who'd never touched the Aliens: Evolved system, gave them the sheets cold, and said as little as possible while they read. The tell isn't whether they like the character — almost everyone is polite about a new sheet. It's whether they can tell you, unprompted, what their character wants before the scenario has even started. If a player looks up and says "okay, so I really need this job to pay off" without being asked, the character's done its job. If they need to ask what their character would do, the sheet hasn't told them enough, no matter how much lore sits underneath it.

WHY THIS IS WORTH THE EFFORT

It would be easy to treat pregens as a lesser form of character writing — the training wheels version, something you dash off quickly because "it's just a one-shot." I think that gets the difficulty backwards. A campaign character has months to become interesting. A pregen has one session and a five-minute head start, and it has to do that with a total stranger at the controls, someone who didn't choose this character out of a hundred ideas in their own head the way a campaign player does. If a pregen doesn't work, there's no next session to fix it in. You get one shot, and the character either grabs someone or it doesn't.

What I've landed on, after building Mig and Diane and watching them run, is that the craft isn't really about writing a good character at all, in the traditional sense. It's about writing a good starting condition — a want sharp enough to generate immediate behavior, a flaw that creates friction with the table around it, and a structure that reveals the rest of the character on a schedule the game controls rather than dumping it all at once and hoping the player finds their way there on their own. Get that right, and a total stranger can pick up a piece of paper, read it once, and by the time the first scene ends, they're not reading a character anymore.

They're playing one.

That's the whole job, really. Not making someone interesting on paper. Making them playable in five minutes by someone who's never met them, and letting the interesting part show up on its own, one act at a time, exactly when it's earned.

Until next time, Dear Readers...