Run a Citation-Existence Audit on a Thought-Leadership Draft Before It Ships

The task

Senior consultants and practice-lead editors run this on any thought-leadership draft — POV memo, deployment case study, transformation white paper — before it goes to the client or the marketing team. The reason is simple: fabricated citations are now showing up in shipped consulting work, and one bad footnote can nuke a vendor pitch or a partner's credibility with a CIO.

Before AI

The manual version is a junior consultant with two browser windows: one for the draft, one for Google. They extract every citation by hand, search each one, verify the author/date/publisher, and flag anything they can't find. On a 20-page white paper with 30-40 citations that's a half-day, and half the time the reviewer skims and misses a stale stat that's been superseded by a newer vendor report.

The workflow

Step 1 — Extract every citable claim. Paste the draft. This prompt pulls out anything that reads like a factual assertion tied to a source, whether formally footnoted or referenced inline ("Gartner says…", "a 2024 McKinsey survey found…").

You are a citation auditor for a management consulting firm reviewing a thought-leadership draft before publication. Your first job is extraction, not verification.

From the draft below, extract every citable claim. A citable claim is any statement that:
- names a source (analyst firm, vendor, government body, academic paper, journalist, executive)
- cites a statistic, percentage, dollar figure, or market size
- references a specific study, report, survey, or dataset
- attributes a quote or position to a named person or organization

Return a numbered table with columns: ID | Claim (verbatim quote from draft, <=25 words) | Named source (or "unnamed") | Type (stat / study / quote / attribution / market-figure) | Date mentioned in draft (or "none").

Do NOT verify anything yet. Do NOT add commentary. Just extract. If the draft contains zero citable claims, say so and stop.

Draft follows:
---

DRAFT: "Rewiring the Mid-Market CFO Stack: A 2026 POV"
By Prakash Menon, Partner, Northstar Advisory

Executive summary
Mid-market finance functions are at an inflection point. Gartner's 2025 CFO Technology Survey found that 74% of mid-market CFOs plan to consolidate their FP&A and close tooling onto a single platform within 18 months, up from 41% in 2023. This aligns with what we are seeing in our own transformation engagements across the $500M–$2B revenue band.

The economics are compelling. A recent McKinsey Global Institute report ("The Productivity Dividend of Finance Automation," March 2024) estimates that fully instrumented close-to-report processes reduce cycle times by 38–52% and free roughly 1.9 FTEs per $1B of revenue. In our engagement with a Midwest industrial distributor (revenue ~$780M), we saw an 11-day close compressed to 4 days over two quarters.

Vendor landscape
Three vendors dominate the shortlist we build for clients: Workday Adaptive, Anaplan, and OneStream. Forrester's Q4 2025 Wave for Extended Planning and Analysis named OneStream a Leader for the fourth consecutive cycle, citing "unmatched depth in financial consolidation." Anaplan, per IDC's 2025 MarketScape, remains the strongest fit for revenue-planning-heavy organizations. Workday Adaptive continues to win on time-to-value; Deloitte's 2024 Finance Benchmarking Study pegged median deployment at 14 weeks for mid-market clients.

The AI overlay
Every serious vendor now ships an agentic layer. OpenAI's enterprise adoption report (June 2026) noted that 61% of Fortune 1000 finance teams have deployed at least one generative-AI workflow in production. Klarna's CFO, Niclas Neglén, stated in a Financial Times interview last October that AI had "removed roughly 40% of routine reconciliation work" inside the company's finance org.

Recommendation
For CFOs of $500M–$2B businesses evaluating this space in the next two quarters, we recommend a three-vendor bake-off structured around close acceleration, driver-based planning, and an AI-agent proof-of-value tied to a single high-volume reconciliation flow. Firms that delay past mid-2026 will, per our internal benchmarking, face a widening capability gap versus consolidators.

Step 2 — Audit each extracted claim for existence and plausibility. The model can't browse, but it can flag citations that don't match known publication patterns, invented report titles, mis-dated Waves, or figures that contradict widely-reported ranges.

