The Headline Result
The client had a hard deadline: 24 plots needed blower door testing inside a five‑day window, on a live site with finishing trades still active. ATSPACE delivered the programme within the agreed window by applying a programme‑led testing method: we controlled readiness, protected access, and avoided wasting test slots on plots that weren’t genuinely ready.
The Real Challenge (Why This Is Hard)
Fast testing programmes usually fail for predictable reasons:
- Plots are booked before they’re actually ready
- Access is messy (keys, security, cleaners, snagging, trades)
- Late penetrations appear after “plot ready” is declared
- Reporting lags, so the site can’t make fast decisions
- Teams test “known‑fail” plots just to tick a box, creating retests and delay
What ATSPACE Was Asked To Do
- Test 24 plots in 5 days
- Reduce retest risk through readiness control
- Keep disruption low on a busy finishing site
- Provide rapid, plot‑level reporting suitable for compliance packs
Our Approach (Speed Comes From Control, Not Rushing)
Step 1: Build a testing map, not just a calendar
We categorised every plot before day one using a simple traffic‑light system:
- Green: test‑ready now
- Amber: ready with minor close‑out
- Red: not ready (do not waste a test slot)
This prevents the most common mistake: forcing tests onto plots that will obviously fail.
Step 2: Daily readiness checks first thing
Each morning, our engineers confirmed readiness on the day’s Green/Amber plots and focused on the highest‑value checks:
- Riser cupboards and access panels (apartments)
- Service penetrations behind kitchens/utility areas
- Threshold and balcony door interfaces
- Loft hatches and ceiling penetrations
- Meter cupboards and incoming services
- Boxing edges and drylining perimeters
Step 3: Two rigs, one consistent workflow
To hit volume without chaos, we ran two test rigs with one shared process:
- Confirm readiness
- Test
- Log observations
- Provide immediate feedback to the site manager
- Issue an end‑of‑day summary so the team could act fast
Step 4: Protect the programme by avoiding “known‑fail” tests
If a plot was clearly Red, we advised swapping it for a Green plot rather than burning a test slot and creating a retest later. This single behaviour protects a tight programme more than anything else.
Real Issues We Faced (And What We Did)
Issue A: Riser cupboards and access panels
A number of riser panels had incomplete edge sealing. These are quick fixes only if found before the slot. Readiness checks prevented wasted test time.
Issue B: Thresholds and balcony door junctions
Several plots had complex balcony threshold interfaces. We flagged these as a repeat risk and ensured close‑out consistency across all plots.
Issue C: Late‑stage M&E penetrations
Some plots had last‑minute works introducing new openings. We agreed a simple rule: any new penetration must be sealed and re‑checked before returning a plot to Green status.
Results
- 24 plots tested within the 5‑day window
- Strong first‑time pass performance, with minor close‑outs identified and completed early
- No programme slip caused by airtightness testing
- Rapid plot‑level reporting supported compliance submissions without a last‑minute scramble
What This Project Proves
If you want fast airtightness testing, you don’t rush the tests — you control readiness and sequencing. The site wins came from:
- categorising plots (Green/Amber/Red)
- early daily readiness checks
- parallel testing with a consistent workflow
- same‑day feedback and reporting
Mini FAQ
How many plots can you test in a day?
It depends on readiness, access and plot type. The fastest programmes rely on readiness checks and smart sequencing, not optimistic scheduling.
Does fast testing increase failure risk?
Only if readiness checks are skipped or “known‑fail” plots are forced into the schedule.
