The Gate Check: Auditing PolicyBazaar's AI Content Pipeline for Missing Quality Gates
Objective: Given a real AI-assisted blog production log, identify which of the lesson's four quality gates are missing and what breaks without them.
You're a content ops analyst on PolicyBazaar's insurance blog team. Leadership just doubled the AI drafting quota with no new hires, and one article got flagged for citing a lapsed premium cap.
Walk a 10-article production log and flag which quality gate would have caught each problem before publish.
Before you start
What you'll need
Free path (everything below is enough to finish)
Free, no setup, easy to filter and sort a production log
The process
1 step
Step 01 of 01
Gate 2 in the lesson requires every stat, date, and named example to have a source before a draft can move forward; an invented or outdated number gets cut, no exceptions.
Given this production log of 10 AI-drafted articles, 3 shipped with stats that were never checked against a source. Which gate was skipped, and what's the fix?
Procedure
- Import the 10-row production log into Google Sheets
- Add a 'Source Verified' column and mark each row Y/N based on whether a source URL is logged
- Isolate the 3 rows marked N, these are the fact-verification gate failures
Row 4: 'health insurance claim settlement ratio hit 99.9% in 2025' — Source Verified: N Row 7: 'premium up to Rs 5 lakh is tax-free under Section 80D' — Source Verified: N (cap is outdated, changed in the last budget) Row 9: 'more than 60% of Indians are now insured' — Source Verified: N
Healthy
Every published stat has a logged source URL and a check date before the article leaves the drafting stage.
Unhealthy
Three of ten articles publish with unverified or outdated numbers because no one owns the fact-check step.
What this means
This isn't a writing-quality problem, it's a missing gate. The brief and voice checks passed; nobody was assigned to verify facts.
So what do I do about it?
| Symptom | Action | Effort |
|---|---|---|
| AI drafts contain a specific stat with no source | Add a mandatory 'Source Verified' column to the production tracker and block publish until it's filled | 30 min |
| A regulatory or pricing number appears in a draft | Route the article to a subject-matter reviewer before the editor pass, not after | 5 min |
Final deliverable
A gate-failure report flagging which of the 3 problem articles lacked fact verification, with a proposed tracker column to prevent recurrence.
See a reference example
Snowflake DevRel blog, Q2 gate audit (excerpt) GATE 2 FAILURE (1 of 8 articles) 'Data warehousing costs dropped 40% industry-wide in 2025' — no source logged, flagged before publish, corrected to a cited Snowflake benchmark stat
Success criteria
You're done when you can:
- Correctly identifies all 3 gate-2 failures in the log
- Proposes a concrete tracker fix, not just 'be more careful'