Quality Management, Codes, Standards, and Specifications
Hierarchy of requirements
Know the difference between a standard (consensus method), a specification (project requirements), and a code (mandatory legal/regulatory rules). A procedure must trace to the governing standard, and the specification tightens or tailors it. Understand calibration block requirements, reference reflector types, and acceptance criteria classes.
Quality management covers document control, traceability, calibration records, and corrective action. A written procedure is only valid if it is approved, current, and followed. Records must allow reconstruction of the inspection.
Traps
- Treating a recommended practice as mandatory-know which documents are normative.
- Missing the requirement to qualify a procedure per the governing standard.
- Ignoring equipment calibration validity dates.
- Confusing acceptance criteria (accept/reject) with recording criteria (what to document).
Rule of thumb
When documents conflict, the more stringent applicable requirement governs, and the specification usually overrides the general standard for a specific project. Always verify revision status before applying acceptance criteria.