Part L Evidence Made Simple: How SAPAPP Helps Builders Avoid Last Minute Compliance Problems

Case study feature

Part L Evidence Made Simple: How SAPAPP Helps Builders Avoid Last Minute Compliance Problems

Two weeks before handover, the site manager had the usual pressure on his desk.

The plots looked close. Kitchens were in. Air testing was booked. The client was asking for completion dates. The problem was not the build itself. The problem was the evidence.

Window specifications had changed. The heat pump model on site was not the same as the early design note. Several insulation photos were sitting in different phones across the team. The SAP assessor had been sent drawings from an older revision. Nobody wanted to find out at the last minute that the Part L evidence pack did not match what had actually been built.

That is where ATSPACE brought in SAPAPP.

This case study shows how a simple, structured evidence process helped a builder avoid a last minute Part L scramble, keep SAP information aligned with site, and give the project team a clearer route to handover.

This case study follows the supplied ATSPACE case study brief format and keeps the project anonymised.

Project overview

• Project type: New build housing
• Project size: 14 houses across two short terraces and four detached plots
• Location: Maidstone, Kent
• Client type: Regional house builder
• Stage when ATSPACE joined: Mid build, before air testing and final SAP submission
• Primary goal: Support Part L evidence and reduce late compliance issues
• Secondary goal: Bring SAP data, site records and product evidence into one clear workflow

Approved Document L Volume 1 gives guidance for dwellings under Part L of the Building Regulations in England. It covers areas including target primary energy rate, target emission rate, target fabric energy efficiency rate, limiting heat gains and losses, air permeability, commissioning and reporting evidence of compliance.

The project was not in serious trouble. That was the point. Most Part L problems do not start as failures. They start as small gaps in information that are left too late.

The challenge, what was at risk

The builder had a tight handover programme and multiple trades finishing at the same time. On paper, the design SAP calculations were workable. On site, the team had made normal construction changes.

Some changes were minor. Some mattered.

A few window U values had been updated after procurement. The hot water cylinder specification had changed due to availability. A small number of thermal junction photos were missing. Ventilation commissioning dates had shifted. The air tightness strategy was clear to the site team, but the evidence trail was spread across drawings, emails, WhatsApp photos and supplier data sheets.

The risk was not just a single calculation issue. The bigger risk was delay caused by poor coordination.

For Part L, the design, the installed specification and the evidence need to tell the same story. SAP is not just a desktop calculation at the end of the job. It relies on accurate inputs from drawings, fabric details, services, air testing, thermal bridging, ventilation and commissioning.

GOV.UK describes SAP as the Standard Assessment Procedure used to calculate a home’s energy performance. Approved Document L also makes clear that air pressure test results are used to show compliance with relevant Part L requirements, and that results need to be recorded and provided in line with the regulation 43 process.

The client wanted a cleaner process before final testing, not a panic after it.

What made this job tricky

1. Several plots were at different stages

Some plots were plastered. Others still had service penetrations open. That meant evidence had to be gathered carefully, plot by plot, without assuming one photograph covered the whole site.

2. Product substitutions had happened

This is common on live projects. The issue is not always the substitution itself. The issue is whether the substitution has been checked against the SAP model and recorded properly.

3. Photos were not consistent

Some photos had no plot reference. Some did not show enough context. Some were taken before the final detail was complete. For Part L evidence, a useful photo needs to show what it is, where it is, and why it matters.

4. The SAP assessor was not getting live site changes

The assessor had information, but not always the latest information. That creates avoidable back and forth near handover.

5. The programme had little room for rework

A missed insulation detail, unconfirmed air barrier line, or wrong product data sheet can cost time when everyone is trying to finish.

Our approach, step by step

ATSPACE used SAPAPP as a practical evidence workflow, not as another admin task for the site team.

The aim was simple. Capture the right information once, in the right format, while it was still visible and easy to check.

Step 1: Review the design SAP inputs

We started by checking the design SAP information against the latest drawings and specifications.

This included:

• Wall, floor and roof build ups
• Insulation thicknesses and lambda values
• Window and door U values
• Thermal bridging approach
• Heating and hot water systems
• Ventilation strategy
• Solar PV allowance where relevant
• Air permeability target
• Plot types and repeated details

The purpose was not to redesign the scheme. It was to find gaps early enough for the builder to deal with them in a controlled way.

Step 2: Build a plot evidence tracker in SAPAPP

We set up the project in SAPAPP with each plot listed separately. The builder could then see what was complete, what was missing and what needed checking.

The tracker covered the main Part L evidence items linked to the SAP model and final reporting.

This included:

• Fabric installation photos
• Thermal junction records
• Window and door evidence
• Heating and hot water data
• Ventilation commissioning information
• Air test results
• As built specification changes
• Final assessor queries

This gave the site manager one clear view instead of a chain of scattered messages.

Step 3: Site walkdown with the construction team

ATSPACE attended site and walked the plots with the site manager and finishing foreman.

We looked at the areas that often create Part L evidence problems:

• Loft insulation continuity
• Cavity closer and reveal details
• Service penetrations through the air barrier
• Meter boxes and external wall penetrations
• Party wall and separating wall junctions
• Floor perimeter insulation
• Duct routes and ventilation terminals
• Heating plant labels and installed model numbers

The tone was practical. The site team did not need a lecture. They needed a short list of what mattered, what was missing and what to photograph before it was covered.

Step 4: Align product evidence with the installed build

The team uploaded product data sheets and installation photos into SAPAPP. ATSPACE then checked whether the information matched the SAP assumptions.

Where items did not match, we flagged them clearly.

For example, one window package had a slightly different U value from the value originally used in the design SAP. That did not mean the plot would fail. It meant the SAP model needed to reflect the actual installed product before final submission.

The same applied to the hot water cylinder and ventilation units. Model references had to be checked against the installed units, not just the early design schedule.

Step 5: Prepare for air testing and final evidence

Approved Document L includes air permeability and pressure testing as part of the dwelling guidance. It also links pressure test results with demonstrating compliance for relevant regulations and the Part L requirement around limiting heat gains and losses.

Before air testing, we helped the builder review likely leakage routes and evidence gaps. This included service penetrations, loft hatches, pipe boxing, external doors, thresholds, extract duct seals and plant cupboards.

The air test was still a real site test. SAPAPP did not replace proper testing. It helped the team prepare properly and hold the results in the right place once available.

What we found on site

The site was generally well built, but the evidence process had weak points.

We found:

• Three plots had missing photographs for floor perimeter insulation
• Two window data sheets did not match the installed frame schedule
• One ventilation unit model reference needed confirmation
• Several service penetrations needed sealing before air testing
• The latest PV layout had not been issued to the SAP assessor
• Some plot photos were useful but not labelled clearly enough
• The design SAP file needed updating to match two procurement changes

None of these items were unusual. That is exactly why they matter.

A late Part L problem often comes from ordinary site changes that nobody has pulled together in time.

Solutions and actions taken

Evidence checklist issued to site

ATSPACE gave the site manager a simple plot by plot checklist inside SAPAPP. Each item showed what evidence was needed and whether it was complete.

Missing photos captured before close up

For plots not yet fully closed, the site team captured missing insulation and junction photos before final finishes covered the detail.

SAP inputs updated

The SAP assessor was issued with a clean schedule of changes. This included updated glazing values, heating system data, ventilation references and PV layout information.

Air leakage risks closed out

Before testing, the team sealed visible service penetrations, checked loft hatches, reviewed extract duct collars and inspected external door thresholds.

Handover evidence pack prepared

Rather than waiting until the end, evidence was organised as the plots moved through completion. That reduced the number of final queries.

Results, with numbers and evidence

The project avoided the late scramble that the builder had been concerned about.

Key outcomes:

• 14 plots tracked individually in SAPAPP
• 41 evidence gaps identified before final submission
• 36 gaps closed within five working days
• 5 remaining items assigned to named people with clear close out dates
• Design SAP information updated before final air testing
• Product substitutions reviewed before handover
• Air test preparation completed across all plots before the booked test window
• Final evidence pack issued in a structured format for the project team and assessor

