Skip to main content

Product assurance

Every claim you make, backed by evidence that still applies

A claim on a datasheet is only as good as the test behind it, and only while the product is still made the way it was tested. Doctilla keeps the two connected, and tells you when a change could break the link.

Request a demo Watch the 90-second film

How it works

From product to claim to evidence to publication

  1. 01

    Model the product

    Products, their configurations and the components in each, with the supplier of every component. Import a product list from Excel or CSV to start.

  2. 02

    Record each claim

    Performance, safety, environmental and other claims, each in the exact words you publish. Upload a datasheet and Doctilla finds the claims in it as drafts.

  3. 03

    Link the evidence

    Test reports, classification reports and certificates, with the version each claim relies on. A claim with no current evidence is flagged for review.

  4. 04

    Know where it's published

    Datasheets, websites and declarations that carry each claim. Doctilla checks web pages and tells you when a claim's wording can no longer be found.

  5. 05

    Control change

    Raise a change, see every configuration, product and claim it could reach, and route it to a technical review. A person concludes it, and the conclusion is final.

Claims, evidence and publications

Every claim you make, the evidence behind it, and where it's published.

Chapters and transcript

Product changes and technical reviews

See what a change reaches, and let a person decide what it means.

Chapters and transcript

Built so it cannot overreach

Doctilla can raise a concern. It cannot sign anything off.

In product assurance the line between 'worth a look' and 'cleared' matters more than anywhere. So the asymmetry is in the data itself, not left to how a screen chooses to show it.

  • Impact rules can only escalate the review a change needs. "Supported" is not an outcome they can store, enforced by the database.
  • Claim review returns concerns only. There is no field in its response that could express a clearance.
  • Publication monitoring reports "claim wording not found", never "claim removed".
  • Datasheet import keeps a claim only if its exact words appear in the document, and creates every claim as a draft.
  • A concluded technical review cannot be amended. If something changes, a new review is raised.
  • Approving or implementing a product change is done by a person in Doctilla, never through the API or an AI assistant.

Questions

Product assurance questions

Is this only for construction products?
No. It suits any manufacturer whose products carry claims that must stay true as materials, suppliers and designs change. It was built with construction products in mind because that's where the consequences of an unsupported claim are clearest.
Does Doctilla decide whether a claim is supported?
No. Marking a claim as supported is a person's judgement, recorded with their name. Doctilla's claim review and impact rules can only raise concerns or escalate; their outputs have no way to express a clearance.
Does it help with the Code for Construction Product Information?
You can import the requirements you work to, whether that's the CCPI, a customer's specification or an internal standard, and map your products, claims and evidence to each one with a rationale. See standards and requirements mapping. Doctilla doesn't supply the text of any code or standard, and it never tells you that you comply.
Can it watch our website for changes?
Yes. Record where each claim is published and Doctilla checks those pages. If a claim's wording can no longer be found, it says exactly that, so a person can find out why. It never concludes that a claim was removed.

See product assurance with your own kind of product

Book a 30-minute demo. We'll walk through the parts that matter to you, using a fully populated demonstration company, and answer anything you want to ask.

Request a demoBrowse the training videos