Controlled product evidence for fire-door manufacturers

Product evidence built for fire-door manufacturers.

Connect product configurations, performance claims, tests, certificates and revisions in one controlled record — ready for today’s compliance work and tomorrow’s digital construction-product requirements.

Create a product recordExplore UK digital requirements

No settled UK digital product record standard exists yet. We track what is law, what is proposed and what is speculation, and say which is which.

The wedge

This is not a QR code generator

Plenty of tools will put a code on a door. The code is trivial. What is hard is being able to say, two years later, which test report supports the 30-minute claim on the configuration that was actually manufactured, and whether the certificate behind it is still in scope.

Fire Product Record holds the structure that answers that question: product families, versions, configurations, permitted components, performance claims, and the evidence linked to each one. The QR code, the public page and the JSON export are outputs of that structure, generated rather than assembled.

How a product record is built

How a product record is builtPRODUCTThe family you sellCONFIGURATIONPermitted component setsCLAIMWhat you declareEVIDENCETests, reports, certificatesDISTRIBUTIONLink, QR, JSON, packPUBLICATIONSnapshot with a hashVERSIONImmutable revisionAPPROVALNamed reviewer signs offEvery arrow is a recorded relationship, not a document folder.
Product → configuration → claim → evidence → approval → version → publication → distribution. Each step is stored as a link between records, so you can walk backwards from a published claim to the test report that supports it.

A claim belongs to a configuration

Fire performance belongs to a tested assembly, not to a product name. A configuration records the variables that can change, the components permitted in each position, the alternatives that are genuinely interchangeable, and the constraints that tie them together.

Record that explicitly and a substituted closer becomes a question with a visible answer at the moment it comes up, instead of a discovery two years later.

Configuration tree for a door assemblyDoor assemblyLeafcore, facings, lippingsFramesection, lining, substrateSealsintumescent, smokeHingestype, number, sizeClosermodel, power sizeLock / Latchmodel, morticingOptional glazingglass, beads, aperture
A claim belongs to a configuration, not to a product name. Change the closer or the glazing and you are describing a different configuration, which may or may not be covered by the same evidence.

Every claim points at its evidence

An FD30S claim supported by a direct test and the classification report that turns it into a classification, applicable to one product version and one configuration, carrying the limitations that came with the field of application. When any part of that changes, the claim is marked for technical review with the reason attached.

Evidence supporting one claimCLAIM · FD30SFire resistance 30 minutes,integrity and smoke controlTEST · TR-001Direct test evidenceCLASSIFICATION · CR-002Field of applicationAPPLICABLE TODoor Family A · version 4 · configuration C1Limitations: leaf ≤ 1000 × 2100 mm · single-acting · timber frame on masonry
The claim points at the evidence, and both point at the version and configuration they apply to. The limitations travel with the link, so a claim can never quietly outgrow the field of application it was classified for.

Who it is for

Small and mid-sized UK fire-door manufacturers, and the people inside them who get asked the awkward questions.

Technical Manager

Knows which test supports which claim, and needs that to survive their own annual leave.

Compliance Manager

Answers customer and client questions about evidence, and needs the answer to be the same one every time.

Certification Manager

Keeps scope schedules, surveillance and renewals aligned with what the factory actually makes.

Technical Director

Wants the gaps found by structure rather than by a customer, a client or an enforcement officer.

Product / NPD

Changes a component and needs to see immediately which claims and configurations that touches.

Quality Manager

Needs revision history, approvals and an audit trail that were recorded at the time, not reconstructed.

What it is not

Not an installer inspection app

It holds what the manufacturer knows about the product. It does not record what a surveyor found on a landing, and it does not manage inspection rounds.

Not a building fire-door register

A register belongs to whoever is responsible for the building and lists the doors installed in it. This is the record behind the product, one level upstream.

Not a compliance verdict

It does not determine whether a product complies with construction-product law. It records claims, evidence and gaps, and marks work as needing technical review.

Not a QR code generator

A QR code is the last five minutes of the job. Everything before it — configurations, claims, evidence, approval, versioning — is the job.

Five statuses, never blurred

Regulatory statements are only useful if you can tell a duty from a plan from a rumour. Every entry in our tracker carries exactly one status, a primary source and the date we last checked it.

LAW
In force now, with a citation to the instrument that creates the duty.
GOVERNMENT COMMITMENT
Government has publicly committed to do it. It is not yet law.
CONSULTATION
Formally consulted on. The outcome is not yet decided, or not yet legislated.
EXPECTED
Reasonably expected from official signals, but with no formal commitment behind it.
SPECULATION
Industry commentary or our own inference. Treat it as an opinion, not a plan.

Read the UK digital requirements tracker

Pricing

Simple monthly plans. Billing is not switched on during the beta — paid plans capture a request and we come back to you.

From

£149 / month

For a small manufacturer bringing product evidence under control.

Prices are launch placeholders during beta.

Four plans, from a single small manufacturer bringing one product family under control to a group with multiple sites and brands. Every plan includes versioned records, evidence with expiry alerts, public records and QR codes.

See all plans

Start with what you already have

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

Start with the family you get asked about most. Add its current version, its configurations, its claims and the evidence behind them, and publish when it is approved.

Create a product recordExplore UK digital requirements