What is a chain of custody for a customer review?
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
A chain of custody for a review is the chronological log of everything that happened to it inside your system: when it was imported and from what source, whether a transaction link was attached, what signals the analysis found, and every moderation decision, in order. In ReviewProof each event is written to the review's provenance chain as it happens, the public certificate summarises the chain, and the full chain detail (a Pro feature) lets an examiner follow one review from arrival to publication without a gap.
What is a chain of custody for reviews?
Chain of custody, borrowed from evidence handling, means an unbroken, timestamped record of an item's passage through every hand and decision. Applied to a review, the item is the review row and the hands are import, transaction-linking, analysis and moderation. The chain's value is negative as much as positive: it proves not only what was done, but that nothing else was done — no silent edit, no quiet deletion, no unlogged hand.
The four events every review should carry
Import: the review enters with its source recorded — the chain starts with where the row came from, not with a claim about it. Transaction link: either a reference is attached (attested or imported, and for published provenance, held as hash and masked form) or the absence is logged — 'no verified-transaction link' is itself a chain event, which is why UNLINKED is a recorded state rather than a shrug. Analysis: the signals computed on the row are written in, so any later reader sees what the system saw. Moderation: the default event is 'kept (no suppression)', and any later decision replaces nothing — it appends. Append-only is the whole game: a chain that can be rewritten is a story, not a record.
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.
Where chains break in ordinary businesses
They break at the hand-offs humans do not log: the spreadsheet where reviews were 'tidied' before import, the platform backend where an assistant unpublished a review last spring, the agency inbox where a complaint was settled by quietly removing a post. ReviewProof cannot log what happens outside it — which is the operational argument for running the whole review workflow inside one system: import there, moderate there, publish the widget from there. The narrower the set of places a review can be touched, the more the chain can honestly claim to be complete, and the more weight the certificate carries when it is examined.
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
Reconstructing a chain after the fact is the fatal habit — reconstructed logs are detectable by their tidiness and their timing, and they convert a documentation gap into a credibility collapse. Letting reviews be moderated in two systems (platform backend and ReviewProof) splits the chain so neither half can claim completeness. And treating the chain as bureaucracy for big companies misses its scale economics: the chain writes itself as events happen, so the small business gets the same rigour for free.
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: one review, followed end to end
A fictional worked example, written to show the numbers and the decisions in practice.
During a franchise vetting, an examiner picked a single one-star review from a coffee shop's file — deliberately the hardest case — and asked to see its life. The chain showed: imported on 4 March from the location's platform export; transaction link attached, booking reference masked; analysed with no signals; moderation event 'kept (default — no suppression)'; a later event recording the owner's public reply; still kept, still published, still one star. The examiner's report used the shop's own phrase back to it: the worst review in the file was also the best-documented. Total elapsed time to produce the chain: minutes, from the Pro chain detail, because it had been written as events happened.
Your five-action checklist
- Run import, linking, analysis and moderation inside one system
- Confirm each imported review shows its import and transaction-link events
- Check the default moderation event reads 'kept (no suppression)'
- Append decisions with reasons; never edit or backfill chain events
- Spot-check one negative review's full chain every audit cycle
Frequently asked questions
What events does ReviewProof log for a review?
Import with its source, the transaction link or its recorded absence, the analysis with its signals, and moderation — starting from 'kept (default — no suppression)' and appending every later decision.
Who can see the full chain?
The certificate summarises provenance publicly. Full provenance chain detail is a Pro and Agency feature, used for disputes, vetting and evidence exports.
Can a chain entry be corrected?
Corrections append; they do not rewrite. That append-only property is what makes the chain evidence rather than narrative.
Why does the default 'kept' event matter?
Because it proves the starting state was non-suppression and makes any later change visible as a change — the absence of a gap is the proof.
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 should an evidence pack for a review dispute contain?
- 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.