Character Keeper Sheets for Solo RPGs
Build a character keeper sheet that tracks motives, promises, scars, inventory, relationships, and unresolved questions without slowing solo play.

A character keeper sheet is not only a stat sheet. In solo play, it is the place where the character becomes easy to return to: what they want, what they promised, what hurt, what they carry, who matters, what changed, and what question still points forward.
Keep Fewer Fields
Start with six fields: name or role, current want, useful strength, costly habit, important connection, and open question. Add game statistics only where the rules require them. If the official game has a sheet, use it as intended, then add a small private keeper note beside it rather than copying or redesigning protected forms for public use.
The keeper sheet is allowed to be plain. A half-page with large boxes may work better than a beautiful dense spread.
Keep the game’s required numbers, conditions, equipment, and progress wherever its rules tell you to track them. The keeper can point to that sheet rather than duplicating every value; if you do copy a changing number, decide which copy is authoritative and update both together. For example, the Ironsworn digital edition includes a character sheet and worksheets in its playkit. Your own game may need different records.
Make a Half-Page Keeper
Copy these prompts onto paper or into a note. Leave room to change the answers, and leave a field blank until it becomes useful.
Name / role:
Current want:
Strength / costly habit:
Connection: What has changed between us?
Promise or obligation: To whom? What would fulfill it?
Important item or condition:
Open question:
Next time, this character will:
Rules sheet or other records kept at:
The item or condition can be a broken lantern, a limited supply, or a scar that affects a decision. Record exact quantities and mechanical effects on the rules sheet when the game requires them. For a recurring person, a name and one sentence about the relationship are enough; expand it into a relationship web if the cast grows.
Track Changes, Not Everything
After each session, change one to three items. A promise was made. A tool was lost. A location became unsafe. A relationship warmed. A scar matters. A question moved from mystery to answer. These changes are more useful than a full recap because they help the next decision.
Update any required game state first, even if more than three things changed. Then choose one to three story details that will matter next time. Cross out a fulfilled promise or answered question and note its outcome briefly; replace it when a new one matters. If nothing changed, leave the field alone. A separate campaign log can hold the sequence of events while the keeper shows the current state.
For example, a courier begins wanting to reach the town, carrying a working lantern, and owing no one a favor. At the gate, she promises the guard she will deliver a message; on the road inside, her lantern breaks. The update might be:
Current want: Find the message's recipient before the market closes.
Connection: Gate guard trusts me with a delivery.
Promise: Deliver the guard's message to its recipient.
Important item: Lantern broken; repair or replace it.
Open question: Who is the message for?
Next time, this character will ask at the market.
If the game tracks the lantern or a resource mechanically, update that record too. The example leaves the recipient unknown instead of silently inventing an answer; discover or choose it when it matters in play.
If you are playing a cozy journaling game, keep emotional changes light and consent-aware. If a prompt pushes into content you do not want, move the change to an object, place, or relationship boundary.
Make It Accessible
Use high contrast, large writing, symbols, or color zones. If handwriting is hard, use index cards, sticky labels, voice notes, or a digital note alongside the analog table. Accessibility tools do not make the session less analog. They make the table usable.
For longer campaigns, keep one “current state” card in front and archive older sheets behind it. You should not have to read the whole campaign to remember what the character wants tonight.
Date the card or note the last session, so an older version is not mistaken for the current one. If a value is missing when you return, check the rules sheet or log. Otherwise, return to a known checkpoint or choose a plausible value and mark it as reconstructed, especially if it affects a later outcome.
Add a Restart Line
End every update with one sentence: “Next time, this character will…” Make it physical or fictional enough to start from: open the sealed letter, ask the innkeeper about the bridge, check the western path, repair the lantern, apologize to Mara.
That line is the character’s return point. It turns the sheet from a record into a playable object.
At the start of the next session, read the want, the relevant connection or obligation, and the restart line. Begin with that action, or revise it if the character’s circumstances have changed. You can keep sensitive notes private or use a brief label instead of writing details you do not want to preserve; the photo-free recap guide offers other ways to remember a session.
Related
Written By
JJ Ben-Joseph
Founder and CEO · TensorSpace
Founder and CEO of TensorSpace and the editor of Fondsites: an engineer working across software, AI, cybersecurity, and biosecurity who builds the site's games and tools.