Many Roads
Use case
Editorial photograph for Editorial review

Editorial review

Communications teams already review what they publish. The cap is volume: when hundreds of authors across regions and languages publish independently, headquarters review is a sampling exercise. What's next is continuous coverage across every draft, with editors spending their time on the parts the model can't handle.

Engagement
Pre-publish editorial review for distributed publishing teams

We build the editorial-review layer that sits between draft and publish in your content workflow. Each draft is checked against the policies that matter to your organization: factual claims that need a citation, language that drifts off-brand, accessibility gaps, basic SEO hygiene. Issues come back in seconds, ranked by severity, with a one-click rewrite for the cases the model can handle confidently. We won't replace editorial judgment on calls that depend on local context, sensitivity, or audience nuance; those still go to a human editor, with the routine issues already handled. The smallest useful version ships in weeks: one policy area, one site, one language, and grows from there.

What it looks like
An NGO's content management system. The left side shows a Create Article form with a draft titled 'Our Impact in Local Communities'. The right side is an AI Content Review panel listing five issues: two high-severity policy violations (an absolute claim of 'thousands' without citation, and 'amazing job' as subjective and promotional), a medium-severity brand voice flag on an overused phrase, and low-severity accessibility (alt text) and SEO suggestions. A 'Fix with AI' button sits at the bottom of the review panel.
What we can build here

Capabilities

Policy claims caught before publish

Communications policy lives in a style guide and a few people's heads. AI brings it into the editor: factual claims that need a citation, promotional adjectives that pull a piece off-tone, regulatory language that needs specific phrasing. The author sees the flag at the moment they wrote the line, not in a review meeting two weeks later.

Brand voice that holds at scale

Every organization has a voice; what's hard is keeping it consistent when hundreds of authors write at once. AI compares each draft to the canonical voice (drawn from your published back-catalog), flagging stale phrases, off-brand register, and formulations that have been over-used across the network. Authors keep their style; the rare drift becomes visible.

Accessibility and SEO checked in the editor

Accessibility and SEO are easy to forget at draft time and expensive to retrofit after publish. AI checks both as the author writes: missing alt text, headings out of order, meta description absent, keywords thin. The author fixes them in the same screen, before the draft reaches an editor.

One-click rewrite for the routine issues

Where the issue has a clear right answer (a softer adjective, a more specific phrase, a missing meta description), AI proposes a rewrite the author can accept, edit, or reject. The hard editorial calls (sensitive language, local context, audience-specific framing) go to a human editor with the routine issues already cleared.

Questions

FAQ

Does this replace our editors?
No. AI handles the routine issues that don't need judgment: missing alt text, broken policy claims, overused phrases. Editors get drafts where the routine work is already done, and spend their time on calls that depend on context, sensitivity, and audience. The editor's signature is still on what publishes.
Does this work with our existing CMS?
Often yes. The review layer plugs into the draft-to-publish step of your content workflow through whatever the CMS exposes (an API, a webhook, an editor plugin). Authors see the flags inside the screen they're already writing in. We don't ask you to migrate the CMS to add the review.
How does the AI know what counts as a policy violation or off-brand voice?
From your own materials. Your style guide, communications policy, and published back-catalog are the source of truth: the model learns the voice you've already established and the rules you've already written, not a generic “good content” standard. Where the policy is ambiguous, the flag is advisory and the editor still decides.
Also relevant in