Aluminium Window Handover Documents: Testing, Cleaning, Maintenance and Warranty Records

A window package rarely fails because someone forgot how to fit a frame. It fails, or is alleged to have failed, because nobody can prove what was installed, what was tested, how it was cleaned, and who agreed to what. The handover pack is the only artefact that answers those questions after the site sheds are removed and the project team disperses. It is a technical document set, not an administrative afterthought, and it deserves to be assembled while the work is still visible rather than reconstructed from memory once the occupants have moved in.

This article sets out what a defensible handover pack for an aluminium window and glazed door package should contain, how test evidence should be recorded, why as-built drawings, cleaning instructions, drainage maps, hardware schedules and glazing records belong together, how maintenance intervals are set by the project rather than by a generic table, and how warranty boundaries can be stated clearly without inventing terms, periods or performance figures that no party has agreed to. It deliberately avoids dimensions, costs, durations, acoustic and thermal values, and any claim of certification, because those are properties of a specific tested system and a specific contract, not of a general guide.

What a Handover Pack Is and What It Is Not

A handover pack is the collected evidence that the installed envelope matches the documented design and that the people who will live with it know how to look after it. It is written for two audiences at once. The first is technical: the builder, the certifier, the facility manager and any future repairer who needs to identify a profile, a glass make-up or a drainage path. The second is the occupier, who needs plain instructions for cleaning and for recognising a problem early.

It is not a sales folder. A pack built from product brochures, generic maintenance sheets and supplier logos will not survive scrutiny, because it says nothing about this building. The distinction is simple: a brochure describes what a product can do, and a handover document records what was actually installed at this address, on this elevation, in this opening, by this contractor, on this date.

The Documents That Usually Travel Together

A drawing register with as-built elevations and opening schedules cross-referenced to identifiable marks.
Test evidence, both from the manufacturing or assembly process and from any site testing that the project required.
Glazing records identifying glass type, make-up, thickness family and safety glazing locations.
Hardware schedules listing each operable item, its function, its adjustment points and its keying arrangement.
Cleaning instructions separated by substrate: glass, coated aluminium, gaskets, seals, drainage components and hardware finishes.
Drainage and weep path information showing how water leaves each opening and where the outlets are located.
Maintenance requirements expressed as tasks with triggers, not as vague encouragement.
Warranty documents and a boundary statement that explains what is covered, what is excluded and who to contact.
Operating instructions for openable windows, sliding doors, screens and any restrictor or safety device.
A contact schedule for the manufacturer, the installer, the glazier and the hardware supplier, with the route for a claim.

Why the Pack Is Assembled Before Completion, Not After

Almost every document in the list depends on information that exists only during construction. The elevation mark painted on a frame before delivery, the batch identification on a glass unit, the torque setting recorded during adjustment, the position of a weep slot before a sill trim is fitted, the photograph of a drainage chamber before the architrave closes it in: none of these can be recovered later without destructive investigation. A pack assembled in the final week is therefore a pack assembled from photographs and memory. A pack assembled progressively, with a nominated person holding the register, is evidence.

Test Evidence: Proving the Assembly Performed

Test evidence is the part of the pack most often requested and least often understood. Two different kinds of testing are routinely conflated, and the confusion causes problems at the worst possible time.

Evidence From the Product and Assembly Process

The first kind is evidence generated by the manufacturer or assembler: the performance testing regime applied to the window system, the quality control records for the batch, the inspection of frames and sashes before dispatch, and the records for any factory-assembled glazing. This evidence establishes that the system belongs to a family that has been evaluated against the relevant standard, in this country, under the conditions that the standard specifies. It does not establish that the units on this building were made correctly, and it does not establish that they were installed correctly. It is a starting point, and it should be presented as such, with the tested configuration clearly matched to the supplied configuration.

That matching exercise is where packs commonly fall short. A system may have been evaluated in one configuration and supplied in another: different opening size, different mullion arrangement, different glass make-up, different hardware, a coupling detail that was not part of the tested specimen. Where the supplied configuration departs from the evaluated one, the departure should be identified and its treatment documented, rather than left for a reader to discover by comparison.

