Client notes
Short notes from newsroom leads, newsletter editors, and independent creators who use the verification workflow daily.
We run a daily news digest with about forty claims per issue. The source scoring module now handles the first pass, flagging low-credibility links before they reach the editor. Our review queue is noticeably shorter, and the team can focus on the ambiguous cases instead of re-checking obvious ones.
We started using the audience sentiment dashboard for our weekly planning meeting. Seeing which topics generated confusion or distrust helped us rewrite headlines and add context boxes. Reader feedback in comments became less repetitive because we addressed the recurring questions directly in the next edition.
With only three people handling fact-checking for a weekly newsletter, the template library gave us a consistent format for source notes and correction logs. We no longer rebuild the same spreadsheet every month. The training workshop also helped us agree on what counts as a verified claim versus a partial match.
Our video team produces two explainers per week, and keeping track of which claims were already checked was a mess. The claim log now lives in one place, searchable by topic and status. Producers can see at a glance whether a statistic was verified in a previous episode or still needs a source.
The planning tools connect our content calendar to the verification pipeline, so we know which pieces are ready for review and which are still waiting on sources. It sounds simple, but it removed the constant back-and-forth in Slack about deadlines and status updates.
Each source you add to a story gets a score based on editorial standards, track record, and transparency. You set the weight for each factor, so a local newsroom can prioritize community knowledge while a wire desk leans on institutional reliability. Scores update as new information comes in, and editors see the reasoning behind every rating before publication.
Yes. The claim log is format-agnostic. You create a claim entry, attach it to a script, a newsletter draft, or a video rundown, and assign a verification status. Review checkpoints sit at each stage of production, so nothing ships without a final check against the log.
Standard analytics show how many people clicked. Sentiment analysis shows how they reacted after reading. We look at comment tone, share context, and engagement patterns across topics to reveal which coverage builds trust and which creates friction. That feeds directly into your editorial calendar.
Most teams are up and running within a week. We map your existing production cycle, import your current story list, and configure the calendar to match your workflow. If you have a template library already, we integrate it. If not, we build one from your past formats.
Yes. We run half-day and full-day workshops focused on verification basics, source evaluation, and claim documentation. The sessions are practical, not theoretical. You leave with templates and checklists that fit your team size and publishing pace.
Absolutely. Independent creators producing daily articles or weekly newsletters often face the same accuracy pressures as larger teams. The modules scale down cleanly. You get the same source scoring, claim tracking, and sentiment tools without the overhead of a full newsroom setup.
Still unsure which module fits your workflow? Send us a note at info@agenceinfact.com or check our detailed answers page for more context.
A practical set of modules that fit into your existing production cycle. Each one targets a specific bottleneck, from source checks to audience signals, so your team can keep publishing without lowering the accuracy bar.
Module 01
Build a transparent scoring framework for the outlets and experts you cite. Assign weights based on editorial standards, track record, and domain relevance, then reuse the same criteria across every story.
Module 02
Keep a shared log of every claim under review, with statuses that move from unverified to confirmed or corrected. Useful for daily articles and weekly newsletters where the same statement often resurfaces.
Module 03
See which formats and topics hold reader attention. The dashboard pulls engagement metrics per article, video segment, and newsletter issue, so planning decisions rest on recent data rather than guesswork.
Module 04
Track how readers react to specific coverage areas. Sentiment scores are paired with comment themes, giving editors a clear read on what resonates and what needs a follow-up or correction.
Module 05
Plan daily, weekly, and monthly output on one board. Assign verification tasks to each slot, set review checkpoints, and keep the whole team aligned on what ships and when.
Module 06
Ready-made checklists, source review forms, and correction protocols for small teams that want to professionalize their process without building everything from scratch.
Not sure where to start? See how these modules apply to different editorial setups on the use cases page, or read about our working principles on the approach page.