30-Day Manuscript Sprint — Only 10 spots left. Apply Now →
Academy

Mystery Writing Guide—Fair Play

12 min read T Tim
Available in: 繁體中文 English العربية Español
Part of series: Genre Writing Masterclass 2 / 5

Most writing advice says to surprise your reader. Mystery fiction flips that on its head -- the best mysteries are the ones where the reader could have figured it out all along.

Think about that for a second. The genre built on secrets and revelation actually demands transparency. Not the kind where the answer is sitting in plain sight, bolded and underlined. The kind where every single piece of the puzzle was available, scattered across the pages, waiting for someone sharp enough to assemble them before the detective does.

Agatha Christie nearly broke this principle with The Murder of Roger Ackroyd. Rich man murdered. Hercule Poirot investigates. Suspects pile up. Standard fare -- until the final pages detonate: the narrator himself is the killer. The entire book is the murderer's journal, and he hid the truth not by lying but by strategically omitting. Silence between sentences. Gaps where confession should have been.

The mystery world split in two. One camp called it genius -- a reinvention of the form. The other called it cheating. A narrator owes honesty to the reader. Hiding facts from your own narration? That crosses a line.

Dorothy L. Sayers settled it with surgical precision: he never lied. He simply did not say everything. Every clue existed in the text. If a reader paid close enough attention, the truth was there before the reveal.

That is the paradox at the heart of mystery writing. The answer must be hidden, and the answer must be findable. The whole genre runs on this impossible balance.

The Fair Play Contract

The 1920s -- the Golden Age. Ronald Knox drafted his "Decalogue." S.S. Van Dine threw down twenty rules. Most of the specifics feel quaint now. Nobody cares about secret passages anymore. But the spirit behind those rules? Unshakable.

One sentence captures it: the reader deserves a fair shot at the answer before the reveal.

Three red lines hold the contract together.

The killer must appear early. A murderer who materializes in the final chapter is not a mystery -- it is a magic trick. Christie's killers almost always show up in the first three chapters. Often as the quietest person in the room. The neighbor sipping tea. The doctor everyone dismissed on page twelve.

What the detective sees, the reader sees. Detectives can interpret better, think faster, notice patterns the reader misses. That is fine. What they cannot do is pull out evidence the reader never encountered. "I actually found a button in the garden three days ago, but I neglected to mention it" -- that sentence murders trust.

Misdirection is fair game. Lying is not. An innocent character who behaves suspiciously? Brilliant. Drawing the reader's attention toward the wrong details? Artful. Exploiting assumptions and biases? Go for it. But writing something objectively false in the narration itself? That is not technique. That is fraud.

Inside these boundaries lives an experience no other genre provides. Mystery readers do not passively absorb story. They compete. They reason alongside the detective, trying to beat the reveal. When the game is fair and they guess wrong, they admire the craft. When the game is rigged -- the difference between being challenged and being cheated is a feeling readers never forget.

Three Levels of Clues

Designing clues might be the most agonizing, addictive work in all of fiction. A good clue lives in contradiction: it must exist so the fairness principle holds, but it cannot be obvious or the puzzle collapses by chapter four.

The solution? Layers.

Surface clues are the ones readers grab immediately. A strand of hair in the victim's fist. A shattered window. A suspect with no alibi. These make readers feel like investigators -- active, engaged, tracking. But surface clues are usually bait. Red herrings. Shiny objects designed to pull attention down the wrong corridor.

Hidden clues do not announce themselves. They sit inside ordinary description, dressed as throwaway details, waiting for the one reader attentive enough to notice. When the truth drops, that reader gasps: "Wait -- chapter three mentioned that." The "of course" moment. Mystery fiction's most addictive hit.

An example. Chapter 3, a dinner scene: "Five people sat around the long table. Mr. Zhang read the newspaper by the window, Miss Li chatted with the person beside her, and Mrs. Wang stirred her coffee with her left hand."

Most eyes slide right past "left hand." But if the killer is left-handed, that detail transforms from background noise into decisive evidence. The reader can flip back and confirm -- the information was always there. Fair. Unquestionably.

