Treat every SKA measure as two questions in sequence. Question one is about scope: do the physical works covered by this project actually trigger the measure? Question two is about proof: does the documentation demonstrate that the requirement was met for this specific project? Studying the two questions separately, then combining them in timed drills, builds the judgment the assessor role actually demands.
Scope First: Why the Fit-Out Boundary Changes Every Measure Decision
Before judging any measure, establish what the project covers: landlord works, Category A fit-out, or tenant Category B works. Scope determines which measures enter the assessment, so it must be fixed before scoring begins.
SKA-style fit-out assessment measures are written around fit-out works rather than whole-building performance. A measure aimed at heating plant, roof fabric, or external works may simply not be triggered by a tenant fitting out one floor where the base building is untouched. Practise reading each measure's intent and asking a concrete question: what physical works on this project would cause this measure to apply? If the answer is none, the measure sits outside the assessment, no matter how well the building performs in that area.
This is the sharpest contrast with whole-building schemes such as BREEAM, where the assessed boundary is the building itself. In a fit-out assessment, every scope decision ripples through the measure list: removing an element of works removes its measures, and any measure the manual designates as mandatory within that scope must still be resolved. Make it a habit to write a one-sentence scope statement — what is being fitted out, by whom, and what is explicitly excluded — before you look at a single measure. That sentence becomes the reference point for every applicability dispute.
| Scope question | Typical consequence | Assessor action |
|---|---|---|
| Is the landlord's mechanical plant part of the works? | Energy measures tied to that plant may not be triggered | Record the exclusion and check no mandatory item depends on it |
| Are finishes and partitions included? | Materials-related measures apply and need product evidence | Flag evidence requirements to the project team early |
| Are external or circulation areas in the works? | Transport and waste measures may come into play | Confirm the boundary in the scope statement |
| Are services being replaced or only retained? | Commissioning-type measures attach to replaced items | Separate retained, modified, and new elements in your notes |
Mandatory Designation vs Scored Measures: Two Different Ways to Fall Short
Scheme manuals designate certain measures as mandatory within a given scope; other measures accumulate toward the score. These fail differently: a missed mandatory item undermines the assessment itself, while a dropped optional measure only reduces the total.
Designation is a property of the measure in the applicable manual, and it interacts with scope: a measure that is mandatory for one type of project may not even be triggered by another. Your first pass through any measure list is therefore a classification task, not a scoring task. Read the manual's designation for each triggered measure and record it explicitly. An assessor who scores confidently but has not tracked which triggered items carry mandatory status has not completed the assessment, because the score cannot rescue an unmet mandatory requirement.
Train the distinction with a three-bucket sort. Bucket one: mandatory items — these need a definitive met-or-not decision backed by evidence. Bucket two: scored measures that are low-cost or already satisfied by standard practice — these are usually safe to claim. Bucket three: scored measures that demand unusual effort or cost — these are where project teams negotiate, and where you must weigh trade-offs. The buckets teach different reasoning: bucket one is compliance logic, bucket three is professional advice about what the client is realistically committing to, and confusing the two produces muddled assessments.
- Bucket one decision: is the mandatory item met, and what single document proves it?
- Bucket two decision: is the claim already justified by the project's routine practice?
- Bucket three decision: what would the client need to change, and is that reflected in the design?
Design Intent vs Delivered Fit-Out: Same Measure, Different Question
Assessment distinguishes what is specified from what was installed and demonstrated. Early-stage judgments rest on specifications and drawings; later judgments rest on as-built records showing the measure was actually delivered.
A specification clause can satisfy a design-stage reading of a measure while the completed works tell a different story if the product was substituted, the control strategy was simplified, or the commitment was never carried through. When you read a measure, label which stage its wording addresses. Language about what shall be provided or specified points to design intent; language about what was installed, commissioned, or recorded points to delivery. A measure can be genuinely met at one stage and unmet at the other, and part of the assessor's interpretation task is knowing which question each clause is asking.
Build this into practice by taking a set of sample clauses and writing two short notes beside each: what evidence would satisfy this at design stage, and what evidence would satisfy it at completion. A specification satisfies the first; installation records, commissioning results, or completed checklists satisfy the second. This habit exposes the gap between a well-written document set and a delivered outcome, and trains you to notice when a project team answers a delivery-stage question with a design-stage document — a substitution of evidence type that should trigger a follow-up, not a tick.
Evidence That Proves vs Documents That Describe
Credible evidence ties a specific measure to this specific project: named products, project-specific records, dated and attributable documents. Brochures, policy templates, and statements of intent describe good practice but rarely prove delivery.
Think in terms of a hierarchy. At the top sit project-specific records: purchase or delivery documentation naming the actual product, commissioning results referencing the installed system, signed logs covering the works in question. In the middle sit project documents that describe intent — specifications, drawings, strategies — which are strong for design-stage questions but not sufficient alone for delivery questions. At the bottom sit generic materials: manufacturer brochures, sample certificates for other projects, and template policies. An adjudication error to avoid is treating the bottom tier as though it reached the top because it mentions the right topic.
The discipline is matching evidence to the clause wording rather than to the topic. If a measure requires verification of what was installed, evidence must identify the installed item for this project, in the installed quantity. If it requires a process to have been followed, evidence must show the process occurring, not merely existing on paper. This is why an assessor's follow-up questions matter: a document that prompts 'which project, which product, which date, whose signature' is a description; one that already answers those questions is proof.
- Does the document name this specific project?
- Does it match the installed or specified item, not a general product range?
- Is it dated within the relevant works period?
- Is an identifiable person or organisation accountable for its content?
- Does it cover the whole scope claimed, or only a sample?
Worked Scenario 1: The Recycled-Content Ceiling That Wasn't Verified
A materials claim supported only by a manufacturer brochure should not be accepted. The correct move is to require project-specific documentation for the actual product installed, because the measure asks what was used, not what the supplier can offer.
Scenario: during a Category B office fit-out, the contractor submits a ceiling-tile claim supported by the manufacturer's marketing brochure, which states that the product range contains recycled content. The apparent mistake is accepting the claim because the brochure mentions recycled content and the ceiling is clearly from that manufacturer. The brochure is a bottom-tier document: it describes a product range, not the sheets installed in this project, on this date, in this quantity. An assessor who accepts it has substituted a description of capability for evidence of delivery.
The better decision is to note the claim as plausible but unverified, then request the project-specific purchase record and the technical datasheet for the specified product, checking that the ordering documentation matches the ceiling schedule. If the installed product is confirmed as the recycled-content variant, the measure can be credited with confidence; if the contractor installed a cheaper variant from the same range, the claim collapses. Why it matters: recycled-content measures depend entirely on what was actually procured, and a range-level claim cannot distinguish between the variant that earns recognition and the variant that does not. Train yourself to write the follow-up request immediately rather than mentally downgrading the claim to 'probably fine'.
Worked Scenario 2: The Lighting Control Credit That Belonged to the Landlord
A measure credit belongs only to works inside the project's scope. If an existing base-building system delivers the benefit but the fit-out did not touch it, the assessor should exclude it, or credit only the parts of the works actually performed.
Scenario: a tenant fit-out occupies a floor in a multi-tenanted building. The team requests credit for a lighting-efficiency measure, pointing out that the floor benefits from an occupancy-controlled lighting system installed by the landlord years earlier, untouched by the fit-out. The apparent mistake is awarding the credit because the measured benefit is real and the occupant genuinely gains from it. But the assessment boundary is the fit-out works, not the occupant's experience; a measure not triggered by the project's works is outside the assessment regardless of how favourably the base building performs.
The better decision is to record the scope exclusion, note in the assessment file that the base-building system was reviewed and found outside the works, and then check whether any measures actually triggered — for instance, controls for lighting newly installed as part of the fit-out — carry mandatory status that now needs resolving. Why it matters: crediting out-of-scope works misrepresents what the assessed project achieved and undermines the boundary that makes fit-out assessment meaningful. It also hides the real question: does the fit-out's own lighting design meet the measures it triggered? A written scope decision, even a one-line note, protects the assessment if the boundary is later questioned.
The Measure-by-Measure Audit Drill and Your Readiness Checks
Rehearse a complete mock assessment: write a scope statement, classify every triggered measure, assign evidence to each, and defend every disputed call by clause wording. Use the rubric below as study milestones, not as a prediction of any exam outcome.
An adaptable preparation sequence: first, learn the scheme's structure — how measures are grouped, how scope and lifecycle stages are defined, and how mandatory designation works — reading the organisation of the manual rather than memorising it. Second, drill scope statements: take varied project descriptions (a single-floor tenant fit-out, a full Category A strip-out, a partly retained interior) and write a one-sentence scope plus a predicted list of triggered measures for each. Third, run the three-bucket classification on each scenario's measure list. Fourth, run evidence-matching drills pairing sample documents to clauses and identifying which tier each occupies. Finish with two full timed mock assessments, reviewing every hesitated decision against the manual's exact wording rather than your instinct.
Check readiness against observable behaviours. You can state a project's scope in one sentence and defend any exclusion from it. You can label any measure as design-intent or delivery-focused and name the evidence type each reading demands. You can classify a measure's mandatory status without notes. When you disagree with a sample answer, your argument cites clause wording and a scope or evidence principle, not general feeling. If any of these checks wobbles, return to the corresponding drill rather than rereading passively. SKA Rating is operated by BRE, which is also the authoritative source for current manual versions and all administrative arrangements; a short visit to the issuer's site is worth one focused session, with your study time going into the drills above.
- Scope check: one-sentence scope statement plus a defensible list of excluded elements for any practice project.
- Stage check: every practice measure labelled design-intent or delivery-focused, with its matching evidence type.
- Evidence check: five sample documents correctly sorted into the three-tier hierarchy, with follow-up questions drafted for the bottom tier.
- Decision check: in your last mock, every disputed call resolved by quoting the clause, not by recollection or intuition.
- Score caveat: treat any self-assessed drill score as a learning milestone that shows which drills to repeat, never as an indication of an exam result.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.