Operational Planning and Control

Introduction

Operational planning and control is the part of a quality management system (QMS) that converts customer, statutory, regulatory and organizational requirements into controlled work. It answers a practical question: How will the organization consistently create and deliver conforming products and services?

In ISO 9001:2015, operational control is primarily addressed in Clause 8, supported by planning, competence, documented information, performance evaluation and improvement requirements. It is not limited to production. It includes customer communication, requirements review, design and development, control of externally provided processes, production and service provision, release, nonconforming outputs and post-delivery activities.

Operational planning must therefore be viewed as an interconnected system rather than a collection of departmental procedures. A purchasing decision may affect design risk; design changes may affect production capability; production records may determine traceability; and release decisions may influence legal compliance and customer safety.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Translate customer and regulatory requirements into operational controls.
2. Plan and control product and service design and development.
3. Qualify suppliers and control externally provided processes.
4. Establish effective controls for production, service delivery, release and preservation.
5. Design traceability and nonconforming-output systems.
6. Apply lifecycle thinking, risk-based thinking and process-based management to operations.
7. Evaluate the effectiveness and limitations of operational controls.

1. Operational Planning as a Process System

Operational planning begins with intended results and ends with evidence that those results were achieved. A useful control logic is:

requirements → risks and resources → controlled process → verification → release → feedback and improvement

Figure: The operational planning and control cycle.

Operational controls should specify, as appropriate:

• what is to be achieved;
• acceptance criteria and performance indicators;
• required people, infrastructure, environment and information;
• process sequence and interfaces;
• inspection, testing, validation or monitoring methods;
• responsibilities and authorities;
• records that demonstrate conformity; and
• actions for risks, changes and nonconforming outputs.

A control is effective only when it changes behaviour or detects failure early enough for action. A procedure that exists but is not understood, resourced or followed is not an effective control.

2. Determining and Reviewing Customer Requirements

2.1 Sources of requirements

Requirements may be explicit or implicit. They can arise from:

• customer specifications, drawings, contracts and purchase orders;
• stated delivery, packaging, warranty and support expectations;
• statutory and regulatory obligations;
• industry codes and technical standards;
• intended use and reasonably foreseeable misuse;
• organizational commitments and capability limitations; and
• requirements generated by the organization itself.

A product may comply with a drawing and still fail because delivery, installation, cybersecurity, labeling or service requirements were overlooked. Requirement determination must therefore consider the whole customer experience and the product or service lifecycle.

2.2 Review before commitment

Before accepting an order or contract, the organization should establish that requirements are defined, differences are resolved, and it has the capability to meet them. The review should address feasibility of technology, capacity, competence, special processes, measurement capability, supply availability, legal obligations, delivery dates and post-delivery support.

For recurring orders, a full review may not need to be repeated if requirements are unchanged and the organization has a controlled method for confirming this. However, changed specifications, unusual demand, new regulations or capacity constraints should trigger renewed review.

2.3 Customer communication

Communication controls should define who communicates, through which channel, and how information is recorded. Relevant communication includes quotations, order confirmation, changes, complaints, feedback, emergency notices, property supplied by customers and post-delivery instructions.

A practical tool is a contract-requirements matrix:

The matrix should be maintained as requirements change and should link requirements to verification activities.

3. Design and Development Controls

Design and development controls are needed when the organization is responsible for establishing or changing product or service characteristics. Design includes service design, software configuration, process design and engineering changes—not only physical products.

3.1 Design planning

Planning should determine stages, reviews, verification, validation, responsibilities, interfaces, resources and required documented information. The depth of control should be proportional to complexity, novelty, safety significance and risk.

A useful distinction is:

• Design input: what the product or service must achieve.
• Design output: what is produced from the design process, such as drawings, specifications, software requirements, work instructions or service scripts.
• Verification: evidence that outputs meet specified inputs.
• Validation: evidence that the resulting product or service meets intended use or application requirements.

Verification may involve calculation review, design inspection, simulation, code review or prototype testing. Validation may require field trials, user acceptance testing, clinical evaluation, pilot service delivery or operational performance testing. Verification asks, “Did we design it according to the specification?” Validation asks, “Does it work for its intended use?”

3.2 Design inputs and outputs

Inputs should be complete, unambiguous and non-conflicting. They may include functional and performance requirements, previous design information, applicable standards, lessons learned, safety requirements, environmental conditions, maintainability and cybersecurity.

