BREEAM Assessor (New Construction) common mistakes
BREEAM Assessor (New Construction) · Understand the traps and how to avoid them.
Treating the BREEAM rating as a fixed points total, so the candidate states that a score of 70% always yields 'Excellent', rather than applying the percentage thresholds and confirming the rating band against the current scheme version and building type.
Candidates memorise a single headline percentage-per-rating table from one scheme version and assume it is universal, ignoring that rating thresholds and the minimum-standards structure are set by the scheme manual in force at registration and can differ between building types and versions.
What to do instead
Learn the rating band boundaries as bands (Outstanding, Excellent, Very Good, Good, Pass) tied to the specific scheme version, and practise stating that the overall percentage is derived from category scores weighted by environmental weightings, then mapped to a band. Always qualify answers with 'for this scheme version and building type'.
Confusing the number of credits available in an issue with the number of points the issue contributes to the overall score, and answering as if one credit always equals one point.
Candidates skim the assessment-issues list and assume a one-to-one mapping, overlooking that category scores are calculated from credits achieved against credits available and then multiplied by environmental weightings before contributing to the overall percentage.
What to do instead
Work through at least one full score calculation by hand from a sample set of issue results, showing credits available, credits achieved, category percentage, weighting and contribution. Be able to explain in words why a category with many credits can contribute few overall points.
Describing the certification route as 'assessor submits and BREEAM issues the certificate', omitting the interim assessment, the QA and audit step by the certification body, and the role of the client and design team in sign-off.
Candidates learn the start (registration) and end (certificate) of the process but skip the middle, because the QA and verification stages are less visible in summary material and are easy to compress into a single step.
What to do instead
Map the route as an ordered sequence: registration, appointment of assessor, evidence collection, interim assessment, QA/audit sampling, final certification, post-construction review where applicable. For each stage, note who acts, what output is produced and what can cause the stage to fail or repeat.
Assuming certification is awarded at design stage and never revisited, so the candidate fails to mention that a final or post-construction assessment is required to confirm as-built performance and that design-stage claims must be verified.
Candidates conflate the interim design-stage assessment with the final certificate, often because the design-stage report is the most visible document in project examples.
What to do instead
State explicitly that the design-stage assessment is interim and that the certificate depends on as-built evidence. Practise describing what changes between design and post-construction (substitutions, commissioning results, as-built drawings) and how those changes are evidenced.
Accepting a manufacturer's marketing brochure or a supplier's self-declared claim as sufficient evidence for a credit without checking that it is current, project-specific and traceable to the credited requirement.
Candidates want to show they can find evidence quickly and treat any relevant-looking document as adequate, rather than applying the evidence hierarchy and checking validity dates, scope and independence.
What to do instead
Apply a three-part test to every evidence item: does it address the exact requirement wording, is it valid and current for the assessment date, and is it traceable to the specific building or specification. Reject documents that fail any part and record why in the evidence log.
Submitting evidence that is undated, unsigned or unattributed, so the QA reviewer cannot confirm who produced it, when, or for which project.
Candidates focus on technical content and treat document metadata as administrative noise, forgetting that auditability depends on provenance as much as on substance.
What to do instead
Before submitting, run a provenance check on each item: named author or issuing organisation, date, project reference, revision status and signature or approval where required. Keep a checklist column for each and refuse to upload items that fail the check.
Leaving evidence collection to the end of the assessment and then chasing documents under time pressure, resulting in gaps, late substitutions and credits claimed on the basis of intent rather than installed or specified fact.
Candidates underestimate how long it takes to obtain signed statements, commissioning records and as-built information from multiple parties, and assume the design team will supply everything on request.
What to do instead
Build an evidence plan at the start of the assessment, mapping each targeted issue to a named responsible party, the document expected and a due date ahead of the assessment deadline. Review the plan at fixed intervals and escalate missing items early rather than at submission.
Presenting personal opinion or 'best practice' as the basis for a credit decision instead of citing the specific assessment issue, its requirement and the scheme manual reference.
Experienced practitioners rely on professional judgement and habit, and candidates carry that over into exam answers without anchoring the judgement to the written requirement.
What to do instead
Adopt a discipline of citing the issue reference and requirement wording before giving any judgement. In practice answers, structure the response as requirement, evidence, conclusion, so the reasoning is visibly tied to the scheme rather than to the candidate's experience.
Failing to declare a conflict of interest, such as assessing a project for an employer or client where the candidate had a design or specification role, and proceeding as if independence were automatic.
Candidates treat the assessor role as purely technical and do not connect the code of conduct to everyday project relationships, especially on small projects where roles overlap.
What to do instead
Learn the independence and declaration obligations as concrete scenarios: prior design involvement, financial interest, close personal relationship, pressure to certify. For each, be able to state the action required (declare, decline, escalate) and to whom the declaration is made.
Treating the online assessment tool as a passive scoreboard, entering data without understanding how the tool calculates scores, what the audit trail records, or how to correct an entry after submission.
Candidates learn the tool by clicking through it rather than by understanding its data model, so they cannot explain the consequences of a mis-entered credit or an unsupported entry.
What to do instead
Practise on a training project: enter a set of issue results, inspect the category and overall score outputs, then trace one entry back through the audit trail. Learn the correction and version-control procedure and be able to describe it step by step.