Evidence From Site Observation and Site Testing

The second kind is evidence generated on the building: installation inspections at defined hold points, records of any water testing carried out on installed assemblies, and the observations that accompany them. Site testing of installed windows and facade areas is governed in Australia by the facade testing framework in AS 4284, which sets out how test chambers, spray arrangements and pressure stages are applied to a portion of a building rather than to a laboratory specimen. Where a project specifies site testing, the record should identify the area tested, the sequence applied, the duration of each stage, the observations made, and the location and nature of any leakage.

Where a project does not specify site testing, that decision should also be recorded. An absence of test results is not the same as an absence of testing requirement, and a pack that simply omits the subject invites the assumption that something was hidden. A short statement confirming that installation quality was verified by inspection at nominated hold points, with the inspection records attached, is more persuasive than a gap.

Recording Results Without Overstating Them

Test records should describe what happened, not what was hoped for. A useful record contains the date, the assembly or area tested, the method applied, the standard or project specification that defined the method, the instrument used, the observations, the outcome, and the corrective action where an observation required one. Photographs should be dated and located. Any re-test should be recorded as a separate event with its own result, not merged into a clean summary.

What a test record should never contain is a performance figure that was not measured. A window that passed a site water test has demonstrated that it resisted that test under those conditions on that day. It has not thereby been assigned a numerical water penetration resistance, an acoustic rating or a thermal value. Those characteristics belong to the evaluated system and to the project specification, and they are documented by the parties who are competent and accountable for them.

As-Built Drawings and Elevation Schedules

As-built drawings are the spine of the pack. Every other document refers back to them, and if they are wrong, everything downstream is unanchored.

What As-Built Drawings Must Reflect

An as-built set for a window package should show each elevation with every opening identified by a unique mark, the configuration of each opening, the direction of operation, the glazing type by reference to the glazing schedule, the hardware type by reference to the hardware schedule, the position of drainage outlets, and the interface conditions at head, jamb and sill. Where the installed condition differs from the documented design, the drawing should show the installed condition, with the variation noted.

The opening schedule is the working index. It should list, for each mark, the level, the room or facade zone, the configuration, the glass reference, the hardware reference, the finish, and the relevant test or inspection record. A schedule that is complete but not cross-referenced is a list; a schedule that is cross-referenced is a retrieval system, and retrieval is the whole point.

Marking Up and Controlling the Set

Marking up should be treated as a controlled activity rather than an informal one. The person who marks up should be the person who can read the installation, and the mark-up should carry a date, a revision and a name. Superseded sheets should be removed from the issued set rather than left in circulation, because a pack containing two versions of the same elevation is worse than a pack containing one imperfect version, since the reader cannot tell which is authoritative.

Frames and glass should be marked in a way that corresponds to the schedule and survives construction. A mark applied with a marker that fades in sunlight, or a label removed during protective film stripping, breaks the link between the physical element and the record. The marking method should be agreed at the start of the project, together with the point at which marks are removed, if they are removed at all.

Cleaning Instructions: The First Clean Decides the Next Decade

Cleaning instructions are the most-read and least-considered part of a handover pack. They are also the part most likely to be followed incorrectly, because the occupier receives them at the moment of maximum distraction and applies them with whatever is already under the sink.

Glass and Coated Surfaces

Instructions for glass should identify the glass by type where the care differs, and should distinguish between the interior and exterior faces. Coated glass, laminated glass with exposed edges, and glass with applied films or markings each carry their own constraints, and the instruction should state them rather than assume the reader knows. The general principles are consistent: use a clean, non-abrasive method, avoid abrasive pads and powders, avoid contact with the frame sealant with aggressive solvents, and remove construction contamination before it cures rather than after.

The most important instruction concerns timing. Material that is allowed to sit on glass through a hot period can bond or etch, and no cleaning method will then restore the surface. The handover should state plainly that contamination is removed promptly, and that the first clean after construction is a deliberate operation carried out with the appropriate method, not a quick wipe at the end of the day.

