Building Approved Supplier Lists That Hold Up

A properly governed approved supplier list, or ASL, is a controlled register of suppliers authorized for defined scopes of work. It establishes more than a vendor name and a purchasing preference. It identifies what the supplier is approved to provide, which standards and specifications apply, what conditions govern the approval, and when reassessment is due.

That scope discipline matters. A machining supplier may be qualified for noncritical structural components but not for pressure-retaining parts. A fabricator with a sound quality manual may still lack the welding procedures, personnel qualifications, NDE capability, or traceability controls needed for a particular project. Broad approvals create blind spots because they imply capability that has not been verified.

The ASL should connect directly to procurement controls, project specifications, inspection and test plans, and supplier surveillance activities. If purchasing can issue a purchase order outside those controls, the list is not functioning as a quality control. If quality cannot explain why a supplier remains approved, the list is not auditable.

Approval criteria should be established by the owner, EPC, or corporate quality function before supplier submissions arrive. Otherwise, evaluators will make inconsistent decisions based on personal experience, commercial urgency, or the apparent polish of a supplier's response.

The criteria need to be specific enough to produce repeatable decisions. They commonly address quality-system maturity, applicable certifications, technical capability, qualified personnel, control of special processes, calibration, material traceability, inspection resources, nonconformance control, corrective action, document retention, and sub-tier management. Depending on the work, they may also include cybersecurity, environmental requirements, export controls, safety performance, insurance, or financial viability.

For high-consequence supply, a certificate should be treated as supporting evidence, not conclusive proof. ISO 9001 certification may indicate that a management system has been assessed, but it does not confirm that the supplier can meet a project-specific code, customer specification, material documentation requirement, or turnover package standard . The approval file must close that gap.

Establish objective approval outcomes as well. A supplier can be approved without restriction, approved conditionally, placed on probation, rejected, or approved for a limited scope. Conditional approval is useful when a supplier has acceptable capability but must close defined gaps before receiving critical work. It is not a substitute for accepting unresolved risk because schedule pressure is high.

Few suppliers are perfect. The question is whether identified deficiencies are understood, contained, and corrected before they affect deliverables. A disciplined ASL process records each gap, assigns a required action, names the responsible party, sets a due date, and verifies closure with evidence.

Not every finding warrants disqualification. A late internal audit or incomplete training record may be correctable without preventing limited approval. Missing procedure qualifications, uncontrolled special processes, falsified records, unresolved repeat nonconformances, or an inability to maintain traceability are different. Those conditions can require rejection, suspension, or escalation to project leadership.

Approval conditions must flow into the purchase order and quality requirements. If a supplier is approved only for a specified manufacturing location, the order cannot be transferred to another facility without review. If the approval requires source inspection before shipment, that hold point must be visible in the inspection and test plan and release process. A condition stored only in a spreadsheet will eventually be missed.

Every supplier decision should leave an auditable record. At minimum, the file should identify the supplier, approved scope, evaluation criteria, evidence reviewed, risk classification, approval status, conditions, approver, effective date, expiration or reassessment date, and performance history. Where audits or corrective actions apply, their records should be linked to the decision.

This is not paperwork for its own sake. When a defect reaches a project site or a client asks why a supplier was selected, the organization needs a factual answer within hours, not a reconstruction based on email threads. A controlled approval file protects the project team, supports defensible procurement, and gives management a clear basis for escalation.

Jags Assurance approaches supplier qualification as an evidence-based control system: define the required standard, verify implementation, document findings, and track corrective actions to closure. That discipline is especially valuable when internal teams need independent capacity or when an approval decision carries material project exposure.

The practical test is simple: if the supplier's work were questioned after installation, could your team show exactly what was approved, why it was approved, what evidence supported the decision, and how performance has been monitored since? Build the list so the answer is yes before the purchase order is released.