A friend sends you a short story at eleven at night with the message: be honest. You read it. You like parts of it. One scene confuses you, the ending feels rushed, and there is a sentence early on you would love to underline — though you are not sure whether the underline is a compliment or a complaint. Now what?

Giving useful feedback is its own craft, separate from writing. It has less to do with taste than with attention: noticing what the story is trying to do, where it succeeds, and where it slips. The goal is not to produce a better version of the story inside your head. It is to hand your friend a clearer view of the one they already wrote.

Read Twice, and Ask One Question First

The first read should cost you nothing. No pencil, no notes, no pausing to admire or wince. Read it the way any reader would, straight through, and pay attention to yourself: where you slowed down, where you skimmed, where you forgot you were reading. Those reactions are your raw material. They are also more reliable than any theory about how a story should work.

The second read is where the work happens. Print it if you can. Use the margin. Mark a line when it lands, a question mark when you lose the thread, a small vertical line when you catch yourself drifting.

Before any of that, though, ask what the writer wants. A first draft needs questions about structure; a fourth draft may only need help with sentences. "Do you want impressions, or line notes?" is a fair question, and the answer will save you an evening. If they say, "I'm not sure the ending works," you know where to spend your attention.

The Checklist: Four Things Worth Tracking

Keep this beside you on the second read. It stops you from giving forty disconnected opinions and helps you see the shape of the whole.

• Plot. Where were you confused, and where were you genuinely surprised? Those are different problems.
• Character. What did you believe about each person by the end, and was that what the story seemed to want you to believe?
• Pacing. Where did you speed up, drift off, or feel the story stall?
• Language. Which sentences did their job invisibly, and which ones made you notice the machinery?

Add one more column if you like: the single image or moment you would still remember tomorrow. Writers rarely hear that, and it is genuinely useful.

Plot: Point at the Confusion, Not the Fix

The most tempting mistake is to hand over a solution. "She should refuse to go" is not feedback; it is a rewrite with extra steps. What you actually know is your own experience of reading, and that is plenty: "I didn't understand why she agreed to drive him home. It felt like the story needed her in the car."

That version gives your friend something to work with and leaves the decision where it belongs. So describe the effect and let them diagnose the cause.

Two distinctions are worth keeping. Confusion is a craft problem: the reader needed information and didn't get it. Surprise is success, even if you didn't like the surprise. And a character behaving against their own nature to move the plot along is worth flagging plainly — "I stopped believing him in the argument scene" — because it is the kind of thing a writer can't see from inside.

Character: Reflect Back What You Saw

Try summarising the protagonist in one sentence as you understood them: "By the end, I thought she was someone who would rather be lied to than be alone." Then let your friend correct you. If their intention was different, that gap is your most valuable note, and it arrived without a single instruction attached.

Two questions do a lot of work here. What does this character want in each scene, and is it visible on the page? And who in this story exists only to help someone else? Secondary characters who appear purely to deliver comfort, warning, or information tend to flatten the scenes around them. Point to the specific scene rather than the general tendency.

Pacing: Mark Where Your Attention Slipped

Trust the drift. Every time you mentally put the story down, make a mark. Then look at what the marks have in common. Often it is a scene that begins a paragraph too early or ends three lines too late, or a stretch of summary where the writer has told you what happened instead of letting you watch it.

Watch the ratio of summary to scene as well. A tense confrontation rendered in long, balanced paragraphs will feel slack no matter how dramatic the content. Conversely, a quiet kitchen scene built from small actions can move faster than a chase. Report the effect, not the diagnosis: "I started skimming around the third paragraph of backstory."

Language: Notes That Don't Rewrite the Story

Line-level notes are where helpful readers so often turn into ghosts with a red pen. If you rewrite a sentence, you are showing them your voice, not improving theirs. Resist it.

Instead, name the effect. "This sentence made me stop and re-read it, and I think that's because the clause order buries the verb." Or, more simply: "I lost the subject halfway through."

Look for habits rather than crimes: the same three adjectives circling a character, a fondness for "just" and "actually", paragraphs that all start with a character's name. Then pick the three clearest examples and say, "this is a pattern worth watching." Marking all forty instances is accurate and useless; it buries the signal in noise.

If a line is genuinely unclear, say so without apology. Clarity complaints are never rude, and the writer can only fix what they know about.

Delivering It: Specific Praise, Few Notes, Real Questions

"I loved it" is kind and empty. Specific praise is worth ten of those: "The burnt toast on the first page did more than a paragraph of backstory would have." That sentence tells your friend their instinct was working, and it tells them which instinct.

Aim for two or three structural notes and no more than five line notes. A reader can act on three things. A reader confronted with thirty will quietly close the file and not write for a week. Ask permission before the heavy notes if the draft is fresh: some writers want the full report, others want one question to hold on to.

Skip the shortcuts. Comparing the story to a published novel is rarely useful, and "I just didn't connect with it" explains nothing. If something didn't work for you, say what you saw, where, and what you expected instead. Then offer to read the next version. That offer matters more than any single note.

A Short Template for Written Notes

If you are sending comments rather than talking them through, keep the shape simple.

1. One or two sentences on what the story does well, with a line or image quoted back.
2. One sentence describing what you think it is trying to do, offered as a guess.
3. Two or three questions, each tied to a page or a scene.
4. A short list of line notes, five at most, phrased as effects rather than corrections.
5. A closing line that is true and forward-looking: "I'd read the next draft."

Then stop. Do not send a second message with the notes you forgot, and do not repeat the same observation three times in the hope it will be taken seriously. Your friend asked for a reader, not an editor-in-residence. Give them an honest, precise account of what it was like to spend twenty minutes inside their story, and trust them to do the rest.

Photo: Monstera Production / Pexels