Unitized Curtain Wall Handover Documents, Replacement Units, and Spare Parts
Why “Handover Included” Is Not Enough
A unitized curtain wall close-out package may be described as “handover included,” “as-built documents provided,” or “spares included.” These labels do not identify the actual files, records, items, custody, destination, review status, or future replacement fields.
A project-specific handover index should connect documents, records, assets, spare items, responsible parties, destinations, and status fields. Required content depends on project documents, contract, owner/operator information requirements, facilities process, and qualified professional review.
This guide addresses post-award close-out and replacement-scope clarification. It does not provide maintenance design, cleaning or repair instructions, access-system operation, warranty interpretation, legal acceptance, universal spare quantities, storage conditions, replacement lead times, or lifecycle-cost advice.
Direct Answer: What Should Handover and Replacement Scope State?
- document categories and content;
- file format, naming, revision, date, recipient, destination, and status;
- record/as-built drawings, model status, and panel schedules;
- product, material, finish, and maintenance information;
- inspection, test, release, receiving, nonconformance, corrective-action, and replacement records;
- replacement-unit identification and configuration fields;
- spare-part categories, basis, quantity field, packaging, storage, custodian, condition, and record link;
- damage, issue, re-delivery, unloading, lifting, reinstallation, adjustment, inspection, and register-update fields; and
- the project-assigned record holder and handover route.
Use Included, Optional, Excluded, Subject to Confirmation, and Open Question for quotation scope. Keep them separate from document/process states and asset/project states.
Status Taxonomy: Scope, Documents, and Assets
Quotation scope
IncludedOptionalExcludedSubject to ConfirmationOpen QuestionDocument / process
Submitted / ReturnedRevised / ReviewedRecord / Final recordHanded overAsset / spare / project
Factory Release / Site ReceivingInstalledSpare identified / storedReplacement requested / issuedRe-delivered / ReinstalledFinal AcceptanceAll statuses are project-defined tracking fields and must not be interchanged. Final record is not automatically Final Acceptance; Factory Release is not automatically Site Receiving; and Handed over is not automatically a warranty, compliance, or contractual conclusion.
Handover Document Index
A handover index is more useful than a single “documents included” line. Build one project-specific list that identifies each category, expected content, status, record holder, and destination.
| Handover category | Example content to list | Document / process status | Record holder / destination |
|---|---|---|---|
| Record/as-built drawings | Final drawings, details, schedules, revisions | Submitted / Reviewed / Record / Final record | Party and destination to assign |
| BIM/model record | Purpose, version, exchange format, record status | Project-defined model status and revision | Model record holder to assign |
| Panel schedules | Panel marks, locations, configurations, final references | Version, review, record status | Schedule holder to assign |
| Product/material information | Product data, finish and maintenance information, approved references | Submitted / Reviewed / Record | Document holder to assign |
| Inspection/test records | Reports, checklists, photos, factory/site records | Report-issued, reviewed, record route | QA/QC/document control to assign |
| Factory/site release records | Factory Release, Site Receiving, damage, condition | Project-defined process status | Responsible party to assign |
| Nonconformance/corrective records | NCR, response, corrective action, close-out reference | Open / Returned / Revised / Reviewed / Record | Responsible party to assign |
| Replacement records | Replacement unit, spare item, damage, re-delivery, reinstallation | Project-defined issue and record status | Record holder to assign |
| Maintenance information | Manuals, inspection information, contacts, limitations | Submitted / Reviewed / Handed over | Owner/operator destination |
| Document index | File name, revision, date, format, recipient, destination, status | Index version and issue status | Document controller to assign |
These are scope and record-control fields, not a universal requirement. Project documents should determine which categories apply and what each file must contain.
Record drawings, models, and schedules
Define what “record,” “as-built,” or “final record” means. Connect drawings and models to panel schedules, locations, configurations, revisions, interfaces, and documented changes. A file label alone does not determine whether it has been reviewed, accepted, or made contractually controlling.
Product, material, and maintenance information
The index may include product data, finish information, maintenance information, inspection notes, contacts, limitations, and document references. Maintenance information is a project-defined category only; this article does not turn it into cleaning, repair, access-system, or operating instructions.
Inspection, test, release, and corrective records
The index may link evidence, photos, checklists, factory-release records, site-receiving records, damage reports, nonconformance records, corrective actions, and replacement records. This identifies close-out evidence only; it does not reproduce testing procedures or QA/QC controls.
Replacement Unit and Spare Parts Register
Use one combined register with separate replacement-unit and spare-part columns. This avoids repeating identification, custody, condition, and record-linkage fields.
| Register field | Replacement unit | Spare part | Status / role field / open item |
|---|---|---|---|
| Identification | Panel mark, asset/tag, location, drawing/model reference | Part name, type, related system/panel | To be confirmed |
| Revision/configuration | Revision, system, dimensions, glass/infill, finish, hardware, interfaces | Product/reference revision and compatible basis | To be confirmed |
| Quantity/basis | Project-defined replacement basis | Project-defined spare basis; no universal quantity | To be confirmed |
| Packaging/storage | Protection, location, label, custodian | Protection, location, label, custodian | To be confirmed |
| Condition/inspection | Condition, inspection date, issue reference, review record | Condition, inventory review, inspection record | To be confirmed |
| Replacement/event | Request, review, issue, re-delivery, reinstallation, adjustment, inspection | Issue, delivery, installation/use, update record | To be confirmed |
| Responsibility | Supplier, carrier, installer, contractor, owner/operator | Custodian, issuer, record holder | Responsibility to assign |
| Record linkage | Panel, drawing, material, inspection, replacement, handover references | Product, panel, maintenance, replacement references | Open Question |
The register is a record-linkage and scope tool. It does not prescribe replacement quantities, delivery dates, storage periods, shelf life, compatibility, availability, or responsibility for future work.
Storage, Identification, and Condition Records
Request information fields rather than giving generic storage or maintenance instructions. The project may need to define:
These are information fields, not universal storage conditions. Do not state temperature, humidity, duration, shelf life, or future usability without project-specific documentation and appropriate professional review.
Damage, Breakage, Replacement, Re-Delivery, and Reinstallation Records
Separate the event record from the work allocation. A close-out or replacement record may identify:
- Event: damage, breakage, shortage, nonconformance, or replacement request.
- Affected item: panel/part, location, configuration, revision, glass/infill, finish, hardware, related records.
- Condition and custody: packaging, transport, receiving, storage, identification, condition.
- Replacement action: request, issue, fabrication or sourcing reference, re-delivery, receiving, register update.
- Site action: unloading, lifting, access, reinstallation, adjustment, inspection, record update.
- Status: Replacement requested, issued, re-delivered, reinstalled, or another defined status.
- Unresolved effects: cost, programme, logistics, installation, testing, maintenance, warranty, and documentation marked To be confirmed.
Record-Holder Responsibility Matrix
Use a project-defined matrix to identify who provides, checks, receives, updates, stores, or controls each close-out record. These fields describe assigned roles; they do not decide legal responsibility or universal ownership.
| Record/activity | Supplier/factory | Carrier/logistics | Installer | Main contractor/project team | QA/QC/document control | Owner/operator/record holder | Status / role / open item |
|---|---|---|---|---|---|---|---|
| Product/factory records | Provide if included | — | — | Coordinate as assigned | Index/review | Receive/store | To be confirmed |
| Inspection/test evidence | Provide if included | Delivery/damage records | Site records | Coordinate review | Compile/index/review | Receive/store | To be confirmed |
| Record/as-built/model files | Prepare/provide if included | — | Provide installation changes | Coordinate final package | Check/index | Receive/retain | To be confirmed |
| Replacement/spare register | Provide item data | Update transport/damage | Update installation/replacement | Coordinate register | Review/update controls | Custody/asset record | To be confirmed |
| Storage/identification | Package/label if included | Protect in transport | Store/handle if assigned | Provide site/storage conditions | Record condition | Custodian to assign | Responsibility to assign |
| Re-delivery/reinstallation | Provide replacement/support | Transport/handling | Lift/install/adjust | Access and coordination | Inspect/record | Update asset records | Responsibility to assign |
| Handover index/close-out | Provide included documents | Provide delivery records | Provide site records | Coordinate submission | Control/index/review | Receive/retain/review | Open Question |
Handover Evidence Checklist
- Is a project-specific handover document index defined?
- Are record/as-built drawings, model/BIM status, panel schedules, and revisions listed?
- Are product/material data, maintenance information, inspection/test evidence, and release/receiving records listed?
- Are nonconformance/corrective-action and replacement records included where required?
- Are formats, filenames, revisions, dates, recipients, destinations, and review statuses defined?
- Are spare panels, gaskets, sealants, hardware, covers, anchors, accessories, or finish items assigned one of the five scope labels?
- Does the replacement register link panel mark to revision, configuration, glass/infill, finish, hardware, and interfaces?
- Are storage location, label, custodian, condition, and inventory fields defined?
- Are damage, replacement, re-delivery, reinstallation, adjustment, and reinspection records assigned?
- Is the record holder named for each document, register, and update route?
- Are unresolved cost, programme, logistics, installation, testing, maintenance, warranty, and documentation effects To be confirmed?
- Are document, process, asset/spare, and acceptance statuses kept separate?
Clarification Questions Before Handover
- What document categories and formats are required in the handover index?
- Which drawings, models, schedules, and revisions are Record or Final record?
- Are product/material data, maintenance information, inspection/test, release/receiving, and nonconformance records included?
- Are replacement-unit and spare-parts registers required, and what basis applies?
- Which spare items use each quotation scope label?
- Which fields identify a replacement unit?
- Who stores, labels, inventories, inspects, and updates spare/replacement records?
- What packaging/protection and condition records are required?
- Who coordinates re-delivery, unloading, lifting, access, reinstallation, adjustment, inspection, and updates?
- Which factory/site/test records are required?
- Who is the record holder and destination for each category?
- Which unresolved effects remain To be confirmed?
FAQ: Handover Documents, Replacements, and Spares
What handover documents should a unitized curtain wall supplier provide?
The project-defined index may include record/as-built drawings, model status, panel schedules, product/material and maintenance information, inspection/test evidence, release/receiving records, corrective records, replacement/spare registers, contacts, and metadata.
Are as-built drawings and BIM/model records automatically included?
Not automatically. Assign one of the five scope labels and define format, revision, status, recipient, destination, review route, and record holder.
What should a curtain wall replacement-unit register contain?
It may link panel mark or asset ID to location, revision, configuration, dimensions, glass/infill, finish, hardware, interfaces, condition, storage, request, delivery, reinstallation, inspection, and record updates.
Are spare panels, gaskets, sealants, and hardware included?
Do not assume inclusion. List each item and classify it, then confirm project-defined quantity/basis, packaging, identification, storage, custodian, condition, and record link.
Who stores and identifies unitized curtain wall spare parts?
The responsibility matrix should identify the custodian, label/inventory owner, condition-record owner, and document/asset record holder.
Who handles re-delivery and reinstallation of a replacement panel?
Separately identify transport, unloading, lifting, access, installation, adjustment, inspection, records, and register updates. Re-delivery alone does not automatically include those activities.
Does a record drawing or handover certificate prove final acceptance?
No automatic conclusion should be drawn. Record and handover statuses are project-defined fields. Acceptance, compliance, performance, warranty, or contract effects require applicable documents and authorized review.
What maintenance information should be handed over?
Request project-defined manuals, product and finish information, inspection information, contacts, limitations, and references required by the owner/operator. This guide does not provide cleaning, repair, access-system, or operating instructions.
Conclusion and Project-Specific CTA
A unitized curtain wall handover package should be treated as an indexed set of project records and close-out responsibilities rather than a single label.
- Build the index. List drawings, model status, schedules, product/material data, evidence, release/receiving, corrective and maintenance records.
- Define the registers. Link replacement units and spares to configuration, revision, identification, storage, custody, condition, and records.
- Separate statuses. Keep document/process, asset/spare, quotation scope, and acceptance status in separate fields.
- Assign record holders. Name who provides, checks, receives, stores, updates, indexes, and hands over each category.
- Record replacement activities. Separate re-delivery, unloading, lifting, access, reinstallation, adjustment, inspection, and record updates.
- Obtain project-specific review. Route maintenance, facilities, contract, warranty, insurance, design, QA/QC, logistics, installation, and acceptance matters to qualified professionals.
Share the handover requirements, document register, record/as-built expectations, panel schedules, replacement/spare basis, storage and identification fields, re-delivery/reinstallation boundary, and responsibility matrix for a project-specific close-out review.
FOWALL’s public pages describe categories such as material verification, inspection, testing, labeling, packaging/protection, document requests, engineering, manufacturing, delivery, and quality-control coordination. Any service availability, scope, fee, technical responsibility, document format, maintenance information, replacement activity, or deliverable must be confirmed for the specific project. This article does not provide maintenance design, repair instructions, warranty, insurance, legal acceptance, performance, price, delivery, or supplier-capability conclusions.