Outputs should be suitable for subsequent processes. They should provide information for purchasing, production, inspection, installation, servicing and acceptance. Outputs should identify critical characteristics and acceptance criteria where necessary.

3.3 Reviews, verification and validation

Design reviews are structured evaluations by appropriate participants. They should identify problems, clarify assumptions and assign actions. Independence is valuable: a person who did not create the design may identify risks that the designer overlooks.

Validation conditions should represent actual or reasonably foreseeable operating conditions. A laboratory test that excludes temperature, user behaviour, network load or maintenance conditions may provide false confidence.

3.4 Design changes

Changes should be identified, reviewed and controlled before implementation. Evaluation should consider effects on conformity, safety, interfaces, regulatory approval, already delivered products and dependent processes. Approved changes require updated specifications, software versions, training, supplier instructions and records.

Configuration management is particularly important for software-intensive products. Version identification, access control, change authorization and rollback capability reduce the risk of using obsolete or unauthorized configurations.

4. Control of Externally Provided Processes, Products and Services

Outsourcing does not transfer final responsibility for conformity. The organization remains accountable for ensuring that externally provided outputs meet requirements.

4.1 Supplier qualification

Supplier selection should be based on risk and capability rather than price alone. Evaluation may consider technical competence, certification, process capability, capacity, financial stability, delivery performance, regulatory history, information security, ethical conduct and environmental performance.

Supplier qualification can include questionnaires, audits, sample approval, first-article inspection, reference checks and performance trials. The evidence required should be proportionate to the consequence of failure. A supplier of office stationery does not normally require the same controls as a supplier of safety-critical castings.

4.2 Types of external provision

Three situations require attention:

1. An external provider supplies an output that becomes part of the organization’s product or service.
2. An external provider delivers an output directly to the customer on the organization’s behalf.
3. An external provider performs a process, or part of a process, that the organization has chosen to outsource.

The third situation is often misunderstood. Outsourcing a process does not remove the need to define process criteria, monitor performance and control changes.

4.3 Purchasing information and monitoring

Purchase information should communicate applicable specifications, approval requirements, competence requirements, inspection arrangements, equipment requirements, records, confidentiality, change notification and right of access for verification or audit.

Supplier performance may be monitored through defect rates, on-time delivery, responsiveness, audit findings, corrective-action effectiveness and total cost of poor quality. A composite supplier score is useful only if its components are defined and weighted rationally. Excessive reliance on a single score can hide serious but infrequent failures.

4.4 Risk-based supplier control

A simple prioritization model may classify suppliers using consequence, likelihood and detectability. If a numerical risk-priority method is used, the organization must define its scales and avoid treating the resulting number as an objective truth. Risk ranking supports judgment; it does not replace it.

Controls can include incoming inspection, certificates of conformity, source inspection, supplier process audits, delegated release, batch testing, approved supplier lists and periodic requalification. Reduced inspection may be justified by demonstrated capability, but it should be reversible when performance deteriorates.

5. Production and Service Provision

Production and service provision should occur under controlled conditions. Controls commonly include documented information, suitable infrastructure, competent personnel, calibrated or verified monitoring resources, defined acceptance criteria, mistake-proofing, release status, identification and control of changes.

5.1 Work instructions and competence

Instructions should be available where work occurs and should describe critical steps without creating unnecessary administrative burden. Competence includes technical knowledge, practical skill, judgment and awareness of consequences. Training attendance alone does not prove competence; observation, testing, supervised performance or output results may be needed.

5.2 Special processes

Some processes cannot be fully verified by later inspection because deficiencies become apparent only during use. Examples include welding, sterilization, heat treatment, adhesive bonding, software compilation and certain service interactions. Such processes require validation of capability, qualified personnel, approved equipment, defined parameters and retained evidence.

5.3 Identification and traceability

Identification distinguishes products, services, batches, lots, configurations, status and ownership. Traceability is the ability to follow the history, application or location of an object through specified stages.

Traceability depth should be risk-based. It may include raw-material heat numbers, production dates, operator and equipment identification, software version, inspection results, shipment destination and installation record. Full traceability is valuable but costly; organizations should define what must be traced, why, and for how long.

5.4 Customer or external-provider property

Property may include materials, tooling, data, intellectual property, premises, equipment or personal information. It should be identified, protected and safeguarded. Loss or damage should be reported and recorded. Digital property requires additional controls such as access management, backup, encryption and secure deletion.

5.5 Preservation

