What Document Review does
Document Review examines your document across several dimensions: Structure and organization:- Logical flow and progression
- Heading hierarchy and consistency
- Section balance and pacing
- Information architecture
- Sentence complexity and length
- Jargon and technical language use
- Transitions between ideas
- Overall readability score
- Missing context or background
- Gaps in explanations
- Unanswered questions
- Areas that need expansion
- Tone consistency
- Formatting issues
- Redundancy and repetition
- Opportunities for improvement
How to trigger Document Review
The Assistant will read through your entire document and provide structured feedback organized by category.
Document Review works with all models, but Max provides the most thorough and nuanced feedback, especially for longer or more complex documents. For quick checks, Fast offers a good balance between depth and speed.
Document Review vs. general Assistant chat
| Feature | Document Review | General Assistant Chat |
|---|---|---|
| Purpose | Structured document feedback | Open-ended conversation and tasks |
| Scope | Entire document analysis | Answers specific questions |
| Output format | Organized by feedback categories | Conversational responses |
| Analysis depth | Comprehensive, multi-dimensional | Focused on your specific question |
| Best for | Quality checks, pre-publish reviews | Quick edits, summaries, content queries |
| Follow-up prompts | Can ask clarifying questions | Continuous conversation |
| Credit usage | Higher (analyzes full document) | Varies by query complexity |
When to use Document Review
Document Review is most valuable in these scenarios:Before sharing externally
Review presentations, proposals, or client-facing documents to catch structural issues, unclear sections, or missing context before sending them out.Quality assurance
Run periodic reviews on important documentation, team wikis, or knowledge base articles to maintain high quality and consistency over time.Content improvement
Get actionable suggestions for blog posts, reports, or long-form writing. The Assistant can identify areas that need expansion, simplification, or restructuring.Collaboration prep
Before sharing with teammates, ensure your document is clear, complete, and well-organized. This reduces back-and-forth and improves collaboration efficiency.Learning and skill development
Use reviews to understand patterns in your writing – recurring clarity issues, structural tendencies, or areas where you consistently need improvement.You can run Document Review multiple times. Make changes based on feedback, then review again to see if the issues are resolved. This iterative approach helps you learn what works and refine your content progressively.
Understanding the feedback
Document Review feedback is organized into clear categories. Here’s how to interpret and act on it:Structure feedback
What it tells you: How well your content flows, whether sections are balanced, and if the information architecture makes sense. Example feedback:- “The introduction is too long relative to the rest of the document”
- “Section 3 lacks a clear transition from Section 2”
- “Heading hierarchy skips from H2 to H4”
Clarity feedback
What it tells you: Whether your writing is easy to understand, if sentences are too complex, and where readers might get confused. Example feedback:- “This paragraph uses passive voice heavily, making it harder to follow”
- “Technical jargon in the first section may confuse non-expert readers”
- “Sentence length averages 35 words – consider breaking into shorter sentences”
Completeness feedback
What it tells you: Gaps in your content – missing context, unanswered questions, or areas that need more detail. Example feedback:- “The document mentions ‘the new process’ but never defines it”
- “Steps 2 and 3 assume prior knowledge not covered in the introduction”
- “No conclusion or next steps provided”
Quality feedback
What it tells you: Tone consistency, formatting issues, and opportunities to polish your content. Example feedback:- “Tone shifts from formal to casual between sections”
- “Bullet points are inconsistently formatted (some end with periods, others don’t)”
- “This concept is explained twice – consider consolidating”
Credit usage
Document Review consumes AI credits based on the length and complexity of your document:| Document Length | Approx. Credit Cost (Fast) | Approx. Credit Cost (Max) |
|---|---|---|
| Short (< 500 words) | ~0.5 credits | ~1-2 credits |
| Medium (500-2000 words) | ~1-2 credits | ~3-5 credits |
| Long (2000-5000 words) | ~2-4 credits | ~6-10 credits |
| Very long (5000+ words) | ~5+ credits | ~12+ credits |
These are estimates based on typical documents. Actual usage depends on document structure, formatting complexity, and the model you choose. Check your credit balance in the Assistant menu.
Tips for better reviews
1. Prepare your document first Make sure your document is reasonably complete before running a review. The Assistant provides better feedback on finished drafts than on rough outlines. 2. Specify your audience In a follow-up prompt, tell the Assistant who the document is for:- “This is for a technical team familiar with the product”
- “The audience is non-technical stakeholders”
- “Written for new users who have never used Craft”
- “Which 3 issues should I fix first?”
- “What’s the most critical structural problem?”
- “Focus on clarity issues only”
- “Review this for tone consistency”
- “Check only for completeness and missing context”
- “Focus on whether the structure makes sense for a beginner audience”
- On-device: Not recommended for Document Review (limited context)
- Core: Quick structural checks on short documents
- Fast: Good balance for most reviews (500-2000 words)
- Max: Best for long, complex documents or when you need the most thorough feedback
Example: Before publishing a blog post
Sarah writes a blog post about using Collections in Craft. Before publishing, she wants to make sure it’s clear and complete.The Assistant analyzes the document and provides feedback:
- Structure: “Introduction is strong, but Section 2 is twice as long as Sections 3 and 4 combined. Consider breaking it into two parts.”
- Clarity: “Several technical terms (relations, properties, views) are used before being defined. Add a glossary or define on first use.”
- Completeness: “The post explains what Collections are but doesn’t cover when to use them vs. folders or tags.”
- Quality: “Tone is consistent. One redundant section at the end restates the intro – consider removing.”
Sarah makes adjustments based on the feedback: splits Section 2, adds definitions, includes a “When to use Collections” section, and removes redundancy.