How should a plumber or trades business prove its reviews?
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
Link every review to a job number, and take the ask off the doorstep. A trades business proves reviews by sending one message when the invoice closes — to the emergency customer and the routine customer alike — with the job reference captured for linking, then importing monthly. The trade's signature risks are doorstep gating (only the relieved, grateful jobs get asked), small-volume distortion (thirty reviews is a whole profile, so every cluster shows), and review text quoting the engineer's own suggested phrasing from the job sheet.
What is trades review provenance?
Trades review provenance ties reviews to completed jobs — job number, invoice or call-out record — and removes solicitation from the point of maximum emotional leverage: a customer's doorstep, moments after water is flowing again or heating restored. The record needs only the job's existence and date; it never needs the job's details, and the published certificate shows a masked job reference, the source and the date, nothing about the property or the problem.
The doorstep is the highest-pressure ask in local business
Consider what a doorstep ask actually is: the engineer, tools in hand, in the customer's hallway, at the end of an emergency the customer was frightened by, saying some version of 'if you're happy, a review really helps us'. The customer's agreement is relief, not judgement — and the jobs nobody asks about are the messy ones, which is gating by circumstance rather than design. The invoice-triggered message abolishes the hallway entirely. It also produces the linking reference for free, because the invoice is the record both of the job and of the ask. Firms that make this one change routinely watch their negative share rise to a believable level and describe the change, accurately, as the month their profile started describing the business.
Volume matters differently per business, too. A location with forty reviews cannot absorb a burst the way a location with four thousand can: five same-day reviews are a rounding error in one file and an eighth of the entire profile in the other. ReviewProof detects a burst when at least five reviews land on one day and that day holds at least 40% of the import, which is why the report must always be read against your own baseline. The worked example on this page uses a small file on purpose: small profiles are where provenance work pays back fastest, because every single review is visible.
Small numbers make every signal loud
A plumber with 60 reviews has a different statistical life from a hotel with 6,000. Five same-day reviews is a burst in this file (and ReviewProof's burst rule — at least five on a day and 40% of the import — is calibrated to catch exactly the small-file pile-up, such as a bought top-up of twenty reviews that instantly becomes a third of your reputation). Five duplicate long texts is a campaign. This loudness is a gift: a monthly import of a small file takes minutes to read completely, row by row, and a trades firm can honestly know its entire provenance position in a way large businesses must sample their way toward. Use the smallness — read every row.
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
Leaving the ask to individual engineers' judgement guarantees eleven different solicitation policies, nine of them accidental violations. Writing example phrases on the job sheet ('mention our tidy work!') scripts duplicates from your happiest real customers. And buying a 'starter pack' of reviews for a new firm is buying the one burst your small file can never hide — in a 40-review profile, 15 bought reviews are not a boost, they are the profile.
The audit mechanics do not change by trade: import the reviews, read the signals traced to your own rows, and publish only what carries a transaction link. What changes is where the risk hides. Service businesses collect reviews at emotional moments — after a repair, a meal, a treatment — and staff under pressure reach for shortcuts: a discount offered at the till, a tablet handed over with the review page already open, a quiet word that unhappy customers should call first. Those shortcuts are precisely the gating and incentive patterns the analysis weights most heavily, and precisely what the FTC rule prohibits. Finding them in your own data first is the cheapest fix there is.
Worked example: a two-van firm reads all sixty-one rows
A fictional worked example, written to show the numbers and the decisions in practice.
A two-van plumbing firm imported its whole profile: 61 reviews. The owner read every row with the report open. Findings: a burst of 9 reviews on one Sunday (all after a genuinely catastrophic weekend of burst mains across the town — 8 of 9 job-linked, filed with the job sheets for that weekend); 4 UNLINKED five-star reviews with similar phrasing that nobody at the firm could connect to any job, traced eventually to a directory-listing salesman who had 'included reviews' in a package (flagged internally, package cancelled, dispute filed with the evidence pack); and zero gating or incentive lines since the invoice-message replaced doorstep asks the previous year. Sixty-one rows, one afternoon, total knowledge of position.
Your five-action checklist
- Trigger the ask from invoice closure, identically for every job
- Capture the job reference in the request record for linking
- Brief engineers: no review asks on the doorstep, ever
- Read the whole file monthly — a small profile permits total knowledge
- File job evidence beside any genuine emergency-weekend burst pack
Frequently asked questions
Our firm only has a few dozen reviews. Is an audit worth it?
More, not less: in a small file every cluster is a large share of your reputation, one bought package can dominate, and the full read takes minutes.
How do burst mains and emergencies affect the burst signal?
A genuine emergency weekend produces stay-linked — job-linked — varied reviews. File the job records with that month's pack and the flag is answered before it is asked.
Can engineers mention reviews if the customer brings them up?
They can thank the customer. They should not steer, suggest wording, or attach anything to it — the system message remains the only solicitation.
Which plan fits a small trades firm?
Free covers one location's complete audit, certificates and widget — sized well past a small firm's monthly volume. Pro adds the evidence export for disputes.
Keep reading
Related guides from the ReviewProof library:
- How should a restaurant prove its reviews are real?
- How should a dental clinic handle reviews and provenance?
- How should a hotel prove its reviews came from real stays?
- How should a salon keep its reviews honest and provable?
- How should a law firm handle client reviews and proof?
- How should an auto repair shop prove its reviews?
- How should a gym keep member reviews honest?
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.