A tenant says a meeting room feels stuffy by midafternoon. The facilities log shows no temperature fault, and commissioning records show the ventilation met its specified airflow. Neither record settles the complaint. Occupancy may have changed, the controls may be hard to use, or the room may now be booked beyond its intended capacity. The first step is to record what people experienced without assuming why it happened, then investigate both the experience and its possible causes.
For building owners and project teams, “customer feedback” can come from clients, residents, visitors, maintenance staff, tenants or users of a public facility. Their needs may conflict. A visitor might want longer opening hours when the operator has limited staffing. A resident might prefer a quieter entrance that an emergency plan requires to remain available. Feedback is evidence to assess, not an automatic instruction to change the building or service.
Define whose experience the decision concerns
Identify the users and decisions in scope. Prospective buyers can comment on apartment layouts; residents can report how those homes perform once occupied. In a clinic, patients may notice problems with wayfinding or privacy, while clinicians, cleaners and maintenance staff encounter different difficulties in the same rooms. Hearing only from the paying client can leave operational needs out of a design review. A public survey, meanwhile, cannot settle a technical question on its own.
Record what each group is well placed to observe. Users can describe discomfort, confusion and barriers. Facilities teams can report how often equipment fails and how easily it can be repaired. Designers and specialist consultants can check proposed remedies against regulations and system capacity. The owner weighs the costs and trade-offs, subject to applicable requirements.
Keep feedback about the product—the building, space or installed system—separate from feedback about the service, such as design communication, handover, maintenance response or booking procedures. “The room is unusable” could point to inadequate ventilation, an unclear occupancy limit or a slow response to faults. Each possibility has a different owner and measure of success.
Collect feedback at the point where it can change something
Before design decisions harden
Early interviews and workshops can show how a service actually operates. Ask people to describe a task, how often they do it, the equipment involved and where it breaks down. “What happens when deliveries arrive during school drop-off?” gives a design team more to work with than “Would you like a larger entrance?” Site observation may reveal workarounds people no longer think to mention, such as using furniture to hold a door open. Give appropriate notice and protect privacy when observing occupants.
For a refurbishment, compare user accounts with maintenance tickets, utility data, room-booking patterns and measured conditions where available. If someone reports glare, check when and where it occurs and what they are trying to do before deciding to darken every window. Record the proposed response while changes to the layout or specification are still feasible.
During construction and handover
Site visits, mock-ups and sample rooms let users assess details they can readily judge: door hardware, counter height, lighting controls and equipment clearances. Set a deadline for comments and explain what can still change. The same request may have very different cost and programme implications after procurement than it did at concept stage. Put accepted changes through formal change control so drawings, budgets and approvals stay aligned.
Handover feedback should go beyond the appearance of the finished space. Have operators try routine tasks, including isolating equipment, reaching filters, adjusting settings and finding the right manual. If a task cannot be done safely, the remedy might be better documentation, training or a physical change. Keep commissioning results and outstanding defects separate from preferences: failure to meet an agreed performance test is not a matter of opinion.
After occupation
A post-occupancy review compares design intentions with actual use. Surveys reach more people, interviews help explain their answers, and walkthroughs pinpoint where problems occur. Add measured data when the question calls for it, without treating sensor readings as a full account of comfort or usability. An early check may catch obvious defects; a later one can reveal problems that emerge with different seasons, staffing or occupancy.
Use a reporting channel people already know, but do not let the loudest complaints stand in for everyone’s experience. Short, specific questions tend to produce more useful replies than “Any thoughts?” Ask visitors which entrance they used, whether signs helped them reach their destination and where they turned unexpectedly. Our discussion of hospital design for patients and staff explains why both groups need to be heard when assessing the same facility.
Turn comments into a testable issue log
Keep the original comments, but give each issue a consistent record for decisions. Capture the location, user group, date, activity, reported effect, frequency and any supporting observations. Classify it as a possible defect, recurring usability problem, new operational need or preference. Retain the person’s wording: “I could not find the lift” should not quietly become “signage is inadequate” before anyone has checked the route.
Group duplicate reports without erasing important differences. Three people struggling at the same junction may point to a repeatable problem. One wheelchair user unable to reach a control also warrants attention; a barrier does not become acceptable because few people report it. Escalate feedback involving safety, accessibility, infection control or possible non-compliance through the relevant professional and operational procedures rather than waiting for a survey trend.
A practical issue record might contain:
- Evidence: the original comment, site observation, relevant drawing, measurement or service record.
- Scope: affected location, times, users and tasks.
- Working hypothesis: a possible cause, clearly marked as unconfirmed.
- Constraints: safety, approvals, budget, lease terms and operational disruption.
- Owner and next action: who will investigate, decide, implement and verify.
Collect only the personal details needed to resolve an issue. Limit access to identifiable responses, and do not publish comments that reveal someone’s health or circumstances. In sensitive settings, provide a private reporting route. Tell participants whether their feedback will inform an immediate repair, a later design review or both, so they know what to expect.
Prioritise by consequence, not popularity alone
Complaint counts can reveal patterns, but they do not provide a complete ranking. A popular request for a different finish may matter less than a single report of a door someone cannot open independently. Triage possible legal and safety issues first. Then consider the severity and frequency of the effect, how many people are exposed, the strength of the evidence, and the cost and disruption of a remedy. Reversibility matters too: trying a new sign is simpler than moving a lift.
Suppose an office receives many comments about a cold lobby and one report that its accessible entrance door is difficult to operate. Inspect the door promptly despite the low report count. Investigate the lobby as well, first establishing when and where people feel cold. Changing a thermostat could make adjacent rooms uncomfortable if deliveries are keeping an automatic door open.
Do not let a numerical score conceal judgment. A short decision note can explain why an issue was escalated, deferred or rejected, what evidence is missing and when the decision will be revisited. This is especially useful when groups want incompatible changes. A quieter café layout, for example, could reduce seating capacity; the owner needs to see both effects.
Test a remedy before making it permanent
Describe the expected result in terms that can be observed. “Improve wayfinding” is too broad; “reduce wrong turns by first-time visitors at the east corridor junction” can be tested. Walk the route with willing participants who do not know the building, note where they hesitate, and trial revised signs or entrance information. Include people with different access needs so the test does not reflect only the most typical visitor.
Small, reversible trials help when the cause or remedy is uncertain. A temporary furniture arrangement can test circulation before a fixed fit-out. Revised booking guidance can show whether an overcrowded room needs a physical change. Temporary measures must still meet applicable safety and accessibility requirements: a trial is no excuse to block an exit or create a trip hazard.
For building systems, agree on a diagnostic plan with competent specialists. If occupants report stuffiness, examine occupancy, operating schedules, controls and relevant air-quality or ventilation information before specifying new equipment. Compare conditions before and after an adjustment under reasonably similar use. If one group benefits but another experiences noise or draughts, record the trade-off rather than declaring success.
Market research offers context, not a substitute for evidence from the property. Zillow Research housing studies, for example, can help owners explore broader housing preferences. Decisions about a particular property’s layout or service still need its maintenance records and residents’ experience.
Close the loop with users and delivery teams
People are more likely to report useful problems when they hear what happened to earlier reports. A reply does not have to promise a change. It should say whether the issue was confirmed, what happens next, who owns the action and when an update is expected. If a request conflicts with a safety requirement or costs too much relative to its benefit, explain the constraint. “Not now” is different from “not feasible.”
Within the project team, connect feedback to the documents that govern delivery. A design change may call for updated drawings, a cost estimate, consultant review, permit assessment, revised operating instructions or agreement from an affected tenant. A service change may need staff training and a new response target instead of construction work. Give each action an owner; otherwise, the same issue can sit in meeting minutes and recur.
Check the result against the original problem. Depending on the issue, that might mean tracking repeat faults, the time needed for a maintenance task, visitor wrong turns, room-use patterns or structured responses about comfort. Compare like with like where possible, and note other changes that could explain the result. Fewer complaints after a tenant leaves do not prove a repair worked.
Use lessons from one project carefully on the next
Keep a lessons register linking each reported issue to its cause, intervention and verified outcome. Some details can become standard practice; others depend on a particular operator or site. If maintenance staff on several projects cannot reach ceiling equipment without moving furniture, the practice may need to revise its access review checklist. One client’s preferred reception layout is not, by itself, a universal standard.
Revisit unresolved items at defined milestones. Before approving the next fit-out package, check whether earlier comments about control labels led to a tested change, an updated specification or a documented decision to keep the existing approach. The record should let the team trace a person’s experience to a drawing, an operating procedure or an explicit decision.