Key Takeaway: Use “Mckenna 1993” as a Decision Lens, Not a Standalone Rule

When teams cite Mckenna 1993, they are typically pointing to an organizing principle—how to structure evaluation, document assumptions, and improve decision traceability—rather than a literal checklist that applies unchanged to every modern procurement case. In practical terms, procurement leaders often reference the idea behind such work to justify a repeatable approach to supplier assessment, documentation quality, and governance. To use this effectively, align the concept with current audit expectations, risk management, and internal compliance requirements, then translate it into policies your organization can actually operate.

Because the citation format “Mckenna 1993” can appear in different professional contexts, this article treats it objectively as a reference point for methodological thinking. Readers will find a step-by-step guide, a comparison table of operational options, and practical conditions for implementation—so that your sourcing outcomes remain defensible, consistent, and aligned with contemporary quality systems.

What “Mckenna 1993” Usually Represents in Procurement Conversations

In procurement and supplier governance, a citation like Mckenna 1993 is commonly used as shorthand for a broader framework: define what “good” looks like, build a structured assessment process, record decision rationale, and reduce variability between evaluators. Over time, organizations adapt these ideas into procurement SOPs, quality agreements, supplier scorecards, and audit planning.

From an industry-expert standpoint, the very valuable part is rarely the author-date reference itself. Instead, it’s the discipline behind it: careful scoping, transparent criteria, and a repeatable evaluation workflow.

Why Landmark References Still Matter (And Where They Can Mislead)

Mckenna 1993 is often cited because early methodological contributions helped standardize how teams think about evaluation and evidence. That said, procurement environments have evolved. If your team treats an older concept as if it automatically covers modern requirements—data security, traceability mandates, regulatory changes, ESG-related due diligence expectations, and supply continuity analysis—you risk gaps.

An expert approach is to use Mckenna 1993 as a “decision lens” and then map it to current standards, internal risk registers, and verifiable supplier documentation. Where modern policy requires additional evidence, you supplement rather than assume.

Practical Evaluation: Turning Citation-Based Thinking Into Supplier Assessment

Teams often struggle not with evaluation effort, but with evaluation consistency. Two evaluators can reach different conclusions if they prioritize different evidence or interpret scoring scales differently. The conceptual contribution implied by Mckenna 1993—structured criteria, documented assumptions, and audit-ready rationale—helps reduce that drift.

To apply this lens, procurement leaders should ensure the evaluation process includes:

• Clear scope: what product/service category is being evaluated, and for which intended use.
• Defined criteria: quality capability, process control, delivery performance evidence, and governance maturity (as appropriate to the spend).
• Documented evidence requirements: what the supplier must submit and in what format.
• Decision traceability: how you reached the final recommendation, including mitigations for gaps.
• Ongoing review triggers: what changes require re-evaluation (e.g., material sourcing changes, plant moves, major nonconformities).

Industry-Neutral Context: Quality, Risk, and Auditability

Even when “Mckenna 1993” is referenced only informally, it points toward the larger operational triad that dominates supplier governance today: quality, risk, and auditability. Very mature procurement systems rely on some combination of quality management discipline and risk-based thinking. The auditability aspect—being able to show why a supplier was selected or continued—often becomes decisive during internal reviews, regulatory checks, customer audits, or dispute resolution.

To keep claims grounded, this article avoids unverified performance figures. Instead, it focuses on process design and governance practices that align with widely used management system concepts.

Procurement Decision Path: How to Reduce Variability Between Teams

If you want “Mckenna 1993” to improve outcomes rather than become a citation that sits in documents, implement a decision path that forces clarity. In practice, that means:

1. Pre-define scoring guidance so evaluators interpret criteria consistently.
2. Require evidence by criterion (e.g., process controls, test/inspection approach, change management practices).
3. Use risk tiers so you don’t apply the same depth of assessment to every low-impact spend category.
4. Capture rationale explicitly, especially when a supplier receives partial approvals or conditional acceptance.
5. Set review cycles and triggers that reflect actual risk exposure.

