Material Certification

The Material Certification register records the compliance documentation received for materials and equipment used on a project — mill certificates, certificates of conformance, test certificates, and concrete test results — each tied to a specific item, supplier, and batch or lot number.

Traceability from an installed material back to the certificate that proves it meets specification is a common audit requirement, and it only works if the certificate is logged against the specific batch/lot it covers at the time it's received, rather than filed separately and matched up after the fact.

Each certificate record has its own compliance status — compliant, non-compliant, or pending-review — set independently for that specific item/batch, so the register can show at a glance which received materials are cleared for use and which are still awaiting review or have failed to meet specification.

The list page shows every certificate with its item, supplier, certificate type and compliance status, filterable/sortable by date received, compliance status, or when the record was created/updated. The detail page shows the full record; create and edit forms share the same fields.

• Item — required. The material or equipment the certificate covers.
• Supplier — required.
• Certificate type — required. One of Mill Certificate, Certificate of Conformance, Test Certificate, Concrete Test Result.
• Certificate reference — required. The certificate's own identifying reference.
• Date received — required.
• Batch/lot — required. The specific batch or lot this certificate covers — this is what ties the certificate to a physical, traceable quantity of material rather than the material type in general.
• Compliance status — one of compliant, non-compliant, pending-review.

Setting compliance status is a direct field edit, done by whoever reviews the certificate against the required specification — the application doesn't perform any automatic compliance check itself.

A material logged as non-compliant here isn't automatically blocked anywhere else in the product (for example, it doesn't prevent a related Procurement request or site delivery) — treat compliance status as the record of the review outcome for whoever manages the register, not an enforced gate.

Can one certificate cover more than one batch/lot? The register records one batch/lot per certificate entry — if a single certificate document actually covers several batches, log one entry per batch so each is independently traceable and independently reviewable.