Distinguish a summary certificate from detailed test evidence

Separate the statement from its supporting data

Identify what evidence you actually have so the next review does not depend on data the document never contained.

Our public material-register example shows a synthetic report beside downloadable output. Use it to inspect how values and source references travel together. The self-service ParseMill trial is for invoice PDFs; supplier test reports and engineering review need a separate fit discussion.

Do not assume that every document called a certificate has the same purpose or level of detail. Inspect its contents and the agreed evidence requirement. A summary may be sufficient for one administrative task while a different technical review requires detailed results; the responsible reviewer decides that sufficiency.

Build an evidence inventory

Use separate fields for document type as stated, supplier claim, numerical data present, test-method references, linked detailed reports and unresolved evidence. W3C: PROV Data Model distinguishes entities and their relationships. Apply that approach by recording the summary and each detailed report as separate sources, with the actual relationship stated in the certificate.

A reference to report T42 is not the same as possession of T42. Mark the reference as mentioned-but-not-supplied until the document is available. When it arrives, check its identity, revision and subject before treating it as support for the certificate.

Review a synthetic certificate package

Synthetic example: certificate C8 states that lot L8 meets specification R4. It mentions test report T42, but the initial package contains only C8.

The inventory contains one supplied source and one referenced source. It does not contain two reviewed documents. A link label or report number should not create the appearance that the receiving team has inspected evidence it cannot yet open.

Check the authority of each claim

NIST: Metrological traceability notes that laboratory accreditation does not itself authorize approval of a particular product. Similarly, a logo or accreditation reference on a certificate should not become an independent receiving approval in your register. Preserve what the issuer says and route any required interpretation to the appropriate reviewer.

If detailed results conflict with the summary, record the conflict and retain both versions. Ask the issuer to resolve the specific inconsistency. Do not discard the inconvenient source or silently change the certificate wording in the spreadsheet to match a preferred conclusion.

Hand over the evidence boundary

A useful cover note states which documents were received, which were inspected, what data they contain and what remains unavailable. Distinguish transcription checked from evidence sufficient and technical approval granted. Each status should name its responsible person and the source version considered.

For a supplier-document fit discussion, bring a summary certificate and a detailed report and specify the distinction the output must preserve. Agree a pilot only after its document scope and review work are clear. Summary certificates are not an input promised by the invoice trial.