Supplier Quality Surveillance (SQS): Definition, Scope & Process

What Is Supplier Quality Surveillance (SQS)?

Supplier Quality Surveillance (SQS) is the planned, risk-based independent oversight you place between a purchase order and a delivered item to ensure quality evidence is collected, verified, and closed before problems turn into cost, delays, or liability.

 

• SQS = risk-based oversight of supplier execution, not a KPI dashboard and not a one-off inspection.
• The core output of SQS is acceptance-grade evidence: traceable records that support decisions (accept / hold / reject).
• SQS spans the full chain: RFQ → PO → ITP/QCP → manufacturing → FAT → shipment → final dossier.
• Strong SQS is defined by coverage logic + trigger rules + closure discipline (NCR → CAPA → verified close-out).
• If you only track scorecards or only do occasional shop visits, you’re not doing SQS—you’re collecting fragments.

If you want a structured pathway (SQS + ITP + reporting), explore the course:
Vendor Inspection & Quality Surveillance Training

 

SQS in one sentence

Supplier Quality Surveillance (SQS) is a risk-based system that ensures supplier execution is independently verified through objective evidence, with clear gates (witness/hold points) and closed corrective actions before delivery.

 

SQS Abbreviations List (Supplier Quality Surveillance & Vendor Inspection Terms)

• SQS – Supplier Quality Surveillance
• RFQ – Request for Quotation
• PO – Purchase Order
• ITP – Inspection and Test Plan
• QCP – Quality Control Plan
• FAT – Factory Acceptance Test
• NCR – Nonconformance Report
• CAPA – Corrective Action and Preventive Action
• QA/QC – Quality Assurance / Quality Control
• QA – Quality Assurance
• QC – Quality Control
• QMS – Quality Management System
• SQM – Supplier Quality Management
• SQE – Supplier Quality Engineer
• NDT – Non-Destructive Testing
• MTC – Material Test Certificate
• EN – European Norm (European Standard)
• IR – Inspection Report
• KPI – Key Performance Indicator

 

What SQS is NOT (3 common misconceptions)

1) “SQS is just supplier KPIs and scorecards”

Scorecards are an outcome measurement tool. SQS is the execution oversight system that produces the evidence your scorecard depends on. If SQS exists only as a dashboard, it becomes lagging indicators without control.

For measurement and scorecard design, see: How To Build A Vendor Scorecard For SQS

2) “SQS is the same as vendor inspection”

Vendor inspection is typically event-based (e.g., FAT, final inspection, selected shop visits). SQS is program-based: it defines coverage across phases, trigger rules, and closure loops so you don’t discover problems at the end.

If you need the inspection baseline and terminology, read: Vendor Inspection Explained — Roles, QA/QC & Standards

3) “SQS is just vendor audit with another name”

A vendor audit evaluates the supplier’s management system and ability to comply (often periodic). SQS monitors the supplier’s actual execution on a specific PO/project, with evidence outputs and gates.

For the decision boundaries, see: Vendor Audit Vs Inspection | Differences & Use Cases

 

SQS vs QA/QC vs QMS vs SQM (quick comparison)

Term	What it is	Primary question it answers	Typical owner	Typical outputs
QA (Quality Assurance)	Prevention + system setup	“Are we set up to do it right?”	Quality management	Procedures, plans, audits
QC (Quality Control)	Verification + detection	“Does the output meet requirements?”	Inspectors / QC	Inspection results, test reports
QMS (Quality Management System)	Organization-wide quality system	“How is quality governed and improved?”	Leadership + QA	Policies, internal audits, KPIs
SQM (Supplier Quality Management)	Supplier lifecycle governance	“How do we qualify, develop, and manage suppliers?”	SQE/SQM	Qualification, ratings, improvement plans
SQS (Supplier Quality Surveillance)	PO/project execution oversight	“Do we have verified evidence the supplier executed correctly—on this job?”	SQS/SQE + project QA/QC	Surveillance plan, visit reports, NCR/CAPA closure, dossier

SQS is where “quality management” meets the real supply chain physics: materials, welds, heat numbers, tests, preservation, shipping, and documentation.

 

Where SQS sits in the RFQ → PO → delivery chain

Most supplier failures are predictable outcomes of weak gates and late discovery. SQS prevents late discovery by defining where and how you will know the truth.

1) RFQ stage: requirements must be surveillance-ready

If the RFQ/contract doesn’t define what evidence counts, SQS becomes negotiation-by-email mid-production. Surveillance-relevant requirements at RFQ typically include:

• Applicable codes/standards and edition dates
• Acceptance criteria (e.g., leakage limits, dimensional tolerances, coating DFT ranges)
• Documentation deliverables (MTC/EN 10204, NDT reports, calibration certificates, data books)
• ITP/QCP requirement and approval workflow
• Witness/hold points logic (what requires presence / approval)

2) PO award: convert requirements into inspection logic

After award, SQS converts contractual requirements into:

• a surveillance plan (coverage + triggers)
• an ITP/QCP that defines steps, responsibilities, and evidence

For practical templates and a step-by-step build flow, use: ITP & QCP in Vendor Inspection — 6-Step Builder + Templates

3) Manufacturing execution: surveillance proves control, not promises

This is where SQS creates value: not by “being there,” but by ensuring the supplier’s controls are:

• Implemented at the right steps
• Producing traceable evidence
• Not bypassed under schedule pressure

4) FAT / final inspection: confirm the package is acceptance-grade

FAT is not just testing. It confirms that:

• The build record is complete
• Test setups are valid
• Results meet acceptance criteria
• Deviations are dispositioned
• The dossier is coherent

5) Shipment and close-out: evidence must travel with the asset