This is where the “Mckenna 1993” mindset—structure plus traceability—translates into measurable operational discipline.

What “Price” and “Supplier Details” Mean in a Defensible Framework

Procurement leaders frequently ask how price and supplier details should be integrated into supplier evaluation. The very defensible approach is to treat price as one input, not the sole determinant—especially when quality or continuity risk exists.

Practically, price must be interpreted alongside:

• Cost-to-serve considerations (how delivery volumes, packaging requirements, or customization affect true cost).
• Quality assurance costs that you either rely on from the supplier or must perform internally.
• Risk of rework or nonconformance, which is often more expensive than the initial unit price.
• Change management stability, which affects reliability of supply and compliance consistency.

Supplier details should be evaluated for verifiability. In many organizations, “details” that matter are not just basic identifiers; they include documented processes, historical performance evidence (where appropriate and non-controversial), and the supplier’s demonstrated ability to manage change.

To make this more concrete, consider two suppliers offering the same service at different rates. Supplier A’s quote includes fewer operational guarantees; Supplier B includes documented inspection points, a defined incident escalation process, and evidence of past delivery stability. If your process treats price as an isolated criterion, you may choose Supplier A and later discover that the “extra cost” will appear as internal rework, schedule delays, or compliance remediation. A defensible framework prevents this by requiring evaluators to explain how price trade-offs interact with quality and risk conditions.

Localization Note: Building Assessment Language Your Team Can Use

If your organization operates near local business hubs, teams often find that evaluation language works top when it matches local procurement culture. For example, in many organizations across “nearby” regions, evaluators may rely on concise supplier questionnaires, in-person audits, or document “walkthroughs” that resemble how local teams discuss compliance with colleagues. The key is not the setting itself, but whether your documentation and evidence requests are clear enough that suppliers can respond without ambiguity.

When teams communicate expectations with a shared tone—formal where required, straightforward where possible—evaluators spend less time clarifying and more time assessing.

Localization also matters for governance: if internal teams use different terminology for the same concept (e.g., “corrective action” vs. “CAPA,” or “change control” vs. “engineering change management”), evaluators can misread evidence or compare submissions unfairly. A practical way to address this is to build a controlled glossary into your supplier assessment package. Doing so makes the “decision lens” consistent even across language differences, time zones, and operational maturity levels.

Comparison Table (Options, Conditions, and Requirements)

The following table compares practical ways organizations incorporate a methodology-like reference such as Mckenna 1993 into supplier evaluation. It focuses on operational choices rather than claims about specific industries.

Step-by-Step Guide: Implementing a Defensible Supplier Evaluation Workflow

Below is a step-by-step approach that reflects the structured, evidence-driven thinking often associated with references such as Mckenna 1993, while staying compatible with contemporary procurement governance.

Step 1: Scope the Purchase and Define “Intended Use”

Start by documenting what the supplier-provided goods or services are intended to do. This step prevents misaligned criteria—one of the very common reasons evaluations end in disagreement.

“Intended use” should cover more than functional requirements. Include context such as operating environment, criticality to downstream processes, interface requirements (technical or procedural), and any constraints related to safety, compliance, or customer obligations. For example, a “packaging service” might be acceptable with basic labeling controls for a non-regulated internal use case, but it may require validated traceability and serialization if it will ship to regulated markets.

In well-run procurement organizations, scope documentation is not treated as a formality. It becomes the foundation for the evaluation rubric and evidence selection. Without it, evaluators often interpret the same submission as “good enough” or “not sufficient” depending on their assumptions about downstream risk.

Step 2: Define Evaluation Criteria and Evidence Requirements

Translate your evaluation goals into criteria that can be supported with evidence. For each criterion, specify:

