Project requirement & evidence review
Window design pressure rating: read and submit requirements
Start with the required project pressure and opening data. Then review evidence for the exact casement-window configuration being considered.
For dealers, importers, design professionals and project owners preparing a reviewable requirement package. This page does not calculate project wind pressure or select a model.
Start with your role
One review path, three different inputs
Dealers establish the market and documentation scope; architects and consultants provide the technical schedule; owners share the project information already available.
Dealer / importer
Lead with the market, project type, package scope and documents the customer or authority expects.
See dealer inputs →Architect / window consultant
Provide the opening schedule, pressures, configuration notes and governing specification.
See consultant inputs →Project owner / consumer
Share drawings, location, available schedules and the design-team contact when known.
See owner inputs →Keep two questions separate
Required by the project is not the same as supported by evidence
The project team establishes the required pressure. A product review checks whether available evidence covers the proposed configuration and installation conditions.
What the building requires
- Project location and governing basis
- Opening-specific pressure and units
- Use, exposure and specification conditions
- Responsible design-professional information
match
What a configuration supports
- Documented size and operation
- Glass, hardware and combined units
- Positive and negative load scope
- Anchorage and substrate conditions
Illustrative example
Read the whole requirement line—not just one number
Keep the opening reference, positive and negative values, units, dimensions and governing note together.
Fictional values shown to explain field structure only. This is not an engineering calculation or an official report.
Regional handoff routes
Submit the terminology used by the project jurisdiction
Do not translate every market into one DP label. Preserve the authority, standard, edition and required expression named in the project documents.
United States
Send the governing code and edition, opening IDs, positive and negative pressures, units, dimensions, configuration and the requested approval or report route.
- Code and edition
- Opening pressure pair
- Size and configuration
- Local document request
Canada
Include the province or territory, applicable project standard and edition, required rating information, opening IDs, sizes, configurations and requested documents.
- Province or territory
- Project standard and edition
- Required rating expression
- Requested documents
Barbados, The Bahamas & Panama
Treat these as separate approval environments. Name the country, authority or code basis, engineer-issued pressures, opening schedule, impact requirement if specified and permit-document needs.
- Country and authority
- Engineer pressure schedule
- Impact requirement if specified
- Permit-document needs
Belgium, Germany, Denmark, UK & Romania
For Belgium, Germany, Denmark and Romania, provide the project specification, applicable national provisions, required pressure or class and Pa values where supplied. For the UK, also identify the project jurisdiction and required declaration or designated-standard route.
- Country and project specification
- National provisions
- Pressure or class
- Declaration route if required
Australia
Provide the project wind classification or engineer-issued pressures together with the AS 2047 document scope requested by the project.
- Project wind classification
- Engineer pressure schedule
- Opening configuration
- Requested AS 2047 scope
Israel & United Arab Emirates
For Israel, include the current mandatory standard or approved import route identified for the project. For the UAE, name the emirate, approving authority, governing standard and consultant-issued wind requirements.
- Country or emirate
- Approving authority
- Governing standard
- Consultant-issued requirements
These routes identify information to submit. The project authority and current project documents remain controlling.
Opening-level mapping
Attach every requirement to a real opening
A building-level note is not enough for configuration review. Give each opening an ID, location, size, operation and pressure pair.
Illustrative elevation only—not an engineering drawing.
Locate
Keep façade, level, zone and opening ID.
Record
Carry size, operation, positive and negative values with units.
Group
Group only openings with genuinely equal requirements and intended configurations.
Connect
Retain mullion and connection details for combined openings.
Casement-window context
Define the configuration before asking what evidence applies
Dimensions, operation, glass, combined units, hardware, anchorage and substrate set the scope of the review.
Category context only Frame width and height for the proposed opening.
Opening type, handing and sash arrangement.
Specified make-up and support conditions.
Mullions, connectors and adjoining frames.
Configuration relevant to the documented assembly.
Fixing method, spacing and edge conditions.
Base material and installation interface.
Report, approval or declaration requested by the project.
Use the category page for product-family exploration after the requirement and evidence scope are clear.
Submission checklists
Send what your role can verify
Better inputs reduce back-and-forth without shifting engineering responsibility to the buyer.
Dealer / importer
Lead with the market and commercial package scope.
- Project country, city and type
- Package scope and quantity range
- Governing basis stated by the project
- Requested approval or report package
- Opening schedule and target dates
Architect / consultant
Provide opening-level requirements and source references.
- Pressure schedule with signs and units
- Drawing references and revisions
- Sizes and configuration groups
- Glass, mullion and installation notes
- Required declarations or reports
Owner / consumer
Share the project information already available.
- Site location
- Drawings or window schedule
- Available wind or structural notes
- Photographs as context
- Architect or engineer contact
Evidence matching
Check scope, not just a document title
Evidence should be reviewed against the intended size, operation, pressure direction, glass, combined configuration and installation conditions.
| Requirement field | Evidence field | Review question |
|---|---|---|
| Size & operation | Documented configuration | Does it cover the same overall dimensions and operating type? |
| Positive & negative pressure | Stated load scope | Are both directions covered at the required values? |
| Combined opening | Mullion and connection scope | Does it cover the same combination and connectors? |
| Anchorage & substrate | Installation conditions | Is the documented fixing method aligned with the base material? |
| Project document route | Report, approval or declaration scope | Is the document type accepted by the project authority? |
Requirement review workflow
From project package to a focused evidence conversation
Submit the available inputs, align the project and configuration scope, review relevant evidence and document the next questions.
Receive
Collect the project requirements, opening schedule and market route.
Clarify
Confirm opening groups, signs, units and unstated conditions.
Match
Compare the intended configuration with the scope of relevant documents.
Respond
Document the next questions, evidence direction and commercial handoff.
The workflow does not replace project engineering approval or promise a fixed response time.
Frequently asked questions
Clarify the requirement before product selection
No. The useful rating is one that meets the project requirement for the intended configuration and conditions; a larger isolated number does not replace a scope match.
Not necessarily. Requirements can vary by opening location and project design, so retain the opening ID and stated values from the project schedule.
They represent opposite pressure directions. Where both are issued, keep both signs and values attached to the opening record.
No. Impact scope and pressure scope answer different questions; both must be checked when the project requires them.
No. Obtain the required project pressure from the responsible design professional or approving authority, then submit it for configuration-evidence review.
Send the available drawings, location, opening information and project contacts. Mark unknown fields clearly so the next information request is specific.
They follow different standards and regulatory routes. Preserve the project’s original terminology, standard, edition, units and authority instead of forcing a direct label conversion.
Ready to prepare the handoff?
Start with the project requirement—not a model guess
Send the available pressure requirements, opening schedule and intended casement configuration so the review can begin with the right scope.
