Review Fern's changes each week
Fern drafts updates when you ship. With Continuous verification on in Fern > Customize > Automations, it also flags articles that no longer match your product. Nothing goes live until someone publishes it, so a short review each week keeps your docs right.
Give this to one owner, usually whoever ships the most product. Owners and admins publish. Contributors can edit Fern's drafts and submit them for review.
Clear Review requests, oldest first
Review requests holds the changes teammates submitted for review, with any note they added. It shows in the sidebar for owners and admins while something is waiting.
Go through Fern's drafts
In Fern, filter the list to Has drafts. A draft from a merged pull request shows the pull request, its author and why Fern made the change. If a pull request should not be documented, mark it Not relevant.
Check the facts, not the wording
Fern writes in your help center's style. What it cannot know is intent, like a feature that is still in beta or a limit you plan to change. Edit a detail in place, or tell Fern in the task, then publish.
Clear Verification
Open Verification and work through Needs review. It fills on its own once Continuous verification is on. Otherwise, run a check with Verify docs. Ask Fern to draft the fix, or choose Not an issue when the difference does not matter to customers. If you choose it by mistake, restore the article from the Dismissed tab. See Keep articles accurate.
Skim the latest audit
When a scheduled audit runs, it lands in Fern's list under Audits. Use Draft with Fern on the findings worth doing and dismiss the rest.
How often
When | What to do |
|---|---|
Each week | The five steps above |
The day a big feature merges | Ask Fern to write it straight away. See When you ship something big. |
Each month | Look for searches that found nothing and ask Fern to cover them. See Read help center reports. |
The review is working when the list stays short and your AI agent rarely hands off questions your docs should answer.