Choose Campaign Management Tools Around the Questions Your Next Session Needs to Answer
The session starts in fifteen minutes.
Your players post in the group chat: this time, they want to return to the Gray Hawk Company’s camp instead of entering the dungeon you prepared.
You open your notes from the last session.
The adventurer Lorne handed the moonstone amulet to Ina, the guide.
An NPC named Kairo left the mercenary company and traveled with the party toward the northern ruins.
The party also promised to retrieve a document for the company, but has not done so yet.
All of that was recorded.
Preparing the next session still leaves you with questions, though.
Who holds the amulet now? Is Kairo still a member of the company? Has he left the camp, or is he still there? Has the party fulfilled its promise? Can the negotiation you prepared still happen as planned?
Reducing these checks is often the reason to search for TTRPG campaign management tools.
You might need session notes that are easier to find, clearer worldbuilding records, information you can share with players, or a way to retain character, item, and faction changes without reconstructing them each time.
World Anvil, Kanka, Foundry VTT, and InkWeave can each handle substantial parts of that work.
They differ in how they organize information, show changes, and support play. Separating those tasks first is more useful than asking which application has the most features.
Session Notes, Worldbuilding, Virtual Tabletops, and World State Are Different Tasks
A campaign tool can offer many features at once.
The GM’s work still falls into several distinct areas.
| What you need to do | Typical questions |
|---|---|
| Keep session notes | Where did the party go, whom did they speak to, and what happened? |
| Organize worldbuilding records | Who is this NPC? Who belongs to this organization? |
| Run the game | How are character sheets, maps, tokens, and dice handled? |
| Share information with players | What can be public, and which secrets should remain GM-only? |
| Maintain world state | Who holds the item now? Where is the character? Which conditions have changed? |
| Trace and validate changes | Where did this state come from? After an earlier event is revised, do later events still hold up? |
These are not mutually exclusive categories of software.
Some campaign managers also provide character sheets. Virtual tabletops can store notes. InkWeave can write session records and manage worldbuilding information; it is not merely a checker you run after the story is finished.
The useful comparison is how much work the GM must do between creating a record, changing it, and using it again.
Having an item page is different from knowing who currently holds the item.
Returning to a point three sessions earlier and finding out who held it then is another capability again.
A feature list containing items, characters, and timelines does not mean every tool handles them the same way.
How Do World Anvil, Kanka, Foundry VTT, and InkWeave Manage a Campaign?
Start with their main workflows and payment models.
| Tool | How information is organized and used | Payment model | What to check |
|---|---|---|---|
| World Anvil | World articles and campaign management features on a website | Free tier and paid memberships | Membership requirements for private content, advanced diagrams, and sharing permissions |
| Kanka | Linked entries for characters, organizations, items, quests, journals, and other records | Free core features, with subscriptions for advanced campaign features | Member roles and permissions, advanced relationship views, and any paid features you need |
| Foundry VTT | A self-hosted or hosted game world that players join through a browser | A one-time software purchase; hosting or additional content may cost extra | Game systems, module compatibility, and your hosting setup |
| InkWeave | A local project combining manuscript text, chapters, world data, and events | Free manuscript editing and export; Pro provides world tracking and the Causality Engine | Pro licensing, how events are recorded, and the virtual tabletop features it does not provide |
Plans and features can change. Check the current version before purchasing.
World Anvil: Connecting Worldbuilding Records with Campaign Work
World Anvil is more than a website for publicly presenting a fictional world.
GMs can use articles to organize NPCs, locations, organizations, and background information. Campaign management features support session preparation, character management, scheduling, and session reports.
Its GM reference interface brings worldbuilding material, campaign notes, and character information together for use during play.
Maps, timelines, and other worldbuilding tools are available too. Feature access and private-content permissions depend on the membership plan.
For the Gray Hawk Company example, you could maintain an organization article, Kairo’s record, and the relevant session reports, then link them together.
That keeps related information from becoming a collection of disconnected documents.
Kanka: Linking NPCs, Inventories, Organizations, and Quests
Kanka focuses on worldbuilding and TTRPG campaign management.
Its entry types include characters, locations, organizations, items, quests, journals, calendars, and timelines. It also provides inventory and relationship features.
It should not be treated as an encyclopedia that only stores character descriptions.
GMs can record possessions, organizational relationships, and quest progress. They can also invite players and control visibility through roles and permissions.
In this example, the amulet can be an item, the Gray Hawk Company an organization, the document retrieval a quest, and Kairo a character connected to those records.
That structure helps GMs consult related information and lets players participate in maintaining it.
Foundry VTT: Working with Characters and Session Information Inside the Game Environment
Foundry VTT is a virtual tabletop, but it does more than display maps.
It also provides character and item records, journal entries, document links, and ways to show material to selected players.
The character sheets and rules automation available depend on the installed game system and modules.
In this example, you could manage the amulet and character records inside the game environment, retain notes from the last session, and reveal specific information to players.
Its distinguishing feature is how closely the information sits alongside the actual operation of the game.
When comparing Foundry, consider your hosting arrangement, game system, and modules as well as the names of its built-in features.
InkWeave: Making Confirmed Events in Session Notes the Source of World State
InkWeave can use manuscript text and chapters to preserve session notes. It also supports characters, items, locations, factions, relationships, and custom attributes.
Its distinction is that confirmed events within that text can change the state of those records.
Lorne handing the amulet to Ina can become an item-transfer event, not just a sentence describing one.
Kairo leaving the company can become a faction-membership change. His journey to the ruins can become a movement event.
InkWeave’s self-developed Causality Engine derives world state from those events in their recorded causal order.
The GM can therefore do more than open the latest record. They can return to a particular point and see the world as it stood then.
Use the Same Session to Test Whether a Tool Can Answer the Next One
Do not compare tools only through empty projects.
Use something that actually happened in your campaign. The differences become easier to see.
For the Gray Hawk Company example, the next session needs at least these answers.
| Confirmed result | What the next session needs to reflect | What you cannot automatically assume |
|---|---|---|
| Lorne handed the amulet to Ina | Ina now holds the amulet | Lorne can still produce it whenever he needs it |
| Kairo left the company | He is no longer a member of that organization | Everyone in the company already knows he has left |
| Kairo traveled with the party to the ruins | He has left the original camp | He will still be standing there when the party returns |
| The party promised to retrieve a document | The promise was made, but the completion condition has not been met | The quest is complete because it appeared in a plan |
All four tools can preserve this information.
The next test is how you obtain the answers.
Which records do you have to open? How are item and character records updated? Can you trace the change? When you look before the last session, do you see the latest result or the state at that earlier point?
If an earlier result is revised, must you check every later reference manually?
These questions are closer to the GM’s actual work than “Does it have session notes?”
Also distinguish world facts from what characters know.
Kairo really leaving does not mean everyone in the company immediately learns about it. Ina receiving the amulet does not mean every party member witnessed the handover.
If those information differences need tracking, the GM must explicitly establish the relevant states. “It was written in the session notes” is not the same as “every character knows.”
You Do Not Have to Move the Whole Campaign into InkWeave
Trying a campaign management tool can feel daunting if it appears to require every NPC, every location, and years of session notes before you can begin.
InkWeave does not require that preparation.
Start with Lorne, Ina, and the moonstone amulet. Test one real transfer.
Create the necessary characters and item, confirm the amulet’s earlier acquisition, and record the handover where it happens.
Then place the cursor before and after the transfer to see how possession changes.
That is already enough to try working with the text and world together.
Once familiar with it, add Kairo, the company, and the ruins.
If you need to track the document assignment, you can establish progress states such as “accepted,” “retrieved,” and “delivered.”
Each step corresponds to information you need now. You do not have to design a large logic table for the entire campaign first.
Your older session notes can remain intact.
If you later want to inspect earlier world states, gradually add the important events needed to reconstruct them. The Causality Engine will not fill in unrecorded history by itself, but getting started does not require turning every past conversation into data.
Characters and Locations Can Respond While You Write Your Session Notes
In InkWeave, established characters, items, and locations are more than searchable names.
The scene-aware panel and Inspector can display relevant state at the cursor’s position in the story.
Write about Ina, and you can check her location and possessions then. Write about the moonstone amulet, and you can check where it has gone. Write about the Gray Hawk Company, and you can inspect its membership and organizational structure at that point.
Images added to characters, items, or locations can also provide visual feedback as you work on the session notes.
You are not left facing a page of text while trying to recall every person and scene from that evening. The world elements your players interacted with can appear alongside the writing, carrying the results recorded so far.
When a character and item appear close together in the text, an event helper can use the current state to ask whether an acquisition, placement, or transfer occurs.
When a character and location appear together, you can check the character’s position and decide whether to record movement.
This does not require a form for every sentence.
Mentioning the amulet does not necessarily transfer it. Remembering the camp does not mean a character has returned there.
Consult and confirm when needed; otherwise, keep writing. The world provides feedback without deciding what happened at the table.
Find the Current State and Trace the Events That Created It
Knowing that Ina holds the amulet is useful before the session.
When players ask how she obtained it, the transfer history matters too.
The Inspector offers different kinds of history queries alongside the state at the current story position.
You can inspect an item’s chain of possession, the places a character has visited, and events in which they joined or left a faction.
Character relationships and organizational structures do not have to remain fixed in a diagram that always shows the latest version.
Before Kairo’s departure, he is still a member of the Gray Hawk Company. After it, the organization should reflect the change.
Those answers come from the same recorded event history, rather than several independent tables the GM must maintain separately.
Session notes can be divided into chapters by session, but events should still follow their causal order within the story. The real-world date you played does not automatically determine which event happened first in the fictional world.
You can know where things stand now and return to the history that brought them there.
Revise an Earlier Result, and the Causality Engine Can Identify Later Events That Lose Their Prerequisites
Suppose you discover a mistake while organizing the notes.
Lorne never acquired the moonstone amulet. He saw it, but ultimately left it where it was.
Changing that passage alone might leave the later transfer untouched. The next session might still treat the amulet as Ina’s possession.
In InkWeave, removing the recorded acquisition means the later transfer must be validated again.
Lorne cannot hand over an amulet he did not hold at that point.
This is not AI reading the notes and deciding that something “seems inconsistent.”
It is InkWeave’s self-developed Causality Engine calculating from explicit event order, possession quantities, and state rules.
If a character holds one amulet and transfers one, they no longer hold it. If they never acquired it, the transfer has no source.
These are mathematical checks of state and quantity, not a language model’s interpretation of the story.
After the revision is saved, the Causality Engine validates the sequence again. Relevant issues appear at the event location and in the project-wide validation dashboard, helping the GM find what needs attention.
The document assignment can work similarly.
If a later reward requires the document to have been delivered, you can explicitly establish that condition. If it remains unmet when the notes reach the reward event, the Causality Engine can identify the missing prerequisite.
It will not quietly mark the quest complete to keep the plot moving.
You can add an event that actually happened, change the later requirements, or accept that the reward cannot yet be given.
Validation covers the entities, events, and conditions you have established. Information, motives, and emotions that have not been explicitly modeled do not become verifiable data merely because they appear in ordinary prose.
Campaign Management Also Includes How Players Receive Information
The GM’s records and the material players can see are not necessarily the same.
Complete session notes may include unrevealed NPC motives, enemy actions, and future plans.
A tool comparison should therefore include who can see what and how information reaches the players.
World Anvil provides ways to share world and campaign material. Check the membership requirements for private content and advanced permissions.
Kanka lets you invite members and control viewing and editing access through roles.
Foundry can show journal entries or individual pages to selected players.
InkWeave is a local writing environment. It can organize the GM’s session notes, worldbuilding information, and world state, then export manuscript text from selected chapters or other scopes.
That does not make InkWeave a campaign website where players log in with individual viewing permissions.
Before exporting material for players, the GM must check it for secrets.
Likewise, using InkWeave alongside another campaign tool does not mean character sheets, items, and events automatically synchronize between them.
Understand data exchange through the features that actually exist. Two applications supporting character management does not mean they are already connected.
Test Whether the Tool Reduces Checks Before Your Next Session
You do not need to test a hundred features first.
Choose something that happened in play and will affect the next session.
| Test | Questions to ask |
|---|---|
| NPC lookup | How quickly can you find Kairo’s information when a player unexpectedly mentions him? |
| Item management | Can you establish who currently holds the amulet? |
| Faction management | Can you see membership and organizational structure after Kairo leaves? |
| History queries | Can you find the events behind the amulet transfer and character movement? |
| Condition tracking | Can you distinguish an accepted assignment from a completed one? |
| Revision checks | After withdrawing an earlier acquisition, can you find the affected later events? |
| Player information | Can you share material in the way you need while keeping secrets private? |
Do not judge only whether the final answer is correct. Consider whether getting to it fits how you work.
Do you have to move between many pages? Is it easy to mistake prepared material for confirmed events? After changing one thing, how much must you check again?
A tool’s value is not limited to storing more information.
It can also reduce repeated checks before and during play, leaving more attention for the players.
Frequently Asked Questions About Managing a Campaign in InkWeave
Can InkWeave Be Used for D&D and Call of Cthulhu?
Yes. It can organize session notes, worldbuilding records, and confirmed changes in state.
D&D items, character locations, factions, and progression can be established and recorded as needed.
Physical clues, character states, and investigation conditions in Call of Cthulhu can use appropriate items, attributes, and flags.
InkWeave does not automatically execute either game’s complete rules. Nor does it infer from session notes how much information an investigator has understood.
Can It Replace a Dice Tool or Virtual Tabletop?
InkWeave does not provide a virtual tabletop like Foundry VTT, and it does not handle dice rolling or combat adjudication.
It works with manuscript text, session notes, world data, and the changes left by confirmed outcomes.
It can still be the GM’s main writing environment for preparing and managing a campaign. That does not mean unrelated tabletop features are included.
Does Every Dice Roll Need an Event?
No.
If a failed roll has no effect on later play, it can remain in the narrative record.
If it causes an item to be lost, a character to move, alertness to rise, or a resource to be spent, record the result that needs to continue counting.
The Causality Engine’s focus is not how many times the dice were rolled. It is what changed because of the outcome.
Can Character Progression and Attribute Changes Be Recorded?
Yes. You can define character identities and custom attributes, then record their changes.
Health, Sanity, stress, and other resources can be tracked once explicitly defined. Race, class, and identity changes can also remain tied to the points where they happen.
D&D leveling and multiclass eligibility, or Call of Cthulhu checks, still depend on the rules and the GM. The Causality Engine does not execute the entire game system for you.
Which Features Require Pro?
You can start with Free for manuscript editing, chapter management, and export.
World entity management, scene-aware features, history tracking, and the Causality Engine require Pro.
Projects are stored locally. Pro includes a limited offline grace period and still requires periodic online license verification.
A Good Campaign Management Tool Makes the Next Session Easier to Start
World Anvil, Kanka, Foundry VTT, and InkWeave are not single-purpose tools.
They preserve session records, organize information, and support GMs in different ways.
The useful comparison is not merely how many entries you can create.
After players hand over the amulet, an NPC leaves a faction, or the party changes its plans, can the tool help you carry those confirmed results forward?
InkWeave brings session notes and world data into the same writing environment.
You record events, and the Causality Engine derives their state.
You revisit earlier passages, and the scene-aware panel and Inspector show the world as it stood then.
You revise an earlier result, and validation shows which later events need attention.
That does not decide the story for the GM. It means the GM does not have to reconstruct the world from scattered notes before every session.
Start with InkWeave Downloads and Pricing, then use the Getting Started Guide to create the characters, locations, and items you currently need.
Try one movement or one transfer from the last session. You do not have to move the entire campaign first.
The next time a player suddenly says, “We want to go back and find that person,” you can know more clearly where they are, what they carry, and which organization they no longer belong to.