AI content quality governance: How Oyster ships faster without sacrificing accuracy

Ethics-first AI content governance: Web lead Josephine Cahill shares Oyster’s velocity-driven workflow, risk tiers, and a legal review process for governing the agentic web.

AI content quality governance: How Oyster ships faster without sacrificing accuracy

Learn the three most impactful content governance practices along with concrete steps you can apply to your own content management workflow.

When an AI hallucination on your website could get a maternity leave policy wrong for an entire country, the stakes go far beyond brand reputation.

AI content quality governance sat at the center of a recent Webflow webinar, Governing the agentic web. Josephine Cahill, Lead, Web at Oyster, shared how her team publishes content at an exponentially higher velocity while keeping accuracy, ethics, and brand consistency intact. Oyster HR helps companies hire, pay, and care for employees in 180-plus countries, and their content covers sensitive topics such as employment law, union rights, and tax obligations across dozens of jurisdictions. A single AI-generated error doesn't just look bad. It affects real people's rights.

This article breaks down the three most impactful content governance practices Josephine shared, along with concrete steps you can apply to your own content management workflow.

Treat accuracy as an ethics requirement

AI content governance goes beyond brand voice when real-world outcomes are at risk

Oyster publishes hiring guides that cover country-specific employment rights. When AI generates a first draft about maternity leave in Argentina or union rights in Spain, the accuracy bar is set by the people who rely on that information, not by internal style preferences.

As Cahill put it: "Is it accurate? That's not just impacting our brand. It's impacting the experience of employees around the world, including their ability to fairly exercise their rights. Does this work for our brand? [Does] it match my ethics and my values and Oyster’s values?"

This reframing shifts AI content governance from a marketing concern to an organizational one. If your website publishes information that people use to make decisions about their careers, finances, health, or legal rights, the standard for what counts as "good enough" changes.

Here's how to apply this to your own content governance model:

  • Audit your content for real-world impact. Identify which pages, collections, or content types carry the highest risk if they contain inaccurate information. Legal content, product pricing, compliance documentation, and medical or financial guidance all qualify.
  • Define your accuracy standard in writing. Add accuracy and ethical alignment to your brand kit and content guidelines so every contributor and AI tool starts from the same expectations.
  • Assign accountability. Decide who owns the final sign-off for high-stakes content. At Oyster, that's the legal team's hiring specialists.

When your content lifecycle includes AI-generated drafts, the question shifts from "Does this sound right?" to "Is this factually correct, and what happens if it isn't?"

That question leads directly to the next governance practice: Building review gates that match the level of risk.

Build mandatory review gates

Enforce human-in-the-loop legal review as a required step before publishing

Oyster's content management workflow follows an AI-first, human-verified approach. AI does the first draft. Humans do the verification. The key is that those human reviews aren't optional.

The process works like this: Oyster's legal team creates country-specific knowledge bases. Those knowledge bases, combined with official government sources, feed into AI-generated first drafts produced against the company's brand kit. From there, the workflow automatically generates Asana tickets for brand, content, and legal review. Only after all three teams approve does the content publish through an LLM-to-Webflow integration.

"We're generating Asana tickets for our brand team, our content team, and critically, our legal team, so our expert specialists [...] are reviewing all of that," Cahill explained. "We create these mandatory stopping points for quality assurance, and we're starting from a position of quality data."

Cahill also emphasized the importance of governing inputs, not just outputs: "We then feed that in with official government sources and produce a first draft against our brand kit." By starting with high-quality data, the team reduces downstream corrections.

To set up a similar content governance structure:

  1. Map your review chain. Identify which teams need to review which content types. This could include brand, content, legal, product marketing, compliance, or regional teams.
  2. Automate the routing. Use project management tools to generate review tickets automatically when a draft is ready. This removes the friction of manual handoffs and keeps the process moving.
  3. Ground your AI in trusted sources. Feed AI tools with proprietary knowledge bases, official sources, and documented brand principles before generation begins. Fewer hallucinations at the start means fewer corrections at the end.
  4. Make the gates non-negotiable. If a review step is optional, it won't survive the pressure of a deadline. Build required approvals into your publishing workflow.

As Cahill summed it up: "We're using AI to create better content, not faster content."

