15.2 Interrelationships of Business Processes

15.2 Interrelationships of Business Processes (CQA BoK IV.B.2 — Understand)

Quick Answer: Organizations deliver quality through interrelated processes—including receiving, design, production, engineering, sales, marketing, and field support—often across multiple sites. Failures frequently arise at interfaces. Conflicting metrics and goals push local optimization that harms the system. At the Understand level, you must recognize these linkages and how they shape audit scope, evidence, and findings. Domain IV (~15% of scored items) expects program and business-system thinking beyond a single checklist.

Auditors who only “own the department they are in today” miss the story. A nonconforming product arriving at a customer may have roots in sales promising an unvalidated option, design change not flowed to production, receiving accepting wrong material, or field feedback never reaching engineering. IV.B.2 trains you to see the system.

---

Why Process Interrelationships Matter in Auditing

A process approach (familiar from ISO 9001 thinking and quality management principles) treats the organization as a network of activities that transform inputs to outputs for customers and other stakeholders. Interrelationships matter because:

1. Handoffs create defects, delays, and lost information.
2. Upstream decisions constrain downstream capability (e.g., design tolerances vs. process capability).
3. Downstream signals (complaints, returns, warranty) should feed upstream improvement.
4. Metrics at one node can sabotage another node’s ability to meet customer requirements.

Scenario — understand the interface.
Production is cited for shipping the wrong configuration. Tracing shows sales entered a custom option not in the approved product catalog; engineering never released a BOM revision; production built from an obsolete traveler. The nonconformity is real in shipping, but the system failure is sales–engineering–production interrelationship and configuration control across processes.

---

Core Business Processes Auditors Must Map

BoK IV.B.2 highlights major process families. You do not need to be a specialist in every function, but you must understand what each contributes and how it couples to quality outcomes.

Receiving (incoming material / inbound logistics)

• Inputs: purchase orders, specifications, approved supplier lists, certificates, inspection plans.
• Quality role: verify identity, quantity, conformity; control nonconforming material; protect traceability.
• Links: purchasing/supplier quality (upstream), production/warehouse (downstream), finance (inventory accuracy).

Failure modes at interfaces: production uses material before release; certificates accepted without verification for critical parts; rejected material not segregated and later kitted.

Design (product/service design and development)

• Inputs: customer needs, regulatory requirements, lessons learned, risk analysis.
• Quality role: design controls, design review, verification/validation, design transfer, design change.
• Links: sales/marketing (voice of customer), engineering/production (manufacturability), field support (use data).

Interface risk: marketing launches features design has not validated; design changes not transferred to work instructions and suppliers.

Production (operations / service delivery)

• Inputs: planned orders, controlled documents, qualified processes, trained people, released material.
• Quality role: process control, in-process inspection, identification/traceability, nonconforming product control.
• Links: receiving and planning (inputs), engineering (process capability), sales (schedule promises), field (failure feedback).

Engineering (process/equipment/manufacturing engineering and technical support)

Often the bridge between design intent and production reality:

• Process validation, tooling, equipment qualification, work instruction accuracy, capability studies.
• Change control for process parameters and equipment.
• Links tightly to design, production, maintenance, and quality control labs.

Sales

• Contract review: can we meet requirements for quality, quantity, delivery, and special terms?
• Order accuracy and promise dates.
• Interface risk: selling “yes” to requirements the QMS cannot meet; failing to flow customer-specific requirements to operations.

Marketing

• Claims, labeling concepts, market requirements, competitive positioning.
• Interface risk: promotional claims exceed validated performance; packaging/label artwork not controlled through change processes shared with design and regulatory.

Field support (service, installation, technical support, complaint intake)

• Installation quality, service repairs, spare parts, complaint capture, return material authorization.
• Critical feedback loop to design, production, and suppliers.
• Interface risk: field failures coded poorly so engineering never sees the true failure mode; service workarounds never enter CAPA.

---

Material, Information, and Decision Flows

When you understand interrelationships, you audit three flows:

1. Material/product flow — physical transformation and movement.
2. Information flow — specs, orders, changes, quality records, metrics.
3. Decision flow — who can accept risk, approve changes, release product, escalate suppliers.

Many “quality problems” are information-flow failures: the right decision maker never received accurate, timely data. Auditors should sample whether change notices, customer complaints, and nonconforming material reports actually reach the processes that must act.

Scenario.
A dimensional failure appears in assembly. Production blames the machine. Engineering tweaks the fixture. Receiving data later shows a supplier lot with borderline material hardness that was accepted under a broadened skip-lot plan after purchasing pressed for cost. The interrelationship: purchasing/supplier quality metrics (cost and delivery) conflicted with production’s capability needs; information about material risk did not trigger enhanced inspection or process adjustment.

---

Multi-Site Organizations

Multi-site and multi-national systems multiply interface complexity:

Audit program implications (ties to IV.A multi-site resource realities):

• Sample interfaces between sites, not only excellence within one showcase plant.
• Verify deployment of corporate requirements and effectiveness locally.
• Follow a product family or customer complaint across sites when ownership is split.
• Watch for “audit tourism” that only visits high-performing locations.

Scenario — multi-site understand.
Corporate design issues a safety-related labeling change. Site 1 implements in two weeks; Site 2 waits for local translation and ships old labels for six weeks. Customer receives mixed labels. The finding is not only Site 2 document control—it is a multi-site change deployment interrelationship failure between corporate design, regulatory/labeling, and site operations.

---

Conflicting Metrics and Goals

IV.B.2 explicitly calls out conflicting metrics/goals. Local KPIs can be individually rational and collectively destructive.

How auditors recognize metric conflict

• Interview goals vs. observed behavior (“We are measured on… so we…”).
• Compare dashboards across functions for opposing incentives.
• Trace decisions at interfaces where one metric “won.”
• Look for rework, expedites, firefighting, and hidden factories as symptoms.

Scenario — conflicting goals.
Purchasing is bonused on cost savings; quality is measured on PPM. Purchasing awards a new supplier mid-quarter without full qualification because savings hit the bonus. Production absorbs variation with 100% inspection. External failure costs rise next quarter. An auditor who understands interrelationships reports the systemic incentive conflict, not only “missing supplier file checklist item 3.”

Understand-level exam items often ask you to identify which interface or metric conflict best explains a failure pattern—not to invent a financial model.

---

Auditing Across Processes: Practical Patterns

Forward and backward tracing

• Forward: Start at order/contract → design/BOM → procurement → receiving → production → ship → field.
• Backward: Start at complaint/return/nonconformance → reverse to process origins.

These strategies (also in audit performance tools) are especially powerful for interrelationship questions.

Horizontal vs. vertical sampling

Writing findings that respect interrelationships

Good systemic finding structure:

• State the requirement (customer, standard, internal procedure).
• State the evidence spanning processes.
• State the effect on product/customer/risk.
• Avoid blaming only the last person who touched the product when evidence shows multi-process failure.

---

Link to Other BoK Topics

• I.A Audit types: Process and system audits are designed to reveal interrelationships better than isolated product checks alone.
• II.A.6 Strategies: Forward/backward tracing operationalizes IV.B.2 understanding.
• IV.B.1 Management tool: Strategy deployment fails when process interfaces are broken.
• IV.B.3 Cost of quality: Interface failures show up as appraisal spikes, internal scrap, and external failures.
• III.E Interviewing: Cross-functional interviews expose conflicting goals.

---

Key Exam Anchors

• IV.B.2 is Understand: know major process relationships (receiving, design, production, engineering, sales, marketing, field support), multi-site effects, and conflicting metrics/goals.
• Quality problems often live at handoffs and in incentive conflicts.
• Multi-site: inconsistent deployment and split ownership are classic interrelationship risks.
• Trap: stopping at the department that shipped the defect when the chain of evidence points upstream/downstream.
• Use tracing and horizontal sampling to make interrelationships visible in evidence.