Preservation protects conformity during internal processing and delivery. It may include handling, contamination control, packaging, storage, environmental control, shelf-life management, transport protection and segregation. Preservation is not merely packaging: temperature-sensitive pharmaceuticals, electrostatic-sensitive electronics and confidential digital files require different controls.

5.6 Post-delivery activities

Post-delivery obligations may include installation, warranty, maintenance, updates, training, product recall, technical support and disposal. The organization should consider legal requirements, potential undesired consequences, product life, customer feedback and lessons from failures.

Lifecycle thinking extends control beyond the moment of sale. It also supports environmental and social responsibility by considering resource use, repairability, reuse, disposal, supplier practices and information security across the value chain.

6. Release of Products and Services

Release should not occur until planned arrangements have been satisfactorily completed, unless an authorized person approves the release and, where applicable, the customer accepts it. Evidence should identify what was checked, against which criteria, by whom and with what result.

A release record might include product or service identity, inspection results, deviations, equipment status, reviewer authorization and date. Electronic systems should prevent unauthorized release and preserve audit trails.

Release is a decision, not simply the last inspection. It should incorporate process records, supplier conformity, change status, unresolved deviations and customer-specific requirements. Where safety or regulatory compliance is involved, release authority should be independent and clearly assigned.

7. Nonconforming Outputs

A nonconforming output is an output that fails to meet a requirement. It may be detected during receipt, processing, final inspection, delivery, installation or use. Controls should prevent unintended use or delivery and should define identification, segregation, disposition, authorization and records.

Possible dispositions include:

• correction or rework;
• concession or acceptance under deviation authorization;
• segregation, return or suspension;
• reclassification for another legitimate use; and
• scrap or destruction.

Reworked outputs should be reverified against defined criteria. Concessions should be approved by authorized persons and, when required, by the customer or regulator. A concession must not disguise a systemic problem or undermine safety.

The organization should also address consequences after delivery. This may require notification, replacement, recall, field correction, software patching or customer support. Nonconformity data should feed corrective action and management review.

8. Measuring Operational Effectiveness

Operational controls should be evaluated using measures connected to intended results. Examples include first-pass yield, defect escape rate, on-time-in-full delivery, supplier defect rate, warranty claims, process cycle time, complaint recurrence, rework cost and release delays.

A basic first-pass yield is:

Here, FPY is first-pass yield and both quantities must refer to the same defined population and period. The measure is meaningful only when “pass” and “rework” are consistently defined. A high FPY can still coexist with poor customer outcomes if inspection criteria are weak or requirements are incomplete.

Worked example

A service centre processes 2,400 claims. Of these, 2,208 are completed correctly without rework. Therefore:

The remaining 192 claims require rework or correction. Management should not conclude that performance is acceptable from 92% alone; it should examine claim complexity, customer impact, processing time and error severity.

Operational metrics should be balanced. Speed, cost and productivity measures should be considered with conformity, safety, employee competence, customer experience and sustainability indicators.

9. Integrated Application: Illustrative Case of a Medical-Device Manufacturer

Background

MedSure Devices, a fictional manufacturer, produces infusion pumps for hospitals. The company outsources circuit-board assembly and software testing while performing final assembly and release internally.

Problem

A field complaint revealed intermittent pump shutdowns. Investigation found that a supplier had changed a capacitor without notifying MedSure. The purchasing system recorded supplier approval but did not link component changes to design approval. Traceability could identify the production batch but not the exact supplier lot used in every pump.

Analysis

The failure involved several connected weaknesses:

• supplier controls focused on delivery and price rather than change notification;
• design-change control did not cover externally initiated component changes;
• purchasing information lacked explicit approval requirements;
• traceability was incomplete at the component-to-unit level;
• software and hardware configuration records were not integrated; and
• release inspection could not reliably detect an intermittent field failure.

Approach and solution

MedSure classified the capacitor as a critical component, revised supplier requirements and required written approval before any material, process or source change. It introduced supplier process audits and periodic first-article verification. The enterprise resource planning system was configured to record component lot numbers against pump serial numbers.

Design engineering added a formal change-impact review covering safety, regulatory submissions, validation status and field inventory. Production introduced barcode scanning and a controlled configuration record linking hardware revision, firmware version and test results. The release process required confirmation that the approved configuration was used.

Outcome