Weak SQS often shows up here as:

• Missing documents
• Conflicting traceability
• Open punch items
• Nonconformities “agreed verbally” but never closed

SQS closes the loop by producing a final, defensible evidence package. For the reporting and dossier structure, see:
Vendor Inspection Reporting: IR, NCR & Final Dossier Guide

 

The evidence model: what “acceptance-grade” means

In inspection and procurement disputes, the deciding factor is rarely opinion—it’s whether you have objective evidence that is:

1. Traceable (links to item/heat/serial/PO/ITP step)
2. Verifiable (signed, dated, calibrated instruments, correct procedure)
3. Complete (covers required steps and hold points)
4. Consistent (no contradictions across reports, certificates, logs)
5. Closed (NCR/CAPA items verified, not “planned”)

Acceptance-grade evidence is the practical definition of “control” in a supplier environment.

 

Surveillance coverage levels (light / standard / intensive) + trigger rules

SQS should not be identical for every PO. It must be proportional to risk and consequence. A three-tier model works well:

Level 1 — Light Surveillance (low risk / proven supplier)

Use when:

• Items are non-critical
• Design/specification is stable
• Supplier performance history is strong

Typical coverage:

• Document review (ITP/QCP, procedures, certificates)
• One verification visit (or remote witness where appropriate)
• Targeted final inspection checks

Level 2 — Standard Surveillance (typical engineered procurement)

Use when:

• Equipment is function-critical or has safety impact
• Complexity is moderate
• Supplier history is mixed or uncertain

Typical coverage:

• Approved ITP/QCP with defined witness/hold points
• In-process verification at key steps (material ID, fit-up, NDT readiness, test preparation)
• FAT witness + dossier review gate

If you need a ready-to-use witness/hold structure, see:
Vendor Inspection ITP Template — Witness & Hold Points

Level 3 — Intensive Surveillance (high risk / new supplier / high consequence)

Use when:

• Equipment is safety-critical
• Consequence of failure is high
• Supplier is new or has a weak performance record
• Schedule pressure increases bypass risk

Typical coverage:

• More frequent presence (owner, client rep, or third-party)
• Expanded hold points (no proceed without release)
• Enhanced evidence requirements (calibration checks, re-tests, independent verification)
• Faster NCR escalation and closure discipline

Trigger rules (when to upgrade surveillance mid-stream)

Even a low-level PO should escalate when triggers occur:

• Rework/repair frequency increases
• Schedule compression creates bypass risk
• Failed tests or borderline results
• Certificate inconsistencies or traceability gaps
• Changes that affect requirements
• Uncontrolled subcontracting

SQS is not static; it’s a controlled adaptive system.

 

How SQS connects to NCR → CAPA → supplier rating (without becoming “just KPIs”)

SQS creates a disciplined feedback loop:

1. Detect a deviation (inspection finding / test failure / document mismatch)
2. Record it as an NCR (requirement reference + evidence)
3. Correct (immediate correction and containment)
4. Prevent recurrence via CAPA (root cause + systemic fix)
5. Verify closure (evidence-based close-out)
6. Update supplier performance (ratings reflect verified outcomes)

Scorecards measure outcomes, but SQS is the mechanism that makes outcomes real. If you want the KPI layer, continue with:
How To Build A Vendor Scorecard For SQS

 

Typical SQS deliverables

A well-run SQS program produces a coherent chain of artifacts:

• SQS plan (coverage level, triggers, roles, cadence)
• Approved ITP/QCP (with witness/hold points and evidence columns)
• Visit reports (what was observed, what was verified, what was blocked)
• Inspection reports (IR) (step-level verification)
• NCRs (requirement-linked nonconformities)
• CAPA records (root cause + verified close-out)
• Punch list / open items log (owned and tracked)
• Final dossier (certificates, NDT, tests, as-built, release evidence)

For a practical reporting workflow and dossier assembly guide, use:
Vendor Inspection Reporting: IR, NCR & Final Dossier Guide

 

Common failure modes of SQS programs (and how to avoid them)

“Paper SQS”

Plans exist, but evidence is thin. Fix this by defining:

• Minimum evidence per phase
• Required traceability fields
• Closure rules for deviations

“Late discovery culture”

SQS starts at FAT. Fix this by pushing gates earlier:

• Material identification
• Process readiness
• Test preparation verification

“No authority at hold points”

Hold points exist but no one enforces them. Fix this by:

• Defining approval owners
• Defining stop-work conditions
• Enforcing escalation time limits

“Open NCRs at shipment”

Supplier promises closure later. Fix this by enforcing:

• a dossier release gate (no shipment without close-out evidence unless formally waived)

 

Frequently asked questions

Is SQS only for large projects?

No. SQS scales down. Even small POs benefit from basic evidence gates (certificate checks, traceability verification, final release control).

Do we need on-site surveillance for SQS to work?

Not always. Some evidence can be verified remotely, but critical gates (tests, hold points, traceability) often require presence by the owner, client rep, or a qualified third party.

Who owns SQS—procurement or QA/QC?

SQS is cross-functional, but ownership must be explicit. Typically supplier quality owns the program, QA/QC owns verification rules, and procurement owns contractual leverage.

How is SQS different from expediting?

Expediting is schedule-focused. SQS is quality-evidence-focused. They can run together, but they are not interchangeable.

What’s the minimum you need for “real SQS”?

A defined coverage level, an approved ITP/QCP, traceable evidence expectations, and a nonconformity closure loop.

 

Next steps

If you want to implement SQS in a consistent, acceptance-grade way—linking ITP/QCP, witness/hold points, reporting, NCR closure, and final dossier release—start here:

Vendor Inspection & Quality Surveillance Training