A buyer does not need every available document; the buyer needs the document that can close the next decision. Use a product data sheet to identify the supplied product and its declared properties, an SDS to communicate hazards, a full laboratory report to review a measured result, a certificate or declaration to verify a defined scope, and a drawing or release record to control project work.
Before accepting any file, match six items: exact product, thickness and finish, intended use, market or project, document revision or validity, and the decision the file is expected to support. If one of those is missing, record a scope gap instead of treating the document as approval.
Fix the Commercial Slab Identity Before Reading Any Evidence
“Sintered stone” is not a usable approval identity. The same design name may be offered in several slab sizes, thicknesses, finishes, body constructions or backed forms, and a project may use different faces or vein directions in different zones. Freeze the purchasable configuration before accepting a value, certificate or sample.
| Identity field | Sintered-stone record | Why the distinction matters |
|---|---|---|
| Design and product code | Commercial design name plus controlled model/SKU. | A visual name alone may be reused across formats or revisions. |
| Body / construction | Full-body, surface design, composition group or other declared construction; note any backing/mesh. | A result for one construction should not silently represent another. |
| Nominal slab and usable size | Factory slab format, usable dimensions, rectified/factory edges and orientation. | Large-format yield, seams, nesting and damage allowances are not visible in a small coupon. |
| Thickness and finish | Nominal/calibrated thickness as declared; polished, matte, textured or other named finish. | Strength, surface tests, processing and appearance can depend on configuration. |
| Batch, lot and face | Production batch/lot, slab or crate ID, face number, bookmatch/sequence and vein direction. | This connects approved appearance and test scope to the material actually shipped and cut. |
| Intended conversion and use | Uncut slab, cut-to-size panel, countertop piece or other supplied form; floor, wall, facade, countertop or furniture use. | Product evidence and assembly/fabrication approval answer different questions. |
The inspected Funtek TDS example identifies CALACATTA A17 / FTK-A17-2607, batch FT-A17-2607, 1600 × 3200 × 12 mm, polished, full-body. Those fields form one declared configuration. Its listed values remain manufacturer-declared internal-lab data unless a cited third-party report establishes the same product scope.
Match Each Buyer Decision to Its Controlling Document
| Buyer question | Evidence | Establishes | Does not establish |
|---|---|---|---|
| What product is being offered? | Current TDS or product data sheet | Code, nominal format, thickness, finish, intended-use statement and declared properties. | Third-party test performance, legal market access or project approval. |
| What hazards must be communicated? | SDS | Hazard classification, composition disclosure rules, handling, first aid, storage and disposal information within the document scope. | Workplace exposure assessment or a complete fabrication control plan. |
| What did a named specimen achieve? | Full test report | Sample identity, method, conditions, units, individual or summary results and laboratory authorization. | The project pass limit unless the report explicitly cites the governing requirement. |
| Does an organization, system or product sit within a certified scope? | Certificate or directory listing | Issuer, holder, site/product scope, standard or scheme, validity and exclusions. | Properties not named in the scope or approval of every SKU. |
| Does an EU construction-product route apply? | Applicable harmonised specification/ETA, declaration and CE information | The route, declared use, essential characteristics and responsible economic operator where the legal conditions are met. | A universal CE requirement for every slab and use. |
| Can this appearance be accepted? | Named sample, full-slab image or mock-up | Colour, finish, pattern scale, edge or assembly appearance at the stated level. | Production conformity unless the approval is tied to batch and change control. |
| Can cutting, procurement or installation start? | Current drawing, submittal response and release record | The approved revision, remaining conditions, responsible approver and exact next action. | Release of any action not stated in the record. |
“Send all certificates” is not a technical request. Name the product, application, destination, property or approval question, and the evidence type required.
The Evidence Chain from Commercial Slab to Released Work
A useful evidence chain follows the physical product from selection to release. It does not jump from a marketing description directly to production. Each record answers a different question and hands a controlled identity to the next step.
- DefineRecord product family, code, dimensions, thickness, finish, intended use and destination.
- VerifyMatch declared properties to reports, certificates or declarations at the correct scope.
- CoordinateTie samples, drawings, interfaces and deviations to the same identity and revision.
- ReleaseName the authorized next action: quote, sample, order, production, cutting, shipping or installation.
The chain can stop at any gate. A report may be authentic but irrelevant to the selected thickness. A sample may match the colour but not the production batch. A drawing may be technically coordinated but still marked “revise and resubmit.” The stop reason belongs in the record so another reviewer does not repeat the same investigation.
Four Checks Before a Document Can Support Approval
| Check | Fields to read | Failure example | Required action |
|---|---|---|---|
| Identity | Manufacturer, product code, design, finish, thickness, format, batch or specimen description. | A 12 mm polished result is submitted for a 6 mm textured facade panel. | Request exact-product evidence or record why a representative family result is acceptable. |
| Scope | Test specimen, product family, site, standard, intended use, exclusions and annexes. | An ISO 9001 certificate is used as proof of stain resistance. | Return to the document family that owns the property question. |
| Status | Issue date, expiry date, report revision, page count, superseded status and directory listing. | Only page 1 of an eight-page report is supplied. | Request the complete, current controlled copy. |
| Result | Units, test conditions, number of specimens, individual values, mean, class and qualifiers. | A class is copied into a comparison sheet without its method or surface finish. | Record the result together with method and conditions. |
| Acceptance | Project specification, product standard, contract, regulation or authority decision. | A method number is treated as its own pass threshold. | Identify the separate acceptance source and compare it explicitly. |
For measured performance, use the detailed test-report review workflow. For method selection, use the ISO 10545 decision map. Those pages separate the test method from the specification limit.
A Report Cover Proves Scope, Not the Result
The inspected Funtek SGS report cover identifies report number SZXEC25052189601, an issue date of 29 May 2025, a testing period, eight total pages, the applicant, a Calacatta White model code, 1200 × 600 mm sample size, 12 mm thickness, and five ISO 10545 test scopes. That is enough to establish the identity declared on page 1 and to confirm that result pages should exist for the named methods.
It is not enough to state the water-absorption value, modulus of rupture, breaking strength, stain class, chemical class or thermal-shock outcome. Those claims require the corresponding result pages, specimen count, units and qualifiers. This distinction is why a cover screenshot cannot replace the full report.
REPORT REVIEW STATUS: SCOPE CONFIRMED / RESULTS PENDING
Product: Calacatta White, FT-CW1260
Reported specimen: 1200 × 600 × 12 mm
Methods listed: ISO 10545-3, -4, -14, -13, -9
Missing for decision: result pages, values/classes, specimen count, acceptance criteria
Next action: obtain complete eight-page controlled report before approvalConnect Samples, Slab Faces, Drawings and Inspection Records
Documents do not control appearance or fabrication unless they connect to physical items. A sample record should carry the product code, finish, thickness, date, recipient and purpose of approval. A full-slab or batch record should explain whether the small sample is a colour reference, a limit sample or a direct production match. A drawing should identify the product and approved sample reference, not just show dimensions.
Inspection then compares the actual order with the released basis: piece or slab IDs, drawing revision, acceptance criteria, observed result, disposition and evidence location. For countertop work, use the cutting-release document pack. For broader contract review, use the project submittal and release workflow.
Approval is a verb with an object. Record whether the reviewer approved the colour sample, the product substitution, the drawing geometry, the purchase, the production batch or the next work activity.
Build the Evidence Register Around Claims and Release Gates
A buyer should be able to answer three questions without reopening every PDF: what claim is under review, which controlled source supports it, and what decision was made. Build one register row per claim or approval object—not one row per file. A single report can support several rows, and one row can require several independent documents.
| Register field | What to record | Why it matters |
|---|---|---|
| Evidence ID | Stable internal ID plus source filename/report/certificate number. | Prevents detached screenshots and renamed files from losing identity. |
| Claim / decision | Exact statement being checked, such as “12 mm polished model water absorption” or “sample colour accepted.” | Stops one file being used to answer unrelated questions. |
| Product scope | Code, family, finish, thickness, format, batch/specimen and intended use. | Makes scope mismatches visible before comparison. |
| Source authority | Manufacturer, laboratory, certification body, designer, engineer, client or authority. | Shows who is responsible for the statement and at what level. |
| Document locator | Title, number, revision/date, page, table/section and persistent storage path. | Allows another reviewer to reproduce the finding. |
| Result / wording | Exact value, unit, class, observation, limitation or response status. | Preserves qualifiers and avoids marketing paraphrases. |
| Acceptance basis | Specification clause, product standard, contract or authority requirement. | Separates evidence from the rule applied to it. |
| Disposition | Accepted, scope gap, criterion missing, clarification, rejected or superseded. | Creates an operational outcome rather than a document archive. |
| Release effect | The named next action and any conditions/exclusions. | Prevents a narrow approval from expanding downstream. |
Version the register with the project. When a product, finish, thickness, test report, certificate, drawing or legal route changes, mark affected rows for re-review. Do not silently overwrite the evidence that supported an earlier decision; retain the superseded state and the reason for change.
EV-042 | Claim: 12 mm polished model — water absorption
Source: Report ______ Rev __, page __, ISO 10545-3
Result: ______ % | Specimens: ____ | Conditions: ______
Acceptance: Spec ______ clause ______ | Limit: ______
Scope match: exact / representative / mismatch
Disposition: ______ | Reviewer/date: ______
Release effect: __________________________________Compare Suppliers Without Flattening Product Scope
Normalize the question, not the numbers. Ask every supplier for the same product configuration, test part/edition, result form, units, specimen scope, report status and acceptance reference. If one supplier provides a TDS summary and another provides a full third-party report, label the evidence levels separately instead of placing both values in one “certified” column.
| Comparison field | Supplier A | Supplier B | Reviewer rule |
|---|---|---|---|
| Product configuration | Code / thickness / finish / size | Code / thickness / finish / size | No numeric comparison until configuration is comparable or difference is declared. |
| Evidence type | Internal TDS / full lab report / certificate | Internal TDS / full lab report / certificate | Do not treat different authorities as equivalent. |
| Method and edition | Exact reference | Exact reference | Record alternate methods; do not convert them by assumption. |
| Result | Original value/class + units | Original value/class + units | Preserve original reported form and statistic. |
| Scope/status | Exact / representative / expired / partial | Exact / representative / expired / partial | A strong number with a weak scope remains a weak decision input. |
| Acceptance conclusion | Met / not met / criterion missing | Met / not met / criterion missing | Use the same named requirement for both. |
A Document Request a Sintered Stone Supplier Can Answer
Replace generic requests with a controlled request line. One sentence should name the exact product and the decision. The response should be stored with the request, not detached in a chat thread.
Project / market: ____________________
Product code / design: _______________
Thickness / finish / format: __________
Intended use and exposure: ____________
Decision to be made: ___________________
Required document and method/scheme: ___
Required revision / validity date: ______
Required scope or acceptance criterion: _
Requested delivery date: _______________
Reviewer / approver: ___________________If the request concerns EU construction-product documentation, first confirm the exact product and intended use through the CPR route decision tree. If the request is still phrased as “SDS or certificate,” use the document-family comparison before contacting the supplier.
Request the Evidence for a Defined Decision
Send the product code, thickness, finish, application, destination market and the approval your team must make. Funtek can identify available product, sample, test, inspection and project records at their stated scope.