Frames, Gaskets, Seals and Drainage Components

Aluminium frames carry a surface finish that is durable but not indestructible. Instructions should identify the finish family and the cleaning approach appropriate to it, note that acidic and alkaline products can attack the finish and the seals, and require that residue is rinsed rather than left to dry. Gaskets and seals should be cleaned without the use of petroleum-based products that swell or harden the material.

Drainage components deserve their own paragraph in the instructions, because they are the components an occupier is most likely to block while cleaning. Weep slots, drainage chambers, sill outlets and any concealed path should be identified as items that must remain clear, and the instruction should say what to do if an outlet appears obstructed rather than inviting improvisation with a sharp tool.

Practices That Cause Damage

Pressure washing directed at gaskets, seals or drainage openings.
Abrasive pads, scrapers and blades used on glass or coated aluminium.
Strong solvents, acids or alkaline cleaners left to dwell on finishes and seals.
Cleaning in direct sun on a hot surface, so that residue dries before rinsing.
Removal of protective film after it has been baked on by exposure.
Using the frame or the sash as a support for ladders, scaffolds or hoses.
Blocking a weep path with sealant, paint or a decorative trim.

Drainage and Weep Maps

A drainage map is a simple idea that is rarely documented. It shows, for each opening type, where water enters the frame system, how it travels, where it collects, and where it leaves. It is not a plumbing drawing. Its purpose is to make the water path legible to a person who will never see inside the frame.

Reading the Map

A useful map identifies the openings that drain, the direction of fall within the frame, the location of weep slots or outlets relative to the sill, the position of any baffle or deflector, and the interface with the sill flashing or the wall drainage cavity. It should distinguish between primary drainage and any secondary or back-up path, and it should note where a path is concealed behind a trim or within a wall build-up, because those are the points where a later alteration can silently disable the system.

The map should also state the maintenance implication directly. If an outlet can be reached and cleared from the exterior, the instruction says so. If clearing requires removal of a bead, a cover or a trim, the instruction says that too, together with the requirement to reinstate the component correctly. An occupier who understands that a weep path exists is far less likely to seal it up while chasing a draught.

Handing the Path Over to the Occupier

The handover conversation should include a physical walk to at least one opening of each type, with the map in hand. Pointing at a slot and explaining what it does takes a few minutes and prevents a category of callbacks that no warranty document can resolve, because the cause is a modification made by the occupant after completion. Where the project includes balconies, screens or added enclosures, the conversation should extend to those, since they frequently alter the drainage of the openings behind them.

Hardware Schedules and Keying Records

Hardware is where a window package becomes an operating system. It is also where the handover pack most often loses precision, because the schedule is written from a catalogue rather than from the installed set.

What the Schedule Should Identify

For each opening, the schedule should identify the hardware family and the function: casement winder, friction stay, sliding roller and track set, multipoint lock, flush bolt, handle, restrictor, screen latch, closer, or any other operable component. It should record the finish, the adjustment points that the occupier or the maintenance contractor may need to touch, and the identification of any component that is safety related, such as a restrictor intended to limit opening travel.

Where an opening has been configured for a specific use, such as an egress path or a ventilation position, the schedule should record that configuration and the operating instruction that accompanies it. A restrictor that is released for cleaning and not reinstated is a safety issue, and the only defence is an instruction that says clearly that it must be reinstated.

Keys, Access and Operating Instructions

Keying records should state how many keys were issued, to whom, and which openings each key operates, without reproducing key cutting information in an uncontrolled document. Master keying arrangements, if any, should be described in terms of hierarchy rather than by listing cuts. The record should identify the party responsible for replacement keys after handover.

Operating instructions should be written for the person who has never operated a European-style tilt-and-turn or a lift-slide door. They should describe the sequence of handle positions, the correct way to move a large sash, the reason a sash should not be forced, and what to do if an opening becomes difficult to operate. Instructions that consist of a pictogram with no text are common and are usually ignored.

