Solo Call of Cthulhu: Playing CoC Alone

Introduction

Call of Cthulhu 7e is built for a Keeper and a group, but many players want to explore an investigation on their own. Solo play can work well if you are honest about what the core books cover and what extra tools you have to bring. This guide explains that boundary, then gives you a repeatable procedure for running a solo case.

Scope First

The core Call of Cthulhu 7e table structure assumes a Keeper and one or more investigator players. The available core sources do not provide a complete solo-play engine, so this is not a replacement for a dedicated solo product or a Keeper-run game.

You can still use CoC material for personal scenario notes, investigator journals, preparation, or a solo framework you already trust. What matters is separating the core game's rules from the extra procedure that decides unknown facts and keeps you from simply writing the answer you want.

This guide uses the word oracle for any neutral method that answers a question you do not want to decide yourself: a tool from a dedicated solo game, a random table, shuffled prompts, or questions prepared before play. An oracle sits outside the Call of Cthulhu 7e rules. It is the extra tool that temporarily performs part of the Keeper's job.

Solo CoC works best when you want to inhabit an investigation, record an investigator's perspective, and be surprised by consequences. It works less well when your main goal is the social energy of a group, a Keeper's performance, or a fully hidden plot created by someone else.

Hot Take

Solo CoC is strongest as an investigation journal with a surprise procedure, not as a way to simulate a perfect Keeper. An oracle can create uncertainty, but it cannot replace the social improvisation and hidden preparation that make a Keeper-run game distinct.

Use solo play to test a character, explore a compact case, or practice turning clues into decisions. Keep the questions narrow, make the method decide unknown facts before you know the answer, and accept complications that alter the next scene. That approach makes the solo experience honest without pretending that the core game contains rules it does not provide.

What Solo CoC Can Do Well

• Build and test an investigator concept before bringing it to a group.
• Write a first-person investigator journal between sessions.
• Prepare a location, NPC web, or clue map from the Keeper side.
• Explore a published solo framework that you have independently chosen and understand.
• Practice the rhythm of asking questions, following leads, making percentile rolls, and accepting consequences.
• Play a small personal case in which a single investigator's profession, relationships, and fears are the center of the story.

The strongest solo cases are compact. A missing colleague, an unusual inheritance, a disturbing letter, a suspicious death, or a request from a trusted contact gives you a human reason to investigate without requiring a city-wide conspiracy. You can discover a larger pattern later. Start with one question that matters to the investigator now.

Avoid treating solo play as a way to "win" a prewritten mystery. Since you are both the audience and the person operating the procedure, the reward comes from following the evidence honestly. A surprising complication, an ugly choice, or a narrow escape is more valuable than proving that your investigator was right from the first page.

What You Need

You do not need a giant setting bible, a custom solo subsystem, or a fully plotted villain before the first scene. In fact, over-preparing the answers removes the mystery. Prepare the pressure around the case and let the procedure decide where that pressure points.

The Solo Investigation Loop

At a table, the Keeper presents a situation, players state what they do, and the Keeper describes the result. Solo play needs to make each of those steps explicit so you do not silently skip from question to desired answer.

Use this loop for every meaningful scene:

1. Frame the situation. Write where the investigator is, what they want from the scene, and what makes the attempt risky or uncertain.
2. Choose an approach. State an action in the fiction before naming a skill: question the mortician, examine the photograph, search the basement, or follow the car.
3. Ask only the unknown question. If the answer is obvious from established facts, decide it. If it should be hidden or surprising, use the oracle.
4. Roll when success is uncertain and failure matters. Use the CoC skill or characteristic that fits the stated approach. Do not turn every descriptive action into a roll.
5. Record the outcome. Add a fact, a cost, a new lead, a deadline, or a changed relationship to your notes.
6. Choose the next lead. End the scene by identifying the new question rather than by writing a conclusion.

This is the same fundamental habit as group CoC: investigate, make a meaningful decision, resolve uncertainty, and live with the consequences. The oracle fills a gap in authorship. It should not replace ordinary reasoning or the rules for actions your investigator attempts.

