How to Give Useful Feedback on Creative Writing

Help a writer make informed decisions with specific, proportionate feedback that respects the work's intention and voice. Ask what kind of response is useful now Before reading, ask what stage the draft has reached and which decisions the writer is making. An early draft may need a response to premise, character desire and structure; sentence-level corrections can distract from those questions. A late draft may need close attention to clarity and continuity. Confirm whether any subjects are difficult to discuss and when the writer wants the notes. Do not promise a depth of review you cannot provide. A focused response to three scenes is more useful than hurried comments across a novel. If the writer asks a leading question—‘Is the ending good?’—translate it into observable concerns: Does the ending follow from earlier choices? Which promise does it fulfil? What remains confusing? Agreement is not the goal; usable information is. Read for intention before correction On the first pass, follow the work as a reader. Note what you think the story wants you to expect, feel and understand. Mark where your attention sharpens, drifts or changes direction. Resist solving each issue immediately. A confusing detail may be clarified a page later, and a repeated image may be deliberate rather than accidental. Summarise the piece back to the writer: whose story it seems to be, what they want, what obstructs them and what changes. This gives the writer evidence about what reached the page. If your summary differs from their intention, the gap is useful; it is not proof that either person has failed. The conversation can then focus on where the intended signals were weak or competing. Describe effects and provide evidence Useful feedback links a reader response to a specific moment. ‘I lost track of who was speaking after the door opened’ is actionable; ‘This is confusing’ is not. Quote a short phrase or identify the scene, describe your interpretation and explain the consequence. Avoid claiming that all readers will react as you did. Separate observation from diagnosis and suggestion. You may observe that tension falls during a long explanation, diagnose that the information arrives before it matters and suggest moving part of it. The observation is strongest; the diagnosis is a hypothesis; the suggestion is one option. Labelling them mentally helps the writer use your experience without treating your proposed rewrite as the only cure. Prioritise what changes the reading experience Group notes by impact. Begin with two or three patterns affecting the whole piece, such as an unclear goal or consequences that arrive too late. Then cover local moments that illustrate those patterns. Leave minor wording and punctuation until the structure is stable. A document crowded with equal-looking comments makes a repeated comma feel as important as a missing motivation. Include strengths with the same specificity. Identify where a choice created clarity, tension, humour or emotional force and explain why it worked. This is not praise added to soften criticism; it tells the writer what to preserve during revision. A balanced response can still be candid. It simply gives an accurate map of the work rather than a catalogue of defects. Offer questions and options without taking over Ask questions that expose choices: What does this character believe will happen if they refuse? Which piece of information should the reader carry into the next scene? Avoid questions that conceal a command. If you have a possible approach, offer it as an example of the kind of change you mean, not replacement prose for the writer to paste. Respect the work's voice, genre and intended audience. A quiet ending is not automatically weak because you prefer spectacle, and unfamiliar syntax is not automatically an error. Say when a note comes from taste or limited genre knowledge. The writer remains responsible for the draft and may decline any suggestion; your role is to improve the information available to their decision. Close the loop thoughtfully End with a short summary of the most valuable next steps and invite clarification, not a defence. If you are exchanging work, agree whether a follow-up read is included. Writers receiving notes can wait before responding, look for patterns across readers and test comments against their intention. They need not implement every note to have listened seriously. Public INK forum discussions are readable without an account and may offer places to discuss craft. Support or voting can be available to signed-in readers where enabled, while posting has its own participation requirements. Use the INK tutorials for platform-specific instructions rather than treating this guide as product documentation. In any setting, respond to the actual work, respect boundaries and never imply that feedback guarantees approval, publication or canon selection. Use a final feedback check Before sending, remove comments that merely restate a preference, combine repeated notes and check that your summary matches the detailed evidence. Read the tone as carefully as the content. Direct language can be kind, while jokes, exaggerated certainty and comments about the writer rather than the draft can make even a valid observation hard to use. If a note concerns sensitive material, describe the effect precisely and stay within the scope the writer requested. Ask whether every major note answers three questions: where did the response occur, what did you experience, and why might it matter to this work's intention? You do not need a solution for every problem. A clear account of the reading experience gives the writer room to invent one. Send the response at the agreed time, then let the writer decide when and how to revise rather than chasing immediate reassurance that your advice will be followed.