What should an evidence pack for a review dispute contain?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
An evidence pack should let a stranger reconstruct your review history without trusting you: the imported rows themselves, the per-review signal analysis, each review's transaction link or its honest absence, the full provenance chain of import and moderation events, and the summary counts — including negative reviews kept. ReviewProof's evidence export (Pro and Agency) assembles exactly that: full provenance chains, the moderation log and the risk report, in one document you can hand over.
What is a review evidence pack?
A review evidence pack is a self-contained bundle of primary records assembled to answer a challenge — a platform dispute, a regulator's question, a partner's due diligence, a charge of suppression or fabrication. Its defining quality is that it contains evidence, not assertions: rows, dates, references (masked where they are customer data), decisions and the reasoning logged at the time, rather than a letter saying the business acted properly.
Assemble it before anyone asks
A pack built during a dispute is assembled under suspicion and time pressure, from whatever can still be found. A pack exported routinely — after each audit cycle, while imports and moderation decisions are fresh — is simply the record, dated before any challenge existed, which is most of its persuasive force. Build the habit at the level of the import rhythm: import, audit, moderate with logged reasons, export, file the pack with its date. When the dispute arrives (a competitor's complaint, a platform's review of your profile, a buyer's vetting), you send a document instead of starting an excavation.
The FTC fake-review rule, 16 CFR Part 465, has been in force since October 2024. It bans fake and AI-generated reviews, buying positive or negative sentiment, insider reviews without disclosure, review suppression, and misrepresenting review sites as independent. ReviewProof was built as the evidence layer for that rule: imported reviews carry a provenance chain — import, transaction link, analysis, moderation decisions — and the Pro evidence export includes the moderation log with negative reviews kept, which is how a business shows suppression did not happen. Proof, in this design, is a record anyone can inspect, not a badge a business awards itself.
What the reader is checking, section by section
Read your own pack as the sceptic will. Rows: are the reviews complete, negatives included, with sources and dates? Signals: does each flagged row name its trigger, so your decisions can be audited rather than merely believed? Provenance: can each review be followed from import through transaction link (or UNLINKED) through analysis to its moderation state, with nothing silently missing? Summary: do the totals reconcile — imported count, verified count, negatives kept? A pack that survives that reading is finished. A pack that needs a covering letter full of explanations is telling you where the underlying record still has holes.
ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.
Mistakes that undo the work
Sending screenshots instead of the export is the commonest downgrade: screenshots show selected text, not the record. Editing the pack — removing an embarrassing chain before sending — converts a strong document into a liability the moment counts fail to reconcile. And exporting only when challenged teaches the wrong lesson: the pack's date relative to the challenge is half its value, so the routine export is the strategy, not a backup chore.
Enforcement and platform action both turn on records, not intentions. A business that can produce the underlying row, its source, its date, its transaction link or the honest absence of one, and every moderation decision taken about it, is in a different position from a business holding only a star average. That is why ReviewProof never silently deletes: imported reviews default to kept, moderation is limited to kept, published or flagged internally, and every decision is written into the chain of custody. The evidence pack (a Pro and Agency feature) assembles that chain so it can be handed over as one document.
Worked example: a dispute answered in one email
A fictional worked example, written to show the numbers and the decisions in practice.
A training provider was reported to a platform by a competitor alleging bought reviews, after a genuine radio appearance tripled its bookings and its review rate. Because the provider exported a pack after every monthly import, it replied the same day with the pre-dated record: 503 imported reviews, a burst in the radio month whose rows were overwhelmingly transaction-linked with varied wording (the report showed the burst flag, and the rows behind it answered it), a gating and incentive count of zero, and 22 negative reviews kept. The platform closed the complaint without removing a single review. The pack did not argue; it demonstrated — and it existed because of a habit, not a crisis.
Your five-action checklist
- Export the evidence pack after every audit cycle, not on demand
- Read it as a sceptic: rows complete, signals traced, chains unbroken
- Confirm the summary reconciles — totals, verified count, negatives kept
- File each dated pack where a dispute responder can reach it in minutes
- Never edit a pack; correct the underlying record and export again
Frequently asked questions
What does the ReviewProof evidence export include?
Full provenance chains per review, the moderation log including negative reviews kept, and the risk report — the complete proof pack, on Pro and Agency plans.
Is the evidence export available on Free?
Free includes the full risk report, certificates and the widget for one location. The exportable proof pack unlocks with Pro ($29/month) or Agency ($79/month).
Are transaction references exposed in the pack?
Published provenance holds references as a SHA-256 hash and a masked form only; the raw reference is never stored, so the pack does not leak customer transaction data.
What disputes does a pack actually settle?
Platform complaints, partner or client due diligence, franchise and sale vetting, and regulator questions — anywhere the other side needs records rather than reassurance.
Keep reading
Related guides from the ReviewProof library:
- What does the FTC fake-review rule actually ban?
- Why does keeping negative reviews protect your business?
- What is a chain of custody for a customer review?
- What is a review provenance certificate?
- What does transaction-backed review provenance mean?
- How do you audit your own reviews, step by step?
- How should you moderate reviews without suppressing them?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.