Airtightness delivery: coordinating trades and verification
Admin · 22 October 2026
Illustrative image. Photo by Frames For Your Heart on Unsplash. Unsplash License.
Airtightness performance depends on connected decisions across design, procurement and site work. Several trades can affect the relevant details, while later changes may alter an arrangement that was previously coordinated. Treating verification as a single event at the end leaves the team with limited opportunity to address an issue. The project needs a planned route from its defined requirement to evidence of the completed work.
This article concerns management and coordination. It does not prescribe technical details, test methods or performance values. Those require appropriately competent specialists and current project-specific requirements. The client and project manager should ensure that responsibilities, information exchanges and verification activities are clear enough for those specialists and delivery teams to do their work.
Establish the applicable requirement
Ask the relevant designers and advisers to identify the requirements that apply to the building and the evidence expected. Record the basis in the controlled project information. Different project types and standards may require different treatment. The team should not select a value or procedure from an unrelated example and assume it establishes the correct requirement.
The Passivhaus Trust’s 2020 good-practice guide provides relevant background within its stated scope. It should not be presented as the current specification for every project. The responsible advisers must confirm the applicable standards, requirements and competent testing arrangements for the actual building.
Identify the design and package interfaces
Ask the responsible designers to define the relevant strategy and identify consequential interfaces. These may involve more than one package or discipline. The coordination record should explain what information each party needs and who produces it. A general note to maintain continuity is insufficient if the receiving teams do not understand their specific scope and connections.
Review the allocation against appointments and package documents with appropriate technical and commercial input. A spreadsheet should not silently assign responsibilities absent from the actual agreement. Where a gap exists, resolve it through the relevant process before the team relies on an assumed owner.
Provide information before the work depends on it
Link significant details and supplier inputs to the design and procurement programme. A trade cannot reliably price or plan an interface that remains undefined. Identify what must be stable before an order, fabrication release or installation activity. Distinguish provisional information from information authorised for a particular use through the project’s status conventions.
Where the team proceeds on an assumption, record its owner and verification route. The decision maker should understand the consequence if the assumption changes. Do not describe the whole package as complete while consequential details remain unresolved without a management plan. The receiving team needs a clear account of what it may rely on.
Coordinate the work sequence
Bring the relevant designers, package leads and delivery personnel together around the interfaces that need planning. The appropriate specialists should identify any inspection or access requirements. The programme should allow for the required activities before subsequent work conceals or restricts the relevant area. This is a coordination question to be resolved through competent technical advice, not an invitation to improvise a method.
Consider a hypothetical interface between an external package and a later services installation. The project needs to understand how the later work affects the earlier arrangement and what information or checks are required. The management task is to assign the question and preserve the agreed response across both packages, rather than assume one trade’s completion resolves every later interaction.
Make the requirement clear to suppliers
Translate accepted design requirements into the appropriate procurement information. Identify the evidence expected from suppliers and the route for reviewing alternatives. A product’s general description does not establish the suitability of the complete project arrangement. The relevant designers and specialists should assess the proposal against the actual scope and interfaces.
Where a substitution changes a material, detail or installation arrangement, obtain the appropriate consequence review before acceptance. The purchasing team should understand which requirements the original selection supported. Keeping that link visible helps prevent an apparently simple change from bypassing a consequential technical assessment.
Plan verification as a process
Ask the responsible specialists to define the checks and testing appropriate to the project, including timing and necessary preparation. Integrate them with the programme and identify who provides access, information and attendance. The purpose is to create a credible evidence route rather than book a late date without understanding what must be ready for the activity.
Clarify who performs the verification, who reviews the output and what establishes acceptance under the project’s arrangements. Administrative receipt of a report is not the same as a competent assessment of its meaning. Keep those roles distinct and identify how a question or limitation is referred to the relevant person.
Record findings and responses precisely
Use issue records that identify the relevant area, requirement and evidence. State what assessment or work is needed to close the question, with an owner and required date. A broad instruction to improve performance gives the team little basis for action or verification. The response should address the defined issue through the appropriate technical and site procedures.
If a change is made, identify connected work and information requiring review. The appropriate specialists should determine the verification needed after the response. Do not close an issue solely because an activity was completed. The project needs the evidence required by its actual acceptance process.
Keep design and installed records aligned
Capture consequential changes through the controlled information process. A final record should reflect the arrangement actually assessed and completed, with relevant limitations visible. Old details can remain in circulation if revisions are not communicated to the people relying on them. Assign responsibility for updating and distributing the information.
At handover, identify the accepted evidence set and outstanding matters. The client and operator should understand what has been demonstrated and what remains subject to action. A summary can be concise while preserving the context needed to interpret the evidence. Avoid a general statement that implies broader assurance than the defined review obtained.
Learn from the interfaces
After delivery, examine where coordination worked and where questions emerged late. Identify whether the cause concerned information timing, responsibility, procurement changes or the sequence of work. Use those findings to improve the next package or project. A longer checklist is not automatically the right response if the underlying problem was an unclear decision owner.
Successful airtightness delivery management connects a defined requirement with competent design, clear package responsibilities and planned verification. It gives the team a way to recognise and resolve interface questions while the relevant work is still accessible and the decisions can be made on an informed basis.
Review one complete interface before repetition
Where an early coordinated review is appropriate, ask the relevant specialists to select an interface that represents the questions likely to recur. Define what the review is intended to establish and the evidence needed. The exercise can test whether the design information, package responsibilities and planned records work together. It should not be presented as proof that every other location has identical conditions.
Record findings in terms the affected trades can act on. Identify the accepted detail, any information still required and the point before which it must be resolved. If the review reveals a scope gap, address it through the actual package and appointment arrangements rather than leaving a general note for site coordination.
Check later changes against the accepted basis. A revised product or service interface may create a new question even where the surrounding work remains the same. The responsible specialists should decide what further review is needed. Preserve that decision and update the relevant records so the initial review becomes a controlled reference, not an assumption that future coordination is unnecessary.
