They should be detailed enough to clearly identify the actual material and special processes used for the part, without forcing reviewers to guess or cross-reference vague shorthand.
For Form 2, the practical standard is not “list everything imaginable.” It is “list enough to support objective traceability back to the engineering requirements and the actual manufacturing record.” If an entry is too generic, it creates avoidable risk during review, internal audit, customer verification, or later investigation.
In most cases, that means the entry should include the specific material or process designation used on the part and the applicable specification identifier. If revision level, source, or processor is needed to remove ambiguity in your environment or by customer flowdown, include it. If your company procedure, customer requirement, or digital FAI workflow defines a stricter convention, that local rule governs.
Materials: identify the material in a way that ties back to the drawing, BOM, certification, and receiving or lot records. Generic descriptions alone are usually not sufficient if multiple alloys, tempers, forms, or specs could fit the same plain-language name.
Special processes: identify the process by its applicable specification or controlled process reference, not just a broad label like heat treat, plating, or NDT.
Source traceability: include the approved processor or supplier when that is part of the required evidence trail or necessary to connect to certs and outside processing records.
Revision or issue status: include it when omission would make the entry ambiguous or when your FAI method requires alignment to controlled specification revisions.
If the drawing calls out a process in a very specific way, Form 2 should reflect that specificity. If the requirement is broad, your entry still needs to identify what was actually performed.
Material names with no specification reference where multiple compliant materials are possible
Process labels like “painted” or “anodized” with no controlled spec or process reference
Internal shorthand that only one planner or quality engineer understands
Entries that do not tie back to certs, router steps, supplier paperwork, or approved processor records
Over-detail is usually safer than under-detail, but it has costs. If teams manually copy long specifications, processor names, and revision strings into Form 2, transcription errors become more likely. That is common in brownfield environments where ERP, MES, QMS, and FAI software are not cleanly integrated.
Under-detail causes a different problem: the FAI may look complete while still being weak on evidence. That often surfaces later when someone tries to reconcile Form 2 against a drawing revision, cert package, purchase order, or outside processing record.
So the real objective is controlled specificity: enough detail to preserve traceability and reviewability, but ideally pulled from governed source data rather than retyped by hand.
If your plant uses a combination of ERP, paper routers, supplier cert packets, and a separate FAI tool, consistency depends heavily on master data quality and mapping discipline. Form 2 quality often degrades when material names in ERP do not match engineering callouts, or when outside processes are tracked differently across purchasing, quality, and production.
That is why full replacement is often not the practical answer. In regulated, long-lifecycle operations, replacing ERP, MES, QMS, and FAI processes at once can fail because of validation burden, downtime risk, integration complexity, and the need to preserve traceability across legacy records. In many cases, tighter data governance and better field-level integration are more realistic than a wholesale reset.
If you are unsure about a specific entry, use this test: could a qualified reviewer determine exactly what material or special process was required, what was actually used, and which records prove it, without relying on tribal knowledge? If not, the entry is probably not detailed enough.
Whether you're managing 1 site or 100, Connect 981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
Whether you're managing 1 site or 100, C-981 adapts to your environment and scales with your needs—without the complexity of traditional systems.
