14.2 Quality Assurance & Surveillance (FAR Part 46)
Key Takeaways
- FAR Part 46 establishes quality assurance policy: the Government obtains supplies and services that conform to contract requirements through appropriate inspection, acceptance, and quality assurance actions.
- Contractors are responsible for controlling quality and tendering conforming supplies/services; Government contract quality assurance verifies conformance and does not shift that primary quality responsibility away from the contractor.
- Inspection and acceptance are distinct concepts—inspection examines conformity; acceptance is the formal act acknowledging the supply/service meets contract requirements (with important legal and payment consequences).
- For services, a Quality Assurance Surveillance Plan (QASP) defines what will be monitored, how, how often, and by whom, using risk-based surveillance tied to performance standards and acceptance criteria.
- Nonconforming supplies/services trigger remedy themes (rejection, correction, consideration, other contract remedies); higher-level quality requirements apply when complexity/risk demands more than standard commercial or basic inspection approaches.
14.2 Quality Assurance & Surveillance (FAR Part 46)
Quick Answer: Ensure Quality (FAI 4.1.2, about 10 questions) centers on FAR Part 46. The contractor controls quality and must tender conforming supplies/services; the Government performs contract quality assurance (inspection/surveillance) and acceptance. For services, build and use a QASP. Know acceptance criteria, nonconformance remedies, and when higher-level quality requirements are needed.
Mission failure often arrives as a quality failure: wrong parts, incomplete services, or "accepted" work that never met the standard. FAR Part 46 — Quality Assurance is the post-award rule set for making conformity real. CON 3990V tests whether you understand who owns quality, how the Government verifies it, and what happens when work is nonconforming—not whether you can recite every inspection clause number.
Why quality is a full 10-question competency
Ensure Quality sits beside Administer Contract for a reason. Administration without quality is calendar watching; quality without administration is a checklist with no authority path. Together they answer: Did we get what we bought, on the terms we wrote?
| Quality failure mode | Typical exam stem pattern |
|---|---|
| Paying for nonconforming work | Invoice approved despite failed inspection |
| COR invents standards | Surveillance against unwritten "best practices" |
| No QASP on complex services | Surveillance is random or purely reactive |
| Acceptance confusion | "Inspected" treated as "accepted" without process |
| Ignoring higher-level needs | Complex system treated like simple commercial buy |
| Soft remedies only | Chronic nonconformance with no rejection/consideration path |
FAR Part 46 policy in one map
Part 46 policy themes for closed-book recall:
- Contracts shall require contractors to provide supplies/services conforming to requirements.
- Contractors are responsible for quality control adequate to meet the contract.
- Government contract quality assurance is performed as necessary to determine conformance.
- Inspection and acceptance terms must be clear in the contract.
- Remedies exist when nonconforming supplies/services are tendered.
- Higher-level quality requirements (e.g., formal quality systems) may be imposed when needed.
Government contract quality assurance vs contractor quality responsibility
This distinction is high-yield.
| Party | Responsibility |
|---|---|
| Contractor | Plan and execute quality control; produce and tender conforming supplies/services; fix nonconformances it causes |
| Government | Perform contract quality assurance (inspection, testing, surveillance) as appropriate; accept or reject per the contract; document results; invoke remedies |
Exam trap: "Because the Government inspects, the contractor is not responsible if defects slip through." False. Government inspection does not relieve the contractor of its duty to control quality and meet requirements (subject to specific contract terms and legal doctrines you need only at awareness level). The Government's inspection is verification, not a substitute for the contractor's quality system.
Exam trap: "Government QA means 100% inspection of every unit always." False. Surveillance and inspection are risk-based and method-selected (sampling, periodic, customer feedback, metrics) depending on criticality, complexity, and history.
Forms of Government contract quality assurance (conceptual)
| Method | Idea |
|---|---|
| In-process inspection / surveillance | Check during performance, not only at the end |
| Final inspection | Check before or at acceptance |
| Testing | Verify attributes against specs |
| Review of contractor quality evidence | Certificates, process data, metrics—used carefully |
| Customer / end-user feedback | Especially for services |
| Audits of quality systems | When higher-level requirements apply |
Inspection and acceptance
Do not treat these as synonyms.
Inspection
Inspection means examining and testing supplies or services (including raw materials, components, intermediate assemblies, and end products, as applicable) to determine whether they conform to contract requirements.
Key points:
- Inspection rights and locations (source, destination, other) are established by the contract.
- The Government may inspect at various points; contractors must provide reasonable access/facilities as required.
- Inspection can find nonconformance before acceptance.
Acceptance
Acceptance is the act of an authorized representative assuming ownership of existing identified supplies tendered or approving specific services rendered as partial or complete performance of the contract.
Why acceptance matters:
| Effect theme | Why exam writers care |
|---|---|
| Performance credit | Acceptance recognizes conforming performance (or acceptance of nonconforming items only under proper authority/consideration paths) |
| Payment linkage | Payment processes often require acceptance evidence |
| Risk transfer themes | Contract terms allocate risk around accepted supplies (details vary by clause—know the concept) |
| Authority | Only authorized persons accept—not every end user who is "happy" |
Exam trap: An end-user says "looks good to me" in a hallway; the COR treats that as final acceptance of a complex CLIN. Wrong unless that person is the authorized acceptance official under the contract/delegation and required inspection is complete.
Scenario — Inspected but not accepted. Supplies fail destination inspection. Vendor argues, "You looked at them, so you accepted." Wrong. Inspection can result in rejection; acceptance is a separate affirmative act.
Acceptance criteria
Acceptance criteria answer: What does "conforming" mean in observable terms?
Sources of criteria:
- Specifications and standards cited in the contract
- PWS/SOW performance standards and AQL/thresholds where used
- Service level measures (timeliness, accuracy, availability)
- Deliverable content/format requirements (CDRL/DID themes)
- Commercial item descriptions and accepted industry standards when the contract adopts them
| Strong criteria | Weak criteria |
|---|---|
| Measurable, testable, tied to the PWS/spec | "World-class support" with no metric |
| Known at award | Invented mid-performance by a COR preference |
| Applied consistently | Strict for Contractor A, loose for Contractor B |
| Documented in QASP/inspection plan | Tribal knowledge only |
Performance-based services: criteria should link to outcomes the mission needs, with surveillance methods that can actually observe those outcomes.
QASP — Quality Assurance Surveillance Plan (services)
For many service contracts, the Government uses a Quality Assurance Surveillance Plan (QASP) to structure surveillance.
What a QASP typically contains
| QASP element | Purpose |
|---|---|
| Performance standards / objectives | What "good" looks like (from PWS) |
| Acceptable quality levels / thresholds | How much deviation, if any, is tolerable |
| Surveillance methods | 100% inspection, random sampling, periodic observation, validated customer complaints, metric review, etc. |
| Frequency / sample size | How often and how much to check |
| Responsible observers | COR, QA specialist, end users feeding data |
| Documentation & reporting | What gets recorded and escalated |
| Incentives / remedies linkage | How results feed deductions, CPARs, award-fee inputs, cure paths (as contract allows) |
Risk-based surveillance
Not every task deserves equal intensity:
- Critical health/safety/mission tasks → denser methods, higher frequency
- Stable high performers → may reduce intensity with documented rationale
- New contractors / new work / past problems → increase intensity
- High-cost CLINS → proportionate scrutiny
Exam trap: QASP is optional fluff on a complex multi-year service contract. For CON 3990V judgment, a serious service buy without a real surveillance approach is an Ensure Quality failure waiting to happen—even if someone forgot the label "QASP."
Scenario — Paper QASP. A beautiful QASP exists in the file, but the COR never samples, never logs, and only reacts to crises. Wrong. A plan without execution is not surveillance.
Nonconforming supplies and services — remedy themes
When tendered performance does not conform:
| Remedy theme | Conceptual use |
|---|---|
| Reject nonconforming supplies/services | Refuse acceptance when rejection is appropriate |
| Require correction / replacement | Contractor fixes at no increased cost when terms require |
| Accept with consideration | Sometimes nonconforming items may be accepted only with proper authority and consideration (price reduction or other benefit)—not casual COR forgiveness |
| Withhold / reduce payment per contract | When clauses and facts support it |
| Document and escalate | Repeated nonconformance → CO remedies, cure mechanisms, past performance impact, possible termination path (later chapters) |
| Do not silently re-baseline the requirement | Lowering the standard without a mod is improper |
Exam trap: "Nonconforming but we need it now—accept fully and pay full price without documentation or consideration." Mission urgency may force hard choices, but the professional path is authorized decision + documentation + consideration/remedy, not pretend conformance.
Scenario — Chronic service shortfalls. Help-desk response times miss the PWS standard 40% of months. COR only "encourages improvement." Better path: document against QASP, apply contractual remedies available, engage CO for formal communications/remedies, and reflect in past performance.
Higher-level quality requirements
Higher-level quality requirements are imposed when the Government needs more than basic inspection—typically a contractor quality management system or formal process controls (examples at awareness level: ISO-type systems, higher-level QA clauses for complex hardware/software).
When they are appropriate (themes):
| Indicator | Implication |
|---|---|
| Complex design, critical safety, or high reliability needs | Basic end-item spot checks may be insufficient |
| Special processes (welding, plating, software assurance, etc.) | Process control and records matter |
| Past quality failures in the domain | Stronger systemic controls |
| Performance specs with high consequence of failure | Prevention over detection |
Exam cue: Higher-level quality is a risk and complexity decision written into the contract—not a default for every commercial off-the-shelf buy, and not something a COR invents after award without contractual basis.
Linking Part 46 to administration and payment
Contract requirements + quality clauses
-> Contractor quality control
-> Government inspection / QASP surveillance (Part 46)
-> Accept / reject / remedy
-> Payment support & past performance (Part 42 admin)
Quality findings should flow into COR reports, CO actions, invoice decisions, and past performance—not die in a private email folder.
CON 3990V closed-book anchors
- Part 46 = quality assurance.
- Contractor owns quality control; Government verifies.
- Inspection != acceptance.
- QASP structures service surveillance (risk-based).
- Acceptance criteria must be contract-tied and measurable.
- Nonconformance -> reject/correct/consideration/other remedies—not silent full-price acceptance.
- Higher-level quality when risk/complexity demands it.
Bottom line: Ensure Quality under FAR Part 46 means buying conformance, not hope. Hold contractors to quality control, execute Government QA and QASP surveillance, separate inspection from acceptance, apply remedies for nonconformance, and escalate higher-level quality when mission risk requires it. On CON 3990V, reject answers that invent standards, ignore nonconformance, or confuse end-user cheerleading with formal acceptance.
Which statement best captures the division of quality responsibility under FAR Part 46 concepts?
What is the primary purpose of a Quality Assurance Surveillance Plan (QASP) on a service contract?
Supplies fail contract specifications at destination inspection. Which Government response best aligns with Part 46 remedy themes?
When are higher-level quality requirements most appropriately considered?