The Art of the Backstory: Writing Character History That Matters - ICE5e Blog

You've rolled your stats. You've picked your class and species. You've chosen spells, equipment, and a name that you definitely won't regret in six months.

Now the character sheet asks for a backstory, and suddenly you're staring at a blank text field wondering if "orphan who wants revenge" is too cliché.

Here's the secret: there are no bad backstory tropes. Orphans seeking revenge have fueled some of the greatest stories ever told. What matters isn't originality—it's utility. A good backstory gives you and your Dungeon Master tools to work with. A great backstory practically writes its own adventures.

The Purpose of a Backstory

Before we talk about how to write one, let's establish why backstories exist in the first place.

A backstory serves three functions:

Character Motivation: Why does your character adventure? What do they want? What are they afraid of?

Roleplay Foundation: How does your character speak, act, and react? What shaped their personality?

Plot Hooks: What people, places, and events from the past might return to drive future stories?

Notice what's not on this list: impressing other players with your creative writing skills. The backstory isn't a novel. It's a toolkit.

The "Start Small" Principle

New players often make backstories too epic. By level 1, their character has already slain dragons, lost entire kingdoms, and made enemies of three different pantheons.

The problem? There's nowhere to go. If you've already done everything, why are you adventuring with a bunch of nobodies in a tavern?

The Fix: Your backstory should explain how you became a level 1 adventurer—not a level 20 legend. Save the epic accomplishments for the campaign itself. Too Big: "I was the general of the Elvish army who single-handedly turned the tide of the Great War." Just Right: "I served as a scout in the Elvish military. When my unit was ambushed, I was the only survivor. I left the service after that."

The second version gives you military training (explaining your class skills), a traumatic event (character motivation), potential enemies (whoever arranged the ambush), and room to grow. You're not a general yet—but maybe you could become one.

The Three-NPC Rule

Here's a practical framework: every backstory should include at least three named NPCs.

Someone who helped you. A mentor, family member, or friend. They represent your ties to the world and give you something to protect.

Someone who wronged you. Not necessarily a villain—maybe just someone you have unfinished business with. This creates built-in conflict.

Someone you wronged. This is the one players forget most often. Flawed characters are interesting characters. Maybe you abandoned someone. Maybe you made a choice you regret. This gives your character an arc—something to make amends for.

When you hand your DM a backstory with three named NPCs, you've just given them three potential quest hooks, three recurring characters, and three ways to make the campaign personal.

Example: Kira, Human Rogue

Helped: Tomás, the fence who taught her how to survive on the streets of Neverwinter. He's getting old now, and his territory is being squeezed by a new guild.
Wronged by: Captain Vance, the city watch officer who framed her brother for a crime he didn't commit. Her brother died in prison.
Wronged: Her old partner, Lira. When a job went bad, Kira ran and left Lira to take the fall. She hasn't seen Lira since—but she's heard rumors that Lira survived, and she's not the forgiving type.

Look at how much story is packed into three sentences each. A DM could run an entire arc in Neverwinter with just these hooks.

The "Because" Test

Every major element of your backstory should pass the "Because" test. You should be able to explain your character's traits, skills, and motivations with a simple "because" statement.

"My character has proficiency in Medicine because she trained as a battlefield medic."
"My character distrusts authority because the local lord's men burned her village."
"My character always keeps a silver coin in her boot because her grandmother told her it would bring her home safely."

If you can't explain why your character has a particular trait or quirk, it's probably just decoration. Decoration is fine—characters should have texture—but the load-bearing elements need foundations.

This also helps with roleplay consistency. When you know why your character does something, you can extrapolate how they'd behave in new situations.

Leaving Blank Spaces

Counterintuitively, one of the best things you can do is not fill in everything.

Leave gaps in your backstory that you and the DM can fill together during the campaign. Instead of detailing exactly what happened to your missing sister, write: "My sister disappeared five years ago. I never learned why."

Now your DM has a mystery to solve. They can make your sister a villain, a victim, a secret agent, or a red herring. You've given them creative freedom while still establishing an emotional anchor.

Good Gaps to Leave:

The identity of a mysterious figure from your past
What really happened during a traumatic event
Where a missing person or object ended up
The true nature of a gift, curse, or prophecy
What happened to your homeland after you left

Using ICE5e: The Journal feature is perfect for tracking these mysteries as they unfold. Start an entry called "The Disappearance of [Sister's Name]" and update it whenever you learn new information. Watching the mystery solve itself over months of play is incredibly satisfying.

Connecting to the World

A backstory that exists in a vacuum is a missed opportunity. Whenever possible, anchor your history to the campaign setting.

If your DM is running a published adventure or homebrew setting, ask them:

"Where would my character have grown up?"
"Are there any factions that fit my background?"
"What major events happened in this world that my character might have experienced?"

Even basic connections help. If the campaign takes place in Waterdeep, your character might have:

Worked at a specific tavern
Had a run-in with a particular noble house
Witnessed a famous historical event
Been trained by an organization the DM plans to use

Suddenly, you're not a stranger in a strange land. You have opinions about the local politics. You recognize street names. The world feels real because your character has a place in it.

The Tragic Backstory Problem

Let's address the elephant in the room: dead parents.

It's become a meme that every D&D character is an orphan with a tragic past. But tragedy isn't inherently bad—it's just overused in a specific way.

The Problem: Tragedy used as motivation without follow-through. "My parents are dead, so I'm sad" isn't a character arc—it's a starting point at best. The Solution: If you use tragedy, make it specific and actionable. Bad: "My family was killed by orcs. I hate orcs." Better: "My family was killed during an orc raid led by a half-orc named Grishnak. I've spent years tracking him. I recently learned he's operating out of the Sword Mountains."

The second version gives the DM an NPC (Grishnak), a location (Sword Mountains), and a clear goal (find and confront him). It also creates interesting roleplaying questions: What happens when you meet a good orc? What happens when you discover Grishnak has a family of his own?

Alternative Motivations:

Not every adventurer needs trauma. Consider:

Ambition: You want to become the greatest wizard in history.
Curiosity: You heard rumors of an ancient library and had to see it.
Duty: Your order assigned you to investigate reports of undead.
Debt: You owe a powerful figure and adventure to pay them back.
Boredom: Noble life was suffocating. You needed real experiences.
Faith: Your deity sent visions of a coming darkness. You're meant to stop it.

Writing for Collaboration

Your backstory doesn't exist in isolation. It needs to work alongside other characters' histories.

During Session Zero, share the broad strokes of your backstory with other players. Look for natural connections:

"We could have served in the same military unit."
"Maybe your mentor and my mentor were rivals."
"What if we both grew up in the same city but in different social classes?"

These connections create instant party cohesion. You're not strangers who happened to meet in a tavern—you have shared history. You have reasons to trust (or distrust) each other before the adventure begins. ICE5e's Party Features let you document these shared backstory elements. Create a wiki page for "How We Met" or add relationship entries between characters. When you need to remember why the Paladin owes your Rogue a favor, it's all there.

The Backstory Document

Finally, let's talk about format. How much should you actually write?

For the DM: One page maximum. Bullet points are fine. Focus on the elements they need to run the game: NPCs, locations, unresolved conflicts, and clear motivations. For Yourself: Write as much as you want, but keep the DM-facing version short. You might have ten pages of internal monologue about your character's psychology—that's great for you, but your DM doesn't need it. The Essential Elements:

Origin: Where are you from? What was your life like before adventuring?

Motivation: Why do you adventure? What do you want?

NPCs: Who shaped you? Who do you love? Who do you hate?

The Hook: What unresolved element could the DM use to bring your past into the present?

Personality Notes: How do you act? What are your verbal tics, habits, or beliefs?

Everything else is gravy.

Example: A Complete Backstory

Torven Ashford, Human Cleric of the Forge Origin: Born in a mining town in the Spine of the World. Son of a blacksmith who made simple tools for miners. The town was poor but proud. Key Event: When Torven was sixteen, the mine collapsed. He was one of the diggers who volunteered for the rescue. He prayed to any god who would listen—and felt something answer. His hands glowed with warmth, stabilizing rubble and healing the injured. Forty-three miners survived because of him. Motivation: That experience showed Torven that ordinary people need protectors. He joined the clergy of the Forge to learn how to help people—not just in emergencies, but in everyday life. He wants to build things that last: walls, communities, hope. NPCs:

Marta Ashford (mother): Still runs the smithy back home. Writes letters asking when he'll settle down.
Brother Aldric: His mentor in the church. Disappeared six months ago while investigating a "corruption in the stone" up north. Torven is worried.
Jessa Torne: A miner he rescued during the collapse. She lost her leg and blamed him for not saving it. The guilt has never left him.

Personality: Speaks plainly. Uncomfortable with praise. Sees work as prayer. Always notices craftsmanship. Carries a hammer that was his father's. Open Questions:

What happened to Brother Aldric?
What is the "corruption in the stone"?
Does Jessa still blame him, or has she found peace?

That's 280 words. It's enough to run a campaign with.

Conclusion

Your backstory is a gift you give to your Dungeon Master. It's raw material they can shape into personal storylines, emotional payoffs, and unexpected twists. The more usable hooks you provide, the more likely you are to see your character's history woven into the main plot.

But it's also a gift to yourself. When you know where your character came from, you know where they're going. Every decision becomes an extension of their journey. Every triumph and failure carries weight.

So take the time to write something real. Something specific. Something that leaves room to grow.

And if you need a place to keep track of it all—your NPCs, your mysteries, your evolving history—ICE5e's character journal is waiting for you.