ISO certificates, fire-related reports, EPDs, REACH information and PFAS screening documents are often grouped together as if they answered the same question. They do not. Each document has its own purpose, issuer, method, sample boundary and use condition.
For fiberglass facer buyers, the safest review is to compare documents by scope before using them in purchasing, technical or customer communication. GRECHO can help organize document requests, but no document should be treated as proof that all products, all samples or all finished boards carry the same result.
Answer first
- Identify what each document is meant to prove before comparing results.
- Check sample, product, method, date, issuer and report boundary.
- Do not extend one certificate or report to all products or finished board systems.
- Use the Resource Center and contact form to request documents by route and review stage.
Key facts
- ISO certificates often describe management-system scope, not every product property.
- Fire-related reports depend on sample construction, method and classification boundary.
- EPD, REACH and PFAS documents have different evidence purposes and should not be merged into one claim.
- Document requests should be matched to the selected product route and buyer decision stage.
Start with the decision you need to make
A document is useful only when it supports a decision. The buyer may need to screen a supplier, compare a product route, prepare a customer package, check a fire-related boundary or decide whether a sample should continue. Those decisions need different evidence.
Before requesting documents, write the decision in plain language. For example, the team may need to review whether an acoustic route such as S02 has relevant document support, or whether an insulation route such as S09 needs PFAS screening evidence.
Build a document comparison matrix
A matrix helps prevent overgeneralization. It also makes it easier for purchasing, technical and quality teams to see where evidence is strong, where it is limited and where a follow-up request is needed.
| Document type | Main question | Boundary to check |
|---|---|---|
| ISO certificate | What management-system scope is covered? | Organization, site, standard, date and certificate scope. |
| Fire-related report | What sample and method were tested? | Construction, classification, method, date and report owner. |
| EPD | What declared product and lifecycle scope are included? | Declared unit, product family, geography and validity. |
| REACH information | What substance or compliance statement is being reviewed? | Product direction, declaration basis and update timing. |
| PFAS screening | What sample or route was screened? | Method, detection scope, sample identity and wording limit. |
Do not mix certificates with product performance
A management-system certificate can support supplier review, but it should not be read as a product performance test. A fire report can support a defined tested construction, but it should not be copied into a different board system without checking relevance. An EPD can support environmental-data review, but it still has declared scope and validity limits.
This distinction matters when documents are used with product routes such as S05 black matte acoustic facing, S10 ultra-low airflow glass facer or S12 foil-composite facers.
Ask for route-specific evidence
A broad request for all certificates can slow the review because the supplier has to infer which route and decision are involved. A route-specific request is easier to answer: state the product direction, intended board system, document type and why the document is needed now.
The Resource Center is the safest public starting point. It explains the request path without exposing private files or suggesting that every document is public.
Buyer checklist
- Selected product route or route shortlist.
- Board application and review stage.
- Document type requested and reason for the request.
- Customer wording or internal decision that the document will support.
- Whether the document must support sample screening, trial review or formal qualification.
Keep private and public boundaries clear
Some documents may be shared only after scope is clear. That does not mean the evidence is missing; it means the document should be matched to the selected route, buyer stage and access rules. Public pages should avoid direct file links unless the document is intentionally public.
When the route and document purpose are clear, buyers can request technical data with the route, document type and review stage included.
Review notes for buyers
The most common document mistake is using the right evidence for the wrong scope. A report may be valid and still not answer the buyer question if the sample, method or product direction does not match.
When several documents are available, compare their purpose before comparing their wording. ISO, fire, EPD, REACH and PFAS evidence should not be collapsed into a single compliance sentence.
If a customer asks for a broad statement, ask which product, route, board system and market the statement must cover. Then compare that wording with the available evidence before responding.
A good document request is short but precise. It names the route, the document type, the decision stage and the wording or evidence boundary that needs review.
Document comparison should also record what is not available yet. A missing document at early screening may simply mean the route is not selected enough for private review, while a missing report at qualification stage may require a different next action.
Keep the document file name, version date and route reference together in internal notes. This helps the buyer avoid sending an old or unrelated document when the project moves from sample review to customer communication.
If a document is shared under a defined review stage, keep that access note with the file. The team should know whether the evidence is public-facing, request-gated, customer-specific or limited to internal screening.
FAQ
Does one ISO certificate prove product performance?
No. ISO certificates usually describe management-system scope and should not be used as product performance reports.
Can a fire report be applied to every board?
No. Fire-related evidence depends on tested sample construction, method and classification boundary.
How should PFAS or REACH information be requested?
Request it by selected route, sample or product direction, and ask what wording and evidence boundary the document supports.
Next step
Document comparison is strongest when every claim stays inside its evidence boundary. Share the route, document type and review stage with GRECHO before using ISO, fire, EPD, REACH or PFAS information in buyer decisions.
