How to critique a novel chapter in 40 minutes

You can critique a novel chapter properly, in forty minutes, and have the writer coming back for more. Most critiques take twice that long and get ignored. The problem is rarely a shortage of opinions. It is that the reader collects the wrong evidence, in the wrong order, and ends up writing a review instead of a set of instructions.

Here is the difference, on the same chapter, from the same reader. First the usual kind:

Really enjoyed this, you have a great voice! I did find the beginning a little slow to get going and I wasn't always sure where we were, but it picked up a lot once things got moving. The description is lovely. Maybe consider tightening the opening slightly? Some of the language felt a touch overwritten in places, though that might just be personal taste. Strong chapter overall, well done.

Seventy words. Warm, well meant, and vague. Now the other kind:

I skimmed paragraph three, the division-of-labour sermon, and came back on the first line of paragraph four when the red-faced man slams the cabin door. Paragraphs one to three are all summary, with Humphrey alone and safe and agreeing with himself.

But don't gut paragraph three. The stout gentleman reading Humphrey's own essay is planted in there, and he pays off in the wreck, still holding the magazine, encased in cork and canvas, asking with monotonous insistence whether there's any danger. That's the best joke in the chapter and it needs the setup.

So: keep the Atlantic, lose the sermon around it, and try opening on the red-faced man's entrance instead.

Five steps, two passes through the chapter.

• Step 1. Read the chapter once at normal speed. Mark two things only: ? where you were confused, ~ where you skimmed.
• Step 2. Close the file. Answer four questions from memory before you look at it again.
• Step 3. Reread. Diagnose only what you marked, and name the causes.
• Step 4. Rank what you found by scope and keep what carries the most weight.
• Step 5. Say what you think the chapter was going for, and ask if you read it right.

Everything below runs on chapter one of Jack London's The Sea-Wolf, free in full at Project Gutenberg. It is a strong chapter with real, fixable problems, written by someone who cannot be hurt by the notes. A shipwreck, a rescue, and a narrator who spends the first page and a half admiring his own essay on Edgar Allan Poe.

You can read the chapter first, but you do not need it to follow the method.

Go at normal speed, start to finish. Your eyes are only fresh to a draft once. The writer can never get that back from you, and neither can anyone who has already heard the plot. The moment you know what happens on page nine, you lose the ability to say whether page four made you want to reach page nine. That fresh read is the exact information the writer asked for, and it is the one thing a professional editor two drafts in can no longer supply.

As you read, leave two symbols behind:

• ? for confusion. You reread a sentence, lost track of who was speaking, or could not picture the room.
• ~ for skimming. Your eyes sped up and started skipping prose.

The skim mark carries most of the value. Skimming starts several seconds before your brain registers boredom, and by the end of the chapter the memory is gone. You are left with a vague sense that the middle sagged, which is the one note nobody can act on.

Close the draft. From memory:

• What did the POV character want?
• What stood in the way?
• What was different at the end than at the start?
• One image you can still see.

A chapter that cannot survive an hour in a reader's memory has a structural problem, and structural problems swallow every line fix underneath them.

The marks from the first pass:

• ~ at paragraph three, the division-of-labour sermon. Back on at "A red-faced man, slamming the cabin door behind him."
• ? at the shrill whistle from dead ahead. Gongs sound, the paddle-wheels stop and start again, and I could not tell whether we had just nearly hit something.
• ~ at the fog-as-infinite-mystery paragraph, a few lines after the launch passes.
• ~ across the screaming-women paragraphs.
• ~ once he is alone in the water, at "Whither was I drifting?"

And the memory test:

• Wanted: to get to San Francisco. Thin. I had to reconstruct it rather than recall it.
• In the way: fog, then another ship, then the sea itself.
• Changed: he starts the chapter calling navigation a mathematical certainty and ends it in the water, unable to swim a stroke.
• Image: the white-bearded man leaning out of the other pilot-house on his elbows, calmly working out where he is going to hit us.

Four out of four means the chapter is structurally sound. That result tells you to spend your notes on the front end and leave the shape alone.

Written up before any diagnosis at all, steps 1 and 2 on their own give you this:

First read, no stopping. I skimmed the paragraph of Humphrey agreeing with himself about specialists, then my attention came on at the red-faced man's entrance. It went off again at the fog meditation, then during the screaming, then once more when he was alone in the water. I got confused at the shrill whistle from dead ahead, where the gongs sound and the paddle-wheels stop, because I couldn't tell whether we'd just nearly been hit. An hour later the image I still had was the white-bearded man leaning out of the other pilot-house on his elbows, calmly working out where he was going to hit us.

Ninety seconds of writing, and it already beats most critiques the writer will ever receive.