• What evidence is acceptable (documents, certifications where relevant, process descriptions, records).
• What format is required (e.g., summaries plus underlying records where appropriate).
• How recent evidence must be (e.g., within a defined timeframe based on your governance needs).

This is the stage where “Mckenna 1993” thinking becomes operational: you turn abstract expectations into observable artifacts. To avoid ambiguity, define what “evidence” means for each criterion. For instance:

• For change management, accept procedures plus recent examples of how changes were assessed and approved (without requiring disclosure of proprietary designs, when appropriate).
• For quality planning, accept documented control plans or comparable process maps tied to the intended use.
• For delivery performance, accept metrics and methodology (how on-time delivery is calculated), not only a “good performance” claim.
• For data security (where relevant), accept documented access control and incident response practices appropriate to the data type and system boundaries.

One practical implementation tip: build a short “evidence instruction sheet” that tells suppliers what to submit, how to label files, and how to map each submission back to the evaluation criteria. This reduces back-and-forth and also makes the resulting record easier for auditors to follow.

Step 3: Apply a Risk Tier to Set Assessment Depth

Use a risk tiering approach so you don’t overburden low-risk categories and don’t under-assess high-risk ones. The purpose is procedural fairness and resource efficiency.

A risk tier model typically considers factors such as: spend size relative to category, criticality to operations, regulatory exposure, safety impact, technical complexity, supplier concentration risk, and the supplier’s history of performance or nonconformance. If your organization is mature, you may also include risk indicators like geographic disruption susceptibility, labor and financial stability signals, or cybersecurity exposure where services involve connected systems.

Importantly, risk tiering should change the depth of assessment—not the requirement to be able to explain the decision. Even if a category is low risk, you still need defensible documentation showing the evaluation steps performed and the rationale for selection or continued approval.

As you calibrate the model, ensure that evaluators understand the difference between:

• Reduced evidence depth (e.g., fewer samples or lighter documentation requirements for low-risk categories), and
• Reduced accountability (e.g., skipping evidence entirely). The second is where governance failures occur.

Step 4: Collect Supplier Details Consistently

Standardize the supplier data intake. Even small inconsistencies—different naming conventions, incomplete process descriptions—can degrade evaluation comparability.

Supplier details can include basic legal and contact information, but also operational data such as facility locations, manufacturing or service sites involved, relevant certifications, and organizational interfaces (who owns what in the quality system). Where “Mckenna 1993” thinking is applied, the focus is not just collecting data; it’s ensuring that each data element is mapped to criteria and used in scoring with traceable references.

A practical approach is to implement:

• Structured submission forms that reflect each criterion;
• Controlled document naming conventions (e.g., “QMS_Policy_2025-05.pdf” rather than “policy.pdf”);
• Data validation rules (e.g., certification expiry checks);
• Mandatory evidence fields for criteria that cannot be scored without evidence.

Consistency is also internal. If you have regional procurement teams, ensure they use the same forms and scoring scales. Localization is helpful for communication clarity, but the underlying evaluation mechanics should be standardized.

Step 5: Evaluate Price in Context

Integrate price with quality and risk considerations. A robust framework considers total cost implications, not only unit price. This step helps prevent “low price wins” outcomes when quality or continuity risk is significant.

Total cost of ownership (TCO) is one useful lens, but you can operationalize it without building a complex spreadsheet. You can start with a simpler structure:

• Direct procurement cost (unit price, setup fees, contract costs).
• Quality-related costs (estimated incoming inspection, defect rate assumptions, expected corrective action costs).
• Operational continuity costs (expedites, downtime risk, requalification costs if suppliers change).
• Compliance and documentation costs (audit support, record retention, regulatory reporting effort).

Even when you cannot estimate each component with high precision, you can still document the assumptions behind the cost comparison. The “decision traceability” aspect matters: auditors and internal stakeholders should be able to understand why one option is selected and how quality and risk trade-offs were handled.