You are now auditing the extracted claims from Step 1. You cannot browse the web. Do NOT invent verification — instead, classify each claim by how confidently a human fact-checker can trust it based on internal plausibility signals.

For every ID from the table, produce:
- Verdict: one of [LIKELY_REAL, SUSPECT, LIKELY_FABRICATED, UNVERIFIABLE_HERE]
- Reason (one sentence): reference specific signals — Does the analyst firm actually publish that report series? Does the report title match that firm's real naming conventions? Is the date plausible given the firm's publishing cadence? Is the statistic within a reasonable range for that domain? Is the named executive real and in that role at the cited time?
- What to check: the exact query or lookup a human should run (e.g., "Search Gartner site for 'CFO Technology Survey 2025' — confirm existence and the 74% figure").

Be blunt. If a report title sounds plausible but you have no memory of it, mark SUSPECT, not LIKELY_REAL. If a stat looks made-up-round (e.g., suspiciously clean 40%/50%/75%) and the attributed source is a press interview rather than a filing, flag it. If a Wave or MarketScape is cited, check whether the vendor category name matches how that firm actually labels it.

Output as a table: ID | Verdict | Reason | What to check.

Step 3 — Produce the reviewer's action list. Turn the audit into something a partner can actually work from in 15 minutes.

Convert the Step 2 audit into a prioritized reviewer action list for the drafting partner. Group items into three sections:

1. BLOCK SHIPPING — any LIKELY_FABRICATED item, or any SUSPECT item that is load-bearing for the draft's central recommendation. For each, quote the exact sentence from the draft that must be removed, replaced, or re-sourced.
2. VERIFY BEFORE SHIPPING — SUSPECT and UNVERIFIABLE_HERE items that are not load-bearing. Give the partner the specific lookup and a suggested time-box (e.g., "5 min: search Forrester's site for the Q4 2025 XP&A Wave").
3. SAFE BUT TIGHTEN — LIKELY_REAL items where the draft's wording overstates or ages the source (e.g., citing a 2023 stat as current, or paraphrasing a quote loosely). Suggest a tighter rewrite for each.

End with a one-line ship/hold recommendation and the count of items in each bucket.

Gotchas

• The model cannot actually browse. Step 2 is a plausibility filter, not proof of existence. LIKELY_REAL still needs a human click-through for anything load-bearing. Treat this workflow as triage, not verification.
• Analyst-firm naming drifts. "Forrester Wave for Extended Planning and Analysis" is real; "Forrester Wave for FP&A Modernization" is not — but the model may not catch subtle relabeling in categories that were recently renamed. Keep a human familiar with the vendor space in the loop.
• Confident-sounding executives are the highest-risk category. Quotes attributed to real CFOs at real companies in real publications are the easiest thing to hallucinate and the hardest to disprove without pulling the actual article. Always click through on any direct quote.
• Round-number stats from press interviews ("40% reduction", "3x productivity") should default to SUSPECT even when the source is real — they're often paraphrased loosely from the original.
• Internal engagement anecdotes (the "Midwest industrial distributor" type) are unverifiable by this workflow. Confirm with the engagement partner directly that the numbers match the SOW record.

Time saved

Roughly 2-3 hours per 15-25 page white paper, based on a manual baseline of a junior consultant spending 4-5 hours to extract, search, and log every citation, versus 60-90 minutes of partner-level review against a pre-triaged action list. The saving is largest on drafts with 25+ citations where the manual approach breaks down into skimming.

What we got when we ran it

We executed every prompt above, in order, against the sample input (model: claude-sonnet-4-6). Outputs below are real and unedited apart from length truncation.

Step 1 output

