Technical assurance is sometimes treated as a final check completed shortly before handover. At that stage, however, many important decisions have already been made and much of the work may already be concealed.
Effective technical assurance begins earlier.
It provides planned and proportionate confidence that the requirements have been understood, the design is suitable, the work can be constructed and the completed installation reflects the approved information.
In retrofit, this is particularly important because existing buildings contain uncertainty. Similar looking properties may contain different materials, alterations and defects. A standard solution may therefore require review before it is applied to every home.
Assurance is not the same as inspection
Inspection is one part of technical assurance, but the two terms are not interchangeable.
Inspection generally examines a product, activity or completed item. Technical assurance considers the wider process through which the outcome was developed and delivered.
This may include:
- Reviewing whether the assessment is sufficient
- Confirming that key risks have been identified
- Checking the design against the project requirements
- Reviewing interfaces between measures
- Considering buildability and sequencing
- Confirming that installation evidence is meaningful
- Checking that changes have been reviewed and recorded
- Verifying that handover information reflects the completed work
This creates confidence throughout the project rather than relying on a final inspection to discover problems.
Begin with the existing building
A technically sound retrofit design depends on a reliable understanding of the property.
The assessment should provide sufficient information about the construction, condition, services, ventilation, occupancy and constraints. Where uncertainty remains, the design should identify how it will be resolved.
Technical assurance should ask whether the information is adequate for the decisions being made.
For example, a proposed insulation system may require confidence about wall construction, exposure, existing moisture condition, internal finishes, junctions and ventilation. Where these matters are uncertain, further investigation may provide more value than progressing with assumptions.
Review the design as a complete system
Individual measures can appear suitable when considered separately but create difficulties when combined.
Insulation may alter heat flow and surface temperatures. Increased airtightness may increase the importance of effective ventilation. New heating controls may affect how occupants use the building. Window replacement may influence background ventilation and junction detailing.
Technical assurance should therefore examine the complete design rather than checking each measure in isolation.
The review should consider:
- Compatibility between proposed measures
- Interfaces with the existing structure
- Moisture management
- Ventilation provision
- Thermal continuity
- Access and maintenance
- Fire and structural considerations where relevant
- Construction sequence
- Resident use and handover
PAS 2035:2023 provides the overarching framework for energy efficiency retrofit in existing dwellings, while PAS 2030:2023 specifies requirements for the installation of energy efficiency measures. The standards address the wider process of retrofit delivery and the quality of installation rather than treating the work as product selection alone.
Apply assurance in proportion to risk
Not every property or detail requires the same level of review.
A repeatable and familiar measure in a consistent property type may require a standard review supported by sample inspections. A complex property, unusual construction or high risk interface may require specialist input, additional survey information or a specific hold point.
A proportionate assurance plan may identify:
- Standard items that can be reviewed through normal project controls
- Important items that require evidence before work continues
- High risk matters that require specialist acceptance
- Repeated details that require first off verification
- Concealed work that must be inspected before closure
This directs attention towards the matters most likely to affect safety, performance or long term durability.
Make evidence purposeful
Photographs and checklists are useful only when they demonstrate something meaningful.
A large quantity of poorly framed photographs does not necessarily provide confidence. Evidence should be linked to the requirement being verified.
A useful evidence plan explains:
- What must be demonstrated
- When the evidence should be captured
- The location and context required
- The person responsible for reviewing it
- What happens when the evidence is incomplete
For concealed work, evidence should be collected before the item is covered. For repeated installations, the evidence should allow the reviewer to distinguish between properties and locations.
Provide constructive challenge
Technical assurance should not become an adversarial process.
Its role is to identify uncertainty, ask proportionate questions and support the team in reaching a defensible technical decision.
Early challenge is usually less disruptive than late rejection. A detail questioned before installation can be revised with limited impact. The same issue identified after several properties have been completed may result in opening up, remedial work and programme delay.
Assurance is most effective when it is integrated with the design and delivery teams while retaining enough independence to provide objective challenge.
Close the loop at handover
The final records should explain what was actually installed.
Approved changes, product information, commissioning records, ventilation information, photographs and resident guidance should be consistent with the completed property.
Where the final records differ from the design, the reason should be clear.
This supports future maintenance, future retrofit decisions and the investigation of any performance concern.
The AISK perspective
AISK views technical assurance as a continuous line of confidence from the initial requirements through to the completed work.
The objective is not to check every decision twice. It is to identify the points at which an error would be difficult or costly to correct and make sure that suitable review occurs before that point is passed.
When assurance is risk focused, timely and connected to delivery, it strengthens quality while supporting programme progress.