For the group-game version of that loop, see How To Play Call of Cthulhu 7e. For a refresher on when and how to use percentile dice, use the Call of Cthulhu Dice Guide.

Prepare Questions, Not Answers

Before the first scene, write a case frame with questions instead of a solution. The questions give your oracle somewhere useful to create uncertainty.

This distinction protects you from two common solo problems. If you prep every answer, you are writing fiction with occasional dice rolls. If you prep nothing, you have no meaningful question to investigate. A few known facts and several real unknowns give the case structure without making it predictable.

Keep the opening grounded. "Why did my mentor mail me a torn photograph the night before disappearing?" is better than "What is the complete secret history of this eldritch cult?" The first question gives you a person, an object, a time pressure, and a reason to visit places. The second is a useful long-term question, but it does not tell you what to do in the first ten minutes.

Keep The Mystery Honest

Solo horror needs a way to produce surprises. Use a neutral oracle, random tables from a product designed for that purpose, or a prepared set of branching questions. Decide the procedure before you know the answer. Otherwise every ominous door leads to exactly the clue your investigator hoped to find, which is efficient but not especially mysterious.

Keep a record of facts, unanswered questions, risks, and consequences. Let failed rolls change the situation. A solo investigation becomes more compelling when it can create a bad turn that you did not author out of existence.

Use three categories in your notes:

• Facts: Things established by a scene, a roll, or an oracle result. Mark the source when useful: "Fact: the telegram was sent from Arkham."
• Theories: Interpretations that might be wrong. "Theory: the sender is trying to lure me to the cemetery."
• Open questions: Specific unknowns that can drive the next scene. "Who had access to the telegraph office after midnight?"

Do not promote a theory to a fact because it would make a neat story. Let later evidence confirm, complicate, or destroy it. This rule gives a solo mystery the feeling of discovery.

Set The Question Before Consulting The Oracle

Weak question: "Does something interesting happen?"

Useful question: "Is the caretaker still at the house when I arrive?" or "Did the missing professor leave a record at the library?"

The narrower question produces an answer you can act on. It also keeps the oracle from taking over the entire scene. If a result is ambiguous, choose the interpretation that creates a concrete decision, not the most elaborate revelation.

Give Bad Results Direction

A failed roll should rarely erase the reason for a scene. Instead, let it create a complication: the witness refuses to cooperate, a search takes too long, the investigator is seen, the evidence is damaged, or an existing danger gets closer. The investigator may not get every detail, but play should still move toward a choice.

This is especially important in solo play because there is no other player to propose a rescue plan while you stare at a dead end. Preserve the forward motion, then make the cost matter.

Run A Scene

Use the following compact procedure when you sit down to play. It works for a five-minute journal entry or a longer investigation scene.

1. Set the scene in one sentence. "At dusk, I visit the university archive to inspect Professor Hale's last request."
2. Write the immediate aim. "I want to learn which files Hale consulted."
3. Name the obstacle. The archivist may be protective, the records may be restricted, or time may be short.
4. State the approach and make any needed CoC roll. Describe the action first, then use the relevant skill if the result is uncertain and important.
5. Consult the oracle only for hidden setting facts. Is the access log missing? Is the archivist lying? Is there a second person in the building?
6. Apply a consequence. A result should change what the investigator knows, risks, owes, fears, or must do next.
7. End with a lead. Write the next question before closing the notebook.

If a scene feels flat, do not add random violence just to force momentum. Add pressure connected to the case: a deadline, a suspicious observer, a contradiction in the evidence, a frightened contact, or an ordinary institution that will not cooperate. The horror becomes stronger when it intrudes on a believable investigation.

Protect The Clue Trail

In a Keeper-run scenario, the Keeper can redirect the group when a clue is overlooked. Solo play needs a visible structure that prevents a single bad roll or mistaken theory from ending the case.

For every major question, create at least two possible ways to pursue it. If you need to learn where a missing person went, you might check their room, speak to a colleague, inspect travel records, or ask a family member. You do not need to know in advance which route holds the answer. You only need enough avenues that a complication changes the plan instead of ending it.