Where price ties occur, your process should specify tie-breaking logic. For example, the tie-breaker might prioritize suppliers with better change management maturity, stronger evidence of process control, or a history of delivering within validated time windows.

Step 6: Decide With Traceable Rationale

Your decision documentation should show:

• What criteria were met
• What gaps existed
• What mitigations were accepted (if any)
• Why the final decision was reasonable for the scoped use

This is the core of using Mckenna 1993 as a decision lens. The goal is not to produce lengthy narratives; it’s to produce traceable logic that connects:

• the scope and intended use (from Step 1),
• the evaluation criteria and evidence requirements (from Step 2),
• the scored outcomes and risk tier (from Steps 3 and 5),
• and the final recommendation (from Step 6).

To make this efficient, many organizations use decision templates with mandatory sections. These templates reduce variability and ensure evaluators capture the same categories of reasoning every time, even under time pressure.

In addition, define what qualifies as “acceptable mitigation” when evidence is incomplete. Mitigations might include conditional acceptance with deadlines, enhanced incoming inspection, probationary contracting, or escalation to quality engineering for additional review. Whatever you choose, document it clearly.

Step 7: Set Conditional Acceptance and Follow-Up Requirements

If the supplier cannot meet all criteria at first, define conditions and deadlines tied to evidence submission and verification. Avoid vague commitments; require measurable deliverables.

Conditional acceptance is a powerful governance tool when used correctly. It allows progress without ignoring risk. But it can become a governance problem if conditions are:

• too vague (“supplier will improve documentation”),
• missing deadlines (“supplier will provide updates soon”),
• unverifiable (“supplier will follow best practices”), or
• not tied to the risk tier (e.g., minimal follow-up for a high-risk category).

A strong conditional approval should include at least:

• Condition description (what exactly is missing or not acceptable);
• Required evidence (what the supplier must submit);
• Verification method (document review, audit, sample review, performance monitoring);
• Due date and responsible parties;
• What happens if it isn’t met (e.g., contract termination, increased inspections, suspension of new orders).

Where relevant, include interim controls. For example, if change management documentation is missing, you might require prior approval for any change requests before production use begins, or you might require enhanced inspection for early lots until evidence is verified.

Step 8: Monitor and Re-Evaluate Using Triggers

Supplier evaluation should not be “set and forget.” Use triggers such as material/process changes, facility moves, significant nonconformities, or customer complaint patterns (as applicable and documented) to determine when re-evaluation is needed.

Re-evaluation triggers should be clear and objective. Examples include:

• Quality events: recurring nonconformities, corrective action failures, or significant escapes into downstream processes.
• Change events: engineering changes affecting product/process critical characteristics, equipment changes, manufacturing transfers, subcontractor additions, or changes in key raw material sources.
• Operational events: facility relocation, major staffing changes in quality leadership, or system upgrades that affect data handling.
• Regulatory or customer requirements: new obligations that require proof of compliance or updated documentation.

Also define re-evaluation frequency. Even without a specific trigger, high-risk suppliers may require periodic audits or evidence refreshes. Low-risk suppliers might need less frequent documentation updates but should still be reviewed over time to confirm continuing suitability.

When re-evaluation occurs, apply the same decision lens: update the evaluation using current evidence, reassess risk tier appropriateness, and document the outcome. This creates continuity in governance and helps prevent “drift,” where supplier status becomes outdated relative to actual performance.

Conditions and Requirements for Successful Adoption

To make a methodology-inspired reference like Mckenna 1993 operational rather than symbolic, organizations generally need the following:

• Governance ownership: procurement should coordinate, but quality/compliance should inform the criteria.
• Training and calibration: evaluators should understand how to apply scoring guidance.
• Controlled templates: consistent supplier questionnaires and evidence checklists.
• Evidence governance: document versioning, retention rules, and review workflows.
• Feedback loops: periodic updates based on nonconformance patterns and audit outcomes.

