HomeLibraryServicesCase studiesBlogAbout
consultance.ai
Book a discovery call →

Services

  • AI consulting
  • AI implementation
  • AI agents
  • Workflow automation
  • RAG systems
  • Voice AI
  • Custom AI development
  • All services

Library

  • AI build library
  • Finance AI automation
  • AiToEarn content agent
  • Fincept Terminal
  • ERPNext
  • SEO + GEO Claude skill
  • Claude for Legal
  • Free Claude Code proxy

Resources

  • Case studies
  • Blog
  • Industries
  • Locations
  • Guide: AI for property management
  • Guide: AI for marketing agencies
  • Guide: AI agents vs Zapier
  • AI glossary
  • vs traditional consulting

Company

  • About
  • Book a call
  • Contact
  • Privacy
  • Terms

© 2026 consultance.ai · AI, implemented.

audit → build → deploy

← Libraryconsultance.ai
Book a build call
Big 4 advisory

The AI Output Verification Pack

For anyone who signs off on an AI-assisted report, model, or board pack: 13 Claude prompts that fact-check every citation, quote, and number before you ship it.

Free — runs in your own ClaudeMedium setup · 4 steps9 ready-to-run prompts
Set it up free — takes 3 minutes ↓Or have us wire it in →
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. 1

    Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. 2

    Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. 3

    Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai ↗
  4. 4

    Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

I want to INSTALL the real setup so Claude runs the verification pass on my actual deliverable and its real sources, not just a chat demo. Walk me through it step by step, do not skip the install. Treat me like a CFO, audit committee chair, general counsel, or deal lead who has never built a Claude Project or installed an Office add-in, and define every term once.

This is NOT a Terminal or coding install. There is nothing to compile. It is two paths: a private Claude Project where the draft and its source documents live (recommended) and an optional Word or Excel add-in for checking the file in place.

## Path 1 (RECOMMENDED) — a private Claude Project for the deliverable and its sources
This is the path that makes verification real. The check only works if Claude can see the actual sources the deliverable cites, not just the draft.

Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account on a Team or Enterprise plan so the data stays in my tenant. Pin **Opus 5**. Nothing to install for this path.
2. **Create the verification desk.** In Claude, create a new **Project** named for the deliverable and the date. A Project is a private workspace with its own knowledge that other chats cannot see. Your draft and your sources stay in your own tenant.
3. **Load the material.** This is the step people skip and then wonder why the pass is weak. Drop in BOTH the draft deliverable AND the documents it cites: the source reports, the filings, the data files, the contracts, the cases. Verification compares the draft against these. No sources loaded means the best Claude can do is mark a line UNVERIFIED.
4. **Run the vault.** Run prompt 01, pick what you are verifying (a report, a model, a legal document, a research piece, a board pack) and your data source (A) upload, or (D) a governed connector if you pull from a VDR or filings database. Then run 02 to 09 in order: citation existence, quote trace, number tie-out, claim against source, the confident-and-wrong sweep, internal consistency, the self-check gate, and the verification report.
5. **Gate it.** Treat prompt 08 (the self-check) as a hard gate. If the unresolved count is above zero, the deliverable is NOT cleared to ship until each item is fixed. A named human signs before anything leaves the firm; a prompt cannot sign.
6. **Shadow run first.** Run the pack on two or three deliverables that already shipped before you trust it on live work. It will catch things in work that already went out. That is the proof. See the 90 day rollout in the bundle.