The organization contained affected inventory, notified relevant customers, replaced suspect units and completed a controlled revalidation. Subsequent audits found that supplier changes were identified earlier and traceability retrieval time fell substantially. The case also demonstrated that inspection at final release could not substitute for upstream design, supplier and configuration controls.

Learning points

1. Outsourced processes remain part of the organization’s QMS.
2. Supplier change control is a design and operational issue, not merely a purchasing issue.
3. Traceability should be designed around risk and potential containment needs.
4. Release evidence must address configuration, not only physical inspection.
5. Lifecycle thinking includes field performance, correction and customer communication.

10. Governance, Ethics and Contemporary Issues

Operational control has ethical dimensions. Organizations should not knowingly ship unsafe outputs, conceal deviations, manipulate inspection records or pressure employees to bypass controls. Quality records must be accurate, attributable, protected and retained for appropriate periods.

Regulated industries may require additional controls for validation, electronic records, product safety, data protection and reporting. ISO 9001 certification does not itself demonstrate compliance with every sector regulation.

Digitalization creates opportunities and risks. Artificial intelligence can support demand forecasting, visual inspection, predictive maintenance, supplier-risk analysis and document retrieval. However, AI outputs require validation, human oversight, data governance, cybersecurity and controls against bias or model drift. An automated inspection system may produce impressive accuracy in test conditions yet fail when materials, lighting or product variants change.

Best practice is to treat technology as a controlled process: define intended use, acceptance criteria, training data, monitoring, change control, access rights, fallback arrangements and accountability. The organization must remain able to explain and challenge consequential decisions.

11. Implementation Guidance

A robust implementation sequence is:

1. Map the customer-to-delivery value stream.
2. Identify applicable customer, statutory and regulatory requirements.
3. Determine critical characteristics and process risks.
4. Assign process owners, authorities and resources.
5. Establish supplier qualification and monitoring criteria.
6. Define design, change, verification and validation controls.
7. Create production, service, release, traceability and preservation controls.
8. Define nonconformity containment and escalation rules.
9. Select balanced performance measures.
10. Audit the system using evidence from actual orders, changes, suppliers and released outputs.
11. Use complaints, failures, audit findings and operational data for improvement.

Controls should be neither superficial nor excessive. Overly weak controls permit failure; overly bureaucratic controls encourage workarounds and obscure important risks. The appropriate level is the level that reliably prevents, detects or contains unacceptable failure at reasonable cost.

Challenges and Limitations

Operational planning is difficult when requirements are ambiguous, demand is volatile, products are customized, suppliers are global or processes are knowledge-intensive. Service outputs may be intangible and produced in interaction with the customer, making conformity harder to define. Small organizations may lack specialist resources for supplier audits, validation or data analysis.

Risk-based controls also have limitations. Risk assessments can be biased, incomplete or based on poor data. Numerical rankings may create false precision. Audits are samples and cannot prove that every transaction conforms. Certification provides external assurance about a management system, not a guarantee that every product is defect-free.

These limitations reinforce the need for competent judgment, transparent assumptions, multiple sources of evidence and continual review.

Chapter Summary

Operational planning and control translates requirements into controlled processes and objective evidence. Effective control begins with complete customer and regulatory requirements, continues through design, sourcing, production and service delivery, and extends to release, post-delivery support and end-of-life considerations. Design controls distinguish inputs, outputs, verification, validation and controlled changes. External providers must be qualified and monitored according to risk, and outsourced processes remain the organization’s responsibility. Production and service controls require competent people, suitable resources, validated special processes, identification, traceability, preservation and protection of property. Release requires authorized evidence of conformity. Nonconforming outputs must be contained, dispositioned and used as inputs to improvement. Lifecycle thinking, ethical governance, reliable data and carefully controlled technology strengthen the QMS but do not replace professional judgment.

Key Terms

Operational planning: Determining how processes will achieve intended quality results.

Acceptance criterion: A condition that an output must satisfy to be accepted.

Contract review: Evaluation of requirements and capability before commitment.

Design input: Requirement used as the basis for design.

Design output: Result of design that provides information for subsequent processes.

Verification: Confirmation that specified requirements have been met.

Validation: Confirmation that requirements for intended use or application have been met.

Configuration management: Control of product identity, versions and authorized changes.

External provider: Organization or person supplying a product, service or process.

Supplier qualification: Evaluation demonstrating a provider’s capability to meet requirements.

Special process: Process whose results cannot be fully verified by subsequent inspection.

Traceability: Ability to follow the history, application or location of an output.

