By task
Fact-check a document before it goes out
Upload a PDF, Word file or deck. We find every checkable claim and check the ones you choose.
The report is due tomorrow. It has been through two reviewers, a round of client comments and at least one AI assistant that tidied the executive summary. The argument holds together. What nobody has done is check the facts one by one: the settlement figure on slide 5, the acquisition on slide 6, the date in the second paragraph. This page shows how to do that with CiteJury. You upload the file, choose the claims that matter, and get a verdict and a suggested fix for each, in one report you can hand to whoever signs it off.
Why documents slip through
Documents fail in the details. Reviewers read for argument and tone, and they rarely reopen the source behind every figure. An AI-assisted draft widens that gap, because its sentences read as if someone already checked them.
In November 2025 Fortune reported that a 526-page health workforce plan Deloitte wrote for Newfoundland and Labrador, which cost the province just under $1.6 million, cited research papers that don't exist. Deloitte said it stood by the recommendations, that AI had been "selectively used to support a small number of research citations", and that it was correcting them. The findings weren't the problem. The supporting detail was, and supporting detail is what ends up quoted.
Courts see the same pattern in legal filings. A public database kept by the researcher Damien Charlotin now lists more than 2,000 decisions in which a court or tribunal found that a party relied on AI-generated hallucinated content, mostly fake citations.
A document check is aimed at that layer: the specific, checkable claims a reader will act on.
How a document check works
Upload a PDF, Word (.docx) or PowerPoint (.pptx) file up to 20 MB, or paste the text. Reading it costs about 1 credit. CiteJury pulls out every checkable claim and shows them as a list, each tagged with where it sits in the document.
You choose which to check, up to 25, and you can reword any of them first. That matters more than it sounds. A sentence lifted from slide 5 might say "the company settled for around $3M", and the check needs to know which company. Then pick a tier for the batch and start. You can leave the page while the checks run.
Each claim gets a full check: a search across several independent search indexes that favors primary sources, a sealed evidence pack, separate answers from the AIs, word-for-word quote checks and a final review. The report brings it together. The Claims tab gives each claim a verdict, a one-line headline and a suggested fix you can copy. The Document tab shows your text with every checked claim highlighted in its verdict color. You can download the whole report as Excel for a reviewer or your own records.
Here's a small example: a short PDF with a famous myth on page 2. CiteJury found three claims and we checked two.
Not visible from the Moon. Astronauts and NASA say so.
Suggested fix: The Great Wall is very hard to see even from low Earth orbit, and it isn't visible from the Moon.
Everest's height checked out. The Great Wall line didn't, and its fix is worded so you can paste it straight over the original. In the full report, every highlighted claim opens its own check, with the sources behind the verdict.
A supplier deck, checked
The real test is a working document. This is a supplier-risk deck, "USDA Risk Assessment Sprint.pptx", where we checked 12 claims across its slides. Seven of the 12 needed attention: five came back Correct, four Incorrect and three Sources disagree.
Wrong amount: a $900,000 penalty plus up to $23M in fixes, not about $3M.
Suggested fix: Trident settled Clean Air Act claims with the EPA, paying a $900,000 penalty and agreeing to spend up to $23 million on refrigerant fixes.
Cause and effect reversed: the fire caused the oil spill.
Suggested fix: Washington's Department of Ecology fined Trident $25,000 after a fire ruptured hoses and spilled oil.
It bought one business unit, not the company.
Suggested fix: Blue Harvest acquired High Liner Foods' scallop business and its New Bedford processing plant.
The errors are the kind that survive review, because each one is nearly right.
- Wrong amount. Slide 5 said Trident Seafoods settled with the EPA for around $3 million under the Clean Air Act. The sources describe a $900,000 penalty plus an agreement to spend up to $23 million on refrigerant fixes. Claude, ChatGPT and Grok all said Incorrect. The suggested fix: "Trident settled Clean Air Act claims with the EPA, paying a $900,000 penalty and agreeing to spend up to $23 million on refrigerant fixes."
- Cause and effect reversed. The deck said Washington fined Trident $25,000 for oil spill negligence that led to a fire. The sources tell it the other way round: a fire ruptured hoses and spilled oil, and the state's Department of Ecology fined the company $25,000.
- Part mistaken for the whole. Slide 6 said Blue Harvest Fisheries acquired High Liner Foods. It bought High Liner's scallop business and its New Bedford processing plant, not the company.
The Sources disagree verdict on the USDA award ("nearly $29M to Blue Harvest and two other firms") is a different kind of signal. It doesn't say the slide is wrong. It says the evidence conflicts, so the figure needs a source you can name, or more careful wording.
None of these would have been caught by rereading the deck. Each needed someone to find the original records and compare them with the slide, line by line. That's the work the check does, with the sources attached so a reviewer can see it was done.
Check a document yourself
- Upload the version you'll send. Claims change in late edits, so a near-final draft works best. PDFs need a text layer.
- Prune the claim list. Keep what a reader would act on or quote: figures, dates, legal and regulatory statements, and claims about named companies and people. Drop opinions and the obvious.
- Add missing context. Edit claims that lean on the slide around them. Replace "the company" with its name and "last year" with the year.
- Choose a tier. Standard, with Claude, ChatGPT and Grok plus a final review, is about 8 credits a claim and suits anything going to a client or a board. Quick, at about 2, is fine for an early draft. Deep, at about 32, searches wider and is worth it for niche regulatory or industry claims.
- Work the report from the top. Start with Incorrect, then Sources disagree, then Can't confirm. Open the sources for anything you'll have to defend.
- Copy the fixes you accept. Paste the suggested wording or adjust it, then download the Excel report for whoever reviews the final version.
You pay what each check actually uses: an estimate is held while it runs and the rest comes back. Failed checks are free.
A pre-send checklist
Whatever the document, the same few kinds of sentence cause most of the trouble.
- Enforcement and legal history. Fines, settlements and lawsuits get rounded, merged and misdated. They're also the claims most likely to upset the company named.
- Deals. Acquired or invested in, the company or one of its divisions, announced or completed.
- Market sizes and survey figures. Check the year, the scope and the publisher. There's a separate guide on tracing a statistic to its source.
- Anything an AI rewrote. Summaries compress: "partial" becomes "full" and "up to" becomes "about".
- Citations. Make sure a cited report says what your sentence says. CiteJury checks the claim, not the formatting of the reference.
- Claims you inherited. Last quarter's deck is a common source of this quarter's errors.
Consultants sending client work can read the guide for client decks and reports, and investors reviewing someone else's deck can see how to check a pitch deck before the partner meeting.
What it won't do
- Read scanned PDFs. There's no OCR, so a PDF without a text layer can't be read.
- Check charts and images. It checks text. A number that only appears inside a chart or picture isn't checked.
- Check everything at once. You choose up to 25 claims per document, so in a long report, pick the ones that carry the argument.
- Open every source. Pages behind paywalls or logins, and some sites that block automated access, can't be read. Each check lists what it couldn't open.
- Validate a bibliography or detect plagiarism. It checks what a sentence claims against sources it finds. It doesn't format or validate a reference list, and it isn't a plagiarism detector.
- Replace your judgment. Verdicts can be wrong or incomplete, and they aren't legal, financial or medical advice. Every claim links to its full check and sources, so you can confirm what you rely on.
CiteJury keeps the text of a document, not the file, and doesn't train AI models on your content.
Most document errors aren't dramatic. They're a rounded figure, a reversed sequence, a division mistaken for a company. They're also the sentences a reader remembers. Checking them before the file goes out leaves you with a source behind every claim you chose to check.
Questions people ask
Which file types can I upload?
PDF, Word (.docx) and PowerPoint (.pptx) files up to 20 MB, or you can paste text. Scanned PDFs without a text layer can't be read, because there's no OCR.
How many claims can I check in one document?
CiteJury finds every checkable claim in the document, and you choose up to 25 to check. You can reword any claim before the checks start.
What do I get at the end?
One report for the whole document: a Claims tab with a verdict, a headline and a suggested fix for each claim, and a Document tab with each claim highlighted in its verdict color. You can download the report as Excel.
How much does a document check cost?
Reading the document costs about 1 credit, and each claim you check is charged as a check at the tier you choose. Credits cost $0.10 each, you pay only what a check uses, and failed checks are free.
Do you keep my file?
No. CiteJury keeps the text of the document, not the file, and doesn't train AI models on your content.
Check the facts before you hit send.
New accounts get 100 free credits. Failed checks cost nothing.