Use a clue ledger with four columns:

At the end of each scene, update the ledger and pick one next action. When you are unsure what to do, choose the lead with the most immediate human stake or time pressure. Do not wait for a perfect solution to form.

Build The Right Investigator

A solo investigator needs reasons to go places and ask questions. Their occupation, personal history, contacts, and obligations therefore matter even more than usual. A character who is only a collection of strong skills can solve rolls but may have no emotional route into the case.

Give the investigator:

• A profession or expertise that naturally grants access to people, records, places, or tools.
• A personal connection to the opening hook: friendship, duty, curiosity, debt, grief, reputation, or fear.
• One ordinary relationship that can become a source of help, pressure, or loss.
• A limit they would rather not cross, even when the case becomes frightening.
• A practical reason to keep investigating after the first unsettling discovery.

Do not make the investigator a lone superhero. They can ask for help, call contacts, hire assistance, consult an expert, and temporarily work with non-player characters. Solo play is about one player's perspective, not necessarily one person doing every task alone.

The Getting Started Guide explains the wider investigator mindset, while What Is Call of Cthulhu? covers the game's human-scale premise.

Use Horror Boundaries Privately

Safety tools still matter when no one else is at the table. You may discover that a subject is more unpleasant to write alone than it sounded in a session pitch. Decide what belongs outside the case, what can exist only off-screen, and what kind of horror you want to emphasize.

One useful private note has three lines:

• Exclude: Material that does not belong in the game at all.
• Fade out: Material that may exist but never needs detailed description.
• Focus: The kind of tension you actively want: isolation, forbidden knowledge, institutional indifference, body horror, a threatening environment, or something else.

Revisit that note whenever the oracle produces a result you do not want to develop. You do not need to accept a prompt just because it was random. Change the result into a different complication, reroll, or close the scene. Your aim is honest uncertainty inside your own boundaries, not self-inflicted discomfort.

A Short Example

Case frame: A medical examiner receives a final note from a former colleague: "Do not let them take the specimen." The colleague has vanished. The investigator wants to learn what specimen is meant and whether the colleague is still alive.

Opening lead: The colleague's office at the hospital. The investigator wants to locate the case file mentioned in the note. The known pressure is that the office will be sealed in the morning.

Scene question: Is the office already being watched? This is a hidden setting fact, so consult the oracle before deciding how the arrival feels.

Action: The investigator approaches through the employee entrance and tries to identify who is near the office before entering. If the situation makes success uncertain and consequential, resolve that attempt using the appropriate CoC skill. Record what follows rather than narrating past it.

Outcome: Whether the investigator finds a watcher, an empty corridor, or an unexpected colleague, the scene should produce a next step you can act on. The case file may point to a shipping company, a mortuary record, or an address. A bad result might mean security now knows the investigator entered the building. The case advances, but the cost changes the next decision.

Notice what was not decided in advance: who is watching, what the specimen is, whether the missing colleague is victim or accomplice, and how far the threat reaches. Those are discoveries for play.

Your First Solo Session

Keep the first session short: one hook, two or three leads, and one hour of real time. Aim to establish a procedure you trust rather than to complete an epic campaign.

1. Create one investigator with a personal connection to a small disturbance.
2. Write one opening question and two possible leads.
3. Choose and write down one oracle method before you begin.
4. Set your private horror boundaries.
5. Play one scene using the solo investigation loop.
6. End by updating your facts, theories, open questions, and clue ledger.
7. Write the first sentence of the next scene before stopping.

Best First Step

If you are new to Call of Cthulhu, play or watch a Keeper-led session first. You will learn the rhythm of clue delivery, Keeper rulings, character interaction, and escalating pressure faster than you will by trying to recreate every role alone.

Start with the Getting Started Guide, then read the Quick Start Guide for a first-session structure. Use solo play as a supplement to that foundation, not a substitute for a dedicated solo product or a Keeper-run game.