Go back to the marks and work out why each one happened. Named causes make this fast, and they compress a note from two paragraphs to two words. The Turkey City Lexicon gives you a full vocabulary in about fifteen minutes of reading. On The Sea-Wolf, the same marks with causes attached:

• The paragraph three skim. It is doing two jobs. The sermon about specialists is Humphrey agreeing with himself, and it is dead. Buried inside it is the stout gentleman reading Humphrey's essay in the Atlantic, which is alive, because it comes back during the wreck.
• The whistle confusion. Gongs sound, the paddle-wheels stop and restart, the whistle fades away sideways. Something serious clearly just happened and nobody in the scene confirms it.
• The fog meditation. Purple, and badly placed. The launch is the closest call in the chapter, and the two paragraphs that follow it are a comic rant and then scenery. Whatever the near miss built gets spent.
• The screaming-women skim. The sound gets seven passes in seven paragraphs: the scream of the women, the screaming bedlam of women, a chorus of lost souls, pigs under a butcher's knife, rats in a trap, and finally Humphrey shrieking as the women had shrieked. Any two would be devastating. Seven is a drone.
• The floating passage. Bogus alternatives. The cold and the numbness get their own paragraph just before this, and they are good. Then the space goes to hypotheticals, at the exact point where he is alone and the danger is finally real.
• The passages that held. The white-bearded man on his elbows. The Leviathan simile. "It bit to the marrow." The stout gentleman still clutching the magazine. All physical, all specific, none of them explained afterwards.

Order by scope: structural above scene, scene above line. Keep the few notes that carry the most weight. Then close by saying what you think the writer was going for, and ask whether you read it right. The intention check is what turns a verdict back into a conversation.

The whole thing assembled, about 400 words:

What I think you were going for: a man who believes the world is a solved problem, taken apart by it inside one chapter. He opens by calling navigation a mathematical certainty and closes in the water unable to swim a stroke. Tell me if that's wrong.

What's working, please protect it: the white-bearded man leaning out of the other pilot-house on his elbows. He's the only calm person in the chapter and he's using that calm to work out where he's going to hit you, which is far worse than panic would have been. Second, the stout gentleman surviving the collision still holding the magazine, asking with monotonous insistence whether there's any danger. Third, "trailing fog-wreaths on either side like seaweed on the snout of Leviathan" and "it bit to the marrow." If you cut for length, cut the fog-as-infinite-mystery paragraph long before you touch any of these.

Note 1, structural. I skimmed paragraph three, the division-of-labour sermon, and came back when the red-faced man slams the cabin door. Paragraphs one to three are summary: Humphrey alone, safe, agreeing with himself. But don't gut paragraph three wholesale, because the stout gentleman with the Atlantic is planted there and he pays off superbly in the wreck. Keep the Atlantic, lose the sermon around it, and try opening on the red-faced man instead.

Note 2, scene. The launch passing dead ahead is the tightest moment in the first half. Gongs, the paddle-wheels stopping, the whistle fading off sideways. Then you spend it twice over, first on the comic rant about dare-devil launches and then on a paragraph of fog philosophy. By the time the real steamboat arrives, the line has gone slack. Consider running the collision straight off the near miss and moving the rant earlier.

Note 3, line, and it's a pattern. Four times inside the wreck you step outside it to tell me the material worked. "The remark was too obvious to make rejoinder necessary." "As distinct and sharp as that of any picture I have seen." "I was struck with horror at the vividness of the analogy." "Just as I had read descriptions of such scenes in books." Every one follows something that had already landed. Cut all four and the disaster gets faster and more frightening at the same time.

Two more I'm not going to develop: the red-faced man carries the whole first act and never gets a name, and the screaming gets seven passes in seven paragraphs when two would flatten me.

Notice where the praise sits. Near the top, and specific. Praise placed there keeps the writer receptive, and specific praise stops them from cutting the things that work.

Critiquing teaches craft faster than drafting does. You cannot see your own blind spots, and roughly half of everyone else's turn out to be yours in a different coat. Milford-style workshops have run on that principle since 1956, and it is why Clarion and Odyssey put twelve writers in a room instead of hiring one teacher.

The catch is that nobody grades your grading. You spend forty focused minutes, send it off, and get back a thumbs-up emoji. Ars Calami closes that loop:

• Writers rate every critique you send. Those ratings move a reputation that is yours, and better ratings match you with better writers and reviewers.
• You are matched to chapters in your genre at your level, so you are never a hard SF reader guessing at a Regency romance.
• Critiques earn credits, and credits put your own chapters in front of several matched readers at once.
• Submit a full arc and it splits across readers, each given context on the chapters they have not seen. Five people on chapter 24 instead of nobody.
• Publishers on the platform read critique histories. A record of notes writers rated highly proves you have taste and can articulate it.
• Copy-paste blocking, draft fingerprinting, version control, and AI provenance on everything you upload.