Document Review Criteria

This document describes the criteria and feedback format used when reviewing business and technical documents at Arda. Apply this process to any document being prepared for publication or team use.

Review Steps

1. Read the Document

Read the complete document before forming any judgments. Take notes on sections that are unclear or inconsistent.

2. Evaluate Against These Criteria

Clarity: Is it scannable? Does it use headers, bullets, and numbered steps where appropriate?

Tone: Professional but approachable. Not salesy, not jargon-heavy.

Readability: Target Flesch score 80+. Active voice. Short sentences.

Structure: Does it have clear sections? Are “Next Steps” or “Action Items” included where the reader would expect them?

Completeness: Are there gaps in logic, missing context, or unstated assumptions?

3. Provide Feedback in This Format

• Strengths: What works well (1-2 bullets).
• Issues: Specific problems with section references (numbered list).
• Suggested Edits: Concrete rewrites for the highest-impact issues.
• Overall Assessment: One sentence summary of the document’s readiness.

4. Apply Approved Edits

If the author approves the suggested edits, apply them directly to the source file. Do not rewrite sections that were not flagged.

Notes

• Match the existing document style and tone. Impose your preferences only when they improve clarity or impact.
• Do not rewrite for the sake of rewriting.
• Flag any content that could confuse a reader if the document is customer-facing.
• For Diataxis-typed documents, verify the document stays within its declared type (see Document Writing Methodology).