Document Feedback Reference Sheet
For the reasoning behind this system, see Why Feedback Order Matters: A System for Document Review.
The Three Tiers
| Tier | Scope | Address | Examples |
|---|---|---|---|
| Higher Order (HOC) | Whole document | First | Argument, structure, purpose, audience fit, completeness |
| Middle Order (MOC) | Sections/paragraphs | Second | Transitions, evidence integration, tone, proportionality |
| Lower Order (LOC) | Sentences/words | Last | Grammar, spelling, word choice, formatting |
The core rule: Always work top-down. Don't polish what might move.
Higher Order Concerns
- Is the central argument clear?
- Does the organization and logical flow make sense?
- Does it meet the requirements (RFP, assignment brief, client ask)?
- Is the level of detail and framing right for the audience?
- Are there missing sections or gaps in reasoning?
The test: If this isn't fixed, does the document fail its purpose?
Middle Order Concerns
- Do sections connect with logical transitions?
- Are sources and evidence introduced and explained well?
- Does each paragraph have a clear purpose?
- Is the tone consistent throughout?
- Are sections proportionate to their importance?
The test: Does this issue affect how a section or group of paragraphs functions?
Lower Order Concerns
- Grammar and punctuation
- Spelling and typos
- Word choice and clarity
- Citation formatting
- Visual formatting (headers, bullets, spacing)
The test: Does this issue affect only this sentence or word?
Label Your Feedback
Tag each comment so authors can prioritize:
[HOC] The structure assumes the reader already knows our methodology. Add context in section 1.
[MOC] The transition between the problem statement and solution is abrupt. Consider a bridge paragraph.
[LOC] Typo in the executive summary: "reccomendations" → "recommendations"
Request the Right Feedback
Match your request to the draft stage:
| Draft Stage | What to Ask For |
|---|---|
| Early | "Focus on higher order concerns only — is the argument right?" |
| Middle | "Structure is locked. Focus on section flow and transitions." |
| Final | "Just need a proofread for lower order issues." |
Quick Decision Guide
Is this about the whole document's success?
→ Higher Order Concern → address first
Is this about how sections or paragraphs work together?
→ Middle Order Concern → address second
Is this about individual sentences or words?
→ Lower Order Concern → address last
Giving Feedback Well
- Make it actionable. "This is confusing" is a complaint. "The causal chain isn't clear — what leads to what?" is feedback.
- Focus on the document, not the person. "This section would benefit from an example" instead of "You didn't explain this well."
- Flag patterns, not instances. "Watch for comma splices throughout" beats marking each one individually.
Receiving Feedback Well
- Address all higher order concerns first (may require significant rewriting)
- Reassess middle order concerns (some resolve themselves after structural changes)
- Handle lower order concerns last (in final, stable text)
