Three guides that cover the daily decisions behind verification, from ranking sources to tracking claims across formats.
A practical framework for building a source scoring system that reflects your channel's editorial priorities, whether you cover local news, science, or politics. The guide walks through the factors that matter, the traps of name recognition, and how to keep the system transparent for your audience.
Read the guideNewsletters move fast and errors slip through easily. This piece outlines a shared claim log, verification statuses, and review checkpoints before each send, plus how to handle recurring claims that resurface in different contexts without slowing production.
Read the guideSentiment data can tell you more than raw engagement numbers. This post explains how to set up sentiment analysis on your content, interpret scores by topic and format, and feed those insights back into your editorial calendar so coverage matches reader expectations.
Read the guideA few definitions and boundaries that shape how verification tools apply to your newsletter, video channel, or daily article output.
A source is any document, person, or dataset you cite in a published piece. The scoring module evaluates editorial standards, correction history, and domain expertise. It does not rank outlets by name recognition alone, and it does not replace your editorial judgment about context.
When the same claim appears in multiple drafts or formats, the system keeps one master record and links each mention to it. This means a quote used in both a video script and a newsletter gets a single verification status, so you are not re-checking the same statement twice.
Sentiment metrics reflect reader reactions expressed in comments, shares, and direct replies. They do not infer intent, political leaning, or the accuracy of a piece. Use them as a signal for engagement, not as a verdict on editorial quality.
Workshops cover verification workflows, source scoring, and claim logs for teams of up to twelve people. They are practical sessions built around your existing production cycle, not general media theory. Each session includes a template pack you can adapt to your own formats.
The library includes checklists, claim logs, and editorial calendars in spreadsheet and document formats. Templates are designed for small editorial teams and assume a basic familiarity with your own publishing tools. They do not include automated integrations or custom code.
Verification records and sentiment snapshots are kept for twelve months, then archived. You can export your data at any time. The platform does not use your content to train external models, and your editorial drafts remain separate from published analytics.