Severity tags and QA block
Lectura de 3 min
A report with 200 suggestions is unmanageable — severity tags help you fix the important ones first.
Three severity levels
| Tag | Meaning | Count |
|---|---|---|
| 🔴 Must-fix | Not fixing it noticeably hurts readers | Usually 5–15 |
| 🟡 Recommended | Fixing it meaningfully improves the experience | Usually 20–40 |
| 🟢 Optional | Polish-level, fine either way | Usually 30–50 |
How to use
Phase 1: handle every 🔴
These are reader-visible.
Phase 2: handle most 🟡
Time / energy permitting.
Phase 3: pick from 🟢
Save for the final polish pass before submission.
Sort
Default sort: severity — 🔴 first, 🟡 middle, 🟢 bottom.
You can switch sort:
- By severity (default)
- By chapter ("what's in Chapter 3")
- By dimension ("what's in Structure")
QA block
Each suggestion has a "Ask editor" button → opens a mini-chat:
- Follow-up: "Why is this must-fix?"
- The editor (AI) explains and goes deeper
- Or "Try revising this passage for me" — AI demonstrates
The QA block uses a small amount of credits (lightweight AI op).
Related
Was this helpful?