## Path 2 (OPTIONAL) — Claude for Word or Excel add-in for checking in place
If I want the citation, quote, and number checks to run inside the live document:
1. In Word or Excel (Microsoft 365 desktop or web): **Home** or **Insert** tab, **Add-ins** / **Get Add-ins**, search **"Claude"**, **Add**. Tell me where the button is in my version.
2. Sign in to the docked Claude side panel.
3. In vault prompt 01 choose data source (C) the add-in. Run prompt 04 (number tie-out) in Excel on a model, or prompts 02, 03, and 05 in Word on a report, so the checks run against the live file. Keep the source documents in the Project so the add-in has something to verify against.
4. Pin **Opus 5** for the verification work.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, citation, footnote, primary source, fabricated source, paraphrase drift, misattribution, tie-out, recompute, false precision, the self-check gate, partner sign-off, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If the add-in is missing, check Word or Excel for Microsoft 365, try the web version, or AppSource. For the Project path there is nothing to install.
- The single most common reason this underdelivers is loading the draft without its sources. Make me load the sources.
- Never paste confidential client material into a public Claude window outside a Project. Use a Project with your tenant controls and follow your firm's data policy.
- This moves the verification work in-house and makes the sign-off defensible. It does not replace the named professional who signs, the subject-matter expert on the substance, or your auditor. Read the audit and compliance overlay before you reduce any external scope. A named human signs. Not legal, tax, or accounting advice.

First message: ask me "Path 1 (a private Claude Project for the deliverable and its sources, recommended) and do you also want Path 2 (the Word or Excel add-in for checking in place)? What are you verifying first (a report, a model, a legal document, a research piece, or a board pack), and do you have the source documents it cites ready to load?" Then start step 1.
Step 2 · run it on your data

Step 1 set it up. These 9 prompts do the work.

the vault

The 9 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 9 prompts, numbered, in order · nothing left out.
Click to copy
You are my verification desk, acting as four people on every pass: a forensic fact checker who has caught fabricated sources before, a research librarian who confirms a citation by finding the actual source, an audit senior who ties every number back to a document, and a paranoid managing partner whose name goes on this and who has been burned once.

Before we start, ask me and wait for my answers:

1. What am I verifying?
   (A) A report or memo with citations
   (B) A financial model or a deck full of numbers
   (C) A legal or contract document
   (D) A research piece or literature review
   (E) A board or investment committee pack

2. Where is the material? This decides how the next prompts run.
   (A) I upload the draft AND the source documents it cites into this Project.
   (B) I paste the draft text, and I will paste sources when you ask.
   (C) I use the Claude add-in for Microsoft Word or Excel on the live file.
   (D) I pull sources from a governed connector (our VDR, a filings database, a market-data terminal).
   (E) A mix.

3. Context: who is the audience for this deliverable, who signs it, and what is the worst outcome if a wrong line gets through (refund, regulator, lawsuit, lost deal, reputational)?

Once I answer, confirm the setup in three lines, then wait for the material. On every later pass: judge a claim only against a source you can actually see. If you cannot see the source, say UNVERIFIED, never assume it is fine. End every answer with: "Verification pass only. A named human signs before this ships."
Click to copy
Using the material from prompt 01, check that every citation in the deliverable actually exists.

For each reference, footnote, link, and source named:
1. State the claim it is attached to.
2. Verdict: EXISTS (you can confirm it from the uploaded sources), UNVERIFIED (you cannot see the source to confirm), or LIKELY FABRICATED (the source has the shape of an AI invention: plausible title, real-sounding author or journal, but no trace in the provided material).
3. For anything not EXISTS, say exactly what you would need to confirm it.

Output a numbered citation table: claim, cited source, verdict, what is missing. Rank the LIKELY FABRICATED items to the top. Do not pass a citation as fine just because it looks well formatted. A clean format is how fabricated sources hide.

End with the count: X exist, Y unverified, Z likely fabricated. Then "Verification pass only. A named human signs before this ships."
Click to copy
Using the material from prompt 01, trace every quotation and every attributed statement in the deliverable.

This is the Deloitte failure mode: quotes pinned on court judgments and papers that never said them.

For each quote or "X said / the ruling found / the standard requires" line:
1. Find the exact source and location (page, section, paragraph) in the provided material.
2. Verdict: TRACED (the source says this, word for word or in clear substance), PARAPHRASE DRIFT (the source exists but does not support the wording or the meaning), MISATTRIBUTED (a real source, wrong author or wrong document), or UNTRACEABLE (no source in the material supports it).
3. Quote the actual source line next to the deliverable's version so I can compare.