Risk-tiered governance ties review depth to content impact.

Tier your content by risk

Match your review depth to how much each piece of content affects your audience

Not every page on your site carries the same stakes. Oyster tiers content by risk level and connects the number of review rounds to each tier. Cahill credited this approach to Jake Hughes, Head of Web Strategy at Typeform, who tiers his content by risk level, similar to any other triage or risk assessment.

Here's how Oyster and Typeform’s three-tier content model breaks down:

  • Tier 1 (highest risk): Country-specific informational content that affects hiring rights, employee benefits, or legal obligations. These pages go through full legal, brand, and content review.
  • Tier 2 (moderate risk): Brand-related content, product launches, and persona-specific pages. These get brand and content review but don't require legal sign-off.
  • Tier 3 (lowest risk): Aggregated content such as awards roundups or republished material from other sources. These receive minimal review.

"Number one is deciding how important [something is,] then connecting the [appropriate] number of review rounds," Cahill said.

This tiered approach directly addresses the capacity problem that comes with high-velocity publishing. Your legal team, your compliance reviewers, and your subject-matter experts all have limited bandwidth. Risk tiering directs their attention to reducing the highest risk.

To build a risk-tiered content governance model for your site:

  1. Categorize your Content Management System (CMS) collections and page types by risk. Identify and rank the impact of incorrect content. Does it affect someone's legal rights, purchasing decision or perception of your brand?
  2. Assign review requirements to each tier. Tier 1 content gets the most reviewers and the longest review window. Tier 3 content gets a quick check before publishing.
  3. Document the tiers and share them with your team. Everyone who creates or publishes content should know which tier their work falls into and what review steps apply.
  4. Revisit your tiers quarterly. As your content strategy shifts, new content types will emerge that need classification.

This model also pairs well with least-privilege access control. Oyster limits each contributor's access to only the CMS collections they need. Cahill described how Oyster limits access to only the collections that each individual needs. That way, “There's no risk of AI hallucinations impacting our site more broadly." Contributors who are new to the platform, or working as contractors, don't get publishing rights at all, which creates a built-in human review step before anything goes live.

Ship with governance, not without it

AI content quality governance comes down to three practices: 

  • Treating accuracy as an ethics requirement
  • Building mandatory review gates into your content management workflow
  • Tiering your content by risk so your team's limited review capacity goes where it matters most. 

Oyster's exponential increase in publishing velocity didn't come from cutting corners. It came from building the right structure around AI-assisted content creation so the team could move faster with confidence.

Webflow gives enterprise marketing and content teams the governance controls to ship at this speed. With Webflow Enterprise, you get granular access controls, staged publishing permissions, and site rollback so your team can publish content at scale while maintaining brand consistency and security. Webflow CMS supports complex, multi-region content operations and has the flexibility to integrate into your existing review workflows and tools.

Watch the full Governing the agentic web to hear Josephine Cahill's complete breakdown of Oyster's AI content governance approach, including the Model Context Protocol incident that rewrote 300 articles and the operational guardrails her team built in response.

Build with Webflow

Webflow Enterprise gives your teams the power to build, ship, and manage sites collaboratively at scale.

Read now

Last Updated
August 17, 2026
Category

Related articles

How Webflow builds security into your site design
How Webflow builds security into your site design

How Webflow builds security into your site design

How Webflow builds security into your site design

Development
By
Webflow Team
,
,
Read article
Website governance for marketing: Create a framework for performance and compliance
Website governance for marketing: Create a framework for performance and compliance

Website governance for marketing: Create a framework for performance and compliance

Website governance for marketing: Create a framework for performance and compliance

Development
By
Webflow Team
,
,
Read article

verifone logomonday.com logospotify logoted logogreenhouse logoclear logocheckout.com logosoundcloud logoreddit logothe new york times logoideo logoupwork logodiscord logo
verifone logomonday.com logospotify logoted logogreenhouse logoclear logocheckout.com logosoundcloud logoreddit logothe new york times logoideo logoupwork logodiscord logo

Get started for free

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.

Get started — it’s free
Watch demo

Try Webflow for as long as you like with our free Starter plan. Purchase a paid Site plan to publish, host, and unlock additional features.