The general character of assessment evidence, why timing matters more than volume, who in a project team normally holds each kind of record, and how credits are commonly lost.
BREEAM, a registered trade mark of BRE, relies on documented evidence rather than unsupported statements of intent. The scheme requires the assessor to connect each claimed outcome to records that show what was decided, designed, specified, installed, tested or managed at the relevant project stage. Evidence varies across the framework, but it commonly includes drawings, specifications, calculations, manufacturer declarations, commissioning records, meeting minutes and dated photographs.
The assessment process does not begin with the assumption that a credit has been achieved and then search for wording to support it. The project first needs to deliver the relevant outcome, and the evidence must allow the licensed assessor to establish that the applicable requirement has been met.
At design stage, evidence usually concerns proposed solutions, calculations, specifications and formal commitments. At post-construction stage, it shifts towards installed products, completed systems, test results, site records and final handover information.
The evidence must also be attributable. A document needs to relate clearly to the assessed asset, area, stage and decision. A generic brochure or undated image may describe a product or concept without proving that it formed part of the project.
Drawings establish location, geometry, layout, system relationships and the physical extent of the works. Depending on the subject, the assessor may need plans, sections, elevations, details, schematics or schedules that show where an assessed feature is proposed or has been installed.
Design drawings are most useful when they are coordinated and carry a clear revision status. An early concept may demonstrate intention but not the final arrangement. A construction issue can show what was instructed, while an as-built drawing can show the recorded completed condition. Those documents are not interchangeable merely because they contain a similar title.
Schedules can link drawings and specifications by identifying products and performance attributes across many locations. Their value depends on consistency with the final design and procurement records.
Specifications record the technical requirements placed on materials, products, systems and workmanship. They can show that the project required a particular performance outcome before procurement or installation.
A specification is strongest when it identifies the relevant property in clear technical terms and assigns responsibility for demonstrating it. Vague descriptions such as sustainable product or high-performance system may express an ambition but provide little evidence of a defined outcome.
Specifications are design-stage evidence, not automatic proof of final installation. A contractor may propose an alternative product, a supplier may change or a value-engineering exercise may revise the requirement. The post-construction assessment must therefore connect the specification with procurement and installation records where confirmation of delivery is needed.
Calculations translate design information into evidence of predicted performance. They may be produced by architects, engineers, cost consultants or specialist advisers, depending on the subject. Their value comes from a transparent method, appropriate inputs, identifiable assumptions and a clear relationship to the assessed design.
A calculation created for one design revision may become invalid when the facade, occupancy, plant, layout or material quantities change. It should not remain in the assessment file simply because it once supported a credit. The project needs to understand which changes trigger revision and who is responsible for updating the analysis.
Technical reports can also record surveys, option appraisals, strategies and specialist conclusions. Their timing matters. A report intended to influence a design decision should exist before that decision is fixed, not be written later to suggest that a process occurred.
Manufacturer declarations can provide evidence about the tested, declared or certified properties of a product. They may include formal data sheets, declarations, certificates or reports identifying the product and the relevant characteristic.
The document must match the product actually specified or installed. A declaration for one product family, formulation, size or manufacturing location may not necessarily apply to another. Marketing literature should not be treated as equivalent to a technical declaration where the assessment requires defined evidence.
Product information also needs version and date control. A later declaration may confirm a characteristic without proving what information was available when the product was selected.
Commissioning records show how installed systems were checked, adjusted and prepared for operation. They can include plans, checklists, test sheets, balancing information, certificates, issue logs and completion records.
These documents belong principally to the delivered asset. A design specification can require commissioning, but only the completed records show what was carried out. Missing results cannot be replaced by a general statement that the contractor normally follows good practice.
The records should identify the system, location, date, responsible party and outcome. Where defects or incomplete items were found, the file should also show how they were resolved. A signed document with no technical content may confirm attendance without proving the required activity.
Meeting minutes can demonstrate that sustainability matters were considered at a particular time, that responsibilities were assigned and that decisions were taken through the project process. They are especially useful where the assessment concerns consultation, option review, coordination or management action.
Minutes are only persuasive when they are contemporaneous and sufficiently specific. A statement added months later that the team discussed sustainability does not show what was considered, who participated or how the discussion affected the project.
Decision logs, action trackers and formal approvals can strengthen the record. They connect discussion with an outcome and show whether actions were completed. The assessor can then follow the sequence from issue identification to project response.
Photographs can show physical conditions, installation, retained features, construction activities and completed works. They are particularly valuable where an element later becomes concealed or inaccessible.
A useful photograph needs context. The location, date and subject should be identifiable, and the image should show the relevant feature clearly. A close-up with no indication of where it was taken may be technically interesting but difficult to connect to the assessed asset.
Photographs do not replace every other form of evidence. An image may show an installation without proving its specification or commissioning, so it works best within a connected evidence trail.
A core principle is that evidence should exist at the time the relevant decision or activity occurs. It should not be reconstructed afterwards to create the appearance of an earlier process.
This matters because some assessment outcomes concern not only the final product but the way the project reached it. An option appraisal completed after the preferred solution was procured cannot genuinely influence selection. Minutes written after construction cannot prove that a coordination meeting took place during design.
Retrospective information can sometimes clarify a genuine event, but it cannot safely replace contemporaneous evidence where timing is part of the outcome. The assessor must judge whether the record demonstrates the real project process rather than a later narrative.
Design-stage evidence asks what the project proposes, what analysis has informed the proposal and what formal commitments have been made. Drawings, specifications, calculations, strategies, appointment records and minutes are therefore prominent.
At this stage, some evidence is necessarily predictive. The building has not yet been completed, so the assessment relies on controlled design information and commitments that can later be verified. The result remains vulnerable to changes during procurement and construction.
A strong design-stage file identifies the responsible party and the evidence expected at completion. It does not merely state that the credit is targeted. It shows how the intended outcome will be carried into contracts, submittals, installation and handover.
Post-construction evidence asks what was actually delivered. As-built information, installed-product records, dated photographs, commissioning results, waste records, completion reports and final management documents become more important.
The final assessment tests whether the design-stage commitments survived the project. A proposed product may have changed, a system may have been omitted or a planned activity may have no completion record. The final evidence must reflect those realities.
Where a design-stage certificate exists, the post-construction review can build on the earlier assessment, but it is not entitled to assume that every commitment was fulfilled. The licensed assessor needs sufficient evidence to confirm the completed outcome.
Architects commonly hold general arrangement drawings, design statements, finish schedules and coordination records. Building-services engineers often hold system calculations, schematics, equipment schedules and commissioning requirements. Structural and civil engineers hold information about structure, materials, drainage and site works within their disciplines.
Contractors and subcontractors commonly hold product submittals, delivery information, installation records, photographs, inspection documents, test sheets and commissioning data. Cost consultants may hold material quantities and procurement records, while specialist advisers hold surveys, models and technical reports.
The client, project manager and facilities team often hold briefs, appointments, minutes, approvals, handover records, policies and operational procedures. The assessor identifies what is needed, reviews what is supplied and connects it to the assessment.
A late change of product or contractor is a common route by which a credit is lost. The replacement may not have the same declared properties, the new supplier may not provide equivalent documentation or the incoming contractor may not understand an earlier assessment commitment.
The change can also break the evidence chain. A specification may refer to the original product, while the as-built schedule names another. A design calculation may use the original equipment, and the commissioning record may not identify the substitute clearly. Even where the replacement is technically suitable, the documentation may no longer demonstrate the claimed outcome.
Change control should therefore include an assessment review before approval. The project needs to identify which credits, minimum standards, calculations and evidence obligations are affected. Discovering the issue during final submission may leave no practical route to recover the claim.
Good evidence forms a connected sequence rather than a pile of unrelated files. A decision appears in minutes or a strategy, enters the design through drawings and specifications, passes into procurement through submittals, appears on site through installation records and is confirmed through testing or handover.
The documents vary across the framework. The commercial technical manual controls those requirements, and an independent information resource should not reproduce the evidence schedule of any individual credit.
The general principle remains consistent: evidence must be relevant, attributable, timely and matched to the actual project. Where the record follows the real sequence of decisions and delivery, the assessor can test the claim. Where the record is reconstructed late or broken by uncontrolled change, the credit remains at risk.
Evidence should exist at the time the relevant decision or activity occurs, because a record reconstructed afterwards cannot demonstrate that an earlier process actually took place.
Drawings, specifications, calculations, manufacturer declarations, commissioning records, meeting minutes and dated photographs are all common forms of evidence.
A design-stage assessment examines proposals and commitments, while a post-construction assessment examines what was actually delivered and installed.
This is an independent information resource. It is not affiliated with, endorsed by, or connected to BRE. BREEAM and BRE are the trademarks of their respective owners and are used here only to identify the scheme described.