How to Verify LOPO Test Reports and Certificate Scope

November 5, 2014

Article overview

Learn how to verify LOPO test reports and certificates by product, model, standard, test specimen, issuer, date, revision and project scope.

Historical archive: product availability, standards and event information may have changed. Contact LOPO for current specifications.

To verify LOPO test reports, begin with the exact product and project requirement rather than the document title or a certificate image. A report is useful only when its specimen, test method, date and scope match the product being considered. A management-system certificate answers a different question from a product test, and neither automatically approves a complete facade assembly.

This page first appeared in 2014 as an archive gallery showing terracotta panel reports, a clay tile report and management-system certificates. Those images preserve company history, but an archive image alone does not confirm that a document is current, complete or applicable to a present order. The checks below turn that old gallery into a practical document-review guide.

Identify What Kind of Document You Have

Start by classifying the file. Similar-looking covers can represent very different evidence. Record the full document name, issuer, report or certificate reference, issue date, revision and every page received. Then compare its stated purpose with the project specification.

Document type	Question it may answer	What it does not prove by itself
Product test report	How identified specimens performed under named test methods	Performance of every size, finish, production batch or fixing arrangement
System test report	How a defined assembly behaved in a stated configuration	Results for changed rails, brackets, anchors, joints, spans or substrates
Product certificate	Conformity within the scope, scheme and period shown	Approval outside that scope or proof that the document remains current
Management-system certificate	Certification of a named organization’s management system	Technical performance of a particular panel, tile or facade
Technical data sheet	Manufacturer information for an identified product range or item	Independent testing unless the supporting report is also supplied

Match the Document to the Exact Product

Check the manufacturer name, factory, product family, item or model reference, clay body, finish, profile, nominal dimensions and thickness. The proposed item should be traceable to the description in the report. A test for one terracotta panel does not automatically cover a solid tile, baguette, brick or special-shaped unit. Begin with the LOPO terracotta panel range, then record the actual model under review.

For a custom profile or finish, ask whether the existing evidence includes it, whether an engineering assessment is available, or whether additional testing is required. Do not infer coverage merely because two products are made from fired clay or share a brand name.

Read the Specimen and Test Configuration

The specimen section often determines whether a report is relevant. Review dimensions, orientation, supports, span, edge conditions, fixings, joints, substrate and conditioning. For a facade-system test, also check rails, brackets, anchors, cavity, insulation, membrane and any safety restraints that formed part of the tested build-up.

Compare the test configuration with current elevations, sections and fixing details. A result may remain useful as reference evidence while still requiring project engineering. The updated terracotta panel technical-data guide explains how to separate product properties from whole-system performance.

Confirm the Standard, Method and Jurisdiction

Record the complete standard designation and edition exactly as printed. Check what property the method assesses, how the result is reported and whether the project’s specification calls for the same method. Standards can be revised, replaced or supplemented, and different jurisdictions may request different evidence.

A pass statement has meaning only with its criterion and scope. Ask the project’s facade consultant, architect, code adviser or approving authority to determine whether the document satisfies local requirements. The manufacturer can provide product documents, but project acceptance belongs to the responsible design and approval team.

Verify Issuer, Date, Revision and Status

Confirm the laboratory or certification body named on the document and its role.
Check issue and expiry dates where shown, plus amendments, annexes and revision history.
Ask whether the file has been superseded, withdrawn or replaced.
Check that every referenced page, schedule and attachment is present.
Confirm that the legal manufacturer and manufacturing site match the offered product.
Request a current copy directly through the project enquiry, not from an undated image search.

The LOPO manufacturing overview identifies the company’s production context. Document review should still establish which named factory and product were within the test or certification scope.

Build a Traceable Project Submittal

A useful submittal connects the specification clause, offered item and supporting evidence. Include a product schedule, drawings, report index and a short compliance matrix stating which document answers each requirement. Mark gaps, qualifications and pending information rather than hiding them.

Identify the required property and acceptance route.
Select the exact proposed product using the LOPO product item listing or a project-specific schedule.
Map each requirement to a current report, certificate, declaration or calculation.
Compare tested and proposed configurations, including fixings and support conditions.
Record review comments, revisions and final approval status.

Common Warning Signs

Pause the review when the product name is vague, pages are missing, the specimen is unidentified, the standard edition is absent, a result is copied without its method, or a certificate image has no verifiable scope. Other warning signs include a factory name that differs from the supplier’s offer, a system result presented as a product property, and a historical document described as current without confirmation.

Archived LOPO Report Downloads

The files below are retained as historical reference copies from the original article. Their upload date, file name or presence on this page does not prove that they are current, complete or accepted for a new project. Before relying on any result, request a controlled copy and confirm the product code, dimensions, thickness, test method, issuing laboratory, report date and project jurisdiction.

Frequently Asked Questions

Does one LOPO panel test report cover every panel?

No. Coverage depends on the report’s product identification, specimen, dimensions, finish, configuration and stated scope. Variations should be reviewed rather than assumed.

Is a certificate scan enough for specification approval?

No. Review the complete, legible document, its schedules, issuer, dates, revision and status. Then confirm that its scope matches the product and project requirement.

Can a management-system certificate replace product testing?

No. It addresses the certified organization’s management system within its stated scope. It does not establish the technical performance of a selected terracotta unit or facade assembly.

Who decides whether a report is acceptable for a project?

The responsible project professionals and relevant approving authorities determine acceptance. The manufacturer supplies information and clarification, while the design team checks its relevance to the specification and installed system.

Request Documents for a Defined Selection

Use the LOPO project enquiry page to identify the application, product code, dimensions, finish, fixing concept, destination and required standards. Ask for the latest applicable documents and their status. That focused request is more reliable than treating an archived report image as universal proof.

Post Views: 856