Glazing Records

Glazing records connect the visible glass to the documentation that governs it. They matter for replacement, for safety, for insurance and for any later dispute about what was supplied.

Identification and Traceability

For each opening or glass mark, the record should identify the glass type and make-up by reference to the glazing schedule, the supplier, the batch or unit identification where available, and the date of installation. Where insulating glass units are used, the unit identification should be recorded before the unit is installed, because the marking is often on an edge that becomes concealed.

Safety Glazing and Insulating Glass Units

Safety glazing locations should be identified explicitly, with the basis for the selection recorded by reference to AS 1288 and AS 2208, and with the marking on the glass confirmed where the standard requires one. The purpose of the record is not to restate the standard but to demonstrate that the selection was made deliberately and that the installed product matches it.

Insulating glass units bring their own documentation needs. AS 4666 covers insulating glass units, including the requirements that apply to their manufacture and their marking. The handover record should identify the unit type, the configuration, the spacer system where relevant to maintenance, and the edge seal protection expectations, since the durability of a unit depends heavily on how its edges are treated during and after installation. Any unit replaced during construction should be recorded as a replacement, with the reason noted, rather than absorbed silently into the schedule.

Maintenance Intervals as Project-Specific Commitments

A handover pack that promises fixed maintenance intervals is making a commitment the author usually cannot keep. The correct approach is to define the tasks, define the triggers, and let the project set the frequency in the light of its own conditions.

Why No Universal Interval Exists

Three project variables dominate. The first is environment: a coastal facade exposed to salt spray, a city site exposed to traffic film, an inland site with wind-borne dust and a rural site with agricultural residue each load the surfaces and the hardware differently. The second is use: a fixed window in a stairwell and a sliding door used many times a day by a large household are not equivalent maintenance items. The third is exposure of the detail: a sill that collects debris, a recessed track, a north-facing elevation, and a roof-level opening all demand attention at different points.

Because these variables cannot be generalised, a responsible pack states that intervals are nominated for the project, records what was nominated, and explains the reasoning in terms of environment and use. Where the pack is being prepared before the maintenance plan is finalised, it should say so and identify who will issue the plan, rather than filling the gap with a number that will later be quoted back as a promise.

Turning Intervals Into a Workable Schedule

A workable schedule lists tasks in the order a maintenance contractor would actually perform them, groups them by access requirement so that scaffolding or elevated work is not mobilised repeatedly for trivial items, and distinguishes between occupier tasks and specialist tasks. Cleaning of glass and tracks is normally an occupier or general-cleaning task. Adjustment of hardware, replacement of gaskets, inspection of seals and verification of drainage are normally specialist tasks.

Each task should have a defined acceptance condition, so that the person performing it knows when it is complete. An instruction to inspect sealant is not a task; an instruction to inspect sealant at nominated junctions for adhesion loss, cracking or separation from the substrate, and to record the result, is a task. The same discipline applies to hardware: check operation, check fasteners, check adjustment, check that safety devices are present and functioning, record the result.

Glass and coated surfaces: clean by the nominated method, inspect for contamination, scratches and edge damage.
Frames and drainage: clear weep slots and outlets, confirm water can leave, inspect for standing water or staining.
Gaskets and seals: inspect for shrinkage, hardening, displacement and adhesion loss at junctions.
Hardware: operate each item through its full travel, check fasteners, confirm restrictors and safety devices.
Sliding tracks and rollers: clear debris, check alignment and travel, confirm the sash does not bind.
Glazing: confirm unit identification remains legible in the record, inspect for condensation within units, edge seal damage or glass damage.
Records: update the maintenance log with date, task, finding and action.

Warranty Boundaries Without Invented Terms

The warranty section is where a handover pack most often overreaches. Statements such as a blanket guarantee of performance, a period that no contract contains, or a coverage that the supplier has not offered are worse than no statement at all, because they create an expectation that will fail at the first claim.

The Boundary Statement

