Reputation management operations: from source record to publication

A defensible reputation service is a controlled case operation, not a stream of hurried public replies. It preserves the original item, separates a review from a complaint or advertising asset, checks what the organisation can prove, obtains the right approval and records the final action. The service pauses when evidence, authority or legal review is missing.

This reputation management operations guide applies to organisations handling consumer reviews about activity in England. Some cited regulator material applies across the UK. It cannot settle the facts of an individual review, the legal status of a statement or the duties of a particular organisation. Those decisions need named, qualified reviewers before publication.

This reputation management operations guide also covers the software layer that carries the case: the review platforms and listening tools that surface an item, the case system that holds the evidence and approvals, and the publishing route that releases an approved reply.

What to take away

Define the service boundary before opening cases

Write a short service charter. Its unit of work should be an identifiable review or related public item, tied to a source and handled through to a recorded disposition. The charter should name eligible sources, intake methods, working hours, decision owners, evidence stores and exit conditions. It should also state what the service does not cover.

Keep media relations, search optimisation, crisis communications, review-platform publishing and paid testimonial production outside the boundary unless they have their own controls. A comment with a service complaint may need a private resolution route, but that does not make the public review a complaint.

The CMA's online reviews guidance, which sits under the Consumer Protection from Unfair Trading Regulations 2008 and is being updated by the consumer provisions of the Digital Markets, Competition and Consumers Act 2024, tells publishers to explain that distinction and not suppress a negative review by diverting it to dispute resolution. That guidance is written for the platform. A business responding on somebody else's platform must still work to that platform's own review policy.

For each in-scope channel — Trustpilot, Google Business Profile, Reviews.io, a sector directory or the organisation's own review page — record whether the organisation owns the publishing surface, can only submit a reply, or must ask another operator to act. This prevents staff from promising edits or removals they cannot make.

Build intake around a preserved source record

The first operator creates a case ID and captures the public location — the Trustpilot review, the Google Business Profile listing, the retailer's own page or the social post — with the visible text, rating if present, apparent publication time, capture time, relevant product or service and any later edit. Store the original separately from notes, as a timestamped capture held in the case system rather than in a working inbox. Do not infer the reviewer's identity, customer status or motive from a display name.

Intake then answers four routing questions:

An uncertain answer becomes an explicit UNRESOLVED field. It must not be converted into a confident label simply to keep the queue moving.

Separate assertion, evidence and decision

Create an evidence packet that keeps three things apart: what the reviewer said, what authorised records show and what the organisation decides to publish. This distinction matters when a review mixes opinion with checkable facts.

The case investigator should list each material assertion without rewriting its meaning. Against it, record evidence owner, source, date, access authority and relevant excerpt. Record limitations and whether the record corroborates, contradicts or cannot answer the point.

The ICO's guidance on the accuracy principle, Principle (d), of the UK GDPR, read with the Data Protection Act 2018, covers the source and status of personal data and the need to consider accuracy challenges. It does not decide whether a review is true or authorise disclosure in a reply.

Evidence can be incomplete or genuinely contested. In that situation, the operationally sound result may be a narrow acknowledgement, a move to an authorised private channel or no public response. The file should show why that option was chosen.

Apply review-integrity controls before response tactics

No operator should create, commission or arrange a purported customer review, nor should a positive sentiment request be disguised as neutral collection.

The CMA's guidance for businesses and agencies on online reviews, which applies the Consumer Protection from Unfair Trading Regulations 2008, says businesses must not pose as customers, commission fake reviews or offer inducements for positive reviews. It also tells agencies to train staff and keep contracts and policies lawful.

If the organisation itself publishes reviews or information derived from them, the control set is wider. The CMA's detailed guidance on fake and incentivised reviews covers fake and concealed incentivised reviews, misleading publication and the steps expected of traders that publish consumer review information, and the fake-review prohibition in the Digital Markets, Competition and Consumers Act 2024 adds a further layer. A qualified consumer-law reviewer must apply that material to the actual operating model.

The service should therefore record collection method, incentive status, selection rule, moderation action and any business relationship affecting presentation. A response team cannot repair a compromised collection process with careful wording.

Draft from an approved claim sheet

The response editor works from the evidence packet, not directly from a monitoring alert. The draft should identify the point it can safely answer, avoid unnecessary personal details, and give a practical route for information not for public discussion.

Promises need an owner and an achievable next action. Do not announce that an investigation proved something unless the file contains the relevant evidence and approval.

When a customer quotation is moved into advertising, open a different job. The CAP Code — the UK Code of Non-broadcast Advertising and Direct & Promotional Marketing enforced by the Advertising Standards Authority — requires marketers to hold documentary evidence that a testimonial is genuine, not to pose as consumers and not to omit material commercial interests. It also addresses permission and relevance. A public review's existence alone does not make every reuse accurate or authorised.

Run a line-by-line clearance with fields for claim, evidence ID, disclosure need, personal-data risk, employment or IP issue, reviewer, decision and date. Keep that record as a single claim-clearance register keyed to the case ID, so a later correction can be traced back to the wording that was approved. Legal review is non-compensating: a polished tone cannot cure a claim that lacks support.

Publish through controlled access

Only a designated publisher should use an organisation's review account. The case record must identify the approved copy, destination, account, approver and publication result. Another person should compare the live reply with the approved version, then capture the URL and time.

Tooling does not remove buyer responsibility. The NCSC's supplier assurance questions cover security ownership, privileged access, incident recovery, data protection, independent assurance and contract terms. Use those questions to request evidence from a monitoring or publishing supplier. They are not a product certificate.

Access should follow job need, with separate human and automated identities where the system supports them. Record failed posts, unauthorised changes and lost access as incidents rather than silently recreating work.

