SAP Calculations for New Build Homes: Getting Part L Compliance Signed Off First Time

The Result

A housing phase had strong design‑stage SAP outputs, but as handover approached, the contractor faced the familiar challenge: the as‑built reality didn’t match the design assumptions perfectly.
ATSPACE managed the transition from as designed to as built SAP by capturing evidence early, updating SAP inputs plot by plot, and resolving inconsistencies before they caused delays.
The project closed the compliance gap cleanly and supported smooth Part L sign‑off at handover.

Project Snapshot

Service: SAP calculations + as‑built updates
Client: Main contractor (mixed‑tenure housing scheme)
Site: Meadowbrook Rise, Phase 2, Plots 51–74, 1–24 Clover Lane, Bedford MK41 7PN
Development: 24 homes (detached + semi‑detached)
Programme stage: Handover and completion packs
Compliance driver: Building Regulations Part L as‑built evidence
ATSPACE delivery: As‑designed SAP review, as‑built evidence capture, plot‑level SAP updates, airtightness integration, handover‑ready outputs
Team: ATSPACE SAP assessor team + compliance coordinator

Why the As Designed → As Built Gap Happens

Even on well‑run sites, drift is normal:

• procurement substitutions
• installer preferences for controls or fans
• lighting specification changes
• PV variations due to roof constraints
• airtightness results differing from design targets
• documentation mismatched to what was installed

The issue isn’t that changes happen — the issue is when they’re not captured until the last minute.

What ATSPACE Was Asked To Do

The contractor needed a controlled close‑out process:

• review as‑designed SAP assumptions and identify drift risks
• capture as‑built evidence consistently
• update SAP inputs plot by plot with a clear audit trail
• integrate airtightness results quickly
• issue handover‑ready outputs to support Part L sign‑off

What ATSPACE Did

Step 1: Identify likely drift points early

We reviewed the house types and flagged high‑risk areas:

• heating system controls
• ventilation strategy + fan models
• PV provision + inverters
• glazing specifications
• lighting variations
• airtightness assumptions vs testing reality

This made the evidence capture focused and efficient.

Step 2: Build a simple evidence pack per plot type

A repeatable template reduced admin and avoided email chains.

Evidence included:

• heating system + controls
• ventilation strategy + fan data
• PV installation confirmation
• glazing performance
• airtightness test results
• substitution logs and plot‑specific variations

Step 3: Update as‑built SAP in line with completions

We updated plots progressively rather than waiting for a batch update at the end.
This prevented bottlenecks and kept compliance stable.

Step 4: Deal with exceptions properly

Where a plot differed from the house‑type model, we:

• recorded it clearly
• reflected differences in that plot’s SAP
• ensured no dwelling relied on generic assumptions

Step 5: Provide clear close‑out notes for the compliance file

Delivered handover‑ready Part L outputs with:

• key assumptions
• evidence references
• confirmation of plot‑specific variations

No ambiguity for future audits or warranty providers.

Problems Faced — and How They Were Solved

Problem 1: Airtightness results differed from assumptions

Fix: Updated SAP immediately and flagged risk areas early. Provided practical tips to prevent drift on remaining plots.

Problem 2: Controls evidence inconsistent

Fix: Standardised evidence requirements and captured them once per plot type, recording exceptions clearly.

Problem 3: PV provision varied by roof constraints

Fix: Reflected PV provision plot by plot and maintained compliance with transparent assumptions.

Outcome

The scheme closed the as‑designed → as‑built SAP gap without handover delays.

Project outcomes:

• as‑built SAP outputs aligned to real installations
• fewer last‑minute queries
• clean completion evidence packs
• improved confidence in Part L sign‑off
• workflow adopted for future phases

Common Mistakes This Project Avoided

• treating as‑built SAP as a last‑minute admin task
• applying generic assumptions across all plots
• waiting for airtightness before starting as‑built updates
• relying on undocumented control assumptions
• discovering compliance drift only after handover dates were fixed

CTA

If you want a smoother route to Part L sign‑off, ATSPACE will manage the move from as designed to as built SAP properly, capture the right evidence, and issue handover‑ready outputs with no last‑minute chasing.

Ask for:

• as‑built SAP updates + plot tracking
• usable evidence‑capture templates for site teams
• SAP support aligned to rolling handovers
• compliance close‑out support when results drift or specs change

Frequently Asked Questions

Why do as‑built SAP updates take longer than expected?
Because evidence is missing or substitutions aren’t logged. A structured pack prevents delays.

Can you update SAP plot by plot during rolling handover?
Yes — and it’s usually the best method to avoid bottlenecks.

What should be captured early to avoid SAP delays?
Heating controls, ventilation data, PV provision, glazing changes and airtightness results.