Fire Product Record
A controlled record for every fire-door product family
Most fire-door manufacturers hold everything they need. It is spread across a document library, a specification spreadsheet, a certification folder and two people who have been there long enough to remember. A product record puts the relationships between those things in one place.
What a product record contains
A product family is the thing you sell and the thing your customers name. Underneath it sits a sequence of versions, each an immutable revision with an effective date, a reason for the change and a named approver.
- Identity: name, internal reference, product type, intended use and external identifiers
- Versions: what changed, when it took effect, who approved it and what it superseded
- Configurations: the variables, permitted components and constraints that define a valid assembly
- Claims: characteristic, value, classification and the standard it is expressed against
- Evidence: tests, classification and assessment reports, certificates, declarations and instructions
- Publications: immutable public snapshots, each with a publication number and a hash
Versions are the spine
Everything else hangs off a version. A claim belongs to a version. A configuration belongs to a version. Evidence is linked to the versions it covers. Without that spine you cannot answer historical questions, and historical questions are most of the questions you get asked.
Approved versions are not editable. Changing an approved product creates the next version, with a reason recorded. That constraint feels restrictive for a week and then quietly becomes the thing that makes the record worth having.
Approval before publication
A version moves from draft, through review, to approved. Only an approved version can be published, and publishing captures a snapshot rather than pointing at live data. The snapshot is hashed, so a published record can be shown to be the same record it was when it was published.
Publishing a second time supersedes the first publication rather than overwriting it. The old publication stays reachable, clearly marked as superseded, with a link to the current one.
What it is not
It is not an installer inspection app, a building fire-door register, or a document management system with a fire-door skin. It holds what the manufacturer knows about the product, not what a surveyor found in a corridor.
And it does not determine whether a product complies with anything. It records what you claim, what supports the claim, and where the gaps are. The technical judgement remains yours.
Common questions
Does it replace our certification scheme records?
No. It records your certificates as evidence, with scope and dates, and links them to the claims that rely on them. The scheme relationship is unchanged.
What happens to products we no longer make?
They stay. A product family can be withdrawn or archived, and its historical publications remain reachable, because someone who bought in 2021 still has questions in 2031.
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.