You spent the week building the next arc. The faction politics, the dungeon, the villain’s plan.

Meanwhile, the best hook for that arc has been sitting in a shared doc since session zero. You read it once. You don’t remember what it said.

Every player handed you a backstory. A dead mentor. A sister who vanished. A debt, a betrayal, a home they can’t go back to. Then the campaign started, the dice came out, and those pages went quiet.

That’s the most underused resource at your table.

Backstories are hooks with names attached

A good plot hook makes a player care. The hard part is manufacturing that caring—why should the rogue risk her neck for a town she’s never heard of?

A backstory solves the problem before you start. The player already told you what their character loves, fears, and owes. They wrote you a list of buttons to press. You don’t have to invent stakes. You have to remember them.

The wizard’s backstory mentions the academy that expelled him. Six sessions later, the villain turns out to be a professor from that academy. That’s not a coincidence the players write off as lazy—it’s a payoff they’ll swear you planned from day one.

Mining the page

Read every backstory with a highlighter and pull out four things:

  • People. Named NPCs—mentors, rivals, family, exes. Each one is a guest star waiting for an entrance.
  • Wounds. The unresolved thing. The death they blame themselves for. This is the emotional engine of an entire arc.
  • Loose ends. “I left in the night and never looked back.” Great—so what’s chasing them?
  • Contradictions. A noble’s son with a thief’s skill set. The gap between those two facts is a story.

Most backstories give you three to five of these. With four players, that’s fifteen-plus hooks you didn’t have to write.

The reincorporation move

Improv has a principle called reincorporation: bring back something from earlier and the audience feels the whole thing was designed. Backstories are reincorporation on a campaign scale.

The trick is timing. A backstory beat lands hardest when the player has half-forgotten they wrote it. Sister vanished in the first paragraph of their bio? Don’t open with it. Let them adventure for two months—then have a prisoner pull back her hood. The table will lose its mind.

But that only works if you remember the detail when the moment arrives. And the moment almost always arrives mid-session, while you’re juggling six other things.

The catch (and the fix)

Here’s why this resource stays buried: backstories are long, you read them once, and the relevant line is never the one on top of your mind when you need it.

So you default to generic hooks. The town needs saving. A stranger offers gold. Functional, forgettable.

This is one of the things Loracle is quietly good at. Keep your players’ backstories alongside your session records, and every name, wound, and loose end becomes searchable. When the party captures a cultist mid-session, you can check in seconds whether anyone has history with that cult—and turn a random encounter into a personal one.

The campaign your players actually want is the one they already described to you.

Go read what they wrote. Then make it come true.