Carpet Tile Submittal Checklist: What to Request Before Approval
TL;DR
A carpet tile submittal checklist should keep the exact proposed product, sample reference, current product sheet, requested reports or certificates, issue dates, stated scope, project questions and reviewer decision in one traceable record. A sample, a logo or a generic declaration is not by itself approval of a different product, a project condition or an installed result.
The direct answer: make a submittal traceable before it is approvable
A carpet tile submittal checklist should keep the exact proposed product, sample reference, current product sheet, requested reports or certificates, issue dates, stated scope, project questions and reviewer decision in one traceable record. A sample, a logo or a generic declaration is not by itself approval of a different product, a project condition or an installed result.
This checklist is for procurement teams and specifiers who need to separate identification, document review and unresolved project questions before approval. It does not turn a submittal into a warranty, test result, installation instruction or supply commitment.
Send a submittal enquiry · Read the RFQ checklist
The carpet tile submittal record
| Field | Record or request | Evidence boundary |
|---|---|---|
| Product identity | Record the UNIJOY series and exact style/code, colourway, module and the sample reference being reviewed. | A similar image, collection name or colour label does not establish the same proposed item. |
| Submittal item | List each item separately: product sheet, sample, report, certificate or supplier statement. | A document title does not establish its current version, scope or applicability. |
| Document control | Record issuer, issue date/version, product identity, specimen if named and stated scope. | A report or certificate cannot be extended beyond its stated product, method and scope. |
| Project interface | Keep zone, layout, adjacent finish, subfloor and installation questions visible as open items. | A product document alone does not settle a site condition or coordination question. |
| Review decision | State approve, reject, revise or pending, plus the named reason and responsible reviewer. | A marked sample or email alone does not close missing technical or project questions. |
What marketing language cannot approve
| Marketing wording | Ask for | Do not infer |
|---|---|---|
| “Approved sample” | The sample reference, product identity, colourway/module, viewing condition and decision record. | It does not prove a future batch, installed appearance, test result or availability. |
| “Certified” | The current certificate, issuer, product identity, date and explicit scope requested by the brief. | It does not prove every requirement, project compliance or a different product. |
| “Meets specification” | A field-by-field comparison against the actual brief and any open variance record. | It does not prove an unreviewed document or site interface. |
| “Commercial grade” | Named product fields, intended zone and current evidence requested for the project. | It does not establish universal suitability, performance or approval. |
| “Ready to install” | Current product-specific instruction and separately recorded substrate/adhesive/site questions. | It does not prove installation compatibility, schedule or installed outcome. |
A checklist for an evidence trail
- Name the proposed UNIJOY series, exact style/code, colourway and module before accepting any document.
- Give every sample, sheet, report, certificate and declaration its own line in the register.
- Check issuer, issue date/version, named product or specimen, method where stated and document scope.
- Compare every requested field with the project brief; record differences as open variances rather than assumptions.
- Keep visual approval, technical evidence and installation-interface questions as separate review tracks.
- Record a named reviewer decision and the reason; do not use a generic approval to close an unknown.
- Send the identified product and open submittal questions through UNIJOY Contact for a current response.
Use the live catalogue to identify the proposed UNIJOY option, then send the submittal register and unresolved evidence questions for review.
Frequently asked questions
What must a carpet tile submittal identify first?
Start with the exact proposed product: series, style/code, colourway and module, linked to the sample reference if one is reviewed. A collection name or image is not enough to control a document set.
Is a sample the same as a technical approval?
No. A sample can support a visual review when its identity and conditions are recorded. It does not by itself establish test results, certificate scope, installation compatibility or an installed result.
How should a report or certificate be checked?
Record the issuer, issue date or version, named product or specimen, stated method where present and stated scope. Request clarification if the proposed product or the project requirement is not clearly within that scope.
What happens when a submittal field is missing?
Leave the item pending and record the missing question, owner and next action. Do not fill a gap with a marketing phrase, a similar product record or an assumption about a project condition.
Sources & further reading
- WBDG — UFGS 01 33 00 Submittal Procedures
- Carpet and Rug Institute — Model Specification for Commercial Carpet (2018)
- Carpet and Rug Institute — Installation Standards
- Interface — Product Inspection installation guidance (peer example)
- UNIJOY — Contact
Figures attributed to other manufacturers are their own published values, quoted for context. Different laboratories, sample build-ups and substrates are not directly comparable.