“The handover was late” is a claim worth checking before answering. It could point to a service failure, a disagreement about the agreed date or work managed by another contractor. Start with the handover record, then establish who can verify the facts and what can safely be said in public.
For architecture practices, developers and property operators, reviews may concern design communication, approvals, construction coordination, leasing or day-to-day management. Those are different responsibilities. A complaint about a maintenance visit should reach the facilities team, not be treated as a marketing task.
Assign ownership before reviews arrive
Keep a short register of the profiles your organization controls: business listings, property profiles and project pages that accept public ratings. Record each profile URL internally, along with its login owner, backup administrator and notification address. Include former premises or completed developments if people still comment on them. If a profile is inaccurate, use the platform’s correction process rather than creating a duplicate listing to separate negative feedback from positive reviews.
Appoint a coordinator to check alerts and maintain a review log, with a named backup for absences. The coordinator does not need to answer everything: a project manager may need to check a design complaint, while a facilities manager investigates a maintenance report. Give the coordinator authority to route each item. Checking notifications on working days may suit a small practice; an operator of occupied buildings may need to monitor more often because safety reports can appear in reviews.
Use a small review log, not a second case-management system
A spreadsheet or existing service desk is often enough. Record when the review was found, the platform, property or project, broad issue category, assigned owner, response status and follow-up date. Add a link to the review where permitted, but keep supporting records in approved organizational storage. Avoid copying a reviewer’s personal details into multiple files.
A simple set of statuses makes it clear what still needs attention:
- New: the comment has been seen but not assessed.
- Checking: the relevant team is confirming the facts and any contractual boundaries.
- Responded: a public reply has been posted and, where appropriate, a private contact route offered.
- Follow-up due: an agreed action needs checking.
- Closed: the action is complete or no further action is possible, with the reason recorded.
Link the public response to the operational case. Do not let a review platform become the only record of a defect or dispute: a reported leak, access failure or unsafe condition also belongs in the established maintenance or incident process.
Set a triage rule that protects urgent cases
Ratings are a poor guide to urgency. A three-star comment about unclear meeting notes needs attention, but a five-star review mentioning a faulty fire door may require immediate escalation. Prioritize the substance of the claim and your team’s responsibility for it.
- Immediate escalation: possible safety hazards, active water ingress, inaccessible essential facilities, threats or allegations needing legal or regulatory review. Use the appropriate incident channel; do not wait for a polished public reply.
- Service investigation: missed appointments, unresolved defects, handover confusion or communication failures. Check dates, scope and responsible parties before promising a remedy.
- Routine response: general praise, suggestions and complaints that can be answered using verified information.
- Platform issue: apparent spam, impersonation or content that breaches platform rules. Record the reason and use the platform’s reporting process. An unfavorable opinion is not, by itself, grounds for removal.
Set internal response targets that match staffing and risk, rather than publishing a blanket guarantee. A coordinator might acknowledge new reviews within two working days, while escalating safety-related claims as soon as they are seen. If the facts are still being checked, a brief acknowledgment is better than an unconfirmed explanation.
Write replies for the reviewer and the next reader
A public reply should show that you understand the concern without exposing confidential information. Thank a positive reviewer, but do not add details about their project that they have not made public. For a complaint, name the general issue, say only what has been checked and offer a practical route for private follow-up. A comment thread is rarely the place to quote contract clauses.
For example: “We understand your concern about the timing of the handover. We are checking the agreed schedule and the items outstanding at that stage. Please contact our project team through the contact details on your handover documents so we can identify the project and respond directly.” This neither concedes an unverified breach nor asks the reviewer to post an address or contract number.
Do not argue over the reviewer’s recollection, disclose tenant details or promise a completion date before the responsible team confirms it. If the business made a mistake, describe the corrective action accurately. If the work falls outside your responsibility, explain that distinction without dismissing the experience. One clear response is usually enough; a prolonged public exchange rarely helps.
Close the loop without pressuring reviewers
Once an issue is resolved, record what happened, who approved the action and whether the public reply needs a factual update. Do not revise a response to suggest a repair is complete when it has only been scheduled. If the platform permits a follow-up, limit it to the confirmed outcome.
Take the same care when asking for reviews. Choose a consistent, appropriate milestone—such as delivery of a design stage or closure of a maintenance request—instead of approaching only satisfied clients. Participation should be optional. Do not reward favorable ratings or make removal of criticism a condition of fixing a problem. Check platform rules and privacy obligations before using contact details collected for another purpose.
Each month, the coordinator can count reviews received, items awaiting investigation and cases past their follow-up date. Categories such as handover information or response time may reveal recurring questions, although a small review sample cannot reliably measure overall client satisfaction. At the next review meeting, pick one unresolved item—say, a reported entrance-door fault—and confirm its work-order number, responsible manager and date for checking the completed repair.