Fire Product Record
Every claim linked to the evidence that supports it
Evidence is only useful in relation to something. A test report on its own answers no question. The same report, linked to a claim and a configuration, with its field of application recorded, answers most of them.
Evidence as records, not attachments
Each piece of evidence is recorded with its type, reference number, issuer, testing organisation or conformity assessment body, issue date, expiry date and review date. Files attach to the record; they are not the record.
Scope is captured explicitly — size limits, permitted frames, tested leaf constructions, hardware requirements, supporting construction — so it can be compared, queried and inherited by the claims that depend on it.
Support types are different kinds of support
A claim can be supported by a direct test, a classification, an extended application assessment, an assessment, a certification or a declaration. These are not interchangeable, and a record that flattens them into "supporting document" throws away the distinction that matters most.
- Direct test — the specimen was tested and this is what happened
- Classification — the test results expressed as a classification, with a field of application
- Extended application — the field of application widened by reasoned assessment
- Certification — a certification body has assessed the product against a scheme
- Declaration — your own formal statement of performance
Dates that raise work
Expiry and review dates turn a static library into something that tells you when it needs attention. The alerts that matter are the ones about consequences: evidence expiring, evidence expired, a claim relying on expired evidence, a claim with no supporting evidence at all, a component changed after the evidence that covered it.
The status a claim gets in those cases is "needs technical review". Not a verdict, not a legal conclusion — a piece of work for a competent person, with the reason attached.
Confidentiality is per document
Some evidence can be published in full. Some can be listed publicly by reference and issuer without exposing the document. Some should not leave the organisation at all. Each evidence record carries its own confidentiality setting, and the public record shows only what has been marked for publication.
Changing a document back to internal takes effect immediately, even for a record that was published while it was public. The snapshot keeps its reference; the file stops being served.
Common questions
Can we upload the reports themselves?
Yes. Files attach to the evidence record with their size, type and SHA-256 hash. Whether a file is publicly downloadable is a per-record decision.
What about evidence we hold from a supplier?
Record it with the issuer and the provenance so it is clear the evidence is third-party derived rather than your own test. Provenance is part of the record.
What this product does not do
Fire Product Record helps manufacturers organise product information, configurations, performance claims and supporting evidence. It does not determine whether a product complies with applicable construction-product law or replace technical, conformity-assessment or legal judgement. Manufacturers remain responsible for the accuracy and approval of published product information.
Bring one product family under control first
Start with the family you get asked about most. One version, its configurations, its claims and the evidence behind them.