---
title: "How to Read Window & Door Test Reports"
description: "Connect a document to the product, specimen and configuration you are actually considering."
slug: "resources/how-to-read-window-door-test-reports"
noindex: false
---

How to Read Window & Door Test Reports

Connect a document to the product, specimen and configuration you are actually considering.

Custom aluminum windows and doors for trade and project procurement. We also accept personal custom aluminum window orders.

For importers, distributors, contractors, project buyers and homeowners planning custom aluminum windows.

## Begin with document identity

Record the title, reference number, named company and document date. Identify whether the file is a test report, certification record, conformity document or a label. These records answer different questions; a cover image alone does not establish all of the conditions in the full document.

## Build a product-to-document checklist

| Check | Question to ask |
| --- | --- |
| Product identity | Which system and opening type are named? |
| Specimen size | What width and height were tested or listed? |
| Configuration | Which glazing, panel arrangement and hardware are described? |
| Test or certification scope | What requirements and results are actually included? |
| Document completeness | Are the schedule, result pages, limitations and attachments included? |
| Your proposed order | Which details match, and which changes need review? |
| Current project use | What confirmation does the project designer or reviewer require? |

## Examples from our document collection

| Website document ID | Public preview | Useful starting point |
| --- | --- | --- |
| RD02 | CSA certificate preview — 80 Series Windows / 128 Series Sliding Door | Request the original holder details, system entries and listed conditions. |
| RD30 | 80 Series Bifold Door — AAMA test preview | Compare the full specimen description with the proposed order. |
| RD23 | AS80 Sliding Door — AS 2047 test preview | Review the tested configuration and result pages. |

## Keep model names distinct

A similar number in a catalogue and a report is a starting point for a question, not proof that the systems are identical. Send both the catalogue product ID and the document reference. Ask the factory to explain the correspondence and any differences in the proposed configuration before using the document in a project submission.

## Ask for a targeted review

Please review catalogue product [ID], opening [ID and dimensions], glazing [details] and project requirements [list] against document [reference]. Identify matching conditions, differences needing review and the full pages required for our project team.

[Browse the redacted document previews](/technical-documents/)

[Compare quotations with the same evidence scope](/resources/compare-window-door-quotes/)

## Is a label the same as a complete report?

No. Ask for the underlying record and relevant schedules or result pages. Keep the label as an identifier rather than a substitute for the full scope.

## Can I apply a report to a different size or glazing choice?

Ask the factory and project reviewer to assess the change against the document scope. Do not assume that a result transfers unchanged to another configuration.

## Does the date on this site confirm current certification status?

A preview does not establish current certification status. Request the complete original record and any current confirmation needed for your project.