How to Write a Character Backstory Your GM Will Actually Use

There's a particular kind of heartbreak that happens in RPGs. You spend three hours writing a detailed backstory — your character's childhood, their mentor, the tragedy that set them on their path, the oath they swore under a blood moon. You hand it to your GM, buzzing with excitement.

Then session one starts, and none of it comes up. Not session two either. By session five, your backstory is a document nobody references, including you. The GM has their own plot. Your backstory was appreciated but ultimately decorative.

This happens constantly. And it's usually not the GM's fault. It's a backstory design problem.

A good backstory isn't a biography. It's a set of narrative hooks — unresolved threads that a GM can grab and pull. The difference is structural, and once you see it, you'll never write a backstory the same way again.

The Four Elements That Make a Backstory Usable

1. An Unfinished Goal

Your character wants something they haven't achieved yet. Not a vague desire ("I want to be powerful") — a specific, actionable objective that creates story opportunities.

Weak: "Kira wants to become the greatest swordsman in the realm." Strong: "Kira is searching for Voss Iremark, the duelist who killed her teacher. She knows he was last seen in the Ashlands, but that was two years ago."

The strong version gives the GM a named NPC, a geographic location, a relationship (teacher), and a built-in quest hook. The GM can place Voss in the next city, introduce someone who knows where he went, or reveal that Voss has his own reasons for what happened. The weak version is a motivation. The strong version is a story waiting to happen.

2. A Relationship With Loose Ends

Your character knows people. Some of those people are still out there, and the relationship isn't resolved.

Types that work well:

• A debt owed. Someone saved your life, and you never repaid them. They might come looking for you.
• A betrayal. You betrayed someone, or someone betrayed you. Either way, that person has feelings about it.
• A missing person. A friend, sibling, or mentor who disappeared. You don't know if they're alive.
• A rival. Someone pursuing the same goal as you, with a personal reason for wanting to beat you to it.

Each of these gives the GM a character they can introduce at any point in the campaign. A debt collector who appears in a tavern. A sibling's name mentioned by a stranger. A rival who shows up working for the same faction. The more specific you make the relationship — names, last known location, the nature of the unresolved tension — the easier it is for a GM to deploy.

3. A Secret

Something your character knows or has done that they don't want others to discover. Secrets are GM gold because they create dramatic irony — the GM knows something the other players don't, and can engineer situations where the secret threatens to surface.

Examples:

• Your paladin broke their oath once, years ago. Nobody knows.
• Your character is using a false identity. Their real name is on a wanted poster somewhere.
• Your rogue stole something from the very organization the party is about to ally with.

Secrets work best when they have concrete consequences if revealed. "I'm secretly sad" isn't a usable secret. "I'm secretly the heir to a throne I fled" is — because it changes how NPCs react to you if they find out.

4. An Open Question

Something your character doesn't know about their own past. This is different from a secret (which the character knows) — an open question is something even the player doesn't have the answer to, which gives the GM explicit permission to fill in the blank.

Examples:

• "I don't know who my parents were. I was raised by the Order of the Pale Shield, and they never told me."
• "I woke up on a beach with no memory of the past year. I have a tattoo I don't recognize."
• "My mentor gave me this amulet before she died and told me to never open it. I've never opened it."

Open questions are invitations. You're telling the GM: here's a blank space in my story — please write something there. Good GMs love this. It gives them a plot thread that's personally meaningful to your character, which means you'll be invested when it comes up.

How to Structure It

You don't need pages. A usable backstory can be half a page. Here's a template:

Who I am: One paragraph. Name, class/role, and the single most important thing about your character's identity.

What happened: Two to three paragraphs. The key events that shaped your character. Focus on events that left unresolved consequences — not a complete narrative arc, but the setup for one.

Who I know: A short list of 2-4 named NPCs with one sentence each about the relationship and its current state. "Mira Voss — my former partner. We split after the job in Thornwall. She thinks I have the map. I do."

What I want: One sentence. Your character's primary unfinished goal.

What I don't know: One sentence. The open question you're handing to the GM.

What I'm hiding: One sentence. The secret.

That's it. Six sections. Half a page. Every line is a hook the GM can use.

Why This Matters Even More for Solo Play

If you're playing with an AI Game Master, backstory design is arguably more important than with a human GM.

A human GM reads your backstory once, absorbs the themes, and improvises connections over time. They have intuition. An AI Game Master works best with structured, specific inputs. The more concrete your backstory hooks — named NPCs, specific locations, unresolved tensions — the more material the AI has to weave into the narrative.

In platforms with persistent world state, your backstory NPCs can become recurring characters. The rival you named might appear in a city you visit. The mentor who disappeared might surface with news. The secret you wrote creates opportunities for dramatic tension that the AI can engineer across sessions.

The same principles apply: specificity beats vagueness, unresolved beats resolved, and names beat descriptions.

Common Backstory Mistakes

The Completed Arc. Your backstory describes a character who already overcame their greatest challenge, avenged their family, and found peace. There's nothing left for the campaign to do. Keep the arc open — the campaign is the resolution.

The Lone Wolf. "My character trusts nobody and works alone." This gives the GM nothing to work with. Relationships are hooks. A character with no connections has no entry points for story.

The Novel. Five pages of detailed prose that the GM will skim at best. Brevity forces you to focus on what matters: the hooks, not the set dressing.

The Generic Tragedy. "My family was killed and I want revenge." It's not that this doesn't work — it can — but it needs specificity. Who killed them? Why? Where is that person now? The tragedy is the setup. The unresolved details are the hooks.

The Bottom Line

A backstory serves one purpose: to give the person running the game — human or AI — material they can use to make your story personal. Every sentence should either create an unresolved thread or provide a named entity (person, place, object) that can appear in play.

Write for hooks, not for history. Your character's past is only interesting insofar as it shapes their present and creates possibilities for their future.

Keep it short. Keep it specific. Keep it unresolved.

Then hand it to your GM and watch the threads start weaving into the story.