Building performance gaps: planning evidence after handover
Admin · 22 October 2026
Illustrative image. Photo by Nastuh Abootalebi on Unsplash. Unsplash License.
When a building performs differently from expectations, the first challenge is to establish what is being compared. The original expectation may be a design prediction, a brief requirement or a general aspiration. The in-use result may reflect a different operating pattern or incomplete data. A useful investigation starts with those distinctions instead of immediately attributing the difference to one product, discipline or user behaviour.
For clients and project managers, evidence planning should begin before handover. The organisation needs to know which outcomes it will review, what information supports the review and who can act on the findings. The relevant specialists should define technical assessments and interpretation. The wider project process should preserve the information and responsibilities needed to make that work possible.
Keep the original expectation traceable
Identify the requirements and predictions that will be relevant in use. Record their scope, assumptions and revisions. A summary statement that the building should be efficient or comfortable is insufficient for a precise comparison. The client needs a known reference and an explanation of what evidence would indicate whether the intended outcome has been achieved.
Distinguish contractual obligations from other project objectives with appropriate professional advice. Their relationships depend on the actual agreements and requirements. An evidence plan should not casually convert a forecast into a guarantee or imply that a management review replaces a formal contractual process. Clear terminology makes the later discussion more useful and less vulnerable to misunderstanding.
Define the questions for the first year
Select the outcomes that matter to the operator and the information needed to understand them. These may involve energy, comfort, usability or another defined aspect of the brief. Keep the scope manageable and purposeful. A large monitoring dataset is not automatically valuable if nobody knows which decision it should support.
Ask the appropriate specialists to explain timing needs and limitations. Some questions may require evidence under different operating conditions, while others can be assessed earlier. The plan should reflect the asset’s actual use and technical requirements. Avoid adopting a standard calendar without considering whether it will produce the information the client needs.
Plan the data route
Identify sources, access, ownership and checks for the required information. The operator may need system records, user feedback or specialist observations. Establish how these will be obtained and connected. If the design does not support the intended measurement, identify the question while there is still time for the relevant team to assess options.
Record the context accompanying the data. Changes in occupation, equipment or operating schedules can affect interpretation. The review should not rely on an unexplained number detached from the conditions under which it was observed. Agree who maintains that context and how significant changes reach the people analysing the result.
Include the people using the building
Users can identify patterns and difficulties not apparent from system records alone. Organise feedback around defined activities and locations, using an approach suited to the review. Explain how the information will be handled through the organisation’s appropriate arrangements. Avoid implying that a small set of responses represents every user or establishes a technical cause by itself.
Consider a hypothetical office where occupants report discomfort in one area during particular periods. The report is useful evidence for investigation, but it does not identify the cause automatically. The relevant specialists may need to examine operation, controls, conditions and other factors. The process should connect the observation to that assessment rather than jump directly to an untested remedy.
Maintain a route to project knowledge
Agree how the operator can obtain clarification from the relevant project participants after occupation. The arrangement depends on the actual appointments and support terms, which need appropriate review. The practical objective is continuity of information and access to competent advice, not an assumption that every member of the construction team remains available indefinitely.
Provide the accepted design and handover records in a form the receiving organisation can use. Identify significant assumptions, changes and limitations. A future investigator should be able to understand the intended arrangement without reconstructing it from an incomplete set of emails or depending on someone’s memory of an earlier design review.
Separate observations from diagnosis
Record what was observed, when and under which conditions. Keep an interpretation or proposed cause distinguishable from that factual account. Several explanations may be plausible at first. The relevant specialist should determine the appropriate investigation and evidence rather than let an early assumption become accepted through repetition.
Use a structured issue record with the question, owner, required response and decision route. The owner coordinating the investigation does not automatically hold every technical responsibility. Identify contributors and the person authorised to approve any consequential change. This keeps the process accountable without blurring the project’s professional and contractual roles.
Compare on a consistent basis
Ask the specialists to explain whether the expectation and observed result use comparable boundaries and assumptions. Where they differ, identify the consequence before drawing a conclusion. CIBSE’s TM54 guidance provides relevant context for operational energy prediction; the project should obtain competent advice on the appropriate in-use evaluation rather than treat a raw comparison as a complete assessment.
A change in use may explain part of a difference without establishing that every aspect of the building is performing as intended. Equally, a difference does not prove a particular defect. The review should preserve those distinctions and identify the further evidence needed. Clear limitations are more useful than a confident conclusion unsupported by the comparison.
Turn findings into controlled action
Where an intervention is proposed, obtain the relevant technical and operational assessment. Identify its purpose, expected effect and any connected requirements. Use the organisation’s actual approval and contractual procedures. A performance review should not create an unofficial route for changing the building without the appropriate responsibilities and evidence.
Plan how the response will be checked after implementation. Record the basis and conditions of the comparison so the team can understand whether the action addressed the issue. Avoid closing a matter solely because work was carried out. The client needs to know what result was observed and whether any further question remains.
Feed the evidence into future projects
The RIBA Plan for Use guide provides professional context for connecting project delivery with building use and feedback. The organisation should retain lessons in a form that influences future briefs and decisions. A long report has limited value if the next project team cannot identify the evidence relevant to its own choices.
Record useful outcomes as well as shortfalls. Understanding why an arrangement worked can help distinguish a sound approach from a favourable circumstance that may not repeat elsewhere. Keep claims proportionate to the evidence and explain context when sharing conclusions beyond the original asset team.
Planning evidence after handover gives the client a more dependable route from expectation to understanding and action. It preserves the original basis, captures actual use and assigns responsibility for interpretation. That continuity helps the organisation respond to performance questions with appropriate expertise rather than assumption, and makes the experience useful for the next project.
Preserve access to the reasoning
Identify which project participants can explain consequential assumptions in the design and commissioning records. Agree the route for obtaining their input under the actual appointments. A final model can contain the result while leaving the operator uncertain about why a particular operating scenario was chosen. Planned access to the relevant explanation can make later investigation more focused.
Record useful clarifications in the controlled information rather than retaining them only in a meeting conversation. The objective is to improve the asset record as evidence develops. When people leave or responsibilities change, the next reviewer should still be able to distinguish the original expectation from a later interpretation or an accepted operational adjustment.