Logic clues operate at the highest altitude. They are not physical objects or buried details -- they are questions. Why did the killer choose that specific time? Why was the victim at that location? Why does one witness's testimony contain a strange gap?

Readers who catch logic clues experience something different from ordinary deduction. They reasoned their way to the answer using their own mind. That accomplishment sits on an entirely different level from finding a weapon under the carpet.

Techniques for Hiding Clues

Placing a clue in plain sight while keeping it invisible. Four methods, each with its own brand of cunning.

Dilution. The most basic. The most effective.

A knife needs to exist in the room, but it should not scream its importance. So: "On the desk sat a stack of files, a half-empty coffee mug, a paper knife, three pens, and a succulent that had seen better days." The knife is right there. The reader's eye drifts to the dying succulent and the cold coffee. Perfect camouflage.

Emotional masking exploits a glitch in human cognition: when strong emotion floods a scene, details vanish.

"She crashed through the door, face white as paper, shaking so hard she could barely stand: 'He is dead! God, he is dead!' She collapsed into the sofa. A faint red mark traced across her right wrist."

What does the reader care about? Her terror. Her collapse. Her words. The mark on her wrist? Nine out of ten readers will not register it. But it is there. Patient. Waiting.

Early planting weaponizes the decay curve of memory. The earlier information appears, the faster the brain discards it.

Chapter 15 needs a food allergy to crack the case. So chapter 1 handles it: "She pushed the shrimp back toward the waiter, mentioning she was allergic to seafood." Fourteen chapters later, that allergy becomes the key to everything. Readers can flip back and find it -- but during the read, almost nobody remembers a throwaway detail from the opening pages.

Dispersion is the cruelest technique. It takes a single clue and shatters it into fragments scattered across different chapters.

Each piece means nothing alone. Fragment A: the killer might be left-handed. Fragment B: a certain character was forced to write right-handed as a child. Fragment C: that same character unconsciously picks up chopsticks with the left hand. Three fragments. Chapters 2, 7, and 11. Only when assembled does the picture emerge. Most readers will never connect them -- and that is both the cruelty and the beauty of dispersion.

The Art of Red Herrings

Red herrings -- false clues planted deliberately to drag the reader toward the wrong suspect. Good ones are the soul of mystery fiction. Without them, guessing correctly becomes too easy and the game loses its thrill.

One iron rule: every red herring must have a legitimate explanation.

A character acts suspicious throughout the story. Motive, opportunity, strange behavior -- the whole package. Turns out not to be the killer. Fine. But there must be a reason for all that suspicion. An affair being hidden. A belief that they accidentally caused the death. Covering for a daughter. Something real.

An unexplained red herring is the cheapest form of deception. The reader asks: "So what was that character's deal?" If the answer is "nothing, just misdirection" -- congratulations, the fair play contract just got shredded.

Christie mastered this. Every suspicious character in her novels has a genuine reason for being suspicious. Every one of those reasons gets revealed before the final page. No loose threads. No unexplained behavior. Every line collected and accounted for. Readers feel that completeness -- even if they cannot articulate it.

Managing Your Clue System in Slima

Tracking clues in a mystery novel is logistics warfare. Where each clue appears, what conclusion it points toward, when the reader accumulates enough information to start deducing -- all of it needs monitoring. Worse: every piece of evidence the detective uses in the reveal must have appeared earlier. Miss one, and the entire deductive structure collapses.

Inside the File Tree in Slima's Writing Studio, build a dedicated tracking folder:

Outline/
├── clue-tracking.md
├── suspect-suspicion-levels.md
├── timeline.md
└── reveal-logic.md

Clue Tracking is the nerve center. It logs each clue's type, first appearance, the conclusion it points to, and the chapter after which a reader has enough information to start piecing things together.

Keep the format functional:

| Clue | Type | First Appears | Points To | Deducible After |
|------|------|---------------|-----------|-----------------|
| Mrs. Wang is left-handed | Hidden | Ch.3 | Killer identity | After Ch.10 |
| Window locked from inside | Surface | Ch.2 | Rules out outsider | Immediately |
| Why that time was chosen | Logic | Ch.6 | Accomplice exists | After Ch.12 |

Open a Split Window to keep both the tracking table and the chapter draft visible simultaneously. Every time a clue lands in the manuscript, log it in the table immediately. This single habit prevents the worst mistake in mystery writing: evidence that appears in the reveal but was never planted in the story.

Using AI to Check Fairness

The mystery writer's blind spot is permanent and unavoidable: already knowing the answer.

Knowing who the killer is makes it impossible to read the manuscript the way a first-time reader would. Are the clues hidden well enough? Too well? The author simply cannot judge -- the evaluation requires a mind that does not know the solution.

Open the AI Chat Panel with Cmd+Shift+A (Mac) or Ctrl+Shift+A (Windows) and ask it to role-play as a first-time reader.

Fairness check:

Paste everything except the reveal chapter. Attach this prompt:

Pretend this is your first time reading this story. Based only on clues present in the text, try to deduce the killer's identity.

List:

  1. Who is the most likely killer? Why?
  2. Every clue supporting your reasoning
  3. Questions the story leaves unanswered

Important: use only information that actually appears in the text. No genre conventions, no meta-knowledge.

Interpreting the results: if the AI nails the killer using the right clues -- too obvious, bury deeper. If the AI finds zero evidence pointing to the real culprit -- not fair enough, add more breadcrumbs. The sweet spot: the AI lists the true killer as one of several suspects but cannot confirm. Right between "possible to guess" and "impossible to be sure."

Reveal verification:

After writing the reveal chapter, feed it back:

Examine every piece of evidence the detective uses to identify the killer:

  1. Did this evidence appear in an earlier chapter? Where?
  2. If not, flag it as "information that appeared from nowhere" -- it needs revision.

This catches deus ex machina -- evidence that materializes during the reveal without any prior setup. The most common fatal flaw in mystery writing.

Killer's perspective audit:

Assume the identity of [character name], the killer. Reread the entire story from their perspective and identify:

  1. Actions that are illogical (knowing something but behaving as if they do not)
  2. Moments that should have drawn suspicion but did not
  3. Any contradictions in the crime timeline

Three checks. After all three, holes in the clue system have almost nowhere to hide.

Using Branches to Try Different Killers

Halfway through the draft, a realization hits: a different character would make a far more compelling killer. Or maybe two options seem equally strong and the only way to know is to write both.

The old method -- "Save As" and then drowning in a sea of duplicate files.

Branches in Slima's Version Control solve this cleanly:

main - Killer is the butler
experiment/killer-wife - What if the wife did it?
experiment/killer-partner - What if the business partner did it?

Inside an experiment branch, rearrange clues freely. Rewrite motives. Rebuild the reveal logic. If the new version works better, merge it back into main. If it falls flat, switch back -- everything exactly where it was. Not a word lost.

Mystery puzzle design is inherently iterative. The first version is almost never the right one. Branches make bold experimentation zero-risk, which is -- for a genre that demands precision in every planted detail -- something close to salvation.

Compare branches side by side in the Version Control panel (Cmd+Shift+G) to see exactly which clues moved, which character behaviors changed, and how the reveal logic shifted.


The argument over The Murder of Roger Ackroyd has been running for nearly a century. Some readers still call it cheating. Others call it the most daring innovation in mystery history.

Neither side won. But the argument itself proved something more important than any verdict: mystery readers care about fairness. Deeply. They do not just want to know who did it -- they want a genuine contest of wits. Win, and the pride is real. Lose, but the game was fair -- respect.

That is what sets mystery apart from every other genre. It does not simply tell a story. It invites the reader inside the story, hands them the same evidence, and says: figure it out.

Place every clue where it can be found. Give the reader an honest chance. Then watch them wrestle with the puzzle -- piece by piece, chapter by chapter, until the final page.

That is the best part of writing mystery. The game itself.

Related Articles