Avoid Errors · Growth Library
Match Feedback to the Revision Target
Ask for surface or deep feedback based on what you are revising
Try this
Before asking for feedback on a student or learning-focused draft, choose the current revision target. Use a surface pass for grammar, spelling, wording, and similar features; use a deep pass for ideas, organization, coherence, or other meaning-level features. Tell the reviewer which level you want them to focus on, revise against that target, and run a separate pass if the other level also needs work.
Check-in: What was the revision target for this pass, and did the feedback actually help you revise at that level?
Evidence: Reviewed · source · A 2024 meta-analysis of 95 papers and 200 treatment/control comparisons in secondary-school and university writing found that feedback effects differed by the level of writing outcome: surface feedback improved surface outcomes, deep feedback improved deep outcomes, and combined feedback could improve both. Results varied by learner group and feedback context, so Brali does not treat all feedback as interchangeable or generalize these estimates beyond educational writing.
Review note: Reviewed against Scherer, Graham, and Busse (2024), a meta-analysis of feedback in secondary-school and university L1, L2, and foreign-language writing. Public guidance is limited to matching the requested feedback level to the intended revision outcome and explicitly excludes universal claims about feedback source, sequence, amount, or transfer to professional and creative writing.
Feedback is easier to use when the reviewer and writer are solving the same revision problem. In educational-writing research, surface feedback and deep feedback did not behave as interchangeable treatments. Brali turns that boundary into a small workflow: name the revision level first, ask for feedback at that level, then revise against the same target.
1. Choose the revision level
Before sending the draft, name what you are actually trying to improve.
- Surface: grammar, spelling, wording, sentence-level form, and similar local features.
- Deep: ideas, organization, coherence, genre-level decisions, and other meaning-level features.
If both matter, decide which one is the target of the current pass instead of asking for every possible comment at once.
2. Write the feedback request
Tell the reviewer what level to inspect. A surface request can ask where language or sentence form needs correction. A deep request can ask whether the main idea, organization, evidence, or coherence needs revision. Keep the request tied to the actual learning or writing task rather than asking for vague ‘general feedback’.
3. Revise at the same level
When feedback arrives, first use the comments that address the chosen target. If the pass was about organization, do not let a pile of local wording edits distract you from the structural decision. If the pass was about surface accuracy, do not assume those corrections also prove that the argument or organization is strong.
4. Use a separate pass when needed
If the draft needs both deep and surface revision, run another pass with the other target after the first set of changes is stable enough to review. This is a workflow choice, not a claim that one fixed sequence is scientifically optimal.
Evidence boundary
The source behind this protocol is a 2024 meta-analysis of experimental and quasi-experimental studies of writing feedback with secondary-school and university students learning in L1, L2, and foreign-language contexts. It found different effects for surface, deep, and combined feedback, with meaningful variation by learner group and feedback source. The literature does not establish that more feedback is always better, that one feedback agent is universally superior, that one pass order is optimal, or that the reported effects transfer unchanged to professional or creative writing.
Questions to consider
Should I always ask for deep feedback first?
No. Choose the pass that matches the current revision goal. If the argument or organization is still changing, deep feedback may be more relevant; if the content is already stable and you are polishing language, a surface pass may be the better target. The source does not establish one universal order.
Is peer feedback always better than instructor or automated feedback?
No. The meta-analysis found different effects across learner groups, feedback sources, and outcomes. This protocol uses a reviewer because the existing Brali page is a peer-review workflow, but it does not claim that peers are universally the best feedback source.
Can I use this approach for a work memo, article, or other professional writing?
You can use the surface-versus-deep distinction as a planning heuristic, but the reviewed evidence here comes from secondary-school and university educational writing. Brali does not claim that the measured effects transfer unchanged to professional, marketing, technical, or creative writing.
Sources
Evidence state: reviewed. Sources are provided so the underlying material can be inspected directly.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-08-21 · reviewed · Brali editorial agent Source: protocol-content-overrides-writing-feedback.json
Replace inherited peer-proofreading copy containing unsupported quantitative claims and fabricated internal observations with a bounded educational-writing protocol derived from a 2024 meta-analysis of feedback for L1, L2, and foreign-language learners. The reviewed claim is limited to matching the level of feedback to the revision outcome; it does not generalize the study to all professional or creative writing.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Reviewed evidence decisions
These source reviews are linked to this hack for provenance. They do not change lifecycle status automatically; any material status change still requires an explicit lifecycle event.
2026-08-21 · propose-protocol ·
writing-feedback-level-match-2024Reviewed source. In the reviewed secondary-school and university writing literature, feedback effects differed by the level of writing outcome: surface-level feedback improved surface-level outcomes, deep-level feedback improved deep-level outcomes, and combined surface-and-deep feedback could improve both. This supports matching a feedback request to the revision outcome rather than treating all feedback as interchangeable.
2026-08-31 · support-existing ·
structured-peer-feedback-provision-2025Reviewed source. In the reviewed educational literature, adding instructional support to peer feedback improved the peer-feedback process overall, and support aimed at the person providing feedback was associated with better feedback-provision quality. This supports Brali's existing educational writing protocol in making the review target explicit and giving the peer reviewer a small amount of structure instead of requesting vague general feedback.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-08-21: reviewed by Brali editorial agent; evidence state is
reviewed.
Canonical source record · Evidence state: reviewed.