A newsroom workflow

How teams usually fit checking into publishing.

There is no single right way. This is the pattern we see work best.

1. DraftThe writer finishes a draft in the CMS.
2. Ask for a checkA button (or a status change to Ready for fact-check) calls your server, which starts an async check with user set to the writer's email.
3. Read the answerWhen it is done, your CMS stores the claims, verdicts and sources against the story.
4. Handle held claimsAny claim that is not_yet_confirmed is in your review queue. An editor decides there. The story stays blocked until it is settled.
5. Gate publishingYour CMS only lets the story go live if no claim is held and no claim is false or misleading, unless an editor overrides it.
6. Publish with the disclosureThe AI disclosure line is published with the story's fact-check box.

Good habits

• Check at the claim level, not only at the end. Short, early checks are cheaper to fix.
• Keep the fact_check_id on the story. It lets you trace any published verdict back.
• Never overwrite a verdict by hand in the CMS. If an editor disagrees, they record a decision in the review queue and note why.