STRATA · BUILDING PRODUCTSIndustry website example · product names and images are illustrative
STRATABUILDING SYSTEMS

TECHNICAL REVIEW / DOCUMENTS

A document matters
when it matches the product.

Performance data, declarations and certificates are not interchangeable. The product, intended use, revision, market and responsibility boundary all need to line up.

S / 10

A PRACTICAL CHECK BEFORE SPECIFICATION

Do not start with a badge.
Start with the scope.

For each product, record the exact model, document revision, intended use and destination market. Then confirm which technical specification or local rule applies. A standard name on a page is not proof that a product complies.

European Commission / Construction Products Regulation overview ↗Reference only. Applicability and current requirements must be confirmed for the exact product and destination.Ask a technical document question ↗
01

Product identity

Model / series, revision and intended use

CHECK
02

Performance evidence

Declared characteristics and test scope for the selected item

CHECK
03

Market applicability

Destination, applicable regulation and current harmonised specification

CHECK
04

Project responsibility

Design, installation, inspection and approval roles

CHECK

MARKET REQUIREMENTS / NOT ONE GLOBAL CHECKLIST

Ask the same four questions
for each destination market.

01

Which product family?

Window, door, façade, glass, sanitary ware or fitting.

02

What is the intended use?

Building type, location, exposure and installation context.

03

Which evidence is current?

Model-specific report, declaration, test scope and revision.

04

Who confirms the installation?

Designer, supplier, installer and local authority responsibilities.

READY WHEN YOU ARE / DEMO 10

Have a schedule, a sketch
or just a first question?

Start with what you know. Add drawings or product lines when they are ready. A formal specification and price still need human review.

Prepare a project request ↗