Flag every PARAPHRASE DRIFT, MISATTRIBUTED, and UNTRACEABLE item as a blocker. A quote with no traceable source does not ship. End with "Verification pass only. A named human signs before this ships."
Click to copy
Using the material from prompt 01, tie every number in the deliverable back to a source.

For each figure, percentage, total, and date that carries weight:
1. Trace it to the source document, the input I provided, or a calculation you can reproduce from those.
2. Verdict: TIED (sourced or reproducible), DERIVED (you can recompute it from tied inputs, show the arithmetic), or UNSOURCED (no basis in the provided material).
3. For DERIVED numbers, recompute and confirm the deliverable's figure matches. Flag any mismatch.

Output a tie-out table: number, where it appears, source, verdict, recomputed value if applicable. List every UNSOURCED number and every recompute mismatch at the top as blockers. Never accept a number because it sounds reasonable. End with "Verification pass only. A named human signs before this ships."
Click to copy
Using the material from prompt 01, test each substantive factual claim against what the cited source actually says.

This is the EY failure mode: a real citation attached to a claim the source does not support.

For each claim that cites or implies a source:
1. Read what the source actually says in the provided material.
2. Verdict: SUPPORTED (the source backs the claim), OVERSTATED (the source says something weaker or narrower), CONTRADICTED (the source says the opposite or materially different), or SOURCE NOT PRESENT (cannot test without the source, mark UNVERIFIED).
3. For OVERSTATED and CONTRADICTED, quote the source line and show the gap.

Rank CONTRADICTED first, then OVERSTATED. These are the lines that survive a citation check but fail on substance. End with "Verification pass only. A named human signs before this ships."
Click to copy
Using the material from prompt 01, hunt for assertions stated with more confidence or precision than the sources support.

Find:
1. False precision: a specific figure or date where the source is vague or a range.
2. Hardened hedges: a source that says "may" or "estimated" turned into "will" or "is".
3. Stale as current: a past data point presented as today's number, with no date.
4. Single source stated as consensus: "studies show" or "it is well established" resting on one or zero sources.
5. Plausible filler: smooth sentences that assert a fact with nothing behind them.

For each, quote the line, state why it overreaches, and give the corrected, defensible version. End with "Verification pass only. A named human signs before this ships."
Click to copy
Using the material from prompt 01, check the deliverable against itself.

1. Numbers that contradict across sections (a figure on page 2 that disagrees with the same figure on page 9).
2. Totals that do not foot, subtotals that do not sum, percentages that do not reconcile to their base.
3. Dates, names, and defined terms used inconsistently.
4. Conclusions that the body does not support.

Recompute every total and percentage. Show the arithmetic. Output a list of every contradiction and every failed recompute with the two conflicting locations. End with "Verification pass only. A named human signs before this ships."
Click to copy
Now verify your own verification. Do not skip this.

1. Re-read prompts 02 through 07 and the deliverable. List anything you marked TIED, EXISTS, TRACED, or SUPPORTED that you cannot actually defend from a source you can see. Move it to UNVERIFIED.
2. Produce a sign-off sheet with four lines, each PASS or BLOCK:
   - Citations: every cited source EXISTS or is removed.
   - Quotes: every quote TRACED to a real source.
   - Numbers: every figure TIED or DERIVED and recomputed.
   - Claims: every claim SUPPORTED by its source, no CONTRADICTED line left.
3. Count the unresolved items. State the rule plainly: if the count is above zero, this deliverable is NOT cleared to ship.

If anything is BLOCK, list exactly what must be fixed and stop. Do not soften the verdict to be helpful. A clean sign-off you cannot defend is the exact failure that cost Deloitte the refund. End with "Verification pass only. A named human signs before this ships."
Click to copy
Using prompts 02 through 08, produce the verification report a reviewer or auditor can keep.

1. One-line verdict: CLEARED or NOT CLEARED to ship.
2. Blocker list: every fabricated citation, untraceable quote, unsourced number, and contradicted claim, each with its location and the fix.
3. The sign-off sheet from prompt 08.
4. A verification log: what was checked, against what sources, and the date, so there is a record of the pass that survives later edits.
5. The single highest-risk line in the document and why.

