Approving Content
EditorAfter reviewing an article, you will either approve it for publication or send it back to the contributor for revisions. This guide covers both workflows.
Approving an Article
When an article meets your quality standards and is ready for a Publisher to take live:

Approved does not mean published
Setting an article to Approved signals that editorial review is complete. A Publisher must still take the separate step of publishing the article to make it visible on the frontend.
Requesting Changes
When an article needs improvement before it can be approved:
Be specific in your feedback
Vague feedback like "needs work" slows down the process. Instead, point to specific sections and explain what should change: "The section on biomarker testing should include reference ranges for the metrics mentioned."
- Factual inaccuracies or unsupported claims
- Missing or incomplete sections that leave gaps in the topic
- Poor formatting that would hinder readability on the frontend
- Title or description that does not accurately reflect the content
- Quiz questions with incorrect answers marked or missing explanations
Approval Best Practices
- Do not hold articles indefinitely — if only minor formatting issues remain, fix them yourself and approve.
- Document your reasoning — brief notes help Publishers understand any context about the article.
- Be consistent — apply the same quality bar across all contributors to maintain fairness and platform standards.