What a document review can establish
A review can record a printed identifier, an explicitly named mill, a heat reference, a grade designation or a country statement. It can show whether those observations agree with expected references supplied by the reviewer. It can also record that evidence is missing or contradictory.
Those are useful results, but their scope matters. A checked field means a person checked a source observation. It does not mean the software tested the material, contacted the issuer or verified that the shipment contains the material described.
Start with an explicit requirement record
Before assessing a report, identify the purchase-order line and the requirements that apply to it. In your existing quality record or spreadsheet, keep a row for each question you need answered. A document with every software field populated may still omit a requirement from the order.
For each row, record the requirement and its source, the source revision or clause reference, the certificate page and row you examined, your observation, and the person responsible for the next decision. Keep the requirement text separate from the supplier’s statement. If the applicable requirement is unclear, assign that question before treating any extracted value as an acceptance result.
This is a suggested working record, not a universal inspection checklist. MeltLedger does not contain a product-standard rules database or an approval workflow. Requirements for testing, acceptance and release remain in your controlled process.
- Observed and checked: you found and checked the stated evidence; identify the exact source.
- Missing or unclear: the required observation is absent or unreadable; name the evidence needed.
- Conflicting: two identified sources disagree; preserve both values and assign a resolution.
- Outside this review: another inspection, technical assessment or approval is required; record its owner.
Keep certificate type and inspection requirements explicit
If your order calls for a particular EN 10204 inspection document, record that requirement and the type actually stated on the source. Do not relabel a document because its layout looks familiar or because a review has been completed.
LRQA describes EN 10204 Type 3.2 services as an independent inspection and assurance process and discusses conditional “intent of” services for material with Type 3.1 certification. That is specialist work subject to requirements, not a conversion performed by extracting text from a PDF. Consult your required standard and responsible inspection professional for the applicable process.
Decide which parts of MTR review to automate
Treat automation as a set of bounded tasks. Extraction proposes what the PDF says. A reference comparison checks selected values against the expected values you enter. An acceptance decision applies the relevant requirements to the correct material and evidence. Completing the first two tasks does not complete the third.
MeltLedger’s optional AI proposes five evidence fields: certificate identifier, explicitly identified manufacturing mill, heat number, steel grade and explicitly stated melt-and-pour country. It does not evaluate chemical composition or mechanical test results against a standard. A reviewed grade designation does not establish that every applicable test or condition has been satisfied.
For shipment comparisons, the current implementation compares manually entered heat and grade references with the report’s selected heat and grade. It requires reviewed certificate values and entered line/source references before showing “Compared values match.” That label describes those reference comparisons only. It does not authenticate the PDF, inspect delivered goods or release material for use.
If a document covers several products or heats, establish which row supports each line before comparing it. The software does not automatically associate every shipment line with a different certificate row. Use the linked reading and procurement guides to plan the human checks around each automated step.
Avoid conclusions that exceed the evidence
Keep “reference matches” distinct from “material accepted.” A heat match is not a physical inspection. A grade label is not a grade-equivalence assessment. An origin statement is not a guarantee of customs acceptance. An image of a signature does not establish the signer’s identity.
When a decision needs more than the supplied document, record the missing check and who is responsible for it. This makes the handover more useful than a single green “compliant” label with no explanation.
Write a handover that preserves open decisions
The following wording illustrates a fictional review of PO-DEMO-42, line 10, and certificate DEMO-17 revision A. The identifiers are invented. Adapt the structure to your own evidence; do not copy the outcome as a real approval.
Keep the statement with the original document, the comparison record and the relevant requirement references. Assign unresolved checks through your existing process. When a corrected document arrives, retain the earlier revision and record which observations were rechecked; an earlier reviewed mark does not establish the correctness of a replacement document.
Scope: certificate DEMO-17 revision A, page 1, compared with PO-DEMO-42 line 10. Heat and grade references were checked against the original and match the entered expected values.
Open decision: the example order requests Type 3.2, while the supplied document states Type 3.1. Refer the document requirement to the responsible quality or inspection professional before recording acceptance.
Not assessed in this review: issuer authenticity, delivered-material identity, chemical or mechanical conformity, and final release. The reference comparison is complete; those decisions remain with the assigned owners.
Where MeltLedger fits
MeltLedger provides source-linked review, optional AI suggestions, shipment reference comparisons, private snapshots and exports. It does not issue certificates, authenticate signatures, verify chemical or mechanical conformity, or give legal or engineering approval.
Use the tool to prepare a clear evidence record for the people responsible for those decisions. A practical first step is to review the fictional sample, then try a certificate you can independently check.
Fictional evidence record: matching fields do not close every requirement
| Field | Observation | Review note |
|---|---|---|
| Heat reference | PO-DEMO-42 and DEMO-17 both state H-204. | Record the checked page and line. Physical material identification remains a separate check. |
| Document type | The example order requests Type 3.2; DEMO-17 states Type 3.1. | Record the discrepancy and the responsible specialist. Do not relabel the PDF. |
| Technical acceptance | The report contains a table of test results. | Presence of a table is not a conformity assessment. Assign review against the applicable requirements. |
| Release decision | Heat and grade reference comparisons are complete. | Keep unresolved requirements visible. A software match status is not release authorization. |
Common questions
Does marking every field reviewed create a certified report?
No. It creates a record of your review decisions, not an independent certificate or approval.
Can MeltLedger upgrade a 3.1 certificate to 3.2?
No. Software extraction and review cannot perform the required inspection or certification process.
Can AI automate mill test report compliance verification?
It can support bounded review tasks, such as proposing source values. MeltLedger does not provide an overall compliance verdict. Define the applicable requirements, check each observation and keep technical acceptance and release with the responsible people.
Does a reviewed grade field confirm chemical or mechanical compliance?
No. It records a checked designation. MeltLedger does not assess test results against material-standard acceptance criteria.
What should I do when an order and the certificate specify different document types?
Record the exact requirement, stated type and source references, then refer the discrepancy to the responsible quality or inspection professional. Preserve the original; do not edit the document type to make it agree.
Sources and scope
LRQA EN 10204 Type 3.2 certification services
Primary description of specialist inspection services. The required document and process depend on your order and applicable requirements.
FROM READING TO REVIEWING
Check your first certificate.
Try 5 unique certificates free, then €49/month for 100 certificates and one user. Human review remains essential.
Start your free accountOr explore the fictional sample