Keep it to two pages. This is the artifact that proves the work was checked. End with "Verification pass only. A named human signs before this ships."

Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.

Book the free audit

Rent it forever, or own it once.

For anyone who signs off on an AI-assisted report, model, or board pack: 13 Claude prompts that fact-check every citation, quote, and number before you ship it.

Path A · free

You just did it

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts ↑
Path B · done with you

We wire it into your business

We would deliver a private verification workspace: the prompts loaded into your Claude tenant, a connector to the sources your deliverables cite (your VDR, filings, market data), the self-check gate wired as a real pre-ship control, and a retained verification log mapped to PCAOB AS 1215, SOX 404, NIST AI RMF, or ISO 42001 so the pass survives edits and your auditor accepts it. Done with you, then handed over so you own it.

Book a build call →
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. Deloitte and EY are referenced as the public, documented failures the pack guards against, no affiliation implied. Your draft and sources stay in your own Claude tenant; we never see them. This produces a verification pass and decision-support, not a sign-off; a named human reviews and signs before any deliverable ships, and the relevant professional standards apply. Not legal, audit, accounting, or investment advice.

Want this running in your business, not just your laptop? We build it and hand you the keys.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI strategy consulting service.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

More like this

Other builds worth a weekend

All repos →
Big 4 advisory

Big 4 Consulting Prompts for Claude

Finance and ops teams run 12 Claude prompts for Big 4 consulting workflows like financial analysis and due diligence, shipping advisory work in minutes instead of weeks.

Setup guide →
Big 4 advisory

Free Big 4 Advisory Agent Kit

For PE deal teams and CFOs: three Claude agents that monitor tax and regulation exposure, read a data room like an FDD associate, and draft the IC memo. The diligence work KPMG advisors bill at $400 an hour, run in house.

Setup guide →
Big 4 advisory

Second Opinion on Audited Financials

A second review on financials someone already signed, in your own Claude. 8 prompts test every estimate and reserve, hunt fraud flags, and write a red-flag memo before you trust the numbers.

Setup guide →
Get the free kitBook a call

Forward this to whoever owns the workflow.

The person drowning in this every week is the one who'll actually want it.

Forward by email
in one line

What is The AI Output Verification Pack?

The AI Output Verification Pack is a big 4 advisory build in the consultance.ai AI Build Library. For anyone who signs off on an AI-assisted report, model, or board pack: 13 Claude prompts that fact-check every citation, quote, and number before you ship it. It fits CFOs, audit committee chairs, general counsel, PE deal leads, and anyone who signs off on a report, model, memo, or board pack that an AI helped write. Setup difficulty is Medium, with 4 plain-English steps.

What does The AI Output Verification Pack do?

For anyone who signs off on an AI-assisted report, model, or board pack: 13 Claude prompts that fact-check every citation, quote, and number before you ship it.

Who is The AI Output Verification Pack for?

It fits CFOs, audit committee chairs, general counsel, PE deal leads, and anyone who signs off on a report, model, memo, or board pack that an AI helped write.

How hard is The AI Output Verification Pack to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 9 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

We would deliver a private verification workspace: the prompts loaded into your Claude tenant, a connector to the sources your deliverables cite (your VDR, filings, market data), the self-check gate wired as a real pre-ship control, and a retained verification log mapped to PCAOB AS 1215, SOX 404, NIST AI RMF, or ISO 42001 so the pass survives edits and your auditor accepts it. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. Deloitte and EY are referenced as the public, documented failures the pack guards against, no affiliation implied. Your draft and sources stay in your own Claude tenant; we never see them. This produces a verification pass and decision-support, not a sign-off; a named human reviews and signs before any deliverable ships, and the relevant professional standards apply. Not legal, audit, accounting, or investment advice.

Want this built into your workflow?

The AI Output Verification Pack is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.

This build comes from our AI consulting and AI implementation practice, serving businesses across the USA and Canada.

Book your free AI audit