Choose the software that carries the case

Most of this work runs on software, and it helps to separate four layers: the review platforms that hold the public item, the listening or monitoring tools that surface it, the case system that holds the evidence and approvals, and the publishing route that releases the reply under a named account.

The platform layer is the organisation's own review page plus Trustpilot, Google Business Profile, Reviews.io or a sector directory. Each offers a business dashboard for replies, review invitations, flagging and reporting, and each exports or connects differently, so build the case schema from what the platform's export or API actually returns.

Listening and monitoring tools such as Brand24, Mention, Sprout Social, Hootsuite and Google Alerts feed intake with alerts and saved searches. Review-management products such as Yext, Podium and Birdeye work from the same platform connections and add review invitations, response drafting and reporting. Case management usually sits in a service desk or CRM — Zendesk, Freshdesk, HubSpot or Salesforce Service Cloud — configured with the fields above rather than used as a shared inbox.

Test these features before buying: a timestamped capture or export of the original item; separate assertion, evidence and decision fields; role-based permissions with a named approver; an audit trail for edits and corrections; retention and deletion rules that match the organisation's data protection policy; a working API or feed for each platform in the source register; reporting that shows the unresolved queue and not just averages; and an export that lets the organisation take its evidence out.

Integrations decide most of the running cost. Ask whether the tool can read and reply on each platform in scope, whether it can write a disposition back to the case system, and who owns the connector when it breaks. Subscription models vary by platform connections, locations, seats and volume, so request a written quote against the approved source register rather than working from a list price, and apply the NCSC supplier assurance questions above to the same purchase.

No product repairs a weak charter. An automated review invitation still breaches the review-integrity controls if nobody sets the selection rule, and a listening tool cannot tell a service complaint from a review.

Fork complaints, corrections and removals

A request for a refund, remedy or private investigation belongs in the complaint process. Link the records, but retain distinct owners and outcomes. The public-case operator should know whether they may acknowledge the complaint, whether a private reference can be mentioned and who decides any later update.

A correction request needs the challenged statement, evidence received, decision-maker and effect on every location where the organisation controls the text. If the organisation republishes a testimonial or rating, correction may require more than changing the response beneath the original review. Preserve the earlier version and reason for change.

Removal requests should state the exact platform rule or legal ground invoked and the evidence supplied. On Trustpilot that means citing its Content Guidelines behind the flagged review; on Google Business Profile it means citing the prohibited and restricted content policy or submitting a legal removal request; on the organisation's own site it means applying its published moderation policy. Never call a review false merely because it is hostile.

Where the organisation runs the review site, the CMA says genuine negative reviews should not be edited, withheld, removed or delayed just because they are negative. Qualified counsel must handle legal conclusions and contested allegations.

Specify service performance without invented promises

An operating standard needs definitions before targets. Useful fields include eligible intake, acknowledgement, evidence-complete case, approval-ready draft, authorised publication, reopened case, correction and incident. For each, write the clock start, pause events, stop event, exclusions, source system, timezone and owner.

Leave every target blank until the organisation measures its present workload and authorises a service commitment. Report the distribution and unresolved queue, not only an average. Quality indicators should include unsupported-claim defects, wrong-account events, missed disclosures, unlinked corrections, inaccessible tasks and cases published without the required approval.

The GOV.UK Service Standard is written for public services. Its themes include understanding users, joining up channels, security, privacy, accessibility, performance data and reliable operation. A private reputation team may use those themes as design questions, but should not claim government assessment or compliance.

Prepare failure and recovery routes

Write runbooks for a source outage, compromised account, accidental disclosure, hostile volume spike, disputed evidence, supplier failure and mistaken publication. Each runbook needs detection, containment authority, preserved evidence, communications ownership, recovery steps and a criterion for resuming ordinary work.

Do not test recovery in a live customer case without authority. Use approved fictional fixtures or properly governed test data, isolate the environment and record what was and was not exercised. Supplier documentation may describe a feature; only the buyer's authorised evidence can show whether its own configuration worked.

Make the release decision visible

A case may close as PUBLISHED, ACKNOWLEDGED PRIVATELY, NO RESPONSE, REFERRED, CORRECTED, REMOVAL REQUESTED or UNRESOLVED. Define those terms locally and keep the evidence trail. A closure label is not proof that the customer's underlying issue was solved.

Before this service launches, appoint the operational owner and named specialist reviewers. Approve the source register, access list, case schema, integrity policy, complaint hand-off, claim-clearance record, publication route, correction log, incident runbooks and measurement dictionary. Test the bounded journey with authorised material, including a negative review, ambiguous identity, missing record, rejected draft, publication failure and correction.

Before this service launches, appoint a named author and fact-checker, re-check every destination, and complete qualified UK consumer, advertising, privacy, data protection, employment, IP, accessibility, security, commercial and legal review. Publication should wait until those sign-offs and the bounded test above are recorded.

Before you act

Common questions

What should the service charter define?

The charter should name eligible sources, intake methods, working hours, decision owners, evidence stores and exit conditions. Its unit of work is an identifiable review or related public item, tied to a source and handled through to a recorded disposition. It should also state what the service does not cover.

How should an uncertain routing answer be handled?

An uncertain answer becomes an explicit UNRESOLVED field. It must not be converted into a confident label simply to keep the queue moving. Intake asks whether the item is a review, complaint, threat, employment matter or media enquiry, and whether restricted handling is needed.

What must a removal request state?

A removal request should state the exact platform rule or legal ground being invoked and the evidence supplied. Never describe a review as false merely because it is hostile. Where the organisation runs the review site, genuine negative reviews should not be edited, withheld, removed or delayed just because they are negative.