| ID | Claim (verbatim quote from draft, ≤25 words) | Named Source | Type | Date Mentioned in Draft | |----|----------------------------------------------|--------------|------|------------------------| | 1 | "Gartner's 2025 CFO Technology Survey found that 74% of mid-market CFOs plan to consolidate their FP&A and close tooling onto a single platform within 18 months" | Gartner | stat | 2025 | | 2 | "up from 41% in 2023" | Gartner | stat | 2023 | | 3 | "McKinsey Global Institute report ('The Productivity Dividend of Finance Automation,' March 2024)" | McKinsey Global Institute | study | March 2024 | | 4 | "fully instrumented close-to-report processes reduce cycle times by 38–52%" | McKinsey Global Institute | stat | March 2024 | | 5 | "free roughly 1.9 FTEs per $1B of revenue" | McKinsey Global Institute | stat | March 2024 | | 6 | "Forrester's Q4 2025 Wave for Extended Planning and Analysis named OneStream a Leader for the fourth consecutive cycle" | Forrester | study | Q4 2025 | | 7 | "citing 'unmatched depth in financial consolidation'" | Forrester | quote | Q4 2025 | | 8 | "Anaplan, per IDC's 2025 MarketScape, remains the strongest fit for revenue-planning-heavy organizations" | IDC | attribution | 2025 | | 9 | "Deloitte's 2024 Finance Benchmarking Study pegged median deployment at 14 weeks for mid-market clients" | Deloitte | stat | 2024 | | 10 | "OpenAI's enterprise adoption report (June 2026) noted that 61% of Fortune 1000 finance teams

…output truncated at 250 words.

Step 2 output

| ID | Verdict | Reason | What to check | |----|---------|--------|---------------| | 1 | SUSPECT | Gartner does publish CFO-oriented research, but "CFO Technology Survey" is not a well-known recurring branded series the way Gartner Magic Quadrant is; the specific title and 74% figure cannot be confirmed from memory. | Search Gartner.com and press releases for "CFO Technology Survey 2025"; confirm the report exists, its exact title, and the 74% consolidation figure. | | 2 | SUSPECT | The 2023 baseline figure of 41% is a companion stat to ID 1 and is equally unverifiable; the 33-point jump in two years is a large and conveniently dramatic swing. | Same lookup as ID 1; confirm whether the 2023 wave of the same survey exists and reported 41%. | | 3 | SUSPECT | MGI does publish automation and productivity reports, and the topic is plausible, but the exact title "The Productivity Dividend of Finance Automation" does not match any MGI report in memory; MGI titles tend to be broader in scope. | Search McKinsey.com/mgi for the exact title; confirm March 2024 publication date and that it covers finance-function cycle times specifically. | | 4 | SUSPECT | The 38–52% cycle-time reduction range is plausible in direction but suspiciously precise for a range, and it depends entirely on the unverified MGI report in ID 3. | Within the same MGI report lookup, confirm the 38–52% figure appears verbatim and is not paraphrased or aggregated from multiple sources. | | 5

…output truncated at 250 words.

Step 3 output

# Reviewer Action List — "Rewiring the Mid-Market CFO Stack: A 2026 POV" Prepared for: Prakash Menon, Partner, Northstar Advisory Auditor note: This list is sequenced by publication risk, not section order. --- ## SECTION 1 — BLOCK SHIPPING These items must be resolved before the draft leaves the building. Either remove, replace with a verified source, or re-source with primary evidence in hand. --- ### BLOCK-A — ID 10: Fabricated Source (LIKELY_FABRICATED) Exact sentence to remove or replace: > "OpenAI's enterprise adoption report (June 2026) noted that 61% of Fortune 1000 finance teams have deployed at least one generative-AI workflow in production." Why it blocks shipping: OpenAI does not publish a known recurring "enterprise adoption report." This title matches no real OpenAI publication series. A client, journalist, or competitor who checks this footnote will find nothing — an immediate credibility catastrophe for a published POV. The stat is also load-bearing: it is the only external evidence offered that the "AI overlay" section describes a real, scaled market phenomenon rather than vendor hype. Required action: Remove the sentence entirely, or replace with a verifiable alternative (e.g., a Gartner or IDC survey on generative-AI adoption in enterprise finance that you can cite with a document URL in hand). Do not publish with this sentence in any form. --- ### BLOCK-B — IDs 1 & 2: Unverified Survey Underpinning the Core Recommendation (SUSPECT, load-bearing) Exact sentence to remove or replace: > *"Gartner's 2025 CFO Technology Survey found that 74% of mid-market CFOs

…output truncated at 250 words.