Regulations, Contracts, and Requirement Precedence

Determine where a requirement comes from

Calibration work can be subject to several requirements simultaneously. A technician must identify their authority, scope, edition, and application before selecting a method. A familiar standard number does not prove that the document governs the current instrument. A procedure written for an electrical meter does not automatically apply to a legal-for-trade scale, a flight component, or a medical manufacturing process.

Statutory or regulatory requirements can be binding for an activity and jurisdiction. Contracts and customer specifications establish agreed obligations within that activity. Accreditation requirements govern the scope and claims made under a particular program. Consensus standards and manufacturer instructions provide methods and technical limits and can become mandatory when adopted by a governing requirement. Internal procedures translate applicable obligations into controlled work instructions. These categories help identify authority, but they do not resolve every conflict by themselves.

Resolve applicability and precedence

Start with the measurand and intended decision. Ask who will use the result and what requirement that decision must meet. Find the actual controlling documents rather than relying on an equipment label or an informal statement that the laboratory always uses one method. Verify versions and effective dates. A newly published standard can have a transition period in a program; a contract can specify a particular edition. Record the governing edition and resolve changes before work.

A customer cannot authorize the laboratory to disregard a binding legal requirement. Conversely, a technically useful voluntary method does not override a binding rule merely because it is newer or more precise. A stricter customer requirement can often coexist with a regulatory minimum when both can be met without conflict. When requirements are incompatible, stop the affected work and escalate to the person authorized to interpret the contract and applicable obligations. Do not silently choose the limit that produces a pass.

For an illustrative case, suppose an internal temperature-calibration procedure lists three points but the accepted customer order requires five points across the actual process range. No governing requirement prohibits the extra points. Contract review should identify capability, additional work, uncertainty, and the appropriate method before accepting the order. Three points cannot be reported as completion of five. If the customer agrees to a changed scope, retain the revised agreement and report the actual work.

Now suppose a hypothetical adopted requirement demands a particular legal verification method and an authorized status for a regulated instrument. An ordinary calibration certificate may provide useful measurement data but does not, by itself, establish that separate legal status. Identify the authorized route and avoid claiming permission to use an instrument for a regulated purpose when that permission has not been established.

Technical deviations and evidence

For an actual departure from a method, follow the applicable deviation process. ISO/IEC 17025 requires documented technical justification, authorization, and customer acceptance for actual method deviations. Using an already permitted equivalent standard is different from an unreviewed departure. Changing excitation, environmental limits, calculation software, or a fixture can affect uncertainty and may require method verification or validation appropriate to the change.

For example, a procedure calls for a four-wire resistance comparison but the available system supports only two-wire measurement. Extra display digits do not compensate for unknown lead resistance. Identify the changed measurand, bias, and uncertainty; establish whether a valid alternative exists and obtain required approval. If it cannot meet the requirement, revise scope honestly or decline that part of the job. Do not report the original four-wire method as performed.

The technical record links the request, controlling requirement, method and revision, actual equipment and conditions, uncertainty, approval, and report. If a defect is found after release, assess affected work through the nonconforming-work process. A paperwork correction alone does not resolve a physical measurement defect. Identify who authorizes work to resume and how the decision reaches the customer and laboratory staff.

Evaluate industry practice sources

Original equipment manufacturer manuals, consensus methods, national metrology guidance, technical literature, and Government-Industry Data Exchange Program (GIDEP) information are possible practice sources. Evaluate provenance, revision, applicability, and laboratory capability before adoption. A shared procedure or alert is useful input; its publication does not validate this laboratory’s execution. Verify a standard method in the actual facility and validate custom or modified methods for intended use. Retain evidence and make current authorized instructions available at the bench.

The exam skill is to determine which requirement applies and what action preserves valid results and honest scope. Distinguish regulation, contract, accreditation, and guidance. A universal ranking slogan cannot replace that analysis.