Each of these conditions can be turned into concrete implementation mechanics.

Governance ownership means that the evaluation system has a “process owner” with authority to maintain rubrics, update evidence packs, and enforce decision documentation standards. Without this, the process becomes a series of ad-hoc efforts and citations become a substitute for control.

Training and calibration are especially important because many evaluation disagreements are actually scoring interpretation differences. Calibration sessions—where evaluators review example submissions and align on scoring—reduce variability and also provide a forum to refine guidance over time.

Controlled templates should be version-controlled. Suppliers should be able to tell which evidence pack version they responded to. Internally, you should be able to reconstruct what requirements were in force at the time of a decision.

Evidence governance includes retention rules, access rights, and document lifecycle management. For audit-readiness, it’s not enough to “have evidence.” You must also be able to retrieve it reliably and show it was the evidence set used at decision time.

Feedback loops ensure continuous improvement. If a supplier passes evaluation but later fails in the field, your process should update criteria or evidence requirements to prevent the same failure type from recurring.

Expert Perspective: Common Failure Modes (and How to Avoid Them)

From an industry expert perspective, the very frequent issues in supplier evaluation programs are not lack of effort; they’re design flaws:

• Over-reliance on a single metric (often price), which can create hidden quality and continuity risk.
• Inconsistent evidence standards, where some evaluators accept partial documentation while others require full records.
• Ambiguous conditional approvals, where suppliers understand the request differently from how internal teams interpret it.
• Weak traceability, making it hard to explain decisions during reviews or disputes.
• Criteria drift, where evaluation standards change informally between business units.

Using a structured lens such as the one implied by Mckenna 1993 helps counter these failure modes—if the organization operationalizes it with governance controls, training, and evidence mapping.

Below are expanded examples of how these failure modes typically show up and how to remediate them.

Failure Mode 1: Over-Reliance on a Single Metric (Especially Price)

Over-reliance on price happens when teams treat procurement like an isolated cost exercise instead of a system problem. For example, an organization might choose a supplier offering the best unit cost, but the supplier’s lead time volatility and limited change control documentation increase the likelihood of production disruptions or nonconformities. Those downstream impacts can dwarf procurement savings.

Remediation: require documented trade-off logic. Even if you use price as a scoring component, you should ensure quality and continuity risk are also part of the decision and that price reductions cannot override a critical quality requirement. Practically, you can implement “hard gates” for certain criteria (e.g., minimum evidence for change control maturity for regulated categories).

Failure Mode 2: Inconsistent Evidence Standards

Inconsistent evidence standards typically occur when evaluators interpret “acceptable documentation” differently. One evaluator might accept a high-level policy statement; another might require records demonstrating implementation. This inconsistency can lead to unfair outcomes and can also weaken audit defensibility.

Remediation: define evidence by criterion. For each criterion, explicitly state what evidence suffices for scoring at each level. Where evidence differs by risk tier, define that difference as well.

Failure Mode 3: Ambiguous Conditional Approvals

Conditional approvals become ambiguous when the organization asks for “improvements” without specifying measurable deliverables. Suppliers respond in ways that are technically compliant from their perspective but not necessarily aligned with what the organization needs.

Remediation: require evidence deliverables that can be reviewed against a checklist. Also define verification methods and due dates. Include explicit outcomes if conditions are not met.

Failure Mode 4: Weak Traceability

Weak traceability appears when decision records do not show the connection between scope, criteria, scores, and rationale. In an audit or dispute, internal stakeholders may not be able to explain why a supplier was selected or why conditions were accepted.

Remediation: use decision templates and evidence mapping. Ensure each score or recommendation references specific evidence items. Keep the decision record complete at the time of approval, not after.

Failure Mode 5: Criteria Drift

Criteria drift happens when business units update evaluation expectations informally, without a controlled process. Over time, the same supplier type can receive different levels of scrutiny depending on who evaluates them.

