drywallDB
Sign in

Methodology

How drywallDB treats data

Construction decisions get audited — by clients, approvals processes and, occasionally, courtrooms. So drywallDB is built to be checked: every value on screen belongs to a stated class, every equivalence judgement cites the versioned rule that produced it, and the boundaries of what the tool will and won’t claim are written down here, in public. This page is the working behind the product.

The three classes of data

Every value drywallDB shows belongs to exactly one of three classes. The same three classes are encoded in our terms of service — this page is the plain-English version of a binding commitment, not marketing gloss.

Declared

Taken verbatim from a cited manufacturer document — a product data sheet, a declaration of performance, or the manufacturer’s own published listings. Each declared value names its source document and revision, and the source documents are archived, so a citation points at the exact edition the value came from, not at a moving web page. Values are reviewed against the source line by line before they enter the catalogue. Where a manufacturer’s own documents disagree with each other, we query the manufacturer and record the answer rather than silently picking a side.

Calculated — always marked *

drywallDB arithmetic over declared inputs, and nothing else. Every calculated value carries the asterisk mark, everywhere it appears — results table, comparisons, data sheets and printed documents alike. The full list of what drywallDB calculates is deliberately short:

Calculated values inherit the declaration basis and nominal character of their inputs. Manufacturers state weight on different bases — one brand declares a minimum, another a typical mass — and a figure derived from a minimum is still a minimum. The mark is the honesty mechanism: you can always tell our arithmetic from a manufacturer’s declaration.

Indicative

Estimates identified as such. The class exists in our terms and our data model, and it is currently empty — nothing in the catalogue today is indicative. If estimated data ever ships (for example, computed build-up performance), it will be labelled as this third class, clearly separated from cited data, and never presented as certified performance.

The equivalence rules — versioned, published, explainable

Cross-brand equivalence is drywallDB’s signature judgement, so it is the last place a hidden heuristic belongs. Matching runs on a fixed, published rule set — currently ≈ rules v1 — and every comparison and substitution document states the version that assessed it. If the rules ever change, the version number changes with them: a document generated under v1 stays attributable to v1. The rules in full:

  1. Same thickness, different brand. Candidates must match the benchmark board’s thickness exactly — a 15mm board is never proposed for a 12.5mm spec — and come from another manufacturer.
  2. The declaration must be covered. Every performance class the benchmark board declares to EN 520 (Type F fire, D density, I impact, R strength…) must also appear on the candidate. Missing one rules it out.
  3. Type A never decides anything. It’s the baseline every plasterboard meets; some manufacturers print it, some don’t. Treating it as a requirement would split identical boards on house style, so it’s read as a labelling convention.
  4. Moisture may be equal or better — never worse. H classes are ordered (H1 best, then H2, then H3). A candidate can match or exceed the benchmark’s class; when it exceeds, the upgrade is stated on its column rather than silently absorbed.
  5. Different forms never swap. A plaster baseboard (Type P), a foil-backed vapour board (EN 14190) and a glass-mat wet-area board (GM) are different products, not upgrades — these must match exactly, in both directions.
  6. Best format wins. Among qualifying boards from a brand, the one closest to the benchmark board’s size and edge is offered.

Two disclosures ride with every assessment. Reaction to fire is never a pass/fail criterion — where the classes differ, the difference is shown for your judgement, not silently gated. And boards that cover the spec and more are listed separately as over-specified alternatives with their extra classes named, because over-performing board usually costs more — they are never mixed in as if they were like-for-like. You can see all of this working on the annotated example comparison.

What drywallDB does not do

The boundaries matter as much as the features. Each of these is a deliberate refusal, stated in the product wherever it is relevant:

Where this is binding

The three data classes and the not-a-certification stance are not just principles — they are written into the terms of service that govern every account. Manufacturers revise their literature; always verify against current manufacturer documents before purchasing or certifying.

Built to be checked. Check it.

Free for 7 days · no card · your email is the account