Guide / Worldbuilding Template

A worldbuilding template for your characters, places, and lore

Every long-running story ends up with the same problem: characters, locations, factions, and lore that need tracking somewhere outside the manuscript. Most writers reach for a spreadsheet or a Notion doc first. Here’s what actually belongs in one, and where it starts to strain once a story grows past a single book.

Characters

The fields worth a column of their own, whatever tool you use:

Name + aliases

Nicknames, titles, what other characters call them

Role

Protagonist, antagonist, supporting — whatever taxonomy you use

Description

Physical description, voice, mannerisms

Relationships

To whom, and what kind — ally, rival, family, romantic, enemy

Tags

POV character, Book 1 only, whatever you need to filter by later

Backstory & notes

The long-form stuff a single cell can’t hold

Appears in

Which chapters actually mention them — tedious to track by hand

Locations

Locations need less structure than characters — most of the work is in the description, not the metadata:

Name + aliases

Including any name that changes across books or POVs

Description

Atmosphere, geography, what a reader should picture

Who lives or rules there

Ties back to your character list

Connected locations

Travel time, borders, who can reach whom

Factions & organizations

Houses, orders, guilds, alliances — anything a character can belong to, and that has its own goals independent of any one member:

Name + aliases

A house, order, guild, or alliance often has more than one name in-world

Description

Purpose, structure, what they want

Members

Which characters belong — and, sometimes, which locations

Allies & rivals

Other factions, and the shape of the relationship

Lore

Magic systems, history, religion, politics — the world-level facts that don’t belong to any one character or place:

Title

Magic system, a historical event, a religion — whatever needs its own page

Category

A tag or heading so it’s not one undifferentiated pile

Content

The rules, so book three doesn’t contradict book one

Where a spreadsheet starts to strain

A spreadsheet or a Notion doc will get you through book one. The trouble shows up later, and it’s always the same three shapes:

Nothing is linked to anything. A “member of the Northern Compact” cell doesn’t know that faction exists as an entity — rename it, and every cell that names it is silently wrong until you find and fix each one by hand.

It doesn’t know the manuscript. Whether a character actually appears in chapter 12 is something you have to remember and go check — the spreadsheet has no idea what you’ve written, so “appears in” is either maintained by hand or not tracked at all.

It doesn’t scale across a series. One sheet becomes one tab per book, or one giant sheet with no way to see “just what’s relevant to the book I’m drafting now” without scrolling past everything else.

The same categories, in InkSpine

InkSpine keeps the same categories — characters, locations, factions, lore — as structured data scoped to the whole series, not just one book, alongside a free-form notes page per entity for the backstory and detail a single field can’t hold. Not every field above gets a form of its own: characters and factions carry aliases, tags, and membership as real fields, while a location is deliberately thinner — a name and a description, with who lives there and what it borders written in its notes page rather than typed into a form. Two differences from a spreadsheet:

1. Links point at the entity, not at a copy of its name. Faction membership is stored on the faction and editable from either side — a character’s page or the faction’s — and an @ reference in the manuscript resolves to the entity itself. Rename a character and both stay correct.
2. “Appears in” is computed from what you’ve actually written, not maintained by hand. Type @ in the manuscript for an explicit reference, or just write a name in ordinary prose — the editor detects it either way and links it back to that character, location, faction, or lore entry.

Because worldbuilding belongs to the series rather than to one book, there’s no tab-per-book duplication to keep in sync — every book draws on the same characters, locations, and factions. And all of it lives as plain Markdown and JSON files on your own disk — readable without InkSpine, forever.

Being straight with you

InkSpine is in private beta, built by one novelist writing their own book in it. The template above works in any spreadsheet or notes app today, no InkSpine required — join the beta when you’re ready for it to stop being separate from the manuscript.