IPVectors
IPVerifier · user guide

Install it, run your first audit, read the verdict.

IPVerifier is a Word add-in. It puts an AI analysis on trial before anyone relies on it: independent frontier models, in fixed adversarial roles, check every assertion against the source document and band the result. This page takes you from the Marketplace listing to a defensible verdict.

Last updated: October 26, 2026 · For IPVerifier 1.0.1

Just installed? Start here.

IPVerifier audits a patent analysis. Point it at a report you are reviewing and it tests every assertion in that report against the source document the report claims to rest on — then tells you which findings hold, which hold with caveats, and which you should not rely on, with the quoted passage behind each one.

That matters because an AI analysis reads the same whether it is right or wrong. A sentence that equates two terms the source never equates looks exactly like the forty true sentences around it. Checking by hand means re-reading the reference end to end, so in practice the analysis ships on trust — and the person who signs it carries the risk.

Two ways to start. If you have a non-confidential analysis of your own, open it in Word and run the audit; the four steps are in section 2 below. If you would rather see finished output first, section 5 has three real reports you can download and read.

Or send us a document and we will run it for you.

To see IPVerifier work on your own material without setting anything up, email us a document and we will run the audit and send the report back to you, usually within two business days. A published application, an expired matter, or an analysis you are free to share all work well.

Please send non-confidential material only. Do not send anything privileged, client-confidential or under seal. We review each request and will say so if we cannot take one on.

Send us a document →

Before you begin

Microsoft WordThe add-in runs as a task pane beside your document.
An IPVectors accountCreated for you when you request access. The add-in signs in to it on first use.
An internet connectionAudits run on the IPVectors cloud, not on your machine.
A report to auditA Reporter analysis open in Word — the document the audit is locked to.

Your source material is never used to train models. What leaves your machine is covered by the EULA and the privacy policy.

1 · Install from Microsoft Marketplace

  1. Open the IPVerifier listing and choose Get it now.
  2. Sign in with the Microsoft account you use for Word, and confirm the permissions prompt. The add-in can read and change your document, and send data over the internet — both are needed to anchor findings to your text.
  3. Word opens with IPVerifier available. If it does not appear, open Word and go to Home → Add-ins → My add-ins, then pick IPVerifier.
  4. Open the task pane and sign in with your IPVectors account.

2 · Your first audit, in four steps

  1. Ready for review — pick the subject, open the process

    Enter the subject patent and choose Check. The pane lists what is ready for review. Open the report you want audited; the add-in binds to the document now open in Word, so every finding and every jump lands in that exact file. Audit the report of record, not a scratch copy.

  2. Choose the compared patent

    Pick the compared-patent block you need defended. The pane shows its sections with the analysis's stated conclusion on each row, and a pre-flight estimate before anything runs. Work in reliance order: the highest-rated candidate first, then anything your position will actually cite.

  3. Pick the sections and run the council

    Tick the sections to audit, then run. The council fetches the authoritative text for that reference and puts each assertion through independent models in fixed adversarial roles — one arguing against the analysis, one for it, with a separate judge. No model grades its own work, and every assertion must cite near-verbatim text from the source. An assertion without support is flagged, not published.

  4. Read the verdict

    Each audited section comes back banded, with the dissent visible and a jump straight to the block in your document. This is the moment that matters: an amber or red band caught here is a credibility problem that never reached your client.

BandWhat it meansWhat to do
Green — verified Supportable by a direct quote from the source.Safe to rely on.
Amber — verified with caveats Inferred rather than stated in so many words.Read it yourself before relying on it.
Red — do not rely The source does not support the assertion.Fix the analysis, regenerate, re-audit.

3 · What you get

  • A banded verdict for every audited section, each finding carrying the passage it rests on.
  • A signed, hash-chained record of the audit, which you can retain for provenance.
  • A review-ready Legal Case Brief curated from the blocks you keep.
  • History — every completed audit is recorded and can be re-opened later.

Corrections belong upstream: fix the analysis in Reporter, regenerate, then re-audit.

4 · Watch an audit, start to finish

Chapter 7 of the IPVectors films — the trial inside Word, and the seal. The full series, including Reporter and Gap-Hunter, is in the film room.

5 · Sample reports

Real output, unedited apart from a sample notice on the first page. The subject is US9730910B2, a patent a United States court held obvious in 2022 — chosen because the references the court relied on are a matter of public record, so the run can be scored rather than admired. Nothing here is legal advice, and every conclusion belongs to the attorney who signs it.

Claim-centric §103 report

The combination analysis for a single claim, limitation by limitation, with the evidence behind each one and the pieces that stayed open.

Download · Word, 91 KB

Provenance appendix

Every reference in that report traced back to how it was found and what it was graded against.

Download · Word, 64 KB

Prior-art report

The ranked references, the claims breakdown, and the function / way / result reading of each.

Download · Word, 135 KB

Signed audit record

The hash-chained JSON an audit produces, as retained for provenance.

Coming soon

Troubleshooting

The task pane looks stale, or a feature I expect is missing.

Word caches add-ins aggressively. Check the build stamp in the pane footer; if it is behind, close Word, clear the add-in cache, reopen, and sign in once.

The verdict refused to audit, or says there is no source text.

The council will not audit without real source text — it states the reason and the fix. The usual causes are a reference with no open-record full text, or an abstract-only paper with too little to check.

A foreign-language patent says it cannot be audited yet.

It needs a verifiable translation first. Produce one in the translation tab and have your expert attest it; the audit then runs against the attested text and says so in the verdict.

The jump to a block did not land anywhere.

The jump tries the exact quote, then the compared block, then the section, and explains itself when all three miss. Jumps need a bound document — reopen the report for review with it open in Word.

I clicked stop but the audit finished anyway.

Cancellation is cooperative. A model call already in flight always completes; the audit stops at the next boundary.

The progress bars stopped but no verdict appeared.

The audit runs on the server, not in the pane. Open History: "done" means the verdict is ready to open, "running" means give it a few more minutes.

Still stuck? Write to us from the contact page and include the build stamp from the pane footer and the subject patent number. That pair is usually enough to answer without a back-and-forth.

IPVectors Inc. is not a law firm and does not provide legal advice. IPVerifier supports the professional who signs the work; it does not replace them.