The builder did not lose time hunting through message threads for photos. The SAP assessor received cleaner information. The site manager had a live view of what was still open.

Most importantly, the project team could deal with Part L evidence while trades were still available and details were still visible.

We do not claim that any process guarantees building control acceptance. Building control decisions remain with the relevant body. What SAPAPP did here was make the evidence clearer, earlier and easier to check.

What the client received, deliverables

The client received:

• Project SAPAPP evidence tracker
• Plot by plot Part L evidence status
• Missing information schedule
• Site walkdown notes
• Product substitution review notes
• Updated information pack for SAP assessment
• Air test preparation observations
• Final evidence folder structure
• Practical close out list for site and office teams

The deliverables were designed for real use. A site manager needs to know what to do next. A contracts manager needs to know what could affect handover. An assessor needs accurate inputs. SAPAPP helped bring those needs together.

Lessons learned, what other projects can copy

Start evidence collection before finishes

Do not wait until plasterboard, ceilings and boxing hide the details. Part L evidence is easier when the work is still visible.

Treat substitutions as SAP events

A change in window, heating, hot water, PV or ventilation specification should trigger a SAP check. It may be fine, but it should not be assumed.

Label photos properly

A photo without a plot number, location or context can be hard to use later. Good evidence is clear, dated, traceable and relevant.

Keep the assessor close to the live build

SAP calculations are only as good as the information going into them. Keep the assessor updated when the site changes.

Use one evidence system

Spreading information across emails, phone galleries and message apps creates risk. One system makes ownership clearer.

Why ATSPACE, beyond compliance support

ATSPACE does not just produce reports and leave the builder to work out the rest.

Our value is in the practical gap between design intent and site reality. We understand that trades change, products change, access changes and programmes move. The job is to keep compliance evidence aligned with the building that is actually being delivered.

With SAPAPP, ATSPACE helped this project by:

• Turning Part L evidence into a live process
• Giving the site team clear actions
• Helping the assessor work from current information
• Reducing avoidable final week queries
• Supporting the builder without overcomplicating the job

Part L evidence is not just paperwork. It is proof that the design, specification and constructed dwelling have been properly coordinated.

FAQ

What is SAPAPP?

SAPAPP is a structured evidence and coordination process used to help collect, track and manage information linked to SAP and Part L requirements. It helps builders see what is complete, what is missing and what needs checking before final submission.

Does SAPAPP replace SAP calculations?

No. SAPAPP does not replace SAP calculations or the role of a qualified SAP assessor. It supports the evidence process by helping organise the information that feeds into the SAP assessment and final project records.

When should a builder start collecting Part L evidence?

Start as early as possible, ideally before key details are covered. Insulation, junctions, air barrier lines, service penetrations and installed product references are much easier to evidence during construction than after finishes are complete.

What causes last minute Part L problems?

Common causes include missing photos, product substitutions, outdated drawings, unconfirmed ventilation data, changed heating equipment, poor air test preparation and SAP inputs that do not match the as built specification.

Is air testing part of Part L evidence?

Yes, for new dwellings where pressure testing applies, air test results form an important part of the evidence route. Approved Document L links pressure test results with showing compliance for relevant building regulations and Part L requirements.

Can product substitutions affect SAP?

Yes. Changes to windows, doors, insulation, heating, hot water, ventilation or PV can affect SAP outputs. Not every substitution creates a major issue, but it should be reviewed before final submission.

What should a good Part L evidence pack include?

It should include accurate SAP inputs, current drawings, product data, installation evidence, commissioning records, air test results, relevant photographs and a clear record of any changes from design to as built.

Does ATSPACE guarantee Part L sign off?

No. ATSPACE does not guarantee building control outcomes. We provide evidence led support, technical review and practical coordination to help builders reduce avoidable compliance risk.

Call to action

Part L problems are easier to fix before the final week.

If your project is moving towards air testing, SAP finalisation or handover, speak to ATSPACE early. We can help you organise the evidence, check the gaps and give your site team a clear route to close out.