Post-occupancy evaluation: turning feedback into action
Admin · 22 October 2026
Illustrative image. Photo by Toa Heftiba on Unsplash. Unsplash License.
A post-occupancy evaluation can generate useful observations without improving the building or the next project. The missing link is often a decision process: someone must interpret findings, identify appropriate advice and obtain agreement on a response. The evaluation should therefore be designed around questions the organisation intends to act on, with clear ownership and a realistic route from evidence to change.
For asset owners and project managers, the objective is to understand the building in actual use. That can involve user experience, operating information and technical assessment, depending on the scope. The relevant specialists should define suitable methods and interpretation. A collection of comments is valuable evidence, but it does not automatically establish the cause of a problem or the correct intervention.
Define the evaluation questions
Begin with the brief and the outcomes the organisation expected. Identify which questions matter after occupation and why. These might concern how a space supports an activity, whether handover information is usable or how actual operation relates to a stated target. A focused scope gives the evaluation a clearer purpose than a general instruction to ask whether people like the building.
Distinguish immediate operational feedback from questions needing a longer period or particular conditions. Ask the relevant advisers to establish suitable timing. The plan should reflect the actual activity and technical requirements rather than adopting a standard date without explanation. Record the limitations of what can be concluded at each stage.
Assign responsibility before collecting information
Identify who owns the evaluation and who can approve follow-up work. The collector, analyst and decision maker may be different people. Make the relationship clear, including how a technical question reaches a competent specialist. Otherwise a report can be delivered successfully while nobody is responsible for deciding what happens next.
Agree the route for issues that need prompt attention through the organisation’s normal procedures. The evaluation should not delay an appropriate response by holding all observations until a final report. Participants need to know the distinction between contributing feedback and using an established urgent reporting route.
Collect evidence suited to the question
Use methods appropriate to the scope and participants, with relevant professional advice. User feedback, observations and operating records can answer different questions. Explain their role and limitations. A response from one group may reveal a useful issue without representing every user’s experience or establishing a general conclusion about the asset.
The RIBA Plan for Use guide provides professional context for connecting project delivery, use and feedback. The organisation should adapt the evaluation to its actual requirements and responsibilities. A generic process is a starting point, not evidence that every relevant performance question has been assessed.
Preserve operational context
Record the conditions relevant to the observation. Occupation, equipment, schedules and management arrangements may differ from those assumed during design. Ask the operator to explain consequential changes and keep that information linked to the evaluation. Without context, the project may compare unlike conditions and attribute a difference to the wrong cause.
Consider a hypothetical workplace where a meeting area is reported as insufficient. The evaluation should examine the actual activities and demand pattern alongside the original brief. The issue may concern changed use, booking arrangements or the physical provision, among other possibilities. The team needs evidence before deciding whether the response is operational, design-related or another type of action.
Separate findings from diagnosis
State what the evidence shows and what remains an interpretation. A repeated observation deserves attention, but its cause may still require specialist investigation. Avoid selecting a remedy solely because it is familiar or easy to purchase. The responsible person should define the next question and obtain suitable advice.
Use a clear issue record with the affected activity or location, evidence, owner and required response. Distinguish a defect process, an operational adjustment and a new requirement through the project’s actual arrangements and appropriate advice. The label should follow assessment rather than being chosen to move the issue away from one team or another.
Prioritise by consequence
Agree how the organisation will identify matters requiring earlier action. The relevant competent people should assess technical or safety-related questions through established processes. Other findings may be ranked by operational effect and practicality. The evaluation team should not treat the largest number of comments as the only measure of significance.
Explain the basis of priority to decision makers. A relatively infrequent issue can have a consequential effect, while a common preference may be less important to the agreed objectives. Preserve the evidence and the reasoning. This helps the organisation allocate effort transparently and avoids a response driven only by the most forceful voice in the discussion.
Turn recommendations into decisions
A recommendation should identify the purpose of the proposed response, the evidence supporting it and the further assessment required. Name the person with authority to decide. If the response changes the asset or operating model, obtain the relevant technical, operational and commercial review through the organisation’s procedures.
Record accepted, rejected and deferred recommendations with reasons. A useful evaluation does not require every suggestion to be implemented. It requires an accountable explanation of how the evidence was considered. Where a matter is deferred, identify the trigger or date for reconsideration rather than leave it indefinitely open without ownership.
Verify the response
Define how the organisation will assess whether the action addressed the original question. The relevant specialists should establish suitable evidence and timing. Completion of work is not automatically proof that the intended improvement occurred. The follow-up should return to the activity or condition that prompted the recommendation.
Keep the comparison basis clear. If operation changes again, explain how that affects interpretation. A favourable movement should not be attributed entirely to one intervention without supporting evidence. Equally, an unchanged result may need further investigation rather than an immediate conclusion that the response was ineffective in every respect.
Feed learning into briefs and standards
Translate consequential lessons into the organisation’s relevant requirements, guidance or procurement practices. A long report stored in a project folder is unlikely to influence a new team unless the useful conclusion is accessible and tied to a decision they face. Retain the context and limitations so the lesson is not applied indiscriminately.
Record successful arrangements as well as difficulties. Understanding why something worked can improve future choices, but the organisation should distinguish a repeatable approach from circumstances unique to one asset. Keep claims proportionate to the evidence and identify when another project needs its own assessment.
Close the feedback loop with users
Explain how findings were considered and what action follows, using a form appropriate to the participants and the organisation’s information requirements. People are more likely to contribute useful feedback when the process has a visible purpose. Avoid implying that every suggestion has been approved if the organisation is still assessing it.
Review the evaluation process itself. Ask which evidence was useful, where ownership was unclear and whether the timing supported action. Improve the next review using those findings. Post-occupancy evaluation earns its value when it creates a dependable route from lived experience and operating evidence to informed decisions, with the results preserved for both the current asset and future projects.
Keep the scope of participation visible in the report. Identify which groups and activities contributed evidence and where coverage was limited, without exposing unnecessary personal information. This helps readers distinguish a useful observation from a conclusion about the whole building. If an underrepresented activity could change the decision, assign the additional engagement or assessment rather than assuming the available responses provide a complete picture.
