A certificate you can trace to the result.

Prepare certificates of analysis from reviewed results and the applicable specification in Seal. Keep source values, reportable values, template versions and issue history connected.

Explore this workflow
Illustration of a seal beside an open evidence folio containing SOP, training and execution records.

Which results belong on this certificate?

Three reportable results are available for batch DP-086. The residual-solvent result is still under review, so the certificate remains a draft.

DP-086 / certificate of analysis

Draft
Example records. Select a row to inspect its source.

Residual solvent

RES-086-S
Method
AM-031 / v02
Reportable value
Not available
Review
Open

No approved reportable value is available in the selected records. The draft must not substitute zero, a previous batch’s result or an assumed conforming statement.

What follows

Complete the source result review and refresh the draft before certificate issue review.

Run the work in Seal.

Resolve the applicable source set.

Select the batch, product, market or customer context, specification, reviewed results and certificate template.

Prepare the certificate.

Apply the agreed statement and formatting rules. Surface missing results and inconsistent references before routing the draft.

Review, issue and retain.

Record the authorised issue decision and delivered version. Link any amendment to the original certificate and its recipients.

Prepare the certificate review note.
neil

Three reviewed results are available. The residual-solvent result is still pending review, so I have not filled it with an assumed value or treated the draft as ready to issue.

From reviewed results to the delivered certificate.

An amendment keeps the first issue.

Correct the certificate without erasing what was previously supplied.

Retain the original document, corrected version, reason, approval and distribution history. Make supersession clear and identify which recipients need the amended certificate.

The document and data export agree.

Use the same selected results and reportable-value rules for the PDF and machine-readable handoff.

Check units, rounding, qualitative statements and missing-value handling in each output. A regenerated preview is not automatically the issued certificate or a new release decision.

The format follows the intended recipient.

Configure product, customer and language-specific templates without separating the certificate from its data.

Review which tests and statements belong in the output, the applicable specification, reportable units and any required translation. Retain the chosen template version. A different presentation must not silently change the result or the criterion against which it was reviewed.

Issue and delivery have their own history.

Keep the authorised issue decision, signature meaning and exact delivered version with the certificate.

Record recipients and the agreed distribution route, whether an existing portal, an API or a document handoff. Scope access and delivery confirmation. If source results change, assess the issued certificate and any amendment or recipient notification rather than overwriting the original output.

Connected to the surrounding work.

Batch releaseSpecificationsLaboratory execution

Keep specialised systems where they belong. Agree the source of each record, the permitted actions and the reconciliation at each handoff.

Explore integrations

Before you get started.

Configure the template, language and required statements for the applicable product and customer. Review that context as well as the result values.
Scope access to reviewed results, versions, units and the approval state. Preserve the source-system reference and define how corrections are reconciled.
No. Certificate preparation, certificate issue and batch disposition are distinct actions with the approvals your quality system requires.

Try it with your own work.

Bring one certificate, its source results and the rules used to issue it.

Book a demo