Remediation: enforce controlled versions of criteria and scoring guidance. Also maintain a governance review cycle so updates are deliberate and approved by a responsible owner.

FAQs

FAQ 1: What exactly is “Mckenna 1993” in procurement terms?

In many organizations, Mckenna 1993 is used as a reference marker for a structured approach to decision-making, documentation, and evaluation criteria. Because the term may appear in different professional contexts, treat it as a conceptual lens and verify the underlying intent in your internal documents or original citation trail.

FAQ 2: Does referencing “Mckenna 1993” guarantee better supplier outcomes?

No. Citations alone do not improve results. Better outcomes come from operationalizing structured criteria, evidence requirements, and decision traceability—consistently applied across evaluators and risk tiers.

FAQ 3: How should price be handled alongside supplier details?

Use price as one input within a broader evaluation that includes quality evidence, continuity risk, and governance maturity. A defensible method explains trade-offs and documents mitigations when price advantages coincide with quality or risk uncertainties.

FAQ 4: What evidence should we request from suppliers?

Request evidence mapped to each evaluation criterion. In general, evidence should support process control claims, quality management practices, change management capability, and the supplier’s ability to deliver consistently for the intended use.

When setting evidence requests, consider what your organization needs to demonstrate internally. For many audits, the question is not “Did the supplier claim they are compliant?” but “Can we show we assessed the supplier against documented criteria and can we explain the decision rationale?” Tailor the evidence pack accordingly.

FAQ 5: When is re-evaluation required?

Re-evaluation is typically triggered by significant changes (process/material/facility), notable quality events, or shifts in risk posture. Define trigger conditions in advance so reviews are consistent and audit-ready.

Additionally, re-evaluation may be needed when internal requirements change. For example, a new data retention requirement or an updated customer audit obligation might require the supplier to submit updated evidence even if production performance has been stable.

FAQ 6: Can we apply the same evaluation structure across all spend categories?

Usually not. Adopt a risk-tier approach: apply deeper assessment for higher-impact categories, and lighter but still documented evaluation for lower-impact ones. This aligns governance with practicality while maintaining fairness.

That said, keep core mechanics consistent. Even if evidence depth changes, the structure—scope definition, criterion mapping, traceable rationale, and decision documentation—should remain consistent across categories. This consistency is part of what makes Mckenna 1993-style thinking defensible across the organization.

FAQ 7: We operate near “nearby” regional supplier clusters—does localization matter?

Localization matters mainly in communication clarity and workflow fit. While the core evaluation logic should remain consistent, local procurement culture can influence how quickly suppliers respond, how evidence is packaged, and how audits are conducted.

Localization is also important for practical supplier engagement. If your region uses a particular format for certifications or common document templates, align your requests where possible. The goal is not to dilute standards; it’s to reduce friction so suppliers can provide evidence efficiently.

FAQ 8: What standards or frameworks can complement this approach?

Many teams align supplier governance practices with recognized quality and management system principles (and relevant regulatory or customer requirements). Choose standards that match your industry context, then ensure your evaluation criteria and evidence requests map to those requirements.

In practice, you can treat standards as “what” requirements and your evaluation workflow as the “how” that collects, verifies, and documents compliance evidence. This pairing helps ensure that supplier evaluation remains both operationally feasible and audit-ready.

References and Source Notes (Reliability-Oriented)

This article provides process guidance and avoids unverified claims. For organizations seeking additional grounding in management system principles and audit practices, reputable starting points include:

• ISO/IEC 17025 (for laboratory competence concepts when applicable to testing evidence).
• ISO 9001 (quality management system principles relevant to process control and documentation practices).
• ISO 19011 (guidelines for auditing management systems).
• OECD guidance on due diligence frameworks (relevant when governance expectations extend to responsible business conduct).

If you need, I can tailor the evaluation criteria and evidence pack structure to your specific spend categories and internal risk tiering model.