Answer a series of questions about your clues, suspects, red herrings, pacing, and final reveal. You'll receive a balance report showing which parts of the mystery may need another look. You won't be asked to enter any story details, and your answers stay in your browser.

This assessment is designed for stories built around a mystery that the reader is invited to consider. It may be less applicable to crime novels in which the culprit is revealed at the beginning.

You'll answer 24 short questions, organized into six categories:

  • Core Mystery
  • Clue Trail
  • Suspect Balance
  • Red Herrings
  • Pacing and Revelation
  • Solution and Fair Play

Takes about 6–9 minutes. One category per screen, with a progress bar the whole way through. Any question that doesn't apply to your story can be marked “Not applicable” instead of forced into a score.

Your answers are scored entirely in your browser and are never sent anywhere. No email, account, or manuscript text required. In-progress answers are saved in this browser's local storage so a refresh won't lose your place — you can clear them any time from the results screen.

About the Mystery Clue Balance Checker

This checker is built for writers who have a mystery drafted, or well underway, and want to evaluate whether the clues, suspects, and reveal work together fairly. It asks specific questions about how your evidence is distributed and how your solution holds up, then scores your answers to surface the areas most likely to need attention.

What does "clue balance" mean?

A balanced mystery gives the reader a real chance to solve it without making the answer obvious. That means essential clues appear before the reveal, suspects are developed enough to be plausible, and the solution follows from evidence rather than a lucky guess or information withheld until the end.

What's the difference between a clue and a red herring?

A clue is a piece of evidence that, correctly interpreted, points toward the truth. A red herring is a piece of evidence or behavior that looks suspicious but ultimately points away from the solution. Good mysteries need both, but a red herring works best when it has its own honest explanation rather than existing purely to mislead.

Why should false leads arise from believable circumstances?

A red herring that depends on a character acting strangely for no reason, or on the writer simply withholding information, tends to feel like cheating once the reader looks back. A red herring grounded in a real secret, motive, or misunderstanding still makes sense on a second read, even after the reader knows it wasn't the answer.

What does "fair play" mean?

In general terms, a fair-play mystery gives the reader access to the same essential information the sleuth uses to solve the case. The reader may not notice every clue, but nothing required for the solution should be invented, withheld, or introduced only after the reveal.

Why should the culprit be surprising but understandable afterward?

A culprit who's obvious from the first chapter removes the tension of not knowing. A culprit who comes out of nowhere feels unearned. The strongest reveals surprise the reader in the moment, then hold up on reflection, because the motive, opportunity, and behavior were quietly in place all along.

Why do beta-reader responses still matter?

This checker works from your own answers about your manuscript, not the manuscript itself. You know what you intended; a reader only knows what's on the page. Beta readers can confirm whether clues actually read as clues, whether a red herring actually misdirects, and when they first suspected the culprit.

Which mystery subgenres can use this?

Cozy mystery, traditional mystery, amateur sleuth, police procedural, historical mystery, paranormal mystery, private investigator stories, and crime or suspense novels built around a central mystery the reader is invited to solve. It's less suited to stories where the culprit is revealed to the reader upfront.

Is this actually private?

Yes. Nothing you enter here is uploaded, tracked, or stored on a server. Scoring happens with JavaScript running in your own browser, and no story details, character names, or manuscript text are ever requested.