A defensible warranty section does four things. It identifies the parties giving the warranty and the parties receiving it. It identifies the documents that constitute the warranty, by reference to the contract and the supplier documentation. It states the process for making a claim, including the contact route and the information the claimant should provide. And it states the boundaries: what is covered, what is excluded, and what the claimant must do to keep the coverage alive.

Where a warranty period applies, it should be quoted from the document that establishes it, with the document referenced, rather than restated in the pack’s own words. Where different components carry different arrangements, the pack should present them separately instead of compressing them into a single headline period. Windows are assemblies of frame, glass, hardware, seals and finish, and those components rarely come from a single source or carry identical terms.

Exclusions and the Language of Fairness

Exclusions should be written so that an occupier can understand them and a repairer can apply them. Common and legitimate exclusions include damage caused by cleaning methods contrary to the instructions, modification or alteration by others, blockage of drainage by debris or applied finishes, glass breakage after handover, normal wear of moving components, and damage from construction activity adjacent to the windows. Each exclusion should be tied to an instruction elsewhere in the pack, so that the reader can see the obligation and the consequence together.

An exclusion that is not linked to an instruction is simply a defence. An exclusion that is linked to a clear instruction is a fair boundary, and it is far more likely to be accepted by an occupant who has been told what to do.

Statutory, Contractual and Builder Obligations

The handover pack sits within a wider framework of obligations that it cannot replace. Statutory warranties, contractual defect liability arrangements, building certification requirements and insurance obligations each operate independently of the manufacturer’s product warranty, and the pack should make that clear rather than implying that the product warranty is the only remedy available. The pack should identify who to contact first, and it should avoid language that discourages an occupier from raising a legitimate issue through the correct channel.

The Regulatory and Standards Framework

References should be used to explain the basis of a requirement, not to decorate a document. In Australia, the National Construction Code, maintained by the Australian Building Codes Board, establishes the performance requirements for building work, and the ABCB publishes the referenced documents and housing provisions that support compliance. The NCC is amended over time, so a pack should record the edition that applied to the project rather than referring to the code generically.

Australian Standards Relevant to Window Handover

AS 2047, Windows and external glazed doors in buildings, which underpins the performance framework for window products and their installation.
AS 4284, Testing of building facades, which provides the framework for facade testing including site testing of installed assemblies.
AS 1288, Glass in buildings – Selection and installation, which governs glass selection and installation, including human impact considerations.
AS 2208, Safety glazing materials in buildings, which supports the identification and marking of safety glazing.
AS 4666, Insulating glass units, which addresses the manufacture and identification of insulating glass units.

These documents should be cited by their current edition and title, and the pack should state which edition the project used. A citation without an edition is ambiguous, and ambiguity in a handover document invites a later argument about which requirements applied.

New Zealand References

For projects in New Zealand, the Building Code and its Acceptable Solutions provide the regulatory setting, with Clause E2 External moisture and E2/AS1 addressing weathertightness, and Clause B2 Durability addressing the durability of building elements. NZS 3604 provides the timber-framed construction framework within which many residential window installations sit, NZS 4223 addresses glazing in buildings, and SNZ TS 4211:2022 addresses window and door performance. A New Zealand pack should reference the applicable documents for the project rather than importing Australian citations, and should record the consent and inspection records that accompany the installation.

A Handover Checklist for the Project Team

The following sequence keeps the pack coherent without turning it into a bureaucratic exercise.

Nominate the person who owns the handover register, and record the nomination in the project documentation.
Agree the opening marks, the glazing schedule references and the hardware references before fabrication.
Collect test evidence as it is generated, and match each tested configuration to the supplied configuration.
Record installation inspections at hold points, with dated and located photographs.
Complete the as-built elevations and the opening schedule, cross-referenced to test and inspection records.
Prepare cleaning instructions by substrate, and include the drainage and weep map as a separate item.
Compile the hardware schedule from the installed set, including restrictors and safety devices.
Record glazing identification before units are concealed, including any replacement units.
Set maintenance tasks and triggers for the project, and identify who will issue the final intervals.
Assemble warranty documents and write the boundary statement from those documents, not from memory.
Walk the building with the occupier, using the pack, and record that the walk occurred.

