As-Designed SAP to As-Built Sap: Closing the Gap at Handover

Case study feature

The Result

A live housing site needed Part L compliance signed off without last‑minute surprises.
ATSPACE managed the SAP calculations plot by plot, controlled the evidence required for as‑built updates, and kept compliance stable throughout procurement and build changes.

The outcome was simple and commercially important: Part L sign‑off achieved first time, with fewer queries, fewer recalculation loops, and no handover delays caused by missing SAP evidence.

Project Snapshot

Service: SAP calculations
Client: Regional housebuilder + principal contractor
Site: Brookfield Gardens, 1–32 Hawthorne Way, Rugby CV21 1QG
Development: 32 new build homes (detached + semi‑detached)
Energy strategy: Fabric‑first, low‑carbon heating by plot type, PV where applicable
Programme stage: Rolling completions and handovers
Compliance driver: Building Regulations Part L + evidence pack requirements
ATSPACE delivery: As‑designed SAP, as‑built SAP updates, evidence‑capture guidance, plot tracking, compliance‑pack support
Team: ATSPACE SAP assessor team + compliance coordinator

Why SAP Becomes a Problem on Live Sites

SAP issues rarely come from poor design — they come from unmanaged drift during construction.

The site faced common real‑world pressures:

  • product substitutions due to lead times
  • differences between plot‑type specifications
  • small changes to heating controls or lighting
  • airtightness + ventilation test results arriving late
  • plot variations not captured clearly

If SAP inputs don’t track the actual build, projects hit compliance problems at the worst moment — handover week.

What SAP Calculations Actually Do in Practice

SAP is the regulated energy‑performance method for new homes. On site, the key truth is:

👉 If the as‑built SAP does not match the as‑built home, you lose time and risk non‑compliance.

A controlled SAP process means:

  • correct fabric + glazing inputs
  • correct heating + hot water system + controls
  • correct ventilation strategy data
  • correct lighting assumptions
  • correct airtightness result
  • a clean evidence trail that stands up at handover

What ATSPACE Was Asked To Do

The housebuilder wanted a controlled, low‑drama approach:

  • complete SAP calculations across all plots
  • protect Part L compliance through design/substitution changes
  • reduce back‑and‑forth evidence chasing
  • provide a clear route to as‑built SAP sign‑off
  • align everything to rolling completions

What ATSPACE Did

Step 1: Plot tracking aligned to the build programme

We created a simple tracker so every plot had clear compliance gates:

  • as‑designed SAP complete
  • plot specification confirmed
  • evidence pack received
  • airtightness result received
  • as‑built SAP updated
  • compliance pack ready

This removed uncertainty and prevented the typical end‑of‑project scramble.

Step 2: Evidence capture the site could actually deliver

We issued a short, practical checklist covering key SAP blockers:

  • insulation/build‑up variations
  • window + door specs (esp. when substituted)
  • heating system + controls
  • PV provision
  • ventilation strategy + fan details
  • airtightness test results

Checklist simplicity = consistent evidence = fewer delays.

Step 3: Control of plot variations

Where a variation existed, we:

  • logged it once
  • applied it consistently

This prevented mismatched SAP outputs between identical plots.

Step 4: As‑built updates in step with completions

We updated SAP as each plot completed, not weeks later.
This ensured compliance paperwork kept ahead of handovers.

Problems Faced — and How They Were Solved

Problem 1: Heating controls changed late

Why it mattered:
Controls materially affect SAP performance.

What we did:
Confirmed installed controls → updated SAP inputs → added correct product info to evidence pack.


Problem 2: PV installed inconsistently

Why it mattered:
If SAP assumes PV but it isn’t installed, compliance can fail.

What we did:
Verified PV plot by plot → updated SAP accordingly → protected compliance.


Problem 3: Airtightness results arrived late

What we did:
Prepared SAP updates in advance → finalised immediately once results came in → avoided delays.

Outcome

The project achieved a clean Part L sign‑off across all 32 plots.

Project outcomes:

  • Part L compliance achieved first time
  • fewer SAP queries late in the programme
  • reduced admin load on the site team
  • as‑built SAP aligned fully to installed specs
  • smoother handover packs with minimal chasing

Common Mistakes This Project Avoided

  • leaving as‑built SAP updates until the end
  • relying on design intent after substitutions
  • missing control changes that shift SAP outcomes
  • assuming PV without plot‑level verification
  • waiting for airtightness results before starting updates

CTA

If you need SAP calculations managed properly across a live site, ATSPACE will control the process plot by plot, keep Part L compliance stable, and deliver as‑built SAP outputs that support first‑time sign‑off and smooth handovers.

Ask for:

  • SAP calculations for new build homes
  • plot tracking + evidence capture support
  • as‑built SAP updates aligned to completions
  • compliance‑pack support for Part L sign‑off

Frequently Asked Questions

What causes SAP delays on new‑build sites?
Missing evidence, late specification changes, and leaving SAP updates until handover week.

Can you manage SAP on rolling completions?
Yes — this is the most effective way to avoid bottlenecks.

Do small product changes really affect SAP?
Yes. Heating controls, ventilation details, lighting assumptions and PV provision can all move the result.