“Fireproof clay terracotta wall tiles” is not a complete technical statement. Fire requirements apply through defined methods, classifications, configurations and jurisdictions. A robust submittal identifies the exact tile and then maps every relevant component and wall interface to the evidence required by the project’s fire strategy.
Start with the project fire question
Ask the responsible fire consultant or code professional to state each required assessment, method, classification or performance criterion. Record whether the question concerns a tile material, surface, external-wall assembly, cavity, attachment, substrate, insulation, fire stopping or another condition. A supplier cannot answer an undefined requirement reliably.
Identify the jurisdiction, building use, height or location where relevant to the project review, and the authority or reviewer who accepts the evidence. Keep design responsibilities clear. This article provides a submittal framework, not a classification or a substitute for the project fire strategy.
Lock the exact product identity
Request a current code and drawing showing length, width, actual thickness, edge, surface, rear profile, tolerances and mass. The archive omitted thickness, so “60 × 242 mm” cannot release a current order. Ask whether WBS9991 remains valid and which current product or family any document covers.
Tie the tile, drawing, declaration, test report, sample and quotation to one revision. Check whether changes in body, thickness, finish or rear geometry require a new review. A title containing “fireproof” cannot bridge a mismatch between the tested specimen and proposed product.
Build a fire-submittal matrix
Requirement
Record the project criterion, method, jurisdiction and responsible reviewer.
Evidence
List report or declaration number, issuer, date, result, scope and limitations.
Configuration
Match tile, adhesive or fixing, substrate, insulation, cavity, joints and orientation.
Status
Track submitted, reviewed, accepted, conditional or rejected, with open actions and owner.
One document may address one row and leave other rows open. Avoid a folder labelled “fire certificates” without an index. The matrix lets the team see whether evidence is product-specific, assembly-specific or unrelated, and prevents a management-system document from being mistaken for performance proof.
Add a cover sheet to every submission that states the exact question being answered, drawing revisions reviewed, proposed configuration, document relied upon and any difference from the tested or assessed arrangement. Highlight exclusions rather than burying them in attachments. The fire reviewer can then confirm acceptance, request clarification or reject the route without reconstructing the supplier’s reasoning from unrelated files.
Review the tested or assessed configuration
Read the complete report or assessment. Confirm specimen identity, dimensions, finish, support, bonding or fixing method, cavity, insulation, joints, orientation, exposure conditions and any field of application. Record limitations, permitted variations and conditions imposed by the issuing or reviewing body.
Compare this configuration with elevations, sections and specifications. If a component differs, do not assume equivalence. Ask the responsible consultant whether additional evidence or a revised assessment is required. Document the conclusion before procurement, mock-up or installation locks in the change.
Coordinate interfaces and penetrations
Map slab edges, compartment lines, openings, vents, services, attachments, parapets, bases and changes between wall systems. Identify who designs each interface and which fire-stopping, cavity barrier or other project detail applies. A tile document cannot approve an unreviewed junction.
Keep fire details coordinated with water management, movement and constructability. A late interface change made for drainage or installation access may affect the reviewed configuration. Use a multidisciplinary detail register so affected fire, facade, structural and architectural reviewers see the same revision.
Carry approved evidence into site QA
Translate the approved configuration into submittals, shop drawings, method statements, inspection points and product identification. Verify delivered components against approved codes and revisions. Record substitutions, concealed work and interface inspections before they become inaccessible.
Use representative mock-ups or benchmarks where the project requires them, but state what they demonstrate. Visual workmanship approval does not establish fire performance unless it forms part of the specified assessment process. The terracotta tile range can support initial product identification only.
Brief procurement, site management and installers on the accepted configuration and the rule for substitutions. Inspection forms should use current product codes and detail references, not generic descriptions such as “fireproof tile.” Photograph labels and concealed interfaces where the project plan requires records. Escalate mismatches before installation continues, because later access may be limited and documentary correction cannot change installed components.
Close the fire record without overclaiming
Before release, align product code, drawing, submittal matrix, accepted wall configuration, quantities, packing and programme. Compare complete scope, including specialist reviews, testing, mock-ups and exclusions. The project gallery may provide design context but is not performance evidence.
Handover should preserve final drawings, accepted reports and assessments, review comments, installed component records, inspection results and approved deviations. State precisely what the evidence covers. Avoid replacing this record with a brochure claim that the tile is simply “fireproof.”