Frequently Asked Questions

Who should prepare the handover pack?

The party responsible for the window package normally compiles the technical content, but the obligation to deliver a complete pack belongs to the head contractor under the contract. The practical answer is that one nominated person holds the register, receives documents from the manufacturer, the glazier, the hardware supplier and the installer, and checks that each item is present and cross-referenced before completion.

Is site water testing always required?

No. Site testing is specified by the project, and its extent depends on the building type, the facade system and the requirements of the specifier or certifier. What is always required is a record of how installation quality was verified, whether by testing, by inspection at hold points, or by both.

Can the handover pack be issued after practical completion?

It can be completed afterwards, but it cannot be compiled afterwards without loss. Marks are removed, cavities are closed, units are concealed and personnel move on. Progressive collection is the only reliable method, and the pack should be treated as a deliverable with its own milestones rather than as a final administrative task.

How long should maintenance intervals be?

Intervals are project-specific. They depend on the environment, the intensity of use and the exposure of the detail, and they should be nominated for the project and recorded in the pack. A pack that states generic intervals is making a commitment that may not suit the building and may later be quoted as a promise.

What should a warranty section say about performance?

It should describe the coverage that the warranty documents actually provide, identify the parties and the claim process, and state the exclusions. It should not assign performance values, ratings or periods that are not established by those documents, because a handover pack cannot create a warranty that no party has given.

What is the most common weakness in a window handover pack?

The missing link between documents. A pack may contain a complete drawing set, a complete glazing schedule and a complete test report, yet fail because no document connects a specific opening to a specific glass make-up, a specific hardware set and a specific inspection record. Cross-referencing is the work that turns a collection of files into evidence.

Conclusion

A window package is handed over twice. The first handover is physical: the keys, the operation, the cleaning, the walk around the building. The second is documentary, and it is the one that determines how the package is judged years later, when a leak appears, a unit fogs, a door drops, or an occupier asks who is responsible.

The documents described here are not elaborate. A drawing set that shows what was built, test evidence that records what was measured, a glazing record that identifies what is in each opening, a hardware schedule that explains how each item works, cleaning instructions that reflect the actual materials, a drainage map that makes the water path visible, maintenance tasks with nominated triggers, and a warranty boundary statement drawn from the documents that create the warranties: together these form a pack that answers the questions a building will eventually ask.

None of it requires invented figures. The strength of a handover pack lies in precision about what is known and honesty about what is not. Where a value belongs to the project, the pack points to the project document. Where a period belongs to a supplier, the pack points to the supplier document. Where a decision was made, the pack records the decision and the reasoning. That discipline is what makes the pack useful to a maintenance contractor, defensible to a certifier, and comprehensible to the person who will live behind the windows for the next several decades.

References

Australian Building Codes Board. National Construction Code 2025, Volume One and Volume Two, including the ABCB Housing Provisions. https://ncc.abcb.gov.au
Standards Australia. AS 2047, Windows and external glazed doors in buildings. https://www.standards.org.au
Standards Australia. AS 4284, Testing of building facades. https://www.standards.org.au
Standards Australia. AS 1288, Glass in buildings – Selection and installation. https://www.standards.org.au
Standards Australia. AS 2208, Safety glazing materials in buildings. https://www.standards.org.au
Standards Australia. AS 4666, Insulating glass units. https://www.standards.org.au
Standards New Zealand. NZS 3604, Timber-framed buildings. https://www.standards.govt.nz
Standards New Zealand. NZS 4223, Glazing in buildings. https://www.standards.govt.nz
Standards New Zealand. SNZ TS 4211:2022, Windows and doors performance. https://www.standards.govt.nz
Ministry of Business, Innovation and Employment. New Zealand Building Code, Clause E2 External moisture and E2/AS1, and Clause B2 Durability. https://www.building.govt.nz

Aluminium Window Handover Documents: Testing, Cleaning, Maintenance and Warranty Records