Preservation: Protection of conformity during processing, storage and delivery.

Release: Authorized decision that requirements for an output have been met.

Nonconforming output: Output that fails to meet a requirement.

Concession: Permission to use or release a nonconforming output under specified conditions.

Lifecycle thinking: Consideration of impacts and controls across stages of an output’s life.

First-pass yield: Percentage of outputs meeting requirements without rework at the first pass.

Review Questions

Short Answer Questions

1. Why is operational planning broader than production control?
2. Distinguish design verification from design validation.
3. What information should normally be included in purchasing requirements for a critical supplier?
4. Why are special processes subject to validation?
5. State four possible dispositions for a nonconforming output.

Long Answer Questions

1. Explain how customer requirements should be determined, reviewed and communicated throughout an organization.
2. Discuss a risk-based framework for qualifying and monitoring external providers.
3. Explain the relationship among identification, traceability, preservation and release.
4. Describe how design changes should be controlled from proposal through implementation and post-implementation review.
5. Critically evaluate the role of lifecycle thinking in operational planning and control.

Analytical / Application Questions

1. A manufacturer has good final inspection results but frequent field failures. Analyze which upstream operational controls may be weak and propose an investigation plan.
2. Design a supplier-control strategy for a company that outsources a safety-critical process but purchases low-risk packaging from another supplier. Justify the different control levels.
3. A service organization reports a first-pass yield of 98% but receives increasing complaints. Analyze why the metric may be misleading and recommend a balanced measurement set.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes design verification from design validation?

A. Verification confirms intended use; validation confirms design inputs.

B. Verification confirms outputs meet inputs; validation confirms suitability for intended use.

C. Verification applies only to suppliers; validation applies only to customers.

D. Verification occurs after delivery; validation occurs before design begins.

Correct Answer: B. Verification confirms outputs meet inputs; validation confirms suitability for intended use.

Question 2

Which action best demonstrates effective control of an outsourced process?

A. Allowing the provider to define all requirements independently

B. Removing the process from internal audits because it is external

C. Defining criteria, monitoring performance and controlling provider changes

D. Selecting the lowest-cost provider without qualification

Correct Answer: C. Defining criteria, monitoring performance and controlling provider changes

Question 3

A service centre processes 2,400 claims and 2,208 pass without rework. What is the first-pass yield?

A. 88%

B. 90%

C. 92%

D. 96%

Correct Answer: C. 92%

Question 4

What is the primary purpose of traceability?

A. To eliminate the need for inspection

B. To follow the history, application or location of an output

C. To guarantee that every supplier is certified

D. To replace customer communication

Correct Answer: B. To follow the history, application or location of an output

Question 5

Which is an example of a special process?

A. A process whose results can be completely verified by final inspection

B. A process requiring no competent personnel

C. A process whose deficiencies may become apparent only during use

D. A process performed only by a customer

Correct Answer: C. A process whose deficiencies may become apparent only during use

Question 6

Before accepting a customer contract, an organization should primarily determine whether:

A. The customer has selected the cheapest quotation

B. Requirements are understood and the organization can meet them

C. All future complaints have been eliminated

D. The supplier has completed production

Correct Answer: B. Requirements are understood and the organization can meet them

Question 7

Which control is most directly associated with unintended release of nonconforming output?

A. Status identification and authorized disposition

B. Increasing advertising expenditure

C. Removing acceptance criteria

D. Avoiding production records

Correct Answer: A. Status identification and authorized disposition

Question 8

Why should supplier controls be proportional to risk?

A. All suppliers have identical processes

B. Control effort should reflect the consequence and likelihood of provider failure

C. High-risk suppliers never require monitoring

D. Low-risk suppliers must always be audited monthly

Correct Answer: B. Control effort should reflect the consequence and likelihood of provider failure

Question 9

Which statement about a concession is correct?

A. It automatically makes a nonconforming output conforming

B. It is permission to use or release an output under specified authorized conditions

C. It eliminates the need to record the nonconformity

D. It is applicable only to office supplies

Correct Answer: B. It is permission to use or release an output under specified authorized conditions

Question 10

Which practice best supports responsible use of AI in quality inspection?

A. Using the model without validation after deployment

B. Allowing the model to change acceptance criteria autonomously

C. Defining intended use, monitoring performance and retaining human accountability

D. Deleting all records of model decisions

Correct Answer: C. Defining intended use, monitoring performance and retaining human accountability