Prepare for this credential by training one specific judgment: matching each performance claim to evidence of the right scope, from the right time, for the right asset. BREEAM positions In-Use as the standard that enables sustainable performance benchmarking and operational asset improvement, so your study should center on distinguishing operational evidence from design-stage documents, distinguishing asset-level from portfolio-level data, and documenting the reasoning behind every judgment. Work through the scenarios below, run the evidence audit exercise, and finish with the readiness checks before attempting practice questions.
What BREEAM In-Use actually assesses, and how it differs from New Construction
BREEAM describes In-Use as enabling sustainable performance benchmarking and operational asset improvement strategies, which makes it fundamentally an existing-building, operations-focused standard rather than a design-stage one.
Compare the three main standards by what they certify. New Construction supports sustainable delivery of high-performing newly built development assets, so the assessment concerns a building being created. Refurbishment and Fit Out improves sustainability outcomes across refurbishment and interior fit out projects, concerning a building being changed. In-Use concerns a building that is simply operating, often long after any design or construction work ended.
This distinction drives how you should study. Design-stage assessment rewards understanding design intent: what specifications, models, and plans promise. In-Use assessment rewards understanding operational reality: what the asset consumes, how it is managed, and how it performs today. When you revise any topic, ask whether you are reasoning about a promise or a measurement. Practicing that classification repeatedly is more useful than re-reading generic sustainability content, because nearly every assessor judgment in an operational context depends on it.
Benchmarking, third-party assurance, and data validation: three named concepts to separate
Three concepts recur throughout In-Use work: benchmarking compares performance against reference points; third-party assurance means an independent assessor validates outcomes; data validation is the act of confirming that supplied information is accurate and appropriately scoped.
Keep them distinct in your head. Benchmarking is a comparative exercise; BREEAM describes benchmarking at asset, portfolio, and market level, and each level answers a different question. Third-party assurance is about credibility: the reason clients rely on BREEAM certification is that an independent professional stands behind the outcome rather than the client grading their own building. Data validation is your working method for delivering that assurance on a specific claim.
A practical study habit is to attach a test question to each concept. For benchmarking: compared to what, and at what scope? For assurance: who is independently confirming this, and on what evidence? For validation: could this document actually demonstrate the claim it is attached to, or does it merely suggest it? Running these three questions over sample claims forces you to reason like an assessor instead of a reader, and it exposes weak evidence quickly during practice.
Worked scenario 1: the design-stage energy model offered as operational evidence
When a client submits a building's original energy model to support an operational performance claim, the correct response is to question whether predicted design data can evidence actual operations, and to request metered consumption records instead.
The scenario: you are reviewing an office asset and the client provides a 2015 design-stage energy model alongside their rating submission, expecting it to demonstrate current energy performance. The plausible mistake is accepting it because it looks technical, authoritative, and quantified. The model is not fabricated; it simply belongs to a different stage of the building's life and describes what the design predicted, not what the building has done since.
The better decision is to classify the model as design-intent documentation, explain to the client that operational claims need operational evidence such as metered consumption records covering the relevant period, and document both the decision and the reason. Why it matters: conflating predicted with actual performance undermines the data validation that third-party certification exists to provide. In your revision, practice writing a two-sentence justification for this kind of call, because articulating the reasoning is itself an assessable skill.
Worked scenario 2: portfolio-average data used for a single-asset rating
When a client offers portfolio-level survey responses or averaged management data to support an individual asset's assessment, the correct response is to check the scope of each data item and identify what must be asset-specific.
The scenario: a property company pursuing certification across a portfolio supplies one set of building management questionnaire responses and asks you to apply them to a specific asset. The plausible mistake is complying, because the answers are broadly true of the whole estate and re-collecting data feels wasteful. The better decision is to distinguish scopes: portfolio-level information may legitimately support some portfolio-relevant matters, but claims specific to one building's operation need evidence about that building, such as site-records, local procedures, or asset-specific metering.
Document the scope of every evidence item you accept: whose data, covering which assets, over what period, and what claim it is being matched to. Why it matters: BREEAM frames benchmarking at asset, portfolio, and market level as distinct activities, and blending scopes makes the resulting rating uninterpretable. A portfolio figure averaged across buildings with different uses cannot describe one building's operation, and an assessor who cannot state an item's scope cannot defend the rating under review.
Documentation and professional standards: writing judgments you can defend
Assessor work is only as strong as its record. Every acceptance or rejection of evidence needs a documented rationale connecting the claim, the evidence item, its scope, and the reason it satisfies or fails the requirement.
Build a documentation habit during study, not after. For each practice claim you evaluate, record four things: the claim being made, the evidence supplied, the scope of that evidence (which building, which period, whose data), and your judgment with its justification. This mirrors the assurance role BREEAM describes: certification is trusted because independent professionals validate data reliably, and reliability depends on a traceable trail rather than a professional memory.
Ethics enters when documentation pressure and client pressure collide. If a client insists that weak evidence supports a claim, your professional duty runs to the integrity of the certification, not to the outcome the client prefers; the correct action is to record what was and was not demonstrated and escalate through appropriate channels where needed. Study this as decision-making, not slogans: rehearse the sentence you would write in the assessment record when a claim is not demonstrated, because having the sentence ready makes the honest call easier under deadline.
Choosing the right frame: a decision table for In-Use versus adjacent standards
A recurring practical problem is deciding which BREEAM frame applies to a client's situation. Use the table below, based on BREEAM's own descriptions of each standard, to classify a client's goal before discussing evidence.
Work through the table actively rather than reading it passively. Take three invented client briefs, such as a newly designed school, an office tower being re-let with new interiors, and a shopping centre the owner wants to benchmark and improve year on year, and place each in the correct row. Then, for the In-Use row specifically, list what evidence you would expect to exist for a building that has been operating for years.
The reason this drill matters is that misclassifying the frame poisons everything downstream: design documents get requested where operational records belong, or operational scrutiny is applied to a project that has not yet produced operations. Classification is fast, testable, and high-leverage, which makes it an efficient early focus of your revision. Once classification is automatic, you can spend remaining study time on evidence judgment rather than framework confusion.
| Client situation | Likely BREEAM frame | BREEAM's description of that frame | Evidence character |
|---|---|---|---|
| A new development is being designed and delivered | New Construction | Supports sustainable delivery of high-performing newly built development assets | Design intent, specifications, models, construction-stage records |
| An existing building is being refurbished or fitted out | Refurbishment and Fit Out | Improves sustainability outcomes across refurbishment and interior fit out projects | Refurbishment scope, project specifications, works records |
| An operating building is to be benchmarked and improved | In-Use | Enables sustainable performance benchmarking and operational asset improvement strategies | Operational data, management practices, current building records |
A practical exercise, a preparation sequence, and readiness checks
Run a two-week evidence audit on a building you know, sequence your preparation from framework classification through evidence judgment to documentation practice, and use the readiness checklist to decide when to attempt full practice papers.
The exercise: choose a building you can observe or work in, such as your workplace or home. Write ten performance claims about it, for example energy consumption, waste handling, water use, and maintenance practices. Sort every claim's supporting evidence into three categories: metered or measured operational data, management or policy documents, and design-stage or historical documents. Expected observations: measured data exists for only a few claims, many claims rest on documents describing intent rather than operations, and at least one claim has no evidence at all. Record which claims you would flag for follow-up and why.
Self-check rubric, scored 0 to 3 per item as a learning milestone only, not a passing prediction: 3 means you can state the claim, evidence, scope, and justification without hesitation; 2 means you need notes; 1 means you can classify but not justify; 0 means the distinction between operational and design evidence is still fuzzy. Then follow this sequence: week one, learn the framework differences using the table drill; week two, run the evidence audit and score yourself; week three, work through scenario-style practice questions, writing full justifications; week four, attempt timed practice sets and review every judgment against the rubric. For administrative details such as current registration or exam arrangements, consult BRE directly at breeam.com rather than relying on third-party summaries, since such details change.
- You can classify any client brief into the correct BREEAM frame in under a minute and justify it.
- You can state the scope, period, and source of every evidence item in a practice scenario.
- You can write a two-sentence defensible justification for rejecting design-stage data as operational evidence.
- You can distinguish asset-level from portfolio-level data and explain what each can legitimately support.
- Your evidence audit rubric scores at 2 or